Menu

Individual skill

public-comment

0upvotes

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.

skills/public-comment/SKILL.md

Read pinned source

Source commit e0009a385c480fb0b5687e7412df67c7c64f7cee

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,541
Repository last updated
Nov 11, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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).
Back to top