plugins/pm-health/skills/prior-authorization-letter/SKILL.md
Write a persuasive prior-authorization / medical-necessity letter to an insurer. Use when asked to write a prior authorization letter, a letter of medical necessity, or to appeal a denied treatment/medication/procedure. Produces a structured letter — patient and request, clinical justification tied to guidelines, treatments tried, and the specific approval asked for — ready for clinician review and signature.
npx skillsauth add mohitagw15856/pm-claude-skills prior-authorization-letterInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
A prior-auth or medical-necessity letter succeeds when it connects this patient's clinical facts to the insurer's coverage criteria — clearly, with evidence, and with the exact request spelled out. This skill structures that argument so the reviewer can approve it quickly, and so an appeal addresses the stated denial reason head-on.
Clinical-safety note: this is a documentation aid, not medical advice. The clinical justification must reflect the treating clinician's judgement and the patient's actual record; the clinician must review, verify, and sign before submission. Do not invent diagnoses, codes, history, or evidence.
Given the treatment and a diagnosis, produce the full letter anyway — structure the argument and insert the standard elements, marking patient-specific facts (codes, dates, prior treatments) to be confirmed rather than inventing them. For an appeal, infer and directly rebut the likely denial reason if it's stated. Never fabricate clinical history or citations.
Ask for these only if they aren't already provided (else mark to confirm):
For an appeal, add a section that quotes the denial reason and rebuts it specifically.
Close with a list of facts to confirm before sending and a clinician-sign-off reminder.
Utilization-management correspondence practice — medical-necessity argumentation tied to coverage criteria, step-therapy documentation, and targeted appeals.
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.