Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From pitch
Runs a pitch through a single managing-editor read instead of the full page-one-meeting panel: one Socratic verdict (green light / revise / kill), no cast, no debate, no dissent round. Trigger on "sharpen this pitch", "sharpen my pitch", "quick editorial read", "give me an editor's take", "run this by an editor", or /sharpen. For a full multi-persona debate instead, use the page-one-meeting skill.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pitch:sharpenThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
One editor, one pass. Take whatever pitch material the user gives you — pasted text, a doc,
One editor, one pass. Take whatever pitch material the user gives you — pasted text, a doc,
a raw idea — and launch the managing-editor agent (Agent tool, subagent_type: managing-editor) with it verbatim, plus the target outlet if the user named one.
Relay the agent's verdict and questions back directly. Don't summarize or soften its voice, and don't write anything to disk — this is a conversational read, not an artifact.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
npx claudepluginhub benjaminjackson/writing-skills --plugin pitch