From pm-journalism
Runs a claim-by-claim fact-check on drafts before publication. Extracts assertions, assigns verification status, flags high-risk claims (numbers, quotes, names, legal), and suggests fixes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-journalism:fact-check-passThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Everything in a published piece is a claim someone can be wrong about — a date, a number, a quote, an implication. This skill does what a good fact-checker does: it pulls every checkable assertion out of the prose, verifies each against a source, and stops the high-risk ones (stats, quotes, anything defamatory) from going out on a "probably right."
Everything in a published piece is a claim someone can be wrong about — a date, a number, a quote, an implication. This skill does what a good fact-checker does: it pulls every checkable assertion out of the prose, verifies each against a source, and stops the high-risk ones (stats, quotes, anything defamatory) from going out on a "probably right."
Given the draft, produce the claim inventory and status — check what you can against the provided/known sources, and for anything you can't verify, mark it clearly rather than guessing. Never assert a fact is confirmed without a basis.
Ask for (if not provided, else infer and label):
Every checkable assertion extracted:
| # | Claim (as written) | Type | Status | Source / basis | Fix |
|---|
The claims that must not publish unverified — statistics, direct quotes and their attribution, named individuals (especially any allegation), superlatives ("first," "only," "largest"), and anything potentially defamatory. Each with what's needed to clear it.
For every 🔴/⚠️: the correction, a hedge to the supportable version, or "cut it." For 🟡: the source to obtain.
What's still open before this can publish, and a note that quotes should be confirmed with the speaker/transcript and legal review sought for anything defamatory.
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.