skills/dispute-letter/SKILL.md
Write a letter to dispute an incorrect charge, bill, or record. Use when asked to dispute a credit-card charge, contest a bill or invoice, challenge a credit-report error, or formally dispute a fee. Produces a clear dispute letter — what's being disputed, why it's wrong, the evidence, and the correction requested — in the firm, paper-trail tone these situations need.
npx skillsauth add mohitagw15856/pm-claude-skills dispute-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.
Disputes are won on a clear paper trail: state precisely what's wrong, attach the evidence, and request a specific correction in writing. This skill writes that letter so it's easy for the other side to verify and fix — and so you have a dated record if it escalates.
Note: this is a drafting aid, not legal or financial advice. Deadlines and rights vary by jurisdiction and provider (e.g. billing-error and credit-reporting rules); confirm the process and time limits with the provider or a qualified advisor, and keep copies of everything.
Given "dispute a $90 charge I didn't authorise", write the full letter anyway — structure the dispute and bracket the specifics (account/reference numbers, dates, amounts) to fill in. Note where supporting evidence should be attached. Never withhold the letter for missing detail.
Ask for these only if they aren't already provided (else bracket to fill in):
Provide a short version for an online dispute form, and notes on documents to attach and any deadline to confirm.
Consumer dispute practice — precise identification, evidence-backed reasoning, a specific requested correction, and a documented paper trail.
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.