From pm-decoders
Decode an insurance claim denial letter — what the cited reason actually means, whether it's commonly overturnable, and the appeal letter that answers it point by point. Use when someone asks 'my insurance claim was denied what do I do', 'decode this denial letter', 'can I appeal this denial', or 'write my insurance appeal'. Produces the denial decode with overturn-likelihood framing, the evidence checklist, the point-by-point appeal letter, and the escalation ladder past the insurer.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-decoders:claim-denial-decoderThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Denial letters are written to end conversations; appeals exist because they often shouldn't. A meaningful share of denials — especially coding errors, "not medically necessary," and documentation gaps — get overturned when someone answers the *stated reason* with evidence instead of outrage. This skill decodes what the denial actually claims, matches each claim to the evidence that answers it, ...
Denial letters are written to end conversations; appeals exist because they often shouldn't. A meaningful share of denials — especially coding errors, "not medically necessary," and documentation gaps — get overturned when someone answers the stated reason with evidence instead of outrage. This skill decodes what the denial actually claims, matches each claim to the evidence that answers it, and writes the appeal that reads like it was drafted by someone who will escalate.
Ask for these only if they aren't already provided:
Read the denial's cited reason and classify it:
The appeal's structure is always the same: restate the denial's exact words → answer that reason specifically with attached evidence → quote the policy language that supports coverage → request the specific action → name the deadline you're inside and the next step you'll take if unanswered. Never argue reasons the letter didn't cite — it teaches them new denial grounds.
1. The decode — the cited reason in plain English, its type, and honest appeal-odds framing (answerable / contestable / likely solid).
2. Evidence checklist
| Denial assertion | Evidence that answers it | Where to get it | Status |
|---|
3. The appeal letter — full text, ready to send: claim details header · "your letter of [date] states: '[quoted]'" · point-by-point response with enclosure references · policy language quoted · the specific request · sent-by-trackable-means note.
4. Escalation ladder — internal appeal level(s) with deadlines → external/independent review rights (jurisdiction- and plan-dependent — check the denial letter's own rights section) → regulator complaint → the demand-letter/counsel threshold.
5. Deadlines box — every date that matters, from the letter and the policy.
End the artifact with, verbatim: "This is a plain-language reading, not legal/financial advice — laws vary by jurisdiction; confirm anything load-bearing with a qualified professional."
Policyholder appeal practice — denial-reason triage, evidence matching, point-by-point appeal drafting, escalation sequencing.
npx claudepluginhub mohitagw15856/pm-claude-skills --plugin pm-decodersGuides 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.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.