skills/public-comment/SKILL.md
Draft a persuasive public comment on a proposed rule, regulation, or plan. Use when asked to comment on a rulemaking, respond to a consultation, submit feedback on a proposed regulation, or write a comment to an agency. Produces a structured comment: your position, specific evidence-based arguments tied to the proposal's text, suggested edits, and the impact — the kind agencies must consider on the record.
npx skillsauth add mohitagw15856/pm-claude-skills public-commentInstall 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.
Agencies must review and respond to substantive comments — but only substantive ones move the needle. A comment that cites the specific provision, brings evidence, and proposes concrete alternative language carries far more weight than "I support/oppose this." This skill drafts that substantive comment.
Ask for these only if they aren't already provided:
Re / docket line — the proposal and docket/reference number, and your position in one line.
Who I am & my interest — brief; establishes standing and why your input is relevant.
Summary of position — what you support/oppose/want changed, up front.
Substantive comments — the core. Each point:
Number them so the agency can respond point by point.
Impact — the concrete effect (cost, burden, benefit, unintended consequence) on you/your community — this is what agencies weigh.
Conclusion & request — restate the specific action requested; offer to provide more info.
Notice-and-comment rulemaking practice (substantive, provision-specific, evidence-based comments with proposed alternatives).
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.