New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Regulatory Feed Watcher

by anthropics in anthropics/claude-for-legal

Pulls the regulatory feeds on your watchlist, drops items under your materiality threshold and reports what is new since the last check, grouped by tier.

OfficialApache-2.0Auto-check passedLegal & Compliance

Install Regulatory Feed Watcher

skills CLI
$ npx skills add anthropics/claude-for-legal --skill reg-feed-watcher -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install anthropics/claude-for-legal reg-feed-watcher --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/anthropics/claude-for-legal.git skills-src && mkdir -p .claude/skills && cp -r skills-src/regulatory-legal/skills/reg-feed-watcher .claude/skills/reg-feed-watcher && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
reg-feed-watcher
GitHub stars
9.6k
Used in
1 other repo
Token cost
~3.7k tokens
SKILL.md length
1,701 words
Files
2 (incl. references)
Skills in repo
147
Repo updated
First seen
Licence
Apache-2.0

At a glance

Pulls the regulatory feeds on your watchlist, drops items under your materiality threshold and reports what is new since the last check, grouped by tier.

  • Works in 4 steps: Coverage check (before pulling) → Pull → Classify → …
  • Asking what is new in the regulatory feeds you track
  • SKILL.md covers Purpose, Load context, Workflow and Output, plus 4 more sections
  • Calls pandoc; reaches federalregister.gov

What it does

The agent loads the `regulatory-legal` plugin's `CLAUDE.md` for the watchlist, materiality threshold, feed configuration and optional digest path. Before pulling, it compares the configured feeds with `references/source-catalog.md`, a curated list of RSS, JSON and HTML sources across US federal, US state, EU and UK, international and aggregator categories, and notes a coverage gap once at the top of the digest without repeating it.

It then pulls every configured tier. Tier 1 free feeds are always active, for example the Federal Register API queried by agency, date range since the last check and document type, returning type, title, abstract, effective date, comment deadline and citation. Tiers 2 and 3 are used only if configured. The filter is the point: output lists what remains after materiality screening, categorized by tier. It can also run from a scheduled agent or classify a pasted development.

When your agent uses it

  • Asking what is new in the regulatory feeds you track
  • Producing a scheduled digest filtered by materiality
  • Classifying a pasted regulatory development against the previous check
  • Spotting gaps between your watchlist and configured sources

Example prompts

  • “Check the feeds and tell me what's new since last time.”
  • “Give me a regulatory update with only the items above my materiality threshold.”
  • “Here is a new agency notice I pasted. Classify it and say how it differs from what we track.”
  • “Does my watchlist cover EU regulators well enough given the feeds I set up?”

Requirements

  • The regulatory-legal plugin configuration in `CLAUDE.md` with a watchlist and materiality threshold
  • Network access to the configured feeds, such as the Federal Register API

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Coverage check (before pulling)
  2. Pull
  3. Classify
  4. Enrich

What it can do on your machine

Read from SKILL.md and the folder at commit 4a6c651. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pandoc

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • federalregister.gov

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Regulatory Feed Watcher loads about 3.7k tokens when it runs, and up to ~7.5k if it reads all its reference files. Until then it costs about 81 tokens; SKILL.md has 1,701 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~81
When it runs · the whole SKILL.md, loaded when a task matches
~3.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from anthropics/claude-for-legal at commit 4a6c651, republished under its Apache-2.0 licence (© anthropics). 1,701 words, ~3,735 tokens.

Download SKILL.mdSave it as .claude/skills/reg-feed-watcher/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
reg-feed-watcher
description
Check regulatory feeds now and report what's new since the last check, filtered by your materiality threshold. Use when the user says "check the feeds", "what's new", "regulatory update", when running from the scheduled agent, or when manually pasting a regulatory development for classification and diff.
argument-hint
[optional: --since DATE]

/reg-feed-watcher

  1. Load ~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md → watchlist, materiality threshold, feed config.
  2. Use the workflow below.
  3. Pull each feed. Filter by materiality.
  4. Output: what's new, categorized by materiality tier.

