Our review
This skill guides the creation of a new SKILL.md file for the catalyst-skills library, following a structured pattern of decomposition, deduplication, verification, and synthesis.
Strengths
- Ensures perfect consistency with existing skill files.
- Breaks down writing into clear, parallelizable steps.
- Includes skeptic checks to validate assumptions.
- Provides a concrete worked example for each new skill.
Limitations
- Requires access to existing reference files to work.
- The template is rigid and may not suit all skill types.
- Does not generate code or infrastructure, only a markdown file.
When you need to add a new skill to the catalyst-skills library and want to follow the standard format.
When creating a skill outside this library or when the structured pattern is not relevant.
Security analysis
SafeThe skill is purely instructional; it describes how to create a markdown file with a specific structure, with no executable commands or risky operations. There is no potential for harm.
No concerns found
Examples
Add a new skill to the catalyst-skills/ library for refactoring legacy code. Follow the ORCHESTRATION-PROMPT.md pattern and match the style of existing skills.Create a skill in catalyst-skills/ that handles database cleanup tasks. Use the fan-out, reduce, verify, synthesize structure from the reference files.Add a skill for writing unit tests to the catalyst-skills library. Make sure it includes analysis tasks, verification questions, and a worked example as described.Add a new skill to the catalyst-skills/ library.
Reference: Read ORCHESTRATION-PROMPT.md for the pattern (fan out, reduce, verify, synthesize). Reference: Read one existing file in catalyst-skills/ (any of them) to match the exact structure and tone.
Skill name: $ARGUMENTS
DO NOT BUILD framework code. Build ONE markdown file only: catalyst-skills/[skill-name].md
The file must include, in this order:
- Problem Pattern — when a ticket matches this skill
- Analysis Tasks — independent, parallelizable investigation tasks (FAN OUT)
- Deduplication — how to consolidate/filter findings (REDUCE)
- Verification Questions — skeptic checks with fresh context, assume false until proven (VERIFY)
- Implementation Checklist — concrete build steps (SYNTHESIZE)
- One worked example with a realistic ticket
Match the formatting, heading style, and level of specificity of the existing skill files exactly. This should feel like it belongs in the same library, not like a different author wrote it.
After creating the file, do not modify any other files.
API Documentation Generator
Documentation
Automatically generates OpenAPI/Swagger API documentation.
Technical Writer
Documentation
Writes clear technical documentation following top style guides.
Add New Skill
Documentation
Creates a new skill file with the required structure, loading style guides and parsing arguments for category, name, and description. Use this when adding a new skill to ensure it follows the standard format and conventions.