skill-creator
Skill6 starsChanged 8 months agoMITView on GitHub
Guide users through creating new cawpilot skills with a structured process and template. Use when the user asks to create a new skill, make a skill, add a skill, build a custom skill, or extend cawpilot's capabilities with new domain knowledge or workflows.
- Reads credentials
189 other projects use a version of this.
Adopted by
Most recently taken up by
- theexperiencecompany/gaiatheir own version, first seen Nov 13, 2026
- maotoumao/Cebiantheir own version, first seen Nov 9, 2026
- SebastienDegodez/copilot-instructionstheir own version, first seen Nov 8, 2026
- idavidov13/agentic-playwrighttheir own version, first seen Nov 8, 2026
- HughYau/AcademicForgetheir own version, first seen Nov 8, 2026
- Ar9av/obsidian-wikitheir own version, first seen Nov 8, 2026
Used with
Projects with it also use taskflow-inbox-triage, community-led-growth and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AtomicBot-aiSkilltaskflow-inbox-triage
Also in 6 projects that use this
nicepkgSkillcommunity-led-growth
Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.
Also in 5 projects that use this
naman10parikhSkillecosystem-reference
Quick-access directory of Claude Code ecosystem repos, skills, plugins, MCPs, and patterns. Use when improving the harness.
Also in 5 projects that use this
naman10parikhSkillfractal-delegation
Also in 5 projects that use this
shalombSkillmermaid-diagram-generator
Guide on creating and editing Mermaid charts safely. Use when asked to draw a diagram, flowchart, or architecture chart. Triggers on: 'mermaid', 'diagram', 'flowchart', 'visualize'.
Also in 5 projects that use this
nicepkgSkillph-community-outreach
Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.
Also in 5 projects that use this
- +5 more from naman10parikh
- +1 more from nicepkg
Other versions189 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 189
- molt-bot/clawdbot★ 395ksame name
- steipete/warelay★ 395ksame name
- moltbot/clawdbot★ 395ksame name
- openclaw/openclaw★ 395ksame name
- steipete/clawdis★ 394ksame name
- moltbot/moltbot★ 394ksame name
- clawdbot/clawdbot★ 394ksame name
- anthropics/skills★ 195ksame name
- openai/codex★ 135ksame name
- google-gemini/gemini-cli★ 109ksame name
179 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- find-skillsSkill
- githubSkill
- public-tunnelSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 185 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 67
Don't overwhelm — start with the essentials, follow up as needed.
- Very specific: line 78
Create the skill directory under skills/ in the workspace:
- Very specific: line 84
Write the SKILL.md following the format above.
- Distinctive: line 85
Use imperative form ("Run the command", not "You should run the command")
- Distinctive: line 87
Keep instructions concise — the agent is already smart, only add what it can't know
- Distinctive: line 88
Prefer examples over explanations
- Very specific: line 92
After creating the skill, tell the user to restart cawpilot so it picks up the new skill.
- Distinctive: line 108
When reviewing a skill draft, check each rule and flag violations before finalizing.
“Common” is measured: kept by at least 6 in 10 of the 185 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill Creator
Guide for creating cawpilot skills — modular packages that extend the agent with specialized knowledge, workflows, and tool integrations.
Skill Structure
skill-name/
├── SKILL.md (required — metadata + instructions)
├── scripts/ (optional — executable code for deterministic tasks)
├── references/ (optional — detailed docs loaded on demand)
└── assets/ (optional — templates, images, files used in output)SKILL.md Format
---
name: skill-name
description: What the skill does and when to use it. Be specific about triggers.
---
# Skill Title
Instructions for executing the skill's workflows.Frontmatter (YAML):
name(required): kebab-case identifierdescription(required): What it does + when to trigger. This is the only thing the agent sees before activating the skill, so be comprehensive about triggers.
Body (Markdown): Procedural instructions, rules, and examples. Target < 500 lines.
References (optional)
For large or multi-domain skills, split details into references/ files and link from SKILL.md:
For deployment details, see [references/aws.md](references/aws.md).The agent loads these only when needed, keeping the context lean.
Scripts (optional)
Include scripts in scripts/ for tasks that need deterministic reliability or are repeatedly rewritten. Scripts can be executed without loading into context.
Assets (optional)
Include files in assets/ that are used in output (templates, images, boilerplate) rather than loaded into context.
Creation Process
1. Understand the Goal
Ask the user:
- What should the skill do? (concrete examples of usage)
- What triggers it? (what would a user say?)
- What external tools or APIs does it use?
- Are there any credentials or secrets involved?
Don't overwhelm — start with the essentials, follow up as needed.
2. Plan the Skill
Identify:
- Core workflows: step-by-step procedures
- Rules and constraints: what to always/never do
- Reference material: schemas, API docs, domain knowledge (split into
references/if large)
3. Create the Skill
Create the skill directory under skills/ in the workspace:
skills/<skill-name>/SKILL.mdWrite the SKILL.md following the format above. Key guidelines:
- Use imperative form ("Run the command", not "You should run the command")
- Include concrete examples of inputs and expected outputs
- Keep instructions concise — the agent is already smart, only add what it can't know
- Prefer examples over explanations
4. Test and Iterate
After creating the skill, tell the user to restart cawpilot so it picks up the new skill. Then test with real prompts and refine based on results.
Privacy-First Rules
Every skill must follow these rules. Enforce them during creation:
- No secrets in skill files — never embed API keys, tokens, passwords, or credentials in SKILL.md or any skill file. Reference environment variables or config instead.
- No user data in skill files — skills are templates, not data stores. Never include PII, usernames, account IDs, or user-specific data.
- Credential handling — if a skill needs credentials, instruct the agent to read them from environment variables or the cawpilot config at runtime. Example:
Read the API key from the `MYSERVICE_API_KEY` environment variable. Never log or display the key. - Output sanitization — instruct skills to never print secrets, tokens, or sensitive data in messages sent back to the user.
- Minimal permissions — skills should request only the access they need. Don't expose broad filesystem paths or network access unnecessarily.
- Data locality — keep user data within the workspace. Never instruct the agent to upload data to external services without explicit user consent.
When reviewing a skill draft, check each rule and flag violations before finalizing.
Writing Tips
- Description is critical — it's the sole trigger mechanism. Include synonyms and example phrases.
- One skill, one domain — don't create catch-all skills. Split by domain.
- No boilerplate files — don't create README.md, CHANGELOG.md, or other non-essential files.
- Progressive disclosure — keep SKILL.md lean. Use
references/for detailed docs, schemas, or API specs that the agent loads only when needed.
Example
A minimal skill for interacting with a weather API:
---
name: weather
description: Fetch weather forecasts and current conditions using the OpenWeatherMap API. Use when the user asks about weather, forecasts, temperature, or conditions for a location.
---
# Weather
Fetch weather data from the OpenWeatherMap API.
## Setup
Read the API key from the `OPENWEATHER_API_KEY` environment variable. Never log or display the key.
## Usage
When the user asks for weather information:
1. Extract the location from the request
2. Call the API:
```bash
curl -s "https://api.openweathermap.org/data/2.5/weather?q=${LOCATION}&appid=${OPENWEATHER_API_KEY}&units=metric"- Parse the JSON response and report: temperature, conditions, humidity, wind speed
- If the location is ambiguous, ask the user to clarify
Rules
- Always use metric units unless the user specifies otherwise
- Never expose the API key in messages
- If the API returns an error, report it clearly without retrying
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

