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, sub…
它会碰到什么
这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。
技能内容
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 specific provision (section/paragraph) it addresses,
- Makes the argument with evidence (data, expertise, precedent, real-world consequence),
- Proposes a concrete fix — suggested alternative language or a specific change, not just objection.
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.
Quality Checks
- [ ] Each point cites the specific provision it addresses and is on-topic for the proposal
- [ ] Arguments are backed by evidence (data, expertise, precedent, concrete impact) — not just opinion
- [ ] It proposes concrete alternative language/changes, not only objections
- [ ] The real-world impact is made specific
- [ ] Position and the exact requested action are stated clearly up front and at the end
Anti-Patterns
- [ ] Do not submit a bare "I support/oppose" — agencies weigh substance, not vote counts
- [ ] Do not argue in generalities — tie every point to the proposal's actual text
- [ ] Do not just object — propose the specific alternative you want instead
- [ ] Do not omit evidence — unsupported assertions are easy to dismiss on the record
- [ ] Do not go off-topic — comments outside the proposal's scope carry no weight
Based On
Notice-and-comment rulemaking practice (substantive, provision-specific, evidence-based comments with proposed alternatives).
想直接用这个技能?
本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。
它属于哪个仓库
exports/openclaw/public-comment/SKILL.md同一个仓库里的其他技能
同名技能的其他版本
有 3 个不同仓库或目录里都有叫 public-comment 的技能。它们内容并不相同,别混用:
- mohitagw15856/pm-claude-skills — Draft a persuasive public comment on a proposed rule, regulation, or plan. Use when asked
- mohitagw15856/pm-claude-skills — Draft a persuasive public comment on a proposed rule, regulation, or plan. Use when asked