Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From skill-maker
Validates skill structure: file layout, YAML frontmatter syntax and fields, naming conventions, description quality, body content, and references integrity. Outputs pass/fail report with fixes.
npx claudepluginhub vcode-sh/vibe-tools --plugin skill-makerHow this command is triggered — by the user, by Claude, or both
Slash command
/skill-maker:validate path to skill folder or SKILL.mdThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Quick Skill Validation Run a fast structural validation check on a skill. Lighter than `/skill-maker:review` - focuses on structure and format, not quality. ## Input The user provides: `$ARGUMENTS` If `$ARGUMENTS` is a path, use it directly. If `$ARGUMENTS` is empty, ask: "Which skill should I validate? Provide the path to the skill folder or SKILL.md file." ## Validation Checks ### 1. File Structure - [ ] SKILL.md exists (exact name, case-sensitive) - [ ] Folder name is kebab-case - [ ] No README.md inside skill folder - [ ] No unexpected files at root level ### 2. YAML Frontmatte...
/validate-skillValidates skill file at given path for structure, quality, security, standards, and ecosystem compliance, producing detailed report with summary, findings, recommendations, and readiness status.
/devkit.verify-skillValidates specified skill against DevKit standards for SKILL.md frontmatter, structure, files, and content quality, reporting compliance issues.
/fire-validate-skillsValidates skills library markdown files for structural integrity: YAML frontmatter, required sections, cross-references, and syntax issues.
/audit-skillAudits Claude Code SKILL.md files for structure, description quality, content effectiveness, progressive disclosure, and more across 4-7 pillars. Supports --full or --mini modes and path/glob inputs.
/audit-skillAudits skill at <skill-path> for YAML compliance, pure XML structure, progressive disclosure, and best practices. Produces findings with file:line locations, compliance scores, and recommendations.
/validateValidates CLI harness for software at given path or GitHub repo against HARNESS.md standards: directory structure, files, Click CLI, core modules, tests, and docs.
Share bugs, ideas, or general feedback.
Run a fast structural validation check on a skill. Lighter than /skill-maker:review - focuses on structure and format, not quality.
The user provides: $ARGUMENTS
If $ARGUMENTS is a path, use it directly.
If $ARGUMENTS is empty, ask: "Which skill should I validate? Provide the path to the skill folder or SKILL.md file."
--- on line 1---name field presentname is kebab-casename matches folder namedescription field present< >)# or ##)references/ are referenced from SKILL.mdscripts/ are referenced from SKILL.mdQuick pass/fail report:
VALIDATION: [skill-name]
════════════════════════
File Structure: [PASS/FAIL] [details if fail]
YAML Frontmatter: [PASS/FAIL] [details if fail]
Description: [PASS/FAIL] [details if fail]
Body: [PASS/FAIL] [details if fail]
References: [PASS/FAIL] [details if fail]
Result: [ALL PASS / X ISSUES FOUND]
If issues found, list each with the specific fix needed.
If all pass: "Skill structure is valid. Run /skill-maker:review for a full quality audit."