Create new agent skills with proper structure, progressive disclosure, and bundled resources.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionwrite-a-skillExecute the skills CLI command in your project's root directory to begin installation:
Fetches write-a-skill from mattpocock/skill and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate write-a-skill. Access via /write-a-skill in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
0
upvotes
Run in your terminal
0
installs
0
this week
—
stars
| name | write-a-skill |
| description | Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill. |
Gather requirements - ask user about:
Draft the skill - create:
Review with user - present draft and ask:
skill-name/
├── SKILL.md # Main instructions (required)
├── REFERENCE.md # Detailed docs (if needed)
├── EXAMPLES.md # Usage examples (if needed)
└── scripts/ # Utility scripts (if needed)
└── helper.js
---
name: skill-name
description: Brief description of capability. Use when [specific triggers].
---
# Skill Name
## Quick start
[Minimal working example]
## Workflows
[Step-by-step processes with checklists for complex tasks]
## Advanced features
[Link to separate files: See [REFERENCE.md](REFERENCE.md)]
The description is the only thing your agent sees when deciding which skill to load. It's surfaced in the system prompt alongside all other installed skills. Your agent reads these descriptions and picks the relevant skill based on the user's request.
Goal: Give your agent just enough info to know:
Format:
Good example:
Extract text and tables from PDF files, fill forms, merge documents. Use when working with PDF files or when user mentions PDFs, forms, or document extraction.
Bad example:
Helps with documents.
The bad example gives your agent no way to distinguish this from other document skills.
Add utility scripts when:
Scripts save tokens and improve reliability vs generated code.
Split into separate files when:
After drafting, verify:
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
greedychipmunk/agent-skills
vercel-labs/agent-browser
rshankras/claude-code-apple-skills
oimiragieo/agent-studio
panniantong/agent-reach
openai/skills
I recommend write-a-skill for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
write-a-skill is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
write-a-skill reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for write-a-skill matched our evaluation — installs cleanly and behaves as described in the markdown.
write-a-skill is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: write-a-skill is focused, and the summary matches what you get after install.
write-a-skill is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
write-a-skill fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
write-a-skill has been reliable in day-to-day use. Documentation quality is above average for community skills.
write-a-skill has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 38