Decision tree and templates for building agent skills that agents actually follow.
Works with
Provides three architecture tiers based on skill complexity: Tier 1 for simple single-file skills, Tier 2 for multi-concept skills, and Tier 3 for large platforms
Includes specialized guides for improving existing skills: modularization, anti-rationalization (preventing agent rule-ignoring), and CSO (search optimization for LLM discovery)
Offers four skill templates covering technique, reference, disci
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionwriting-skillsExecute the skills CLI command in your project's root directory to begin installation:
Fetches writing-skills from sickn33/antigravity-awesome-skills 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 writing-skills. Access via /writing-skills 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
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
31.1K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
31.1K
stars
Dispatcher for skill creation excellence. Use the decision tree below to find the right template and standards.
Create a NEW skill:
Improve an EXISTING skill:
Verify Compliance:
| Component | Purpose |
|---|---|
| CSO | "SEO for LLMs". How to write descriptions that trigger. |
| Standards | File naming, YAML frontmatter, directory structure. |
| Anti-Rationalization | How to write rules that agents won't ignore. |
| Testing | How to ensure your skill actually works. |
references/templates/---
name: my-technique
description: Use when [specific symptom occurs].
metadata:
category: technique
triggers: error-text, symptom, tool-name
---
# My Technique
## When to Use
- [Symptom A]
- [Error message]
| Mistake | Fix |
|---|---|
| Description summarizes workflow | Use "Use when..." triggers only |
No metadata.triggers |
Add 3+ keywords |
| Generic name ("helper") | Use gerund (creating-skills) |
| Long monolithic SKILL.md | Split into references/ |
See gotchas.md for more.
Before deploying any skill:
name field matches directory name exactlySKILL.md filename is ALL CAPSmetadata.triggers has 3+ keywordsreferences/ for more)@ force-loading in cross-references/write-skill command for guided skill creationCreate a Tier 1 skill:
mkdir -p ~/.config/opencode/skills/my-technique
touch ~/.config/opencode/skills/my-technique/SKILL.md
Create a Tier 2 skill:
mkdir -p ~/.config/opencode/skills/my-skill/references/core
touch ~/.config/opencode/skills/my-skill/{SKILL.md,gotchas.md}
touch ~/.config/opencode/skills/my-skill/references/core/README.md
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
sickn33/antigravity-awesome-skills
JuliusBrussee/caveman
JuliusBrussee/caveman
davila7/claude-code-templates
whyashthakker/agent-skills-marketing
mattpocock/skills
Solid pick for teams standardizing on skills: writing-skills is focused, and the summary matches what you get after install.
writing-skills fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
writing-skills is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
writing-skills has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend writing-skills for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
writing-skills has been reliable in day-to-day use. Documentation quality is above average for community skills.
writing-skills reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for writing-skills matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: writing-skills is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in writing-skills — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 62