メニュー
Validates plugin structure and metadata across the marketplace. Use when asked to "verify plugins", "validate plugin structure", "check plugins", or after making changes to plugin files.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
A relentless one-question-at-a-time interview that sharpens a plan, decision, or idea until shared understanding is reached — not limited to software. Use when the user wants requirements or a decision clarified before acting, wants to stress-test their thinking, or asks to "grill me", "詰めて", "brainstorm this".
Executes an implementation plan or agreed work by orchestrating fresh subagents — one implementer per task, a reviewer between tasks — while the main model plans, briefs, and evaluates without writing code itself. Use when the user asks to "implement the plan", "start implementation", "実装して", or hands over a plan or spec to execute.
A feedback-loop-first discipline for diagnosing hard bugs and performance regressions. Use when the user reports something broken, throwing, failing, flaky, or slow, or asks to "diagnose", "debug this", "原因を調べて".
Builds a clearly-marked throwaway prototype to answer a design question before committing to an implementation. Use when the user wants to sanity-check whether logic or a state model feels right, explore what a UI should look like, or asks to "prototype this", "試作して".
Creates an Architecture Decision Record for a decision that is hard to reverse, surprising without context, and the result of a real trade-off. Use when such a decision has just been made, or the user asks to "record this decision", "ADRにして", or mentions decision records.
Reviews the diff since a fixed point along two axes run as parallel subagents — Spec (does the change match what was asked?) and Standards (repo conventions plus a code-smell baseline) — and reports them side by side. Use when the user asks to review a branch, work-in-progress changes, a diff, or "review since X".
SOC 職業分類に基づく
| name | verify |
| description | Validates plugin structure and metadata across the marketplace. Use when asked to "verify plugins", "validate plugin structure", "check plugins", or after making changes to plugin files. |
Validate all plugins in the marketplace for correct structure and metadata.
Read marketplace.json at .claude-plugin/marketplace.json. Verify it has name, owner (with name and email), and plugins array.
For each plugin in the plugins array, verify:
source path exists as a directory.claude-plugin/plugin.json exists at the source path and contains required fields: name, description, version, authorname in plugin.json matches the name in the marketplace entryversion follows semver format (e.g., 0.2.0, 1.0.0)For each skill directory under plugins/<name>/skills/:
SKILL.md existsname and descriptiondescription includes trigger phrasesreferences/ directory exists, verify it contains at least one fileReport results: