Agent Coverage Check Skill for Claude
Check agent configuration coverage across hierarchy levels and phases. Use to ensure complete agent system coverage.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/majiayu000/claude-skill-registry --skill agent-coverage-checkWhat comes with it
896 bytes besides the instructionThe instruction itself
7 sections, as written by the authorAgent 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
Other skills for the same job
different authors, same section of the catalogue
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
How to use it
Take majiayu000/agent-coverage-check from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.