$ loading_
Track open NPRM comment periods, decisions, and upcoming filing deadlines.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "comments" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/claude-for-legal/main/regulatory-legal/skills/comments/SKILL.md 2. Save it as ~/.claude/skills/comments/SKILL.md 3. Reload skills and tell me it's ready
List all currently open NPRM comment periods and group them by time to deadline, prioritizing undecided items due within 14 days.
A list of open comment periods with ID, regulation name, deadline, days left, decision status, and owner.
Log a decision for CMT-001: not-filing. Rationale: the rule does not apply to our business scope.
The tracker is updated with the decision and a brief rationale for that item.
Log a decision for CMT-014: filing. Rationale: we plan to file comments on Section 3, and set an internal review reminder.
The item is updated to filing, with a prompt or reminder for internal review before the official deadline.
When a team is tracking multiple NPRMs, it helps centralize open comment periods and highlight undecided items nearing deadline to reduce the risk of missing them.
When counsel or the owner decides to file, not file, or waive, the skill records the decision and rationale in the tracker for later review and team visibility.
For newly detected NPRMs or items still undecided near the deadline, it can work with Slack notifications to alert the owner, especially at 14-day and 3-day thresholds.
The README explains that /comments is used to surface open NPRM comment periods, group them by urgency, and record filing, not-filing, or waived decisions with --decide. It reads local tracker and owner configuration, can send Slack reminders for new or still-undecided items near deadlines, and prompts for an internal review reminder when a filing decision is made. It also highlights legal review considerations before submission-related drafting.
NPRMs have deadlines. The decision to file a comment or not is an attorney call — but the deadline disappearing without a logged decision is the risk. This skill surfaces open comment periods and records decisions.
~/.claude/plugins/config/claude-for-legal/regulatory-legal/comment-tracker.yaml → all tracked NPRMs and their status.
~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md → default comment decision owner.
## Comment Period Tracker — [date]
### ⏰ Deadline in <14 days
| ID | Regulation | Deadline | Days left | Decision | Owner |
|---|---|---|---|---|---|
| CMT-001 | [name] | [date] | [N] | Undecided | [owner] |
### 🟡 Open (>14 days)
[same table]
### Recently decided
| ID | Regulation | Decision | Rationale |
|---|---|---|---|
| CMT-002 | [name] | Not filing | [reason] |
---
**Total open:** [N] **Undecided with deadline <30 days:** [N]
/regulatory-legal:comments --decide CMT-001
Decision: [filing / not-filing / waived]
Rationale: "[brief — e.g., 'Rule doesn't apply to our model' or 'Filing comment on Section 3']"
Updates tracker. If decision is "filing": prompt for filing deadline reminder (comment deadline minus 5 business days for internal review).
On first detection of an NPRM (populated by reg-feed-watcher): Slack DM to
comment decision owner if Slack MCP is configured and owner_slack is set.
Reminder at 14 days before deadline if decision is still "undecided." Reminder at 3 days before deadline if still undecided — elevated urgency.
Before logging a decision as "filing" — and always before producing a comment letter or regulator-response draft for submission: Read ## Who's using this in ~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md. If the Role is Non-lawyer:
Submitting a comment or response to a regulator has legal consequences. It's a public statement of the company's position, it's on the record in the rulemaking or enforcement matter, and positions taken here bind the company and can be used against it in subsequent proceedings. Have you reviewed this with an attorney? If yes, proceed. If no, here's a brief to bring to them:
- The rulemaking or inquiry (regulator, docket, deadline)
- What the proposed comment/response says and on what sections
- Open questions and what's unresolved
- What could go wrong (adverse admissions, inconsistent prior positions, coordination-of-comment concerns with trade associations)
- What to ask the attorney (should we file at all; should we file jointly through a trade group; are there positions we should not take)
If you need to find a lawyer: your professional regulator's referral service is the fastest starting point (state bar in the US; SRA/Bar Standards Board in England & Wales; Law Society in Scotland/NI/Ireland/Canada/Australia; or your jurisdiction's equivalent).
Do not log a "filing" decision or produce a submission-ready draft past this gate without an explicit yes. Tracking views, deadline reminders, and "not-filing / waived" decisions do not require the gate.
/regulatory-legal:reg-feed-watcher.The
comment-decisiongap_typesemantics, the per-send Slack confirmation rule, and the comment-tracker.yaml schema live in the gap-surfacer reference skill — load it before doing substantive work.
It is used to review open NPRM comment periods, track deadlines, and log decisions such as filing, not-filing, or waived. Its main purpose is to avoid missing a deadline without a recorded decision.
The docs indicate it reads tracked NPRMs and statuses from comment-tracker.yaml, plus the default decision owner from CLAUDE.md. If Slack MCP is configured and owner_slack is set, it can also send reminders.
The tracker is updated and prompts for an internal review reminder, typically five business days before the comment deadline. The docs also note legal-review checks before producing materials intended for submission.
Search watched skill registries, preview matches, and inspect SKILL.md before installing.
Draft DMCA notices, triage incoming claims, and prepare counter-notice drafts.
Standardize new matter intake and generate matter files plus a structured log.
Compare proposed handbook edits and identify cross-reference and state supplement impacts.
Review offer letters and restrictive covenants with jurisdiction-specific hiring checks.
Manage matter workspaces to separate, switch, and archive client contexts.
Log and retrieve decisions with provenance, supersession, and audit trails.
Create stakeholder updates tailored to audience, cadence, and communication goals.
Open protocol for recording and retrieving regulatory letters and related instruments.
Argue decisions, record reasons, and return finished files.
Evaluate code review feedback rigorously before deciding whether to implement it.
Draft common legal responses from templates with built-in escalation checks.