Agent skill · Workflow & Productivity

public-comment

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.

mohitagw158561,255★ · 1 repos on radarProfile →
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill public-comment --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 3 KB
Bundled scripts: none
Path: skills/public-comment/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Public Comment Skill 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. ## Required Inputs Ask for these only if they aren't already provided: - **The proposal** — the rule/regulation/plan, ideally the specific sections or docket number. - **Your position & interest** — support, oppose, or amend; and who you are (individual, business, org — it affects standing/weight). - **The substance** — your reasons, and any data, expertise, or real-world impact you can cite. - **Desired outcome** — the specific change you want (kill it, delay it, amend a provision). ## Output Format ### Public comment: [rule / docket] **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: - **Cites the specif

What's inside
Steps it walks through
  1. Required Inputs
  2. Output Format
  3. Public comment: [rule / docket]
  4. Quality Checks
  5. Anti-Patterns
  6. Based On
More from pm-claude-skills
All skills →
About this skill
What does the public-comment skill do?

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.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill public-comment --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going