メニュー
從 candidate-queue.md 讀取待審候選 skill，進行去重、合併、review， 使用者批准後呼叫 skill-creator 實際建立。 觸發詞：「extract-skill」「抽取 skill」「建立 skill 從 queue」「處理 skill 候選」 「有 skill 候選待建立」「extract skills from queue」「把候選做成 skill」
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | extract-skill |
| description | 從 candidate-queue.md 讀取待審候選 skill，進行去重、合併、review， 使用者批准後呼叫 skill-creator 實際建立。 觸發詞：「extract-skill」「抽取 skill」「建立 skill 從 queue」「處理 skill 候選」 「有 skill 候選待建立」「extract skills from queue」「把候選做成 skill」 |
將 agent 在執行過程中發現的重複模式，從候選 queue 整理後建立為正式 skill。
需要 /Users/fredrick/.gemini/skills/extract-skill/../improve/candidate-queue.md（由 capture-skill-candidate hook 或 propose.sh 寫入）。
讀取以下位置的 candidate-queue.md（優先順序）：
{cwd}/.claude/skills/improve/candidate-queue.md（project-level）~/.claude/skills/improve/candidate-queue.md（user-level）取出所有 status: pending 的項目。
若無 pending 項目，輸出「candidate-queue.md 目前無待處理候選」並結束。
對 pending 候選執行：
status: duplicate，建議改為呼叫 /improve 增強既有 skillhit_count 累加hit_count < 2 的候選降優先級（顯示但標記為 low-confidence）對每個高品質候選（hit_count >= 2 或使用者明確要求處理），顯示：
## Skill Candidate: {name}
**Hit count**: {hit_count}（首見 {first_seen}，最近 {last_seen}）
**Reason**: {reason}
**Steps**:
{steps（逐行展開）}
**Suggested trigger phrases**: {invoker_hints}
---
**建議的 SKILL.md description 草稿**：
{根據 reason + steps 生成的 description 段落}
**請選擇**：[A] Approve [S] Skip [R] Reject [M] Merge to existing skill
A (Approve) → 進入 Step 4S (Skip) → 跳過本候選，保留 pending 狀態R (Reject) → 標記 status: rejectedM (Merge) → 詢問要合併到哪個既有 skill，提示使用者改用 /improve呼叫 /skill-creator 建立 skill，或引導使用者提供以下資訊：
建立完成後：
candidate-queue.md 該項目 status: created✅ {skill-name} 已建立 → {skill_path}## Extract Skill 執行摘要
- 處理候選：{N} 個
- 已建立：{list}
- Rejected：{list}
- Skipped（待下次）：{list}
- Duplicate（建議 /improve）：{list}
/extract-skill 只推薦 hit_count >= 2 的高品質候選；低品質候選在報告末尾列出Document codebase as-is via parallel sub-agents. Use when researching how code works, mapping architecture, or answering questions about existing systems. Auto-detects thoughts/ directory — if present, integrates historical context and syncs; if absent, skips those steps.
Create the Questions artifact before codebase research, design, planning, or implementation. Use for feature tickets, architecture changes, unclear code work, CRISPY/QRSPI Questions phase, or when the agent needs to define code-answerable unknowns and human questions before researching or planning.
Create a concise Design Concept artifact after questions and codebase research are available. Use for CRISPY/QRSPI Design phase, architecture alignment, feature design discussion, or turning current-state research into a small human-reviewable proposed shape before detailed planning.
Create an interface-first Structure Outline before detailed planning or implementation. Use for CRISPY/QRSPI Structure Outline phase, vertical planning, method signatures, type contracts, API/component boundaries, or converting an accepted design concept into end-to-end slices with verification checkpoints.
Create comprehensive handoff documents for transferring work to another agent session. Use when the user requests to create a handoff, end a session, or document work-in-progress for future continuation.
Create detailed implementation plans through interactive research and iteration. Use when starting a new feature or ticket that needs a comprehensive technical plan. Saves plans to the repo-appropriate plans location and emits Personal Knowledge events when applicable.