opencode-skill-auditor

To identify overlapping capabilities and redundancies across code skills, you can audit the skill library to locate duplicate functions and propose consolidations. This process analyzes the repository to map dependencies and highlight areas for consolidation to avoid duplication.

The best way to plan modularization for a monolithic skill repository is to analyze the skills directory to generate a modularization plan. This breaks down monolithic skills into reusable components, maps dependency relationships, and documents migration paths to future-proof the catalog.

You validate frontmatter integrity and documentation structure by auditing the skill library to ensure future compatibility and maintainability. This assessment checks naming conventions, frontmatter completeness, and structural documentation to guide maintenance decisions.

Yes, you can analyze specific skill directories instead of the entire repository by providing their paths as input. For example, you can focus the modularization and redundancy analysis on a targeted directory like skills/opencode-skill-auditor.

Dependency mapping works by evaluating all skills in the repository to produce structured analyses of interdependencies and coupling. This highlights missing modularization opportunities and generates assessment reports to guide ongoing maintenance decisions.