skill-creator
This skill provides guidance for creating effective skills.
This skill should be used when orchestrating complex writing workflows with multiple phases. It provides two-agent orchestration patterns, the two-gate content readiness assessment, 10 baseline writing strategies, 20+ situational strategies, and quality checkpoints. Inspired by
$ npx -y skills add robertguss/claude-code-toolkit --skill writing-orchestration --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/writing-orchestrationContext preview
The summary Claude sees to decide when to auto-load this skill.
This skill should be used when orchestrating complex writing workflows with multiple phases. It provides two-agent orchestration patterns, the two-gate content readiness assessment, 10 baseline writing strategies, 20+ situational strategies, and quality checkpoints. Inspired by
name: writing-orchestration description: This skill should be used when orchestrating complex writing workflows with multiple phases. It provides two-agent orchestration patterns, the two-gate content readiness assessment, 10 baseline writing strategies, 20+ situational strategies, and quality checkpoints. Inspired by the Spiral Writing System.
A complete orchestration system for complex writing workflows. This skill provides the strategic layer that coordinates agents, applies writing strategies, and ensures content quality.
This skill applies when:
Complex writing benefits from separation of concerns:
User Request
↓
[Orchestrator] → Classify → Research → Two-Gate Assessment
↓
├── Not Ready → Gather more material/clarity
↓
└── Ready → Handoff to Writer
↓
[Writer] → Apply Strategies → Create Drafts
↓
Quality Checkpoints → OutputBefore any content creation, apply this assessment:
**Question**: "Could the writer create this without inventing facts?"
| Outcome | Action | |---------|--------| | ✓ Pass | Have concrete examples, data, quotes available | | ✗ Fail | Need to research/gather material first |
**Pass signals**:
**Question**: "Do we know EXACTLY what message to convey?"
| Outcome | Action | |---------|--------| | ✓ Pass | Clear, specific communication goal | | ✗ Fail | Need to interview for clarity |
**Pass signals**:
| Material | Message | Action | |----------|---------|--------| | ✓ | ✓ | Handoff to writer immediately | | ✓ | ✗ | Interview for message clarity | | ✗ | ✓ | Research/gather material | | ✗ | ✗ | Interview for both |
These strategies apply to ALL content. Reference [baseline-strategies.md](./references/baseline-strategies.md) for full details.
| Strategy | Rule | Transform | |----------|------|-----------| | **reader-zero-context** | Add 3-6 word orienting phrases | "Stripe handles billing" → "Stripe, the payments platform, handles billing" | | **subject-verb** | Subject + verb in first 5 words | "There were students who..." → "Students completed..." | | **activate-verbs** | Precise verbs over is/was | "Markets were down" → "Markets plunged" | | **watch-adverbs** | Let strong verbs carry load | "whispered quietly" → "whispered" | | **limit-ings** | Simple tense over continuous | "are running tests" → "run tests" | | **prefer-simple** | Everyday language unless technical | "utilizes stochastic gradient" → "learns by trial and error" | | **cut-big-small** | Edit hierarchically | Paragraphs → Sentences → Words | | **ban-empty-hypophora** | No self-answered questions | "The payoff? Our app..." → "Our app..." | | **present-active-tense** | Direct, immediate language | "debuts today" → "is out now" | | **one-idea-per-sentence** | Single clear point | Split compound thoughts |
Choose based on content type and goals. Reference [situational-strategies.md](./references/situational-strategies.md) for full list.
Before finalizing content, verify:
Extend Claude Code with specialized workflows, automatic formatting, and better defaults. Skills give Claude domain expertise—brainstorming methods, documentation generation, book writing pipelines.
Repo: robertguss/claude-code-toolkit
This skill provides guidance for creating effective skills.
This skill should be used when writing in the distinctive style of David Heinemeier Hansson (DHH). It applies when creating blog posts, technical articles,…
This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide. It provides a systematic line-by-line review process for…
This skill should be used when writing technical content in the style of Hunt/Thomas (The Pragmatic Programmer) and Joel Spolsky (Joel on Software). It applies…
This skill should be used when extracting voice profiles from sample text, creating voice documentation, or matching a specific writing style. It applies when…
A collaborative brainstorming system designed for multi-session ideation projects that span days or weeks.