skill-factory

To turn code patterns into reusable skills, analyze your codebase to extract recurring workflows and generate a self-contained SKILL.md file. This file documents the pattern, concrete file paths, and wiring steps to reduce manual toil and ensure consistent automation across agents.

The best way to document recurring tasks is by generating a complete SKILL.md blueprint. It codifies established naming conventions and concrete file paths from your repository into a reusable format that can be shared across agents.

Yes, you can generate a SKILL.md for a repository with multiple established patterns. The skill factory applies to codebases with recurring tasks, analyzing existing workflows and codifying them into a reusable blueprint with clear wiring references.

To ensure your generated skill follows existing repository conventions, the skill factory analyzes your codebase and extracts established patterns. The resulting SKILL.md uses concrete file paths from the project and includes a clear registration and wiring step.

You should not use a skill factory for codebase automation if your repository lacks multiple recurring tasks or established patterns. The tool requires existing workflows to analyze and codify into a reusable SKILL.md blueprint.