From interskill
Audit an existing skill against best practices — checks structure, frontmatter, invocation control, description quality, and anti-patterns. Use when verifying a skill before deployment.
How this skill is triggered — by the user, by Claude, or both
Slash command
/interskill:auditThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Verify a skill follows best practices and the official specification.
Verify a skill follows best practices and the official specification.
Given a skill path (SKILL.md or skill directory), check each item below. Report findings as PASS/WARN/FAIL.
--- delimitersname field present (lowercase, hyphens, max 64 chars)description field present and specific (includes trigger keywords)gen-skill-compact.sh --check <dir> to verify freshness)disable-model-invocation: true set if skill has side effects (deploy, commit, send)user-invocable: false set if skill is background knowledge onlyallowed-tools declared if specific tools neededcontext: fork used for isolation where appropriateintermesh.yaml exists and command -v intermesh >/dev/null 2>&1 succeeds, run intermesh manifest validate <path>/intermesh.yaml; report its diagnostics as normal audit findings.SKIP rather than WARN/FAIL and continue the existing audit unchanged.intermesh.yaml is not an audit finding unless the user explicitly requires Intermesh routing metadata.Skill Audit: {skill-name}
──────────────────────────────
Structure: {N}/6 pass
Invocation Control: {N}/4 pass
Content Quality: {N}/5 pass
Anti-Patterns: {N}/4 pass
──────────────────────────────
Overall: {PASS | WARN (N issues) | FAIL (N issues)}
Issues:
- [WARN] Description could be more specific
- [FAIL] Missing disable-model-invocation for deploy workflow
npx claudepluginhub mistakeknot/interagency-marketplace --plugin interskillGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.