Automated summary
This guide helps create a new skill file following the catalyst-skills library's fan-out, reduce, verify, synthesize pattern.
Strengths
- Ensures consistency with existing skills via a strict template.
- Breaks down work into parallelizable analysis tasks.
- Includes explicit deduplication and skeptic verification steps.
- Offers a fully worked realistic example.
Limitations
- Relies on reference files like ORCHESTRATION-PROMPT.md being present.
- Builds only a single markdown file, no framework code.
- May be overkill for trivial skills.
When adding a new reusable skill to a structured library like catalyst-skills and matching its established format.
When creating a simple standalone prompt or a skill that does not need to fit an existing library pattern.
Security analysis
SafeThe skill only instructs to read local files (ORCHESTRATION-PROMPT.md and an existing skill) and create a new markdown file within the catalyst-skills/ directory. No destructive commands, network activity, or exfiltration. It is entirely safe to execute.
No concerns found
How this analysis is madeExamples
Add a new skill to catalyst-skills/ named 'refactor-legacy' with a worked example about breaking up a monolithic function.Add a new skill 'debug-first-failure' to the catalyst-skills library following the standard pattern.Add a new skill to catalyst-skills/ for writing database migrations, including a realistic ticket example and verification questions.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.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/create-catalyst-skill-ms9wnz22/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/create-catalyst-skill-ms9wnz22' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/create-catalyst-skill-ms9wnz22/download' --output '.skill-downloads/create-catalyst-skill-ms9wnz22/SKILL.md.part' && mv '.skill-downloads/create-catalyst-skill-ms9wnz22/SKILL.md.part' '.skill-downloads/create-catalyst-skill-ms9wnz22/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/create-catalyst-skill-ms9wnz22/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Supabase Docs Authoring
Documentation
Write, edit, and review Supabase documentation content including guides, tutorials, reference docs, and partials. Follow style guides and MDX/TOML validation rules.
Create Architecture Decision Record
Documentation
Create a new Architecture Decision Record with sequential numbering, register it in the AgentDB graph, and link related ADRs.
Plan update with deep research
Documentation
Updates a plan document by launching parallel subagents to analyze a topic across all compiler passes, then consolidates findings into the plan doc.