From pm-journalism
Pitches news or feature stories to editors with a specific angle, reporting plan, and format fit. Designed for reporters and freelancers writing query letters.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-journalism:story-pitchThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Editors kill most pitches in ten seconds because they can't find the story — just a topic. A topic is "AI in schools." A story is "the district that banned AI, then quietly reversed after test scores dropped." This skill sharpens a topic into an angle an editor can say yes to, and shows you can actually report it.
Editors kill most pitches in ten seconds because they can't find the story — just a topic. A topic is "AI in schools." A story is "the district that banned AI, then quietly reversed after test scores dropped." This skill sharpens a topic into an angle an editor can say yes to, and shows you can actually report it.
Given the topic or reporting lead, write the full pitch — find the specific angle and the "why now," and propose the reporting. If the idea is still a topic, say so and offer 2–3 angle options.
Ask for (if not provided, else infer and label):
The specific story, not the topic — the tension, the turn, or the character at its center.
3–4 tight paragraphs:
Proposed format (news, feature, investigation, Q&A), rough length, and section — matched to the outlet. A line on why you (access, expertise, track record).
A one-line note on timing and how you'll follow up if you don't hear back.
npx claudepluginhub mohitagw15856/pm-claude-skills --plugin pm-journalismGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
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.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.