writing-skills

Use when creating, updating, or improving agent skills.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "writing-skills" with this command: npx skills add sickn33/antigravity-awesome-skills/sickn33-antigravity-awesome-skills-writing-skills

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?

  1. Create a NEW skill:

  2. Improve an EXISTING skill:

  3. Verify Compliance:

📚 Component Index

ComponentPurpose
CSO"SEO for LLMs". How to write descriptions that trigger.
StandardsFile naming, YAML frontmatter, directory structure.
Anti-RationalizationHow to write rules that agents won't ignore.
TestingHow to ensure your skill actually works.

🛠️ Templates

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

  1. Identify goal → Use decision tree above
  2. Select template → From references/templates/
  3. Apply CSO → Optimize description for discovery
  4. Add anti-rationalization → For discipline skills
  5. 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

MistakeFix
Description summarizes workflowUse "Use when..." triggers only
No metadata.triggersAdd 3+ keywords
Generic name ("helper")Use gerund (creating-skills)
Long monolithic SKILL.mdSplit into references/

See gotchas.md for more.

✅ Pre-Deploy Checklist

Before deploying any skill:

  • name field matches directory name exactly
  • SKILL.md filename is ALL CAPS
  • Description starts with "Use when..."
  • metadata.triggers has 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-skill command 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

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

docker-expert

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

clean-code

No summary provided by upstream source.

Repository SourceNeeds Review
3.4K-sickn33
General

nextjs-supabase-auth

No summary provided by upstream source.

Repository SourceNeeds Review
3.2K-sickn33
General

nextjs-best-practices

No summary provided by upstream source.

Repository SourceNeeds Review
3.1K-sickn33