· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →LECG v0.2.0+codex.20260914234654
Research regulatory changes
From the developer
Not specified in the available declarations: limitations, pricing & account requirements.
Set up my compliance profile and help me choose US states.
Developer declarations; not independently tested. Listing last checked Nov 22, 2026. Package observed Nov 21, 2026.
From the marketplace listing
A disciplined horizon-scanning workflow for legal and compliance teams. You build a compliance profile once — jurisdictions, sector, headcount, data and AI exposure, supply chain, materiality thresholds — and each scan queries US federal, optionally selected US states, EU, and UK primary sources for what has changed since your last run, suppresses what you have already seen, and scores each development for whether it binds you, what it would take to comply, and by when. Every claim carries a link to the primary source and a verbatim quote from the provision it rests on; anything that cannot be sourced is reported as a named coverage gap rather than summarised from memory. Outputs include an executive memo, a client alert, obligation register rows, a short digest, and a forward compliance calendar. Regulatory intelligence, not legal advice.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →---
name: assess-materiality
description: Assess one named regulatory development in depth against a business's compliance profile — whether it binds them, which provisions engage, what would have to change operationally, and by when. Use when the user names or pastes a specific regulation, rule, directive, statutory instrument, bill, or consultation and asks whether it applies to them, what it means for them, or what they need to do about it. Complements horizon-scan, which finds developments; this one analyses a single development.
---
Read `../../references/runtime-safety.md` before using this workflow. Resolve relative paths from this skill directory. To use a sibling skill, read its `../<skill-name>/SKILL.md`; no special invocation tool is required.
Deep-dive one development. Where `horizon-scan` triages breadth, this goes to depth on a single
instrument the user cares about.
**Read `../../references/citation-discipline.md` first. It governs everything below.** The depth
here makes provenance more important, not less — a detailed operational analysis built on an
unsourced threshold is confidently wrong in a way a one-line finding never is.
---
## 1. Identify the instrument precisely
The user may give you a name, a number, a URL, a pasted extract, or a vague description. Pin it down
to a specific instrument with an identifier before analysing anything.
- **Resolve it to a primary source and fetch it.** Federal Register document number, CELEX,
UK SI `year/number`, or a state instrument identified by state, type, session, and official
number. For a named state instrument read `../../references/sources-us-states.md`; an
explicit one-off assessment does not change saved recurring state selections. Use `../../references/sources-us-federal.md`, `sources-eu.md`, `sources-uk.md`.
- **If you cannot find it, say so.** Do not analyse an instrument you could not locate. A
plausible-sounding name may be a misremembering, a proposal that was never adopted, a measure
under a different number, or nothing at all. The correct response is:
> I could not locate a primary source for that. Can you share a link or the official number? I
> searched <sources> on <date> and found nothing matching.
Never produce an analysis from recall to be helpful. This is the single most likely way this
skill could cause harm.
- **If several instruments could match, ask which** rather than picking the most likely. Amending
instruments, corrigenda, and consolidations often share most of a title.
## 2. Get the profile
Ask for the compliance profile. Without it there is no "material to whom," and the answer collapses
into a generic summary the user could get anywhere.
If they don't have one, you can still analyse the instrument, but say clearly that applicability is
unassessed and ask the specific facts that decide it — usually jurisdiction, headcount, data types,
and whether they are consumer-facing.
## 3. Read the instrument and extract, with quotes
- **Scope** — who it binds, in its own words. Quote the scope provision.
- **Lifecycle stage** — proposed, in consultation, adopted, in force, or applying from a date.
- **Every date** — comment deadline, entry into force, application, staged milestones, first
reporting date. Each quoted separately from the provision that sets it.
- **Thresholds** — headcount, turnover, data volume, product class. Quoted.
- **Substantive obligations** — what must actually be done.
- **Penalties and liability**, including whether any is criminal or personal.
- **Exemptions and derogations** — often where the answer actually lives, and commonly missed.
Where the instrument amends another, **read the amended instrument too**. An amending act's text is
often unintelligible in isolation ("in Article 4, replace 'six' with 'twelve'"), and reporting the
amendment without the underlying provision tells the user nothing.
## 4. Assess applicability against the profile
Apply `../../references/materiality-rubPreview of the first 4,000 characters. Read full instructions →
--- name: compliance-calendar description: Build a forward calendar of dated regulatory obligations from scan findings or a compliance profile — comment deadlines, entry-into-force dates, applies-from dates, staged transition milestones, and first reporting dates — each carrying the source link and the quote that establishes it. Use when the user asks what is coming up, what deadlines they face, what to diarise, or wants a compliance calendar or timeline for a quarter, year, or specific regulation. --- Read `../../references/runtime-safety.md` before using this workflow. Resolve relative paths from this skill directory. To use a sibling skill, read its `../<skill-name>/SKILL.md`; no special invocation tool is required. Turn findings into dates the user can diarise, each traceable to the provision that sets it. **Read `../../references/citation-discipline.md` first.** This skill carries the highest fabrication risk in the plugin: an unsourced date here gets entered in a diary, relied on, and either missed or acted on early. **A date with no quotable source is omitted and listed as a gap — never estimated, never interpolated, never carried over from a similar instrument.** --- ## 1. Get the input Either the findings from a `horizon-scan` run, a specific instrument, or a compliance profile (in which case run a scan first, or work from the domains in scope). ## 2. Extract every dated obligation For each finding, pull out **every** date, not just the headline one. A single instrument commonly carries several, and the one that matters to this user may not be the first: - consultation or comment deadline - adoption date - entry into force - applies-from / application date - staged milestones — by obligation, entity class, or product category - first reporting date, and the reporting period it covers - transitional or grandfathering cut-offs - review or sunset dates **Each becomes its own calendar entry.** Do not collapse a staged regime into a single date — the staging is usually the operationally important part, and a business may be in scope for one stage and not another. ## 3. Source every date individually Each entry carries the link and the verbatim quote from the provision that sets it. Different dates in one instrument usually come from different provisions; cite each to its own. **Derived dates.** Where a date must be computed — an EU act's "twentieth day following that of its publication," a UK SI's "the day after the day on which these Regulations are made" — show the arithmetic, quote the provision, and label it derived: > **28 September 2026** — entry into force *(derived: 20th day after OJ publication 8 September > 2026)* · "shall enter into force on the twentieth day following that of its publication in the > *Official Journal of the European Union*" · [CELEX 32026R1975](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32026R1975) **Undated obligations.** These are common and must be represented honestly, not dropped and not guessed: - A proposed US rule has no effective date — `effective_on` is `null`. The comment deadline is the one possible fixed date; hearing, registration, and other procedural dates may also be set. - A UK SI may commence "on such day as the Secretary of State may by regulations appoint," which means **no date exists yet**. - An EU directive's transposition deadline binds member states, not businesses; the business date comes from national law, which is outside v1 coverage. Put all of these in an **Undated / pending** section with the reason and what will fix it. This section is often the most useful part of the calendar, because it tells the user what to keep watching rather than implying nothing is coming. ## 4. Flag lead-time mismatches Compare each entry's `effort` score to the time available. Where effort exceeds lead time, flag it — this is frequently the single most valuable output of the whole plugin: > ⚠️ **Lead-time risk** — `program_change` due in 41 d
Preview of the first 4,000 characters. Read full instructions →
--- name: compliance-profile description: Build or update the compliance profile that scopes every horizon scan — the business's legal entities, operating jurisdictions, sector, headcount, data and AI exposure, supply chain, and materiality thresholds. Use when the user is setting up for the first time, has no profile yet, or needs to change one after a business change such as a new jurisdiction, product line, or headcount shift. Emits a portable YAML block the user saves and supplies to later scans. --- Read `../../references/runtime-safety.md` before using this workflow. Resolve relative paths from this skill directory. To use a sibling skill, read its `../<skill-name>/SKILL.md`; no special invocation tool is required. The profile is the plugin's only memory. It scopes the scan to one business and carries the scan state that makes later runs incremental. Getting it right is what separates a relevant scan from a generic one. Read `../../references/profile-schema.md` for the full field reference and vocabulary. --- ## 1. Establish whether this is new or an update Ask for an existing profile block first. If there is one, go to §5. ## 2. Interview — ask only what you cannot infer Work through the schema, but do not read it out as a form. Ask in the order below, group related questions, and infer what you reasonably can from what the user has already said — then state your inference so they can correct it. **Identity and footprint** (needed) - Legal entities and where each is incorporated - Where the business actually operates — use the `operating_jurisdictions` vocabulary - For US coverage, offer federal-only (default) or federal plus selected states. Ask which states matter, accept names or postal codes, and save them in `coverage.us_states` using the schema. Explain state research is bounded by reachable official sources. Ask only if the preference is not already clear; never enable every state automatically. - Sector, in the user's own words; add NAICS/SIC if they know them - Headcount per jurisdiction, roughly - Public company? If so, listing venues - Revenue band, roughly **Exposure** (this is what makes the scan specific — worth the time) - What personal data: customer, employee, health, biometric, children, financial, location - AI anywhere: in the product, in hiring, in credit decisions, internal only - Consumer-facing? Payments? - Regulated products - Export-controlled items; any touchpoints with sanctioned jurisdictions - Physical sites, and how far the supply chain is mapped - Unionised workforce **Thresholds** - Report at `medium` and above (default), or a different cut - Anything to always surface regardless of score — default is criminal liability, personal liability for directors and officers, and licence conditions ### How to ask well **Don't ask what you can infer, but do confirm it.** If they say "we're a UK SaaS business selling to consumers in Europe," set `consumer_facing: true`, `sector` to software, and propose `UK` and `EU` — then say what you assumed and let them correct it. **Headcount matters more than it looks.** Several employment and reporting obligations turn on thresholds, so an approximate number per jurisdiction is worth pressing for gently. "Roughly how many people in the UK — under 50, under 250, or more?" gets there without an interrogation. **Push a little on the exposure flags, and only there.** These are where a wrong value produces confidently irrelevant results. `biometric` and `children` in particular pull in materially different regimes, and users often don't volunteer them — face unlock, age-gated sign-up, or a photo feature all count. Ask directly. **Don't guess an exposure flag to be safe.** Setting `biometric: true` on a hunch floods every later scan with irrelevant high-impact findings and trains the user to ignore the output. If you don't know, ask; if the user doesn't know, record it as unknown and say the next scan may miss or over-report in that area.
Preview of the first 4,000 characters. Read full instructions →
--- name: horizon-scan description: Scan US federal, optionally selected US states, EU, and UK primary regulatory sources for new and upcoming changes since the user's last scan, scoped to their saved compliance profile, and return each finding with a source citation and a materiality score. Use when the user asks what regulatory or compliance changes affect their business, what is new since their last scan, what is coming up, or which consultations are open. Requires a compliance profile; if the user has none, run the compliance-profile skill first. --- Read `../../references/runtime-safety.md` before using this workflow. Resolve relative paths from this skill directory. To use a sibling skill, read its `../<skill-name>/SKILL.md`; no special invocation tool is required. Produce a deduplicated, source-cited list of regulatory developments relevant to one specific business, with a materiality score on each. **Read `../../references/citation-discipline.md` before producing any output. It governs everything below, and where anything here appears to conflict with it, it wins.** The short version: every claim needs a link fetched in this session, a verbatim supporting quote, and per-claim sourcing for dates, deadlines, thresholds, and penalties. No link, no claim. --- ## 1. Get the profile Ask the user for their saved compliance profile block. If they don't have one, run `compliance-profile` first — do not scan against guesses about their business, because a scan scoped to the wrong business is worse than no scan. Read `../../references/profile-schema.md` to interpret it. Extract: - `last_scan_date` → the start of the scan window. Today is the end. - `operating_jurisdictions` → which source registry files to use - `coverage.us_states` → optional selected states; absent means none - `coverage.pending_state_baselines` → first/re-enabled state windows from the schema - `coverage.pending_scope_baselines` → historical and standing-law checks for scope changes - `domains_in_scope` → which domain sections apply - `exposure_flags` → the applicability triggers - `materiality_thresholds` → the reporting cut - `reported_ledger` → what to suppress - `watch_keywords` / `exclude_keywords` → extra searches and noise suppression State the window and scope back to the user in one line before scanning, so a wrong profile is caught before the work rather than after: > Scanning 2026-07-11 → 2026-09-09 · US-Federal, EU, UK · privacy_ai, employment, esg, > trade_sanctions, consumer_protection · reporting at medium and above. ## 2. Announce uncovered jurisdictions — before scanning, not after Announce selected states (or “state coverage off”), their scan windows, and any profile states not selected. Identify EU member-state implementation, local law, and unsupported jurisdictions as excluded. For example: > State research enabled: California and New York. Not searched: Texas (not selected), > city/county law, and EU national implementation. Source coverage will be reported by state. This goes first, not in a footnote. A user who believes a jurisdiction was searched when it was not is the worst outcome this skill can produce. ## 3. Select sources Load only the registry files you need: - `US-Federal` → `../../references/sources-us-federal.md` - Nonempty `coverage.us_states` → `../../references/sources-us-states.md` - `EU` → `../../references/sources-eu.md` - `UK` → `../../references/sources-uk.md` Then read `../../references/cross-industry-domains.md` for the domains in scope, to get the applicability triggers and the agency slugs and feeds to watch per domain. ## 4. Query primary sources first Before ordinary delta queries, process pending scope baselines under `profile-schema.md`. Announce their affected scope and historical window separately. Search older developments and current standing obligations, including older rules with ongoing duties or transitions; do not constrain that standing-law review by publication date. Use the rele
Preview of the first 4,000 characters. Read full instructions →
--- name: regulatory-change-brief description: Render horizon scan findings into a finished deliverable — an in-house executive or board memo, a law-firm client alert, obligation register rows for a compliance tracker, or a short email or Slack digest — with citations carried through to the reader. Use when the user asks to write up, summarise, or circulate regulatory findings, or asks for a memo, alert, briefing, digest, or register entries from a scan. --- Read `../../references/runtime-safety.md` before using this workflow. Resolve relative paths from this skill directory. To use a sibling skill, read its `../<skill-name>/SKILL.md`; no special invocation tool is required. Turn findings into something the user can send. The analysis is already done by `horizon-scan` or `assess-materiality`; this skill is about audience and format. **Read `../../references/citation-discipline.md` first.** Then the rule that governs this skill specifically: **citations travel to the reader.** A brief is where sourcing is most tempting to strip for readability and where stripping it does the most damage — the recipient is further from the source than the user is, and often acts on it. Templates: `../../references/output-templates.md`. --- ## 1. Ask which format, if not obvious | Format | Audience | Shape | |---|---|---| | `exec-memo` | In-house: GC, exec team, board | What changed, what it means for us, what we're doing, what we need | | `client-alert` | Law firm: clients or a client group | What changed, who it affects, what to do, how we can help | | `register` | Compliance tracker / obligation register | Structured rows, CSV-ready | | `digest` | Email or Slack, internal circulation | Short, scannable, links out | Infer from context where you can — "write this up for our board" is an `exec-memo`, "send to clients" is a `client-alert`. Ask only when genuinely ambiguous. Also ask, or infer, **who the reader is and what decision they face**. A board paper for an approval decision is a different document from an FYI to the same board. ## 2. Filter to what this audience needs For a client alert, first obtain the client's saved business profile, or run `compliance-profile` for that client before discovery. Never substitute the law firm's own profile. For a client group, agree an explicit representative profile and disclose its limits; keep materially different clients in separate profiles and ledgers. If findings came from another profile, run `horizon-scan` against the client profile before drafting: filtering a firm-scoped scan cannot recover missed rules. Existing findings may be reused only when their scope matches and sources are reverified. Start the alert with a concise summary of the client business, jurisdictions, activities and unresolved applicability facts that scoped the research. A brief is not a scan with a header on it. Cut hard, and cut by relevance to the reader: - **exec-memo / digest** — `binds_us` and `likely` only, at the profile threshold or above. `monitor_only` items belong in an appendix or nowhere. Put `unassessed` items in a separate questions section when material to the decision; never present them as duties. - **client-alert** — items discovered against the client or agreed client-group profile. Be explicit about that audience and individual applicability limits. - **register** — everything reportable, since a register is a system of record rather than a read. ## 3. Carry the citations through Non-negotiable, per format: - **exec-memo / client-alert** — inline linked references at each claim, plus a closing sources list with `official_id`, publisher, and `retrieved_on` for each item. - **register** — mandatory `source_url` and `official_id` columns. A row without them is not written. - **digest** — every item links to its primary source. A digest is the format most likely to be forwarded onward with no further context, which makes the link matter more, not less. **If an item's provenance
Preview of the first 4,000 characters. Read full instructions →
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 21, 2026.
plugins_6aa2e3dfeac4819199d6e0df1d881288
Download plugin data (JSON)Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.