From pm-journalism
Produces a risk assessment and operational plan for protecting a confidential journalistic source, covering threat modeling, secure communication, publication anonymization, and honest promises.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-journalism:source-protection-planThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A source who trusts you can be burned by a metadata field, a predictable meeting pattern, or a document only three people had. Protecting a source is operational, not just a promise. This skill maps how the source could realistically be identified and closes those channels — before, during, and after publication.
A source who trusts you can be burned by a metadata field, a predictable meeting pattern, or a document only three people had. Protecting a source is operational, not just a promise. This skill maps how the source could realistically be identified and closes those channels — before, during, and after publication.
Given the situation, produce the full plan — reason about the specific ways this source could be exposed given who they are and who wants to find them. Be honest about residual risk; do not over-promise anonymity you can't guarantee. This is defensive practice, not legal advice — recommend a media lawyer for legal exposure.
Ask for (if not provided, else infer and label):
Who is the adversary, what can they access (comms metadata, building logs, document distribution lists, timestamps), and the realistic ways this source could be identified — including the small-N problem ("only 5 people had this").
Safer practices: end-to-end encrypted channels, minimizing metadata, secure drop/transfer options, device hygiene, meeting tradecraft, and how records are stored (and what not to keep).
The redaction/anonymization plan for the piece: stripping document metadata, paraphrasing telltale phrasing, generalizing identifying details, withholding the small-N specifics, and timing that doesn't finger the source.
What to actually promise the source (and what you can't guarantee), how attribution will read, and what happens if you're legally compelled — communicated honestly up front.
The risks that remain after all mitigations, stated plainly, and the recommendation to involve a media lawyer.
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.