plugins/pm-lifeadmin/skills/insurance-claim/SKILL.md
Write a clear insurance claim letter or appeal that supports a payout. Use when asked to write an insurance claim, file a claim letter, document a loss for insurance, or appeal a denied claim. Produces a structured claim — policy and incident details, the documented loss, the amount claimed, and the evidence — or an appeal that rebuts the denial reason, ready to submit.
npx skillsauth add mohitagw15856/pm-claude-skills insurance-claimInstall 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.
Claims get paid faster when they're complete and well-documented: the right policy and incident details, an itemised loss, and the evidence attached. This skill writes that letter — or, for a denial, an appeal that addresses the insurer's stated reason directly — so the adjuster has everything they need to say yes.
Note: this is a drafting aid, not legal, financial, or insurance advice, and it does not guarantee a payout. Coverage, deadlines, and procedures depend on your policy and jurisdiction — read your policy, meet the insurer's deadlines, and consult a qualified advisor for complex or high-value claims. Never misrepresent facts; insurance fraud is a crime.
Given "file a claim for water damage from a burst pipe", write the full claim anyway — structure it and bracket the specifics (policy number, dates, amounts, itemised losses) to fill in, and list the evidence to attach. Never withhold for missing detail; never inflate or invent losses.
Ask for these only if they aren't already provided (else bracket to fill in):
For an appeal, add a section that quotes the denial reason and rebuts it with the policy wording and evidence.
Provide a document checklist and notes on policy deadlines to confirm.
Insurance-claim practice — complete incident documentation, itemised evidenced loss, and denial-specific appeals grounded in policy wording.
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.