mcpbeat Sign in

Writing Orchestration Skill for Claude

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.

6k tokens
context cost
the whole folder, loaded on every use
4
files
instructions only
0
copies elsewhere
how many repositories repackaged it
102
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/robertguss/claude-code-toolkit --skill writing-orchestration

What comes with it

16 585 bytes besides the instruction
references/baseline-strategies.md
references/quality-checkpoints.md
references/situational-strategies.md

The instruction itself

33 sections, as written by the author

Writing Orchestration Skill

A complete orchestration system for complex writing workflows. This skill provides the strategic layer that coordinates agents, applies writing strategies, and ensures content quality.

When to Use This Skill

This skill applies when:

  • Coordinating multiple writing agents
  • Applying strategic writing decisions
  • Assessing content readiness before drafting
  • Selecting and applying writing strategies
  • Running quality checkpoints on drafts

Two-Agent Architecture

Complex writing benefits from separation of concerns:

Orchestrator Role

  • Classifies requests (information vs. content)
  • Applies two-gate assessment
  • Gathers research and context
  • Hands off to writer when ready
  • Never creates content directly

Writer Role

  • Creates drafts using strategies
  • Applies style guides
  • Produces variations (EXPLORATION mode)
  • Refines based on feedback (REFINEMENT mode)
  • Uses tools for all content (never in chat)
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 → Output

Two-Gate Content Readiness Assessment

Before any content creation, apply this assessment:

Gate 1: Material Sufficiency

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:

  • Specific examples available
  • Data points confirmed
  • Expert quotes accessible
  • No major claims need fabrication

Gate 2: Message Clarity

Question: "Do we know EXACTLY what message to convey?"

| Outcome | Action |

|---------|--------|

| ✓ Pass | Clear, specific communication goal |

| ✗ Fail | Need to interview for clarity |

Pass signals:

  • Can state thesis in one sentence
  • Know the audience specifically
  • Know the desired action
  • Angle is differentiated

Decision Matrix

| Material | Message | Action |

|----------|---------|--------|

| ✓ | ✓ | Handoff to writer immediately |

| ✓ | ✗ | Interview for message clarity |

| ✗ | ✓ | Research/gather material |

| ✗ | ✗ | Interview for both |

10 Baseline Strategies (ALWAYS Apply)

These strategies apply to ALL content. Reference 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 |

20+ Situational Strategies (Select 3-4)

Choose based on content type and goals. Reference situational-strategies.md for full list.

Hook & Opening

  • hook-effectiveness - Counterintuitive or surprising openings
  • tension-builder - Create and resolve tension
  • pattern-twist - Set expectations, then break them

Structure & Flow

  • order-words-emphasis - Important words at sentence ends
  • sentence-length - Vary for rhythm (short for impact, long for flow)
  • paragraph-length - Mix for visual rhythm
  • ladder-abstraction - Alternate concrete ↔ abstract

Style & Voice

  • elegant-variation - Avoid word repetition
  • passive-aggressive - Strategic passive for emphasis
  • punctuation-pace - Use punctuation for rhythm
  • key-words-space - Give important terms breathing room

Persuasion & Engagement

  • essential-name-filter - Only names that add value
  • name-of-dog - Specific details for authenticity
  • original-images - Fresh metaphors, avoid clichés
  • show-and-tell - Balance showing with telling

Narrative & Story

  • narrate-scenes - Immersive scene-setting
  • cinematic-angles - Camera-like perspective shifts
  • dialogue-compression - Tight, purposeful dialogue
  • reveal-traits - Character through action

Quality Checkpoints

Before finalizing content, verify:

Opening Quality

  • [ ] Opening is counterintuitive or surprising
  • [ ] Leads with most compelling insight/moment/problem
  • [ ] No chronology/setup/version numbers in opening
  • [ ] Hook earns the next sentence

Body Quality

  • [ ] Body delivers on opening's promise
  • [ ] Concrete sensory details present
  • [ ] Each paragraph has clear purpose
  • [ ] Transitions are smooth

