sickn33/agentic-awesome-skills21 files

Writing Skills

Use when creating, updating, or improving agent skills.

Specification
Skill ID
sickn33/agentic-awesome-skills/writing-skills
Publisher
sickn33
Repository
agentic-awesome-skills
Installs
0
Files
21
Synced
Sep 23, 2026
How to use it

Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.

sickn33/agentic-awesome-skills/writing-skillsInstalls these files
  • SKILL.md
  • anthropic-best-practices.md
  • examples.md
  • gotchas.md
  • graphviz-conventions.dot
  • persuasion-principles.md
  • references/anti-rationalization/README.md
  • references/cso/README.md
  • references/standards/README.md
  • references/standards/metadata-standard.md
  • references/templates/discipline.md
  • references/templates/pattern.md
  • references/templates/reference.md
  • references/templates/technique.md
  • references/templates/tier-3-platform.md
  • references/testing/README.md
  • references/tier-1-simple/README.md
  • references/tier-2-expanded/README.md
  • references/tier-3-platform/README.md
  • render-graphs.js
  • testing-skills-with-subagents.md

What this skill tells the agent

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:
  • 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
  1. 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)
  1. Verify Compliance:
  • Check metadata/naming -> Standards
  • Add tests -> Testing Guide

📚 Component Index

ComponentPurpose
[CSO](references/cso/README.md)"SEO for LLMs". How to write descriptions that trigger.
[Standards](references/standards/README.md)File naming, YAML frontmatter, directory structure.
[Anti-Rationalization](references/anti-rationalization/README.md)How to write rules that agents won't ignore.
[Testing](references/testing/README.md)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

  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

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Use this skill in a project

Open any RiverX project, search the Skills panel for sickn33/agentic-awesome-skills/writing-skills, and install it in one click.

Use this skill