How do I install the Writing Skills skill?

Run npx skillmds@latest add mccteam/writing-skills in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Writing Skills skill do?

Use when creating, updating, or improving agent skills. It is listed under AI & ML on SkillMD.

Is Writing Skills safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Writing Skills?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Writing Skills free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Writing Skills?

mccteam (@mccteam) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Writing Skills by mccteam — Agent Skill

Name: Writing Skills
Author: mccteam

File contents

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:

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

---name: writing-skillsdescription: Use when creating, updating, or improving agent 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:** - Is it simple (single file, <200 lines)? -> [Tier 1 Architecture](references/tier-1-simple/README.md) - Is it complex (multi-concept, 200-1000 lines)? -> [Tier 2 Architecture](references/tier-2-expanded/README.md) - Is it a massive platform (10+ products, AWS, Convex)? -> [Tier 3 Architecture](references/tier-3-platform/README.md)2. **Improve an EXISTING skill:** - Fix "it's too long" -> [Modularize (Tier 3)](references/templates/tier-3-platform.md) - Fix "AI ignores rules" -> [Anti-Rationalization](references/anti-rationalization/README.md) - Fix "users can't find it" -> [CSO (Search Optimization)](references/cso/README.md)3. **Verify Compliance:** - Check metadata/naming -> [Standards](references/standards/README.md) - Add tests -> [Testing Guide](references/testing/README.md)## Component Index| Component | Purpose ||-----------|---------|| **[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](references/templates/technique.md) (How-to)- [Reference Skill](references/templates/reference.md) (Docs)- [Discipline Skill](references/templates/discipline.md) (Rules)- [Pattern Skill](references/templates/pattern.md) (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 Works1. **Identify goal** -> Use decision tree above2. **Select template** -> From `references/templates/`3. **Apply CSO** -> Optimize description for discovery4. **Add anti-rationalization** -> For discipline skills5. **Test** -> RED-GREEN-REFACTOR cycle## Quick Example```yaml---name: my-techniquedescription: 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](gotchas.md) for more.## Pre-Deploy ChecklistBefore 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

Frequently asked questions

Writing Skills