Agent skill
kit-verify
(ePost) Use when preparing a release, running pre-init checks, auditing kit health, or when asked to "verify", "audit kit", "pre-release check"
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/kit-verify
Metadata
Additional technical details for this skill
- keywords
-
verify audit pre-release health-check lint
- platforms
-
[ "all" ] - connections
-
{ "requires": [ "kit-agents" ] } - agent affinity
-
[ "epost-kit-designer", "epost-code-reviewer" ]
SKILL.md
Kit Verification Workflow
Pre-release/pre-init audit pipeline. Ensures kit integrity before epost-kit init or release.
When to Use
- Before running
epost-kit initon a project - Before creating a release/tag
- After batch-editing skills, agents, or connections
- When CI gate needs to validate kit health
CLI Command
epost-kit verify # full audit, errors block
epost-kit verify --strict # warnings also block (CI mode)
What It Checks
- Reference validation — all agent/skill/command refs point to valid targets
- Connection integrity — extends/requires/enhances targets exist, no cycles, bidirectional conflicts
- Frontmatter completeness — skills have description, keywords, platforms
- Package.yaml sync — skills on disk match provides.skills declarations
- Skill-index staleness — index count matches actual SKILL.md count
- Orphan detection — skills not referenced by any agent or connection
- Dependency graph — auto-generates
docs/skill-dependency-graph.md(mermaid)
Exit Codes
0— pass (may have warnings/info)1— fail (errors found, or--strictwith warnings)
Integration
- Wire as pre-commit hook:
epost-kit verify --strict - Wire in CI:
npx epost-kit verify --strict --dir . epost-kit initcan optionally run verify before generating.claude/
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?