skills/case-for-support/SKILL.md
Write a fundraising case for support that makes donors want to give. Use when asked to write a case for support, a fundraising case statement, a major-gift or campaign case, or the core argument for a donation appeal. Produces a persuasive case — the need, your solution and why you, the impact a gift makes, specific funding opportunities with amounts, and a clear ask — donor-centred, not org-centred.
npx skillsauth add mohitagw15856/pm-claude-skills case-for-supportInstall 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.
The case for support is the spine of all your fundraising — every appeal, proposal, and pitch draws from it. It works when it's donor-centred: not "help us, we need money" but "here's a problem you can solve, and here's exactly what your gift makes possible." This skill writes that case — urgent, evidence-backed, and built around the donor as the hero.
Given "write a case for support for our literacy program", produce the full case anyway — build the argument from the mission described, and mark invented evidence or figures as (example — replace with real data). Never fabricate statistics as real; never withhold for missing detail.
Ask for these only if they aren't already provided (else infer and label for replacement):
| Gift | What it funds | Impact | |---|---|---| | $50 | … | … | | $500 | … | … | | $5,000 | … | … |
Mark invented figures/evidence as (example — replace with real data).
Fundraising practice — donor-centred case construction (need, solution, credibility, impact, urgency, ask) with gift-level impact framing.
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.