skillsMaintenance

Skill refactoring is triggered by detecting strong and weak signals such as large file sizes, repeated content, and difficult information discovery. This Skill systematically identifies these maintenance indicators to evaluate when your skills library requires optimization.

The best way to split a large SKILL.md file is through vertical splitting. This refactoring strategy breaks the file into logical subdirectories and updates the main SKILL.md to serve as a navigation hub for improved discoverability.

Knowledge compression works by systematically reducing content redundancy and archiving outdated information within the skills library. This refactoring method optimizes workflow by ensuring documentation remains concise and easily discoverable.

You should start skill maintenance when a SKILL.md file grows over 500 lines or when you notice repeated content. These strong and weak signals indicate that your documentation requires refactoring to maintain code quality and discoverability.

Yes, you can standardize pull requests for skill refactoring. This approach provides specific templates for Pull Requests and evaluation reports to ensure consistency and standardize the maintenance process across your skills library.

Yes, this refactoring approach handles outdated content through archiving. It addresses issues of skill size, content redundancy, and discoverability by applying actionable strategies to clean up and maintain the skills library.