菜单
Use when a workflow built on an MCP server has stabilized and should become a production skill, or when the user says "convert this MCP workflow to a skill". Produces a skill with a bundled script that calls the underlying API directly, eliminating the per-session MCP token overhead.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when a question has a factual or best-practice answer but a single response might hallucinate, or when the user asks to "get consensus" or "sanity check this with multiple agents". Spawns N subagents on the same question with varied personas and tallies answer frequency.
Use when a question has real trade-offs and no single right answer: architecture choices, library selection, design direction. Runs a multi-round debate where agents see each other's positions across rounds, converge, and a synthesis is produced. For factual questions, use consensus instead.
Use when triaging an inbox: fetching unprocessed emails, classifying each into a label taxonomy, and applying labels via the provider's API. Provider-agnostic skeleton; scripts/label.py must be wired to your email provider before first use.
Use when a PRD or spec exists and needs to become an executable backlog. Breaks the document into GitHub issues structured as vertical-slice tracer bullets, marks each as HITL or AFK, and files a final QA issue. Requires the gh CLI.
Use when implementing any task that should end in a commit. Encodes the definition of done: understand, implement with red-green-refactor for backend logic, run typecheck and tests until clean, then commit. Also the unit of work for autonomous loops.
Use when creating or revising any Claude Code skill, or when the user says "write me a skill for X". Encodes the house conventions: frontmatter style, body structure, when to bundle scripts, and project vs user scope.
| name | mcp-to-skill |
| description | Use when a workflow built on an MCP server has stabilized and should become a production skill, or when the user says "convert this MCP workflow to a skill". Produces a skill with a bundled script that calls the underlying API directly, eliminating the per-session MCP token overhead. |
MCP is the prototype surface; skills are the production surface. A connected MCP server preloads its tool definitions into every session - a heavyweight server costs 15-25K tokens before you type anything. A skill costs its frontmatter (~60 tokens) until invoked, and a bundled script costs near zero because deterministic work happens in code, not in context. The Lab 3 email labeler measured an order of magnitude fewer tokens after conversion.
Convert when: the workflow is repeated, its steps have stabilized, and the MCP server's tools map to a documented API. Don't convert one-offs or workflows still changing shape.
scripts/ directory. Everything requiring judgment (what to do with the data, edge-case decisions) stays in SKILL.md prose. If the script needs the model's judgment mid-run, restructure: script fetches, model decides, script applies./context before and after; report the savings as a number. That number is the point.