Strategy Compliance

  • [ ] All 10 baseline strategies applied
  • [ ] 3-4 situational strategies visible
  • [ ] Each sentence expresses one clear idea
  • [ ] Technical terminology oriented with context

Style Guide Compliance

  • [ ] Voice matches profile/guide
  • [ ] No prohibited words/patterns
  • [ ] Formatting rules followed

Content Modes

EXPLORATION Mode (New Content)

When creating new content:

  • Generate 3 different drafts
  • Vary angle, not just words
  • Apply all strategies to each
  • Let user choose direction

REFINEMENT Mode (Editing)

When user provides feedback:

  • Work with existing draft
  • Preserve voice and structure
  • Apply specific changes requested
  • Keep what works

Handoff Protocol

Orchestrator → Writer

[Research summary if applicable - 2-3 sentences]
[Material gathered: list key assets]
[Message clarity: thesis statement]
[Style guide: name if applicable]
[Mode: EXPLORATION or REFINEMENT]

Writer → Orchestrator (Rare)

Only when:

  • User explicitly requests brainstorming
  • New research topic needed
  • Web search required
  • Significant scope change

Integration with Commands

/writing:plan

Uses Orchestrator patterns:

  • Request classification
  • Research phase
  • Two-gate assessment
  • Material gathering

/writing:draft

Uses Writer patterns:

  • Strategy application
  • Mode selection
  • Draft creation
  • Quality checkpoints

/writing:review

Uses both:

  • Orchestrator: coordinate review agents
  • Writer: apply fixes

/writing:compound

Captures patterns that worked for future orchestration.

References

  • baseline-strategies.md - Full 10 baseline strategies with examples
  • situational-strategies.md - 20+ situational strategies
  • quality-checkpoints.md - Detailed checkpoint criteria

Other skills for the same job

different authors, same section of the catalogue
Writing Skills
by ZhanlinCui
×4

Use when creating new skills, editing existing skills, or verifying skills work before deployment

26k tokens scripts
Prompt Library
by ComeOnOliver
×2

Curated collection of high-quality prompts for various use cases. Includes role-based prompts, task-specific templates, and prompt refinement techniques. Use when user needs prompt templates, role-play prompts, or ready-to-use prompt examples for coding, writing, analysis, or creative tasks.

4k tokens
Edge Strategy Designer
by BaggaT236
×1

Convert abstract edge concepts into strategy draft variants and optional exportable ticket YAMLs for edge-candidate-agent export/validation.

7k tokens scripts
Langgraph Fundamentals
by langchain-ai
vendor ×1

INVOKE THIS SKILL when writing ANY LangGraph code. Covers StateGraph, state schemas, nodes, edges, Command, Send, invoke, streaming, and error handling.

6k tokens
Harness Model Protocol
by ComeOnOliver
×1

Analyze the protocol layer between agent harness and LLM model. Use when (1) understanding message wire formats and API contracts, (2) examining tool call encoding/decoding mechanisms, (3) evaluating streaming protocols and partial response handling, (4) identifying agentic chat primitives (system prompts, scratchpads, interrupts), (5) comparing multi-provider abstraction strategies, or (6) understanding how frameworks translate between native LLM APIs and internal representations.

12k tokens
Skill I18n
by ComeOnOliver
×1

Translate SKILL.md and README.md files into multiple languages for sharing skills internationally

11k tokens
Agent Setup Maintenance
by langfuse
vendor

| Shared workflow for editing Langfuse's repo-owned agent setup under `.agents/`. Use when changing AGENTS files, shared skills, `.agents/config.json`, generated shim behavior, provider discovery paths, or install-time agent sync.

769 tokens
Datalineage Summary
by google
vendor

>- Summarizes Google Cloud Data Lineage graphs to help users debug data quality issues and understand data provenance for BQ/GCS. Use when summarizing upstream and downstream data flows, and presenting complex lineage data as an intuitive Markdown report. Don't use for generic BigQuery queries, editing lineage relationships, or downstream deprecation. Don't use for downstream blast-radius impact analysis (use datalineage-bigquery-asset-impact-analysis skill instead).

2k tokens

How to use it

Copy the folder

Take robertguss/writing-orchestration from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.