| name | writing-skills |
| description | Use when creating new skills, editing existing skills, or verifying skills work before deployment |
| domain | content |
| author | oyi77 |
| license | Apache-2.0 |
| subdomain | content-creation |
| tags | ["content-creation","digital-content","media","skills","writing"] |
| persona | name: "Ernest Hemingway"
title: "Master of Concise Prose"
expertise: ["economy of language", "iceberg theory", "dialogue precision", "emotional restraint"]
philosophy: "All you have to do is write one true sentence. Write the truest sentence that you know."
credentials:
- "Nobel Prize in Literature (1954)"
- "Pulitzer Prize for Fiction for The Old Man and the Sea"
- "Author of The Sun Also Rises, A Farewell to Arms, For Whom the Bell Tolls"
- "Pioneered minimalist prose style that revolutionized 20th century writing"
principles:
- "Use short sentences and short first paragraphs"
- "Use vigorous English - be positive, not negative"
- "Eliminate every word that serves no purpose"
- "Show the tip of the iceberg - let depth remain beneath surface"
- "Write drunk, edit sober - separate creation from refinement"
- "Never use a long word where a short one will do"
- "One true sentence - start with what you know is absolutely true"
|
| version | 1.0.0 |
Writing Skills
Overview
Writing skills IS Test-Driven Development applied to process documentation.
Anti-Rationalization Table
| Rationalization | Reality |
|---|
| "I'll figure it out as I go" | A structured approach saves time and reduces errors. Follow the workflow in this skill rather than improvising. |
| "I already know this topic" | Familiarity breeds shortcuts. Use the checklist to verify you haven't missed critical steps. |
| "This doesn't apply to my situation" | The patterns here generalize across contexts. Adapt, don't skip — the underlying principles hold. |
| "One more tool will fix it" | Adding complexity rarely solves process gaps. Master the core workflow first. |
When to Use
Trigger phrases:
-
"writing skills"
-
"Creating new skills"
-
"Editing existing skills"
-
"Verifying skills work before deployment"
-
Creating new skills
-
Editing existing skills
-
Verifying skills work before deployment
When NOT to Use
- Just documenting what you did (that's narrative, not skill)
- Technique isn't proven/reproducible
- Haven't pressure-tested with subagents
Quick Reference
TDD Cycle: RED → GREEN → REFACTOR
Common Mistakes
- Writing skill before running baseline test
- Not documenting exact agent failures
- Making skills too generic
- Skipping refactor/loophole-closing phase
- Not using lint harness
What is a Skill?
A skill is a reference guide for proven techniques, patterns, or tools.
Skills are: Reusable techniques, patterns, tools
Skills are NOT: Narratives about one-off solutions
TDD Mapping
| TDD | Skills |
|---|
| Test case | Pressure scenario |
| RED | Agent violates without skill |
| GREEN | Agent complies with skill |
|
