writing-skills
219
总安装量
214
周安装量
#1243
全站排名
安装命令
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill writing-skills
Agent 安装分布
claude-code
171
gemini-cli
154
opencode
154
codex
122
cursor
118
Skill 文档
Writing Skills (Excellence)
Dispatcher for skill creation excellence. Use the decision tree below to find the right template and standards.
â¡ Quick Decision Tree
What do you need to do?
-
Create a NEW skill:
- Is it simple (single file, <200 lines)? â Tier 1 Architecture
- Is it complex (multi-concept, 200-1000 lines)? â Tier 2 Architecture
- Is it a massive platform (10+ products, AWS, Convex)? â Tier 3 Architecture
-
Improve an EXISTING skill:
- Fix “it’s too long” -> Modularize (Tier 3)
- Fix “AI ignores rules” -> Anti-Rationalization
- Fix “users can’t find it” -> CSO (Search Optimization)
-
Verify Compliance:
- Check metadata/naming -> Standards
- Add tests -> Testing Guide
ð Component Index
| 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. |
ð ï¸ Templates
- Technique Skill (How-to)
- Reference Skill (Docs)
- Discipline Skill (Rules)
- Pattern Skill (Design Patterns)
When to Use
- Creating a NEW skill from scratch
- Improving an EXISTING skill that agents ignore
- Debugging why a skill isn’t being triggered
- Standardizing skills across a team
How It Works
- Identify goal â Use decision tree above
- Select template â From
references/templates/ - Apply CSO â Optimize description for discovery
- Add anti-rationalization â For discipline skills
- Test â RED-GREEN-REFACTOR cycle
Quick Example
---
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]
Common Mistakes
| 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.
â Pre-Deploy Checklist
Before deploying any skill:
-
namefield matches directory name exactly -
SKILL.mdfilename is ALL CAPS - Description starts with “Use when…”
-
metadata.triggershas 3+ keywords - Total lines < 500 (use
references/for more) - No
@force-loading in cross-references - Tested with real scenarios
ð Related Skills
- opencode-expert: For OpenCode environment configuration
- Use
/write-skillcommand for guided skill creation
Examples
Create 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