Automated summary
Creates and populates new skill guides for recurring tasks by analyzing the codebase and gathering context.
Strengths
- Provides a structured template for documentation.
- Integrates codebase analysis for concrete examples.
- Includes anti-patterns and examples to avoid common mistakes.
Limitations
- Requires an existing codebase with identifiable patterns.
- Relies on user input to define the initial topic.
- Limited to text-based skill definitions, no support for rich formats.
Use this skill when you need to document a recurring task or pattern in a standardized format for AI agents.
Do not use it for one-off tasks or when the pattern is not yet clear or well understood.
Security analysis
SafeThe skill only creates a directory and a markdown file using 'mkdir -p', which is non-destructive. It does not execute arbitrary code, exfiltrate data, or disable safety features.
No concerns found
How this analysis is madeExamples
/add-skill Running tests with pytest/add-skill Deploying to production with Docker/add-skill Naming conventions for React componentsAdd Skill
Create and populate a new skill guide for recurring tasks.
Usage: /add-skill [name or topic]
Process
1. Get Skill Topic
If $ARGUMENTS is empty, use AskUserQuestion tool to ask:
- "What task or pattern should this skill document?"
2. Analyze Codebase
Search the codebase to find:
- Existing patterns related to this skill
- Code examples that demonstrate the pattern
- Common files/modules involved
3. Gather Context
Use AskUserQuestion tool to ask 2-3 clarifying questions:
- When should developers use this pattern?
- Are there any anti-patterns or common mistakes to avoid?
- Any project-specific conventions for this task?
4. Create Skill Structure
mkdir -p .context/skills/[skill-slug]
5. Populate SKILL.md
Create .context/skills/[skill-slug]/SKILL.md:
# Skill: [Name]
## When to Use
- [Situation 1 - based on analysis]
- [Situation 2]
- [Situation 3]
## Step by Step
### 1. [First Step]
[Explanation]
```[language]
# Code example from this codebase
[actual code found in the project]
2. [Second Step]
[Explanation]
[code example]
3. [Third Step]
[Explanation]
[code example]
Anti-Patterns
Don't:
- [Bad practice 1 - why it's bad]
- [Bad practice 2 - why it's bad]
Do:
- [Good practice 1]
- [Good practice 2]
Examples from This Codebase
[Example 1 Name]
Located at: [file path]
[relevant code snippet]
[Example 2 Name]
Located at: [file path]
[relevant code snippet]
Related
- [Link to related ADR if applicable]
- [Link to related skill if applicable]
## Output
Created: .context/skills/[slug]/SKILL.md
Skill: [Name]
Steps documented: X Examples included: X from codebase Anti-patterns: X identified
## If You Get Stuck
If you cannot make progress after 3 attempts at the same step:
1. Stop immediately
2. Explain what you're trying to do and what's blocking you
3. **Use AskUserQuestion tool** to ask the user how to proceed
Never loop indefinitely. If you find yourself repeating the same actions without progress, stop and ask for help.
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/add-skill-mrx3y0gd/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/add-skill-mrx3y0gd' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/add-skill-mrx3y0gd/download' --output '.skill-downloads/add-skill-mrx3y0gd/SKILL.md.part' && mv '.skill-downloads/add-skill-mrx3y0gd/SKILL.md.part' '.skill-downloads/add-skill-mrx3y0gd/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/add-skill-mrx3y0gd/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.