ai-inventory
EU AI Act per-system inventory — track each AI system's role (provider, deployer, importer,…
Review open NPRM comment periods, log decisions, track deadlines. Use when an NPRM has a comment window open and you need to surface deadlines, decide whether to file, or record a filing / not-filing / waived decision (--decide CMT-ID).
$ npx -y skills add anthropics/claude-for-legal --skill comments --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/commentsContext preview
The summary Claude sees to decide when to auto-load this skill.
Review open NPRM comment periods, log decisions, track deadlines. Use when an NPRM has a comment window open and you need to surface deadlines, decide whether to file, or record a filing / not-filing / waived decision (--decide CMT-ID).
name: comments description: Review open NPRM comment periods, log decisions, track deadlines. Use when an NPRM has a comment window open and you need to surface deadlines, decide whether to file, or record a filing / not-filing / waived decision (--decide CMT-ID). argument-hint: "[optional: --decide CMT-ID]"
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.
---
is done — follow the rulemaking through `/regulatory-legal:reg-feed-watcher`.
> The `comment-decision` `gap_type` semantics, 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.
Reference agents, skills, and data connectors for the legal workflows we see most — in-house commercial, privacy, product, corporate, employment, litigation, regulatory, AI governance, IP, and the learning side of the practice (law school clinics and
EU AI Act per-system inventory — track each AI system's role (provider, deployer, importer,…
Run an AI impact assessment — structured intake, risk analysis, regulatory classification per…
Run the cold-start interview — learns your AI governance practice and writes…
Guided customization of your AI governance practice profile — change one thing without…
Manage matter workspaces — new, list, switch, close, or detach (practice-level).…
Keep the AI policy current with practice — weekly sweep of saved AIAs, triage results, and…