Loading...
Loading...
Found 10,127 Skills
WeCom message skill. It provides capabilities including session list query, message record pulling (supports text/image/file/voice/video), multimedia file acquisition and text message sending. It is triggered when users need to "view messages", "check chat records", "send a message to someone", "what are the recent messages", "send a message to the group", "see what pictures/files have been sent".
Ping-pong TDD 세션의 첫 번째 단계. TrackerBoot MCP에서 스토리를 가져오거나 직접 붙여넣은 스토리 내용을 받아들이고, 프로젝트 스택과 컨벤션을 감지하며, 협력하여 태스크 분해를 계획하고, /tdd-task와 /tdd-commit이 사용할 .tdd-session.md 파일을 작성합니다.
Used when a feature has been implemented but lacks design documentation and implementation plans. Automatically generate documents conforming to /hi-brainstorm and /hi-ace formats based on existing code and git history.
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.
Retrieve a GitHub issue using the `gh` CLI, analyze it, and spawn a PM + developer team to address it. Accepts an issue URL, issue number, or `owner/repo#number`.
Use when another skill or agent needs a review panel assembled, retained, or converged — invoked by /review-loop, /plan-review, and code-reviewer, not directly by users.
Adopt the Three Provinces and Six Ministries style code review, output structured review conclusions in five stages: Zhongshu Sheng, Shangshu Sheng, Six Ministries, Menxia Sheng, and Jinyiwei
Use when starting a new project with Maestro or when no .maestro.md context file exists yet. Run once per project.
Systematic evidence-based debugging using runtime logs. Generates hypotheses, instruments code with NDJSON logs, guides reproduction, analyzes log evidence, and iterates until root cause is proven with cited log lines. Use when the user reports a bug, unexpected behavior, or asks to debug an issue.
Use this skill whenever the user wants to work with the Loops CLI from the terminal. This includes installing or updating the CLI, authenticating, storing and selecting API keys, validating credentials, and running commands for contacts, contact properties, lists, events, and transactional email. Trigger on phrases like "Loops CLI", "loops auth login", "loops contacts create", "loops contacts update", "loops events send", "loops transactional send", "loops api-key", "brew install loops-so/tap/loops", or any time the user wants to use Loops from the shell instead of application code.
Set up Notion integration token. Use when Notion commands fail with auth errors, or when user wants to connect their Notion workspace. Takes 2 minutes — user creates an integration at notion.so/my-integrations and pastes the token.
Morning preparation. Calendar lookahead, meeting context loading, open threads from yesterday, active task review. Extends briefing with actionable prep.