Purpose

Pull the feeds. Filter by materiality. Output what's left. The filter is the value — unfiltered feeds are noise.

Load context

~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md → watchlist, materiality threshold, feed configuration, digest output path (if set).

references/source-catalog.md (in this skill's directory) → curated catalog of RSS/JSON/HTML sources across US federal, US state, EU/UK, international, and secondary/aggregator categories. Use when configuring new sources or when the user's watchlist has coverage gaps (see Step 0).

Workflow

Step 0: Coverage check (before pulling)

Before running the pull, compare the watchlist + feed configuration in CLAUDE.md against references/source-catalog.md:

  • Which categories (US federal / US state / EU-UK / international) does the user care about per their watchlist?
  • Which of those categories have zero or very few sources configured?

If there's an obvious gap — e.g., user watches "EU regulators" in the watchlist but has only edpb.europa.eu configured in feeds, missing ICO, CNIL, DPC Ireland — surface it once at the top of the digest:

Coverage gap noticed: Your watchlist includes [category], but only [N] feeds are configured. The source catalog lists [X] options in this category (e.g., [top 2-3 names]). Want me to suggest additions? Run /regulatory-legal:cold-start-interview --redo to update, or edit ~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md directly.

Don't nag the same gap repeatedly — if the user has explicitly said "skip state AGs for now," respect that. Note state in CLAUDE.md so it sticks.

Step 1: Pull

Pull from all configured feed tiers. Every installation has Tier 1. Tiers 2 and 3 are additive — use them if configured, skip if not.

Tier 1 — Free feeds (always active)

For each regulator in the watchlist:

  • Federal Register API (https://www.federalregister.gov/api/v1/documents) — query by agency slug, date range (since last check), document type. Returns structured data: document type, title, abstract, effective date, comment deadline (for NPRMs), and citation. Covers all US federal agencies.
  • Direct regulator RSS — fetch and parse any RSS URLs in ~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md feed configuration (SEC, FTC, CFPB, state agencies, EU DPAs, etc.).

Agency slug reference for common watchlist regulators:

RegulatorAPI slug
FTCfederal-trade-commission
SECsecurities-and-exchange-commission
CFPBconsumer-financial-protection-bureau
CPPA (CA)RSS only — cppa.ca.gov/feed
DOLlabor-department
HHShealth-and-human-services-department
FCCfederal-communications-commission

For any regulator not in this list: check federalregister.gov/agencies for the correct slug, or fall back to direct RSS.

Tier 2 — Paid feeds (if configured)

  • Paid regulatory feed MCP: Query for updates since last check date, filtered to watchlist regulators.
  • CourtListener MCP: Same.

De-duplicate across tiers — the same document may appear in multiple sources. Prefer the richest source for the enriched output.

No silent supplement. If the feed pull returns few or no results for a regulator in the watchlist, report what was found and stop. Do NOT fill the gap from web search or model knowledge without asking. Say: "The feed check returned [N] items from [regulators hit]. Coverage appears thin for [regulator / topic]. Options: (1) broaden the date window, (2) try a different feed or MCP, (3) search the web — results will be tagged [web search — verify] and should be checked against the issuing authority's website before relying, or (4) stop here. Which would you like?" A lawyer decides whether to accept lower-confidence sources; Claude does not decide for them.

Source attribution. Tag every citation and regulatory item with where it came from: [Federal Register], [<regulator> RSS], [CourtListener], or the specific MCP tool name for items retrieved via connector; [web search — verify] for items from web search; [model knowledge — verify] for items surfaced from the model's training data; [user provided] for manually-pasted items. Items tagged verify carry higher fabrication risk than tool-retrieved items and should be checked first. Never strip or collapse the tags — they are the user's fastest signal about which citations to verify.

Secondary sources. Some catalog entries (IAPP, FPF, Hogan Lovells, Covington, Lexology, JD Supra, Artificial Lawyer, LawSites, and similar commentators/aggregators) report on primary regulatory action but are not the primary source. Tag any item pulled from these feeds with [secondary source] in addition to the feed-name tag — e.g., [IAPP Daily Dashboard] [secondary source]. In the digest, when a secondary-source item describes a regulator action, add a note: "→ Trace to primary: [link to regulator site if known, otherwise 'find on <regulator>.gov before relying']." Do not classify a secondary-source item as "Always material" on its own strength — bump it down a tier until the primary source is located.

Tier 3 — Manual entry

If the user has pasted regulatory text or a summary rather than invoking from a scheduled feed check: treat the pasted content as a single item, skip to Step 2 for classification, and record source as "manual entry." No feed pull required. This path works regardless of subscription status.

Record the check timestamp after pulling. Next scheduled run pulls from here forward.

Step 2: Classify

Each item gets a materiality tier per ~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md:

Item typeMatch against threshold
Final ruleUsually "always material"
Proposed rule / NPRMUsually "review-worthy" — and always log comment deadline
ANPR (Advance Notice of Proposed Rulemaking)Review-worthy for strategy, not compliance — no imposed requirements yet, but signals direction and carries a real comment deadline. Log the comment deadline. Route to /regulatory-legal:policy-diff only as a pre-positioning analysis, not as a gap-closure diff.
RFI (Request for Information)Same as ANPR — pre-rule, no compliance obligation, but comment deadline is real and direction-signaling is the value.
Enforcement actionSector match → material; related-practice match → review-worthy; neither → FYI or skip
GuidanceReview-worthy
Speech / blog / statementFYI or skip per threshold
SettlementDepends — novel theory or big number → review-worthy; routine → skip

ANPR / RFI handling — specific. Pre-rule items are distinct from NPRMs in one important way: they don't change the law, but they do carry comment deadlines and they signal the regulator's direction. Treat them as a separate branch:

  • Do not classify an ANPR / RFI as "always material" — the compliance impact is zero until a rule issues.
  • Do classify as review-worthy if any of the issue areas in the notice touch the watchlist's always-material categories (e.g., an ANPR on open banking in a fintech watchlist).
  • Do log the comment deadline to ~/.claude/plugins/config/claude-for-legal/regulatory-legal/comment-tracker.yaml with item_type: ANPR or item_type: RFI so the downstream tracker can distinguish these from compliance gaps.
  • Do include in the digest entry a line that says explicitly: "Pre-rule. Comment deadline [date]. Route to /regulatory-legal:policy-diff only as a pre-positioning analysis (no compliance gap yet)." This primes the policy-diff skill to use its compressed pre-positioning branch rather than a full gap-closure diff.
  • Route to the comment-tracker, not the gap-tracker. Comment-decision items are not compliance gaps; they belong in the comment tracker, and gap-surfacer uses the comment-decision gap_type (or declines to ingest, if the team routes these separately).

NPRM comment deadline handling:

For every NPRM classified at any tier above "skip":

  • Extract comment deadline (Federal Register API returns this as structured data)
  • If comment tracking is enabled in ~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md: append to ~/.claude/plugins/config/claude-for-legal/regulatory-legal/comment-tracker.yaml with status "undecided" and the default comment decision owner from ~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md
  • Include comment deadline in the output entry
Show full SKILL.md (545 more words)Show less
Step 3: Enrich

For each item above FYI tier:

  • One-line summary (what changed)
  • Why it might matter here (the relevance hook — "this is about [practice you do]")
  • Link to source
  • Effective date or comment deadline if applicable

Don't summarize FYI items individually — just count them.

Output

The digest goes into the chat by default. Also write it to a shareable file whenever the output contains one or more items above FYI, unless the user's CLAUDE.md explicitly sets Digest output → chat only.

File output behavior:

  1. Look for Digest output path in ~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md. If set, write there. Default if unset: ~/regulatory-legal-digests/reg-digest-YYYY-MM-DD.md.
  2. Create parent directories if needed.
  3. Write the full digest as Markdown (same content as the chat output, including the work-product header, source tags, and the verify-citations footer).
  4. If a file already exists at the path for today, append a new section with a timestamped subheader rather than overwriting — the same day may see multiple runs (morning digest, ad-hoc check).
  5. After writing, tell the user: "Digest written to <path>. Share as-is, or convert to .docx with Pandoc: pandoc <path> -o <path>.docx."
  6. If the write fails (permission, missing directory the user didn't authorize creating, disk), fall back to chat-only output and say so — don't silently drop the file request.

Format on disk matches the chat format exactly (below). Markdown renders well in GitHub, Notion, Obsidian, Google Docs (via "Import as Markdown" or Pandoc), and most email clients.

markdown
[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]

## Regulatory Feed Check — [date]

**Period:** [last check] to [now]
**Feeds checked:** [list active tiers — e.g., "Federal Register API, FTC RSS, TR"]
**Items found:** [N] total

### Bottom line

[N gaps need action by [date] — top 3: X, Y, Z]

### 🔴 Always material

**[Regulator] — [Title]**
[One-line summary]. [Relevance hook]. Effective [date].
[Link]
→ Recommend: run policy-diff against [likely affected policy]

[repeat for each]

### 🟡 Review-worthy

**[Regulator] — [Title]**
[One-line]. [Relevance]. [Deadline if any].
[Link]

[NPRMs: include "💬 Comment deadline: [date] — decision pending" if comment tracking enabled]

[repeat]

### 📝 FYI

[N] items — [expandable list of titles + links, no summaries]

---

**Last check updated to:** [timestamp]
**Comment tracker:** [N] NPRMs with open comment decisions — run /regulatory-legal:comments to review

---

**Verify citations before relying on them.** Regulatory citations here were AI-generated and have not been checked against a primary source. Before acting on any rule, guidance, or enforcement action above, confirm it against Westlaw, your firm's research platform, or the issuing authority's website — check accuracy, effective date, and current status. AI-generated regulatory citations are sometimes fabricated, misquoted, or stale. Source tags on each item (e.g., `[Federal Register]`, `[web search — verify]`) show where the citation came from; `verify` tags carry higher fabrication risk and should be checked first.

Config-dependent fallbacks

This skill reads the watchlist, materiality threshold, and feed configuration from ~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md. When a required value is still [PLACEHOLDER] or empty, say so in the output — specifically, not generically:

  • Watchlist empty: stop and say "The watchlist in your configuration is empty. I can't pull feeds without knowing which regulators to watch. Run /regulatory-legal:cold-start-interview --redo or edit ~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md and add at least one regulator."
  • Materiality threshold empty: fall back to the default tiers and append: "This output used the default materiality tiers because your configuration doesn't have custom thresholds set. Tune them with /regulatory-legal:cold-start-interview --redo or by editing ~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md."
  • Feed configuration empty: run Federal Register API only and append: "This output used only the free Federal Register API because your configuration doesn't list direct RSS or paid feeds. Add feeds with /regulatory-legal:cold-start-interview --redo or by editing ~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md."

Say nothing about config when the relevant values are populated.

If nothing above FYI: "All quiet. [N] FYI items, nothing needing attention."

Handoff

  • To policy-diff: Any "always material" item with a likely policy impact → offer to run the diff.
  • To gap-surfacer: If a diff finds a gap → tracked.
  • To comment-tracker: Any NPRM classified above "skip" → comment deadline logged automatically if tracking is enabled.

Close with the next-steps decision tree

End with the next-steps decision tree per CLAUDE.md ## Outputs. Customize the options to what this skill just produced — the five default branches (draft the X, escalate, get more facts, watch and wait, something else) are a starting point, not a lock-in. The tree is the output; the lawyer picks.

What this skill does not do

  • Read every item in full. It classifies and enriches; deep reading is for the items that survive the filter.
  • Change the materiality threshold. If the filter is wrong, edit ~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md.
  • Require TR or CourtListener. Free feeds are the baseline; paid feeds add depth.

© anthropics, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in regulatory-legal/skills/reg-feed-watcher of anthropics/claude-for-legal.

  • SKILL.md
  • references/source-catalog.md

Open the folder on GitHubat commit 4a6c651

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in anthropics/claude-for-legal, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Regulatory Feed Watcher next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Regulatory Feed Watcher compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Regulatory Feed Watcher this skillanthropics/claude-for-legal9.6k1 repos~3.7kAutomated safety check: PassApache-2.0
HIPAA Pre-Deployment Compliance Checkmaziyarpanahi/openmed5.5k—~2kAutomated safety check: PassApache-2.0
Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance9431 repos~2.3kAutomated safety check: PassMIT
ISO Standards Readiness EvidenceK-Dense-AI/scientific-agent-skills48k1 repos~4.6kAutomated safety check: NotesMIT
Iso42001Sushegaad/Claude-Skills-Governance-Risk-and-Compliance9431 repos~3.7kAutomated safety check: PassMIT
Legal Compliance SearchSerein-81/financial_rag148—~1.6kAutomated safety check: NotesNone

Similar skills

  • HIPAA Pre-Deployment Compliance Check

    maziyarpanahi/openmed

    Walks a data pipeline against the HIPAA Privacy and Security Rule checklist and produces a gap report before it processes patient data.

    5.5k GitHub stars~2k tokensUpdated today
    Legal & ComplianceAuto-check passed

  • Hipaa Compliance

    Sushegaad/Claude-Skills-Governance-Risk-and-Compliance

    Expert HIPAA compliance assistant for healthcare and software contexts.

    943 GitHub starsUsed in 1 repo~2.3k tokens
    Legal & ComplianceAuto-check passed

  • ISO Standards Readiness Evidence

    K-Dense-AI/scientific-agent-skills

    Organizes scope, controlled documents, risk files and traceability into draft evidence for human review against ISO 13485, 14971, 17025 and 15189.

    48k GitHub starsUsed in 1 repo~4.6k tokens
    Legal & ComplianceAuto-check: notes

  • Iso42001

    Sushegaad/Claude-Skills-Governance-Risk-and-Compliance

    Expert ISO 42001 AI Management System (AIMS) compliance advisor.

    943 GitHub starsUsed in 1 repo~3.7k tokens
    Legal & ComplianceAuto-check passed

  • Legal Compliance Search

    Serein-81/financial_rag

    Looks up current company registration rules, industry licences and compliance obligations in China through live web search, tailored to the business profile.

    148 GitHub stars~1.6k tokensUpdated 4 mo ago
    Legal & ComplianceAuto-check: notes

  • Ad Compliance Review

    zh-xx/legal-assistant-skills

    广告合规审核技能，用于审核广告素材是否符合中国广告法及相关法规。适用场景：(1) 用户提交广告文案、广告素材要求合规审核时；(2) 用户提到"广告审核""广告合规""广告法审查"等关键词时；(3) 用户要求检查广告内容是否存在违法违规风险时；(4) 用户提交房地产、食品、医疗、药品、互联网等行业广告要求专项审核时。审核依据涵盖《广告法》《反不正当竞争法》及行业专项法规。

    173 GitHub stars~1.2k tokensUpdated 5 mo ago
    Legal & ComplianceAuto-check passed

More from anthropics/claude-for-legal

All 147 skills in this repo

  • Legal Clinic Client Intake

    anthropics/claude-for-legal

    Official

    Structures a legal clinic client intake interview and produces a case summary with cross-area issue spotting, conflict flags and triage classification.

    9.6k GitHub starsUsed in 3 repos~3.2k tokens
    Auto-check passed

  • Supervisor Review Queue

    anthropics/claude-for-legal

    Official

    Holds student work in a queue for a legal clinic professor to approve, edit-then-approve or return before anything reaches clients or courts.

    9.6k GitHub starsUsed in 3 repos~1.1k tokens
    Auto-check passed

  • Tabular Document Review

    anthropics/claude-for-legal

    Official

    Builds a review grid with one row per document and one column per data point, each cell cited to a verbatim quote, built for M&A diligence and other batch reviews.

    9.6k GitHub starsUsed in 3 repos~4.3k tokens
    Auto-check passed

  • Product Launch Legal Review

    anthropics/claude-for-legal

    Official

    Runs a category-by-category legal review of a product launch from a PRD or tracker ticket, calibrated to your team's framework, and writes a review memo in house format.

    9.6k GitHub starsUsed in 2 repos~5k tokens
    Auto-check passed

  • Legal Skills Registry Browser

    anthropics/claude-for-legal

    Official

    Searches watched registries for community legal skills, shows matches with descriptions and offers the full SKILL.md before anything is installed.

    9.6k GitHub starsUsed in 2 repos~620 tokens
    Auto-check passed

  • Contract Renewal Tracker

    anthropics/claude-for-legal

    Official

    Shows which contracts renew soon and when notice must be sent by, working from a maintained renewal register, and warns about missed cancellation windows.

    9.6k GitHub starsUsed in 2 repos~3.1k tokens
    Auto-check passed

Categories

Questions about Regulatory Feed Watcher

What does Regulatory Feed Watcher do?

Pulls the regulatory feeds on your watchlist, drops items under your materiality threshold and reports what is new since the last check, grouped by tier. md` for the watchlist, materiality threshold, feed configuration and optional digest path.md`, a curated list of RSS, JSON and HTML sources across US federal, US state, EU and UK, international and aggregator categories, and notes a coverage gap once at the top of the digest without repeating it.

When should I use Regulatory Feed Watcher?

Regulatory Feed Watcher fits situations like: asking what is new in the regulatory feeds you track; producing a scheduled digest filtered by materiality; classifying a pasted regulatory development against the previous check; spotting gaps between your watchlist and configured sources.

How do I install Regulatory Feed Watcher in Claude Code?

Run `npx skills add anthropics/claude-for-legal --skill reg-feed-watcher -a claude-code`. Or copy the skill folder (regulatory-legal/skills/reg-feed-watcher in anthropics/claude-for-legal) into .claude/skills/reg-feed-watcher in your project. Claude Code loads it when a task matches its description.

How do I install Regulatory Feed Watcher in Codex?

Run `npx skills add anthropics/claude-for-legal --skill reg-feed-watcher -a codex`. Or copy the skill folder (regulatory-legal/skills/reg-feed-watcher in anthropics/claude-for-legal) into .agents/skills/reg-feed-watcher in your project. Codex loads it when a task matches its description.

Can I use Regulatory Feed Watcher in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add anthropics/claude-for-legal --skill reg-feed-watcher -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/reg-feed-watcher, .gemini/skills/reg-feed-watcher, .github/skills/reg-feed-watcher and .opencode/skills/reg-feed-watcher in your project.

What does Regulatory Feed Watcher need to run?

Going by SKILL.md and its folder, Regulatory Feed Watcher needs the command-line tools its instructions call (pandoc). Our summary lists: The regulatory-legal plugin configuration in `CLAUDE.md` with a watchlist and materiality threshold; Network access to the configured feeds, such as the Federal Register API.

Does Regulatory Feed Watcher access the network?

SKILL.md names 1 domain. In commands or code: federalregister.gov; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Regulatory Feed Watcher safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Regulatory Feed Watcher use?

Regulatory Feed Watcher is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Regulatory Feed Watcher use?

About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.8k tokens, read only when the agent opens those files.

What are the alternatives to Regulatory Feed Watcher?

Skills that share tags, products or a category with Regulatory Feed Watcher: HIPAA Pre-Deployment Compliance Check (maziyarpanahi/openmed, 5.5k stars), Hipaa Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 943 stars), ISO Standards Readiness Evidence (K-Dense-AI/scientific-agent-skills, 48k stars) and Iso42001 (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 943 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Regulatory Feed Watcher?

anthropics (a GitHub organization, an official publisher) maintains it in anthropics/claude-for-legal, which has 9,629 GitHub stars. The repository holds 147 skills in this directory. The repository was last updated on September 29, 2026.

Source: anthropics/claude-for-legal on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.