plugins/pm-gov/skills/foia-request/SKILL.md
Draft a public-records request (FOIA / FOI / state open-records) that's specific enough to get records and hard to deny. Use when asked to write a FOIA request, records request, or freedom-of-information request to a government body. Produces a properly-scoped request: the records sought, date range and format, fee-waiver and expedited-processing asks where applicable, and citations to the governing statute.
npx skillsauth add mohitagw15856/pm-claude-skills foia-requestInstall 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.
Public-records requests fail when they're too vague ("all documents about X") — agencies reject or stall them. A good request is specific: named record types, a date range, the right custodian, and the statutory hooks for fees and timing. This skill drafts a request that's easy to fulfil and hard to deny.
Educational drafting aid. Public-records laws vary by jurisdiction (US federal FOIA, US state open-records laws, UK/EU FOI, etc.) — confirm the governing statute, agency, and deadlines for the specific case.
Ask for these only if they aren't already provided:
To: the agency's FOIA/records officer (address/portal). Date.
1. Statement of request — "Under [the governing statute, e.g. the Freedom of Information Act, 5 U.S.C. § 552 / the [State] Public Records Act], I request the following records:"
2. Records sought — a numbered, specific list. For each: record type, subject, custodian if known, and the date range. Specific beats broad — narrow, well-defined items get filled; sweeping ones get denied.
3. Format & delivery — preferred format (electronic/native), and delivery method.
4. Fees — a fee category statement and, where applicable, a fee-waiver request (e.g. disclosure is in the public interest / non-commercial) with brief justification, plus a cap ("please contact me before incurring fees over $X").
5. Expedited processing (if applicable) — the basis (urgency, media, imminent public need).
6. Response-time note — cite the statutory response deadline and request acknowledgment.
7. Contact & signature.
FOIA / public-records practice (specificity, statutory citation, fee-waiver & expedited-processing provisions).
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.