Agent skill
agent-coverage-check
Check agent configuration coverage across hierarchy levels and phases. Use to ensure complete agent system coverage.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/development/agent-coverage-check
SKILL.md
Agent Coverage Check
Verify complete agent system coverage across all dimensions.
When to Use
- After adding new agents to system
- Validating agent system completeness
- Finding gaps in coverage
- Ensuring all development phases covered
Quick Reference
# Check all coverage dimensions
./scripts/check_agent_coverage.sh
# Check specific dimension
./scripts/check_level_coverage.sh
./scripts/check_phase_coverage.sh
./scripts/check_section_coverage.sh
Coverage Dimensions
Hierarchy Levels:
- L0: Chief Architect (1)
- L1: Section Orchestrators (6)
- L2: Design Agents (per section)
- L3: Specialists (per module)
- L4: Engineers
- L5: Junior Engineers
Development Phases:
- Plan
- Test
- Implementation
- Package
- Cleanup
Sections:
- Foundation
- Shared Library
- Tooling
- First Paper
- CI/CD
- Agentic Workflows
Coverage Report Format
Hierarchy Coverage:
L0: ✅ 1 agent
L1: ✅ 6 agents
L2: ✅ 12 agents
L3: ✅ 24 agents
L4: ✅ 3 agents
L5: ✅ 1 agent
Phases:
Plan: ✅ Covered
Test: ✅ Covered
Implementation: ✅ Covered
Package: ✅ Covered
Cleanup: ✅ Covered
Sections:
Foundation: ✅ Orchestrator + agents
Shared Library: ✅ Orchestrator + agents
Gap Patterns
Missing level: Any level with 0 agents
Missing phase: Phase not assigned to any agent
Missing section: Section without orchestrator
References
agent-validate-config- Validate individual agent configsagent-test-delegation- Test delegation completeness.claude/agents/- All agent configurations
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?