メニュー
Use when validating a new or changed Claude Code skill, checking structural and repository policy compliance, testing whether descriptions trigger accurately, or grading representative skill outputs before deployment.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Creates a new specialist agent as two stitched source files, base.md plus frontmatter/claude.json, proposing model, effort, and permissions by role archetype and confirming them with the user before writing. Use when adding a new subagent, defining a new specialist role, scaffolding an agent definition, or when update-agent hands off new-agent creation.
Discover, validate, stitch, and install specialist agent templates contributed by Essential and other enabled plugins in the same marketplace. Use when asked to install agents, set up subagents, refresh the agent team, or configure Claude Code on a new machine.
[Description] — third person, what the skill does plus a 'Use when...' clause with concrete trigger phrases a user would actually type; 25-60 words; lead with the key use case.
Update explicitly selected agent definitions to the current two-file template or a stated behavior change while preserving useful role expertise, trigger boundaries, context, collaboration links, and working voice. Use when migrating agents to a template revision, correcting agent configuration, or batch-updating selected agents; require an exact selector and route genuinely new roles to create-agent.
Enforce coding standards mechanically across a selected scope with batched linters and independent reviewers. Use when source files need lint-error correction, standards enforcement, or consistent formatting, including calls extended by another plugin's portable lint profile; behavior-changing repairs belong to fix.
Review semantic correctness, security, test intent, documentation, sibling consistency, and alignment with the implementation plan. Use after code changes or for explicit review requests; report findings without editing code and leave mechanical standards enforcement to lint.
| name | verify-skill |
| description | Use when validating a new or changed Claude Code skill, checking structural and repository policy compliance, testing whether descriptions trigger accurately, or grading representative skill outputs before deployment. |
| model | opus |
| context | fork |
quick_validate.py owns repository policies only; it must not duplicate the
evolving Claude schema.Shared authoring policy lives at
${CLAUDE_SKILL_DIR}/../../constitution/references/authoring-invariants.md.
SKILL.md, skill directory, plugin, marketplace, or plugins path.structural, functional, or full (default full).evals/evals.yaml and representative prompts.${CLAUDE_SKILL_DIR}/scripts/quick_validate.py on the target. Review body length,
description budget, unresolved local references, and placeholders.references/functional-mode.md for execution and
grading details.The validator does not require fixed headings, personas, diagrams, subagent prompts, XML report envelopes, or a section literally named “Skill Completion.”
claude plugin validate --strict <plugin-path>
python3 "${CLAUDE_SKILL_DIR}/scripts/quick_validate.py" <skill-or-plugin-path>
python3 "${CLAUDE_SKILL_DIR}/scripts/run_trigger_eval.py" --help
Run the first two commands after every fix iteration. Trigger and functional results must include the prompt, observed behavior, and pass/fail rationale.
Return a concise per-skill verdict with official validation status, policy issues, functional/trigger evidence when applicable, and actionable failures.