Stats
Actions
Tags
From content-writing
Use when the user wants to run a multi-stage sequential editorial refinement on a piece of writing — typo cleanup → UK English standardisation → flow & polish → headings → proofreading/fact-checking → source/citation insertion → SEO polish. Each stage is a focused agent prompt; output of stage N is input of stage N+1. Triggers include "polish this draft", "run the editing pipeline", "writing squad", "iterative editing", "multi-pass refinement".
How this skill is triggered — by the user, by Claude, or both
Slash command
/content-writing:editorial-pipelineThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Apply a sequence of focused editorial refinements to a draft, passing output from each stage as input to the next. The pipeline reads 7 agent prompts from `./agents/` and applies cross-cutting constraints from `./rules/` to preserve author voice, maintain detail level, and track changes.
Apply a sequence of focused editorial refinements to a draft, passing output from each stage as input to the next. The pipeline reads 7 agent prompts from ./agents/ and applies cross-cutting constraints from ./rules/ to preserve author voice, maintain detail level, and track changes.
/content-writing:new-workspace)blog-post-v1, opinion-piece-draft)rules/author-voice.md to preserve tone and registerRead the rules. Load and parse rules/author-voice.md, rules/detail.md, rules/folder-structure.md, and rules/version-control.md. These constraints apply to every stage.
Set up working directory. Create <workspace>/editorial-pipeline/<draft-name>/ under the user's workspace data directory:
${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/content-writing/<workspace>/editorial-pipeline/<draft-name>/
Write the original draft to 00_original.md in this directory.
Run each stage in order (or user-specified order):
agents/basic-typo-reviewer.md (stage 1)agents/uk-english-standardiser.md (stage 2)agents/flow-and-polish.md (stage 3)agents/headings.md (stage 4)agents/proofreader.md (stage 5)agents/add-sources.md (stage 6)agents/seo-reviewer.md (stage 7)Apply each agent inline. For each stage:
<stage-number>_<stage-name>.md (e.g., 01_basic-typo-reviewer.md, 02_uk-english-standardiser.md)./rules/ — especially author voice, detail preservation, and version-control comments if the rules specify themPresent progression to user. After each stage, summarize changes made and offer the user options: continue to next stage, skip the next stage, reorder, or stop.
Final output. Save the fully refined version to final.md in the same directory. Emit a summary of all changes across stages and the location of the working directory so the user can inspect any intermediate.
01_..., 02_..., etc.) written to the workspace editorial-pipeline subdirectoryfinal.md with the fully refined drafteditorial-pipeline/<draft-name>/npx claudepluginhub danielrosehill/claude-code-plugins --plugin content-writingCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.