القائمة
Diagnose why a Claude Code skill is under-triggering, over-triggering, undiscoverable, or misconfigured.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Optimize a rough prompt with an independent subagent, present several CONCISE ready-to-run variants for the user to pick or edit, then EXECUTE the chosen prompt directly in the current session. Unlike prompt-optimizer (advisory only — it just hands back text), prompt-pilot closes the loop: optimize → choose → run. TRIGGER when the user wants both optimization AND execution: "优化并执行", "优化提示词后直接做", "优化指令然后执行", "帮我把这个需求优化好再做", "optimize and run my prompt", "improve this prompt then do it", "refine my prompt and execute it", or when the user explicitly invokes /prompt-pilot. DO NOT TRIGGER when the user only wants advice/text back with no execution ("优化prompt", "改进prompt", "rewrite this prompt", "how to write a prompt for") — that is prompt-optimizer. DO NOT TRIGGER for "优化代码" / "优化性能" / "optimize this code" / "optimize performance" — those are refactoring or performance tasks. DO NOT TRIGGER when the user says "直接做" / "just do it" with no request to optimize — execute the task normally without this skill.
Analyze raw prompts, identify intent and gaps, match ECC components (skills/commands/agents/hooks), and output a ready-to-paste optimized prompt. Advisory role only — never executes the task itself. TRIGGER when: user says "optimize prompt", "improve my prompt", "how to write a prompt for", "help me prompt", "rewrite this prompt", or explicitly asks to enhance prompt quality. Also triggers on Chinese equivalents: "优化prompt", "改进prompt", "怎么写prompt", "帮我优化这个指令". Specially handles short Chinese bug reports (the dominant real-world use case): runs Bug Report Triage to extract repro/expected/actual/environment, asks up to 3 clarifying questions if ≤ 2 fields are present, and inserts systematic-debugging as a hard prerequisite before any code change. DO NOT TRIGGER when: user wants the task executed directly, or says "just do it" / "直接做". DO NOT TRIGGER when user says "优化代码", "优化性能", "optimize performance", "optimize this code" — those are refactoring/performance tasks, not prompt optimization (unless the user exp
Use when writing, reviewing, or refactoring SwiftUI code for iOS or macOS, including state management, view composition, performance, Liquid Glass adoption, or Instruments `.trace` capture/analysis for hangs, hitches, CPU hotspots, or excessive view updates.
Convert an H5 / web app's source into a native SwiftUI iOS app by native rewrite (NOT a WebView shell, NOT a transpiler). Use when the user wants to port, re-implement, or migrate a web/H5 frontend to native SwiftUI with high visual fidelity, asks to "turn this web app into a real iOS app", or wants a measured render-diff convergence loop against a browser baseline. Auto-detects the web stack (v1: vanilla + React; other stacks are detected then gated, not guessed), extracts design tokens, calibrates a cross-renderer fidelity floor, rewrites per component, and drives a bounded render→diff→correct loop that reports a quantified visual residual plus an independent judge verdict. It does NOT promise literal pixel-identity: cross-renderer differences impose a measured floor it reports honestly. Triages canvas/WebGL/complex-animation/3rd-party-SDK/backend surfaces instead of silently emitting wrong code.
Distill methodology from superpowers and BMAD-METHOD docs into the active conductor track's spec.md / plan.md / review.md as intent-layer overlays. Use when user asks to "distill superpowers into conductor", "把 superpowers/bmad 提炼到 conductor", "import method docs to track", "seed conductor with brainstorming/TDD/verification gates", or "feed BMAD PRD/architecture/story/QA principles into the track". Writes only inside marker blocks so it never competes with code-derived facts and re-runs cleanly. DO NOT use for general superpowers invocation, code refactors, or to summarize this codebase.
Humanize PROSE drafts — articles, blog posts, public-account 公众号 copy, marketing copy, sermons, technical write-ups — that read like an LLM produced them. Chinese-first, supports zh/en mixed text. Cross-checks output against the Wikipedia "Signs of AI writing" taxonomy before delivery. TRIGGER when user asks to remove AI tone or humanize TEXT/DRAFT/ARTICLE/COPY/稿/文章/帖子: "去 AI 味", "去ai味", "降低机器感", "改得像真人写的", "不要 AI 腔", "humanize this draft", "humanize this article", "remove AI tone", "de-ai this writing". DO NOT TRIGGER for code cleanup, dead-code removal, AI-generated source code, or "deslop" of codebases — those belong to ai-slop-cleaner. DO NOT TRIGGER for prompt optimization — that is prompt-optimizer.
استنادا إلى تصنيف SOC المهني
| name | skill-debugger |
| description | Diagnose why a Claude Code skill is under-triggering, over-triggering, undiscoverable, or misconfigured. |
Systematic debugging tool for Claude Code skills that are not being selected correctly or are behaving incorrectly once invoked. Focus on the current Claude Code skill model: name and description drive discovery, while optional metadata controls invocation and execution behavior.
name distinct?description clearly say when to use the skill?disable-model-invocationuser-invocableallowed-toolsmodel, context, agent, hooksSymptom: skill exists but Claude almost never uses it.
Bad: description: Helps with various tasks
Good: description: Review code for bugs, regressions, and missing tests.
Symptom: wrong skill triggers instead.
Fix: narrow the promise and make the boundary explicit.
Symptom: Claude Code says the skill does not exist.
Check:
~/.claude/skills/<name>/SKILL.md.claude/skills/<name>/SKILL.mdSymptom: package exists but does not load correctly.
Fix: folder name and name: must match.
Symptom: behavior is wrong after the skill loads.
Audit:
disable-model-invocationuser-invocableallowed-toolsSkill: code-review
Status: not triggering
Root cause: description overlaps with broader review skill
Fix: tighten the description around review findings and regressions
=== Skill Debugging Report ===
Skill: financial-analyzer
Path: ~/.claude/skills/financial-analyzer/
Status: rarely triggers
Issues Found:
1. [CRITICAL] Description is too broad
2. [HIGH] disable-model-invocation is blocking auto-selection
3. [MEDIUM] No negative boundary for generic analytics requests
Recommendations:
1. Rewrite description around investing workflows
2. Set disable-model-invocation: false if auto-selection is intended
3. Add a When NOT to Use section
Test three classes of prompts:
SKILL.md parse correctly?name distinct?description say when to use the skill?disable-model-invocation suppressing auto-selection?user-invocable blocking direct use?allowed-tools too restrictive or too loose?When to Use or equivalent section?When NOT to Use boundary?Before: description: Helps with code analysis
After: description: Review code for bugs, regressions, maintainability issues, and missing tests.
Do not stuff many adjacent use cases into one description.
## When NOT to Use
- For generic implementation work, use `executor`
- For scorecard-style audits, use `skill-quality-analyzer`
If the skill should auto-trigger, do not leave disable-model-invocation: true.
If the skill should be callable directly, do not leave user-invocable: false.
Folder: ~/.claude/skills/code-review/
YAML: name: code-review
If the skill is derived from a vendored upstream baseline, keep baseline guidance intact and move project-specific behavior into clearly labeled local sections.
SKILL.md has valid frontmatternamedescription clearly states when to use the skillRecommended order:
skill-creator for authoring or structural revisionsskill-quality-analyzer for static issuesskill-debugger for routing/configuration issuesskill-tester for prompt-level verificationAfter fixes, the skill should: