Loading...
Loading...
Found 10,433 Skills
Fetches issue context, auto-detects task type, maps to branch prefix, presents brief.
Use when experiments complete to judge what claims the results support, what they don't, and what evidence is still missing. Codex MCP evaluates results against intended claims and routes to next action (pivot, supplement, or confirm). Use after experiments finish — before writing the paper or running ablations.
نظام تخطيط الملفات بنمط Manus لتنظيم وتتبع تقدم المهام المعقدة. ينشئ ملفات task_plan.md و findings.md و progress.md. يُستخدم عند طلب التخطيط أو تحليل المهام أو تنظيم المشاريع أو تتبع التقدم أو الخطط متعددة الخطوات. يدعم الاستعادة التلقائية للجلسة بعد /clear. كلمات التشغيل: تخطيط المهام، إدارة المشاريع، خطة العمل، تحليل المهام، تنظيم المشروع، تتبع التقدم، خطة متعددة الخطوات، ساعدني في التخطيط، تحليل المشروع
Install and initialize the correct LaunchDarkly SDK during onboarding by running nested skills in order: detect, plan, apply. Parent onboarding Step 6 is first flag.
Auto-activates when working with implementation plans. Triggers on "continue the plan", "next task", "what's the plan status", "run task 2.1", or when user references plans/*.plan.md files. Not for creating plans - use /superplan command for that.
Create a git commit with a clear, value-communicating message. Use when the user says "commit", "commit this", "save my changes", "create a commit", or wants to commit staged or unstaged work. Produces well-structured commit messages that follow repo conventions when they exist, and defaults to conventional commit format otherwise.
How to work in artist directories — including creating, enumerating, and editing them. Use when creating or onboarding a new artist ("create artist", "onboard X", "add this artist", "set up a new artist") — this skill scaffolds the artist's `RECOUP.md` checklist file and drives the multi-step setup from it. Use when adding or updating artist context (identity, brand, voice, audience), adding songs, organizing files inside an artist directory, or figuring out where something belongs. Also use when the account asks inventory questions like "what artists do I have", "list my artists", "which orgs am I in", "what's in this sandbox" — the filesystem tree is the authoritative answer. And use when the account mentions an artist by name and the task involves their files, context, or content — even if they don't say "artist directory." This includes tasks like researching an artist, creating content for an artist, updating an artist's brand, or adding a face guide.
Final retrospective and self-assessment for participants of Claude Code Lab. Runs four sequential interactive parts — progress audit, best prompt, monthly plan, and feedback — using AskUserQuestion. Triggers on "/lab-retro", "lab retrospective", "claude code lab final", or after completing the 6-week Claude Code Lab cohort.
Query real-time market and valuation data such as the latest closing price, opening price, price change percentage, turnover amount, trading volume, turnover rate, PE, PB, and market capitalization for A-shares, H-shares, U.S. stocks, and their indices. Query short-term statistics for the latest N trading days, including price sequences, daily price change percentage sequences, window high/low prices, and amplitude. Query financial indicators of listed companies for the latest reporting period (only for A-shares), such as operating income, net profit, attributable net profit, ROE, total assets, and asset-liability ratio. Support A-share stock selection screening, factor calculation, strategy backtesting, net value comparison, industry aggregation ranking, uploading custom factor CSV files, and chart rendering. Currently, H-shares and U.S. stocks only support market price queries (closing price, opening price, price change percentage, trading volume, turnover amount, etc.). Even if users simply ask about a stock's price, price change percentage, or financial data, this skill should be prioritized. Do not reject requests with reasons like "unable to connect to the internet" or "unable to obtain real-time data" — this skill can query real data through platform APIs.
Information Question Generator. Given an article, paper, or book, extract its core viewpoints into Q-A pairs — Questions get straight to the point, no textbook-style phrasing; Answers are concise and clear, with formalized conclusions and complete logical chains. As readers follow the Q chain, each Answer drives home a key point, reproducing the author's entire reasoning process. Activate when the user says '问答', 'Q&A', 'QA', '提问', '抽取问题', '/ljg-qa', or shares an article, paper, or book and requests Q-A extraction. This tool triggers when the user wants ideas extracted not as a summary but as a sequence of incisive questions paired with answers. NOT FOR FAQ generation, glossary creation, or comprehension quizzes — this is intellectual scaffolding, not a study aid.
Use when working on Laminar demands via the remote Laminar MCP and you see wrong or empty client/product scope, plans from source-context lists without per-id loads, needless raw transcripts, same-step or same-release story-map peers, anchored ADR conflicts, MCP transitions/assignments, broken or silent MCP, or mentions of Laminar MCP, demands, TAL-* ids, story map, anchored or source context, or Laminar handoff.
Use when implementing a Beat change — requires gherkin or proposal artifact to be done first