/ai-inventory
When this runs
The user wants to manage their AI system inventory under the EU AI Act. The
core idea the skill exists to enforce: role and tier are per-system, not
per-company. A single organization can be a provider of System A, a
deployer of System B, and an importer of System C. Each combination
triggers a different set of obligations under the AI Act. The inventory
exists so those assessments are tracked where you can find them — the
obligations themselves are derived in conversation, not from a table.
What to do
Read the config. Read
~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md.
If it doesn't exist or still has [PLACEHOLDER] markers, direct the user
to /ai-governance-legal:cold-start-interview first.
Read the inventory. Inventory lives at
~/.claude/plugins/config/claude-for-legal/ai-governance-legal/ai-systems.yaml.
If it doesn't exist, create it with an empty systems: list when the
first add runs.
Dispatch on the argument:
- No argument, or
list → show the inventory table (see List below).
add → run the Add flow.
edit <id> → show the current record, ask what to change, update one
field, confirm, write.
classify <id> → run the Classification walk-through on an
existing record, updating role, tier, role_basis, and tier_basis.
show <id> → show the full record.
On list, offer the dashboard:
"Want the full dashboard? Filter by status / tier / EU nexus / owner.
Say the word."
Close every action with a hook into the lawyer's work.
After any write, say:
Recorded. When you're ready to walk through obligations for this
system, just ask — I'll do it in-conversation and flag where the AI
Act article mapping needs your verification. I don't derive
obligations from a table because the mapping is complex and changing.
List format
Render as a compact table:
| ID |
Name |
Owner |
Status |
EU nexus |
Role |
Tier |
Next review |
| sys-001 |
Resume screening |
HR / Jamie |
in_production |
yes |
deployer |
high_risk |
2026-08-01 |
| sys-002 |
Email drafting assistant |
IT / Priya |
in_production |
no |
deployer |
limited |
2026-12-01 |
Under the table, show counts by tier and a line: "N systems flagged for
review within 30 days."
Add flow (interview)
Ask, one field at a time (or accept a paste). The required fields are
name, owner, description, status, eu_nexus. The rest can be
deferred — say so explicitly: "you can come back to classification with
/ai-governance-legal:ai-inventory classify <id>."
- Name. Short label for the system.
- Owner. Person or team accountable for it day-to-day.
- Description. One or two sentences. What does it do, and against
what data?
- Status.
planned | in_development | in_production | deprecated.
- EU nexus. Is the system deployed in the EU/EEA, offered to users in
the EU/EEA, or used to produce outputs that affect people in the
EU/EEA? If any of these are true, EU AI Act analysis applies.
- Proceed to classification? Offer to run the walk-through now, or
skip and come back later.
Assign an ID: sys-NNN where NNN is the next integer in the file.
Classification walk-through
The walk-through produces role, role_basis, tier, tier_basis. Both
bases are tagged [verify against current AI Act text] — not because the
skill is hedging, but because the article mapping is complex and the AI
Act is still phasing in. The lawyer owns verification.
Step 1: Role
Who does what to this system?
Options, with the distinguishing test:
- Provider — you develop it (or have it developed) and place it on the
EU market or put it into service under your own name or trademark.
- Deployer — you use it under your own authority, not for personal
non-professional use. (Most common inside companies.)
- Importer — you bring an AI system into the EU from a provider
established outside the EU.
- Distributor — you make an AI system available on the EU market
without being the provider or importer.
- Authorized representative — you act on behalf of a non-EU provider
and are established in the EU.
- Product manufacturer — you put a general-purpose AI system (or
another AI system) into a product under your own name/trademark. Treated
as provider for the product.
Dual-role flag. If the user substantially modifies a vendor system
(fine-tunes on their own data, changes the intended purpose, rebrands),
they may become a provider of the modified system even if they started
as a deployer. Call this out when they describe any modification beyond
configuration. [verify against current AI Act text — Article 25, provider obligations and substantial modification]
Write the role. Write role_basis in one sentence.
Step 2: Tier
What does the system do, and does the use case fall into a regulated
category?
Check in order:
A. Article 5 prohibited practices. [verify against current AI Act text — Article 5]
Summaries, not definitive text:
- Subliminal or deceptive techniques materially distorting behavior
- Exploiting vulnerabilities (age, disability, socio-economic status) to
materially distort behavior
- Social scoring by public authorities leading to detrimental treatment
- Real-time remote biometric ID in publicly accessible spaces for law
enforcement (narrow exceptions)
- Biometric categorization inferring race, political opinions, union
membership, religious or philosophical beliefs, sex life, or sexual
orientation
- Emotion recognition in the workplace or education (medical and safety
exceptions)
- Facial image database scraping from the internet or CCTV
- Predictive policing based solely on personality traits
If matched → tier is prohibited. Flag the use case as stop and route to
the governance team's prohibited-practice workflow.
B. Annex III high-risk areas. [verify against current AI Act text — Annex III]
Summaries:
- Biometric identification and categorization
- Critical infrastructure (digital infrastructure, road traffic, supply of
water / gas / heating / electricity)
- Education and vocational training (access, evaluation, proctoring,
monitoring prohibited behavior)
- Employment, worker management, self-employment access — recruitment,
selection, promotion, termination, task allocation, monitoring, performance
- Essential private and public services (public benefits, credit scoring
for individuals, risk assessment and pricing for life/health insurance,
emergency dispatch)
- Law enforcement (risk assessment, polygraphs, deepfake detection,
reliability of evidence, profiling)
- Migration, asylum, border control (risk assessment, travel document
verification, examination of applications)
- Administration of justice and democratic processes (research and
interpretation, influencing elections)
If matched → tier is high_risk. Note the Annex III area and subsection.
C. GPAI. [verify against current AI Act text — Article 51 and surrounding]
- GPAI: model trained on broad data at scale, designed for generality,
capable of competently performing a wide range of distinct tasks.
- GPAI + systemic risk: cumulative compute > 10^25 FLOPs, or designated
by the Commission.
D. Limited risk. Chatbots interacting with natural persons, deepfakes,
emotion recognition and biometric categorization systems outside Article 5
scope — transparency obligations apply.
E. Minimal risk. Everything else.
Write the tier. Write tier_basis in one sentence, citing the article or
Annex entry that matched, tagged [verify against current AI Act text].
Step 3: Recommendations
Offer three next steps:
- "Want me to walk through obligations for this system? I'll do it in
conversation — I don't derive them from a table."
- "Want to run
/ai-governance-legal:aia-generation to produce a full
impact assessment?"
- "Want to set a next review date? I'll add it to the inventory."
Record format
systems:
- id: sys-001
name: "Resume screening tool"
owner: "HR / Jamie"
description: "Filters inbound CVs against job criteria"
status: in_production # planned | in_development | in_production | deprecated
eu_nexus: true # deployed, offered, or affects people in the EU/EEA
role: deployer # provider | deployer | importer | distributor | authorized_rep | product_manufacturer
role_basis: "We license from VendorX and deploy internally [verify against current AI Act text]"
tier: high_risk # prohibited | high_risk | limited | minimal | gpai | gpai_systemic
tier_basis: "Annex III(4)(a) — employment, recruitment selection [verify against current AI Act text]"
obligations_assessed: false
obligations_note: "To assess: as deployer of a high-risk system — human oversight, input data quality, monitoring, record-keeping, informing workers, FRIA if public body/service — see Article 26 [verify against current AI Act text]"
next_review: "2026-08-01"
review_trigger: "on substantial modification or annually"
created: "2026-05-11"
updated: "2026-05-11"
Why this skill does NOT auto-derive obligations
The inventory stores role, tier, and the basis for each. It does NOT
contain a hardcoded role × tier → obligations table.
When the user asks "what are my obligations for System X?", the skill
does the analysis in conversation, tagged [verify], and routes to
/ai-governance-legal:aia-generation for the formal impact assessment
if needed.
This is deliberate:
- Article mapping is complex and the AI Act is phasing in through 2027.
- Confident-and-wrong on a compliance obligation ends up in a board memo.
- The inventory is a registry for the lawyer. The lawyer owns the
obligation analysis.
Guardrails
- Never classify silently. The classification walk-through must be
visible; do not auto-classify from a system description.
[verify] tags stay. They are not hedging — they are the point.
Do not strip them in outputs.
- Flag substantial modification. Whenever a system is modified beyond
configuration, prompt the user to re-run
/ai-inventory classify —
modification can change role.
- Don't declare obligations from a table. If asked, do the analysis
in conversation and route to
/aia-generation for anything that needs
a formal record.
1---2name: ai-inventory-anthropics3title: 'AI inventory'4description: EU AI Act per-system inventory — track each AI system's role (provider, deployer, importer, distributor, authorized representative, product manufacturer) and risk tier (prohibited, high-risk, limited, minimal, GPAI, GPAI+systemic). Role and tier are assessed per system, not per company. Use when the user says "ai inventory", "add an ai system", "what systems do we have", "classify this ai system", "eu ai act register", or "ai system registry".5author: anthropics6author_url: https://github.com/anthropics/claude-for-legal/tree/main/ai-governance-legal/skills/ai-inventory7license: Apache-2.08version: 0.1.19execution_mode: open10jurisdiction: general11practice: regulatory12language: en13metadata:14 source: https://skillmd.com/skills/thomasmoreai/ai-inventory-anthropics15---1617# /ai-inventory1819## When this runs2021The user wants to manage their AI system inventory under the EU AI Act. The22core idea the skill exists to enforce: **role and tier are per-system, not23per-company.** A single organization can be a *provider* of System A, a24*deployer* of System B, and an *importer* of System C. Each combination25triggers a different set of obligations under the AI Act. The inventory26exists so those assessments are tracked where you can find them — the27obligations themselves are derived in conversation, not from a table.2829## What to do30311. **Read the config.** Read32 `~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md`.33 If it doesn't exist or still has `[PLACEHOLDER]` markers, direct the user34 to `/ai-governance-legal:cold-start-interview` first.35362. **Read the inventory.** Inventory lives at37 `~/.claude/plugins/config/claude-for-legal/ai-governance-legal/ai-systems.yaml`.38 If it doesn't exist, create it with an empty `systems:` list when the39 first `add` runs.40413. **Dispatch on the argument:**4243 - No argument, or `list` → show the inventory table (see **List** below).44 - `add` → run the **Add** flow.45 - `edit <id>` → show the current record, ask what to change, update one46 field, confirm, write.47 - `classify <id>` → run the **Classification walk-through** on an48 existing record, updating role, tier, role_basis, and tier_basis.49 - `show <id>` → show the full record.50514. **On list, offer the dashboard:**52 "Want the full dashboard? Filter by status / tier / EU nexus / owner.53 Say the word."54555. **Close every action with a hook into the lawyer's work.**56 After any write, say:57 > Recorded. When you're ready to walk through obligations for this58 > system, just ask — I'll do it in-conversation and flag where the AI59 > Act article mapping needs your verification. I don't derive60 > obligations from a table because the mapping is complex and changing.6162## List format6364Render as a compact table:6566| ID | Name | Owner | Status | EU nexus | Role | Tier | Next review |67|----|------|-------|--------|----------|------|------|-------------|68| sys-001 | Resume screening | HR / Jamie | in_production | yes | deployer | high_risk | 2026-08-01 |69| sys-002 | Email drafting assistant | IT / Priya | in_production | no | deployer | limited | 2026-12-01 |7071Under the table, show counts by tier and a line: "N systems flagged for72review within 30 days."7374## Add flow (interview)7576Ask, one field at a time (or accept a paste). The required fields are77`name`, `owner`, `description`, `status`, `eu_nexus`. The rest can be78deferred — say so explicitly: "you can come back to classification with79`/ai-governance-legal:ai-inventory classify <id>`."80811. **Name.** Short label for the system.822. **Owner.** Person or team accountable for it day-to-day.833. **Description.** One or two sentences. What does it do, and against84 what data?854. **Status.** `planned | in_development | in_production | deprecated`.865. **EU nexus.** Is the system deployed in the EU/EEA, offered to users in87 the EU/EEA, or used to produce outputs that affect people in the88 EU/EEA? If any of these are true, EU AI Act analysis applies.896. **Proceed to classification?** Offer to run the walk-through now, or90 skip and come back later.9192Assign an ID: `sys-NNN` where NNN is the next integer in the file.9394## Classification walk-through9596The walk-through produces `role`, `role_basis`, `tier`, `tier_basis`. Both97bases are tagged `[verify against current AI Act text]` — not because the98skill is hedging, but because the article mapping is complex and the AI99Act is still phasing in. The lawyer owns verification.100101### Step 1: Role102103> **Who does what to this system?**104105Options, with the distinguishing test:106107- **Provider** — you develop it (or have it developed) and place it on the108 EU market or put it into service under your own name or trademark.109- **Deployer** — you use it under your own authority, not for personal110 non-professional use. (Most common inside companies.)111- **Importer** — you bring an AI system into the EU from a provider112 established outside the EU.113- **Distributor** — you make an AI system available on the EU market114 without being the provider or importer.115- **Authorized representative** — you act on behalf of a non-EU provider116 and are established in the EU.117- **Product manufacturer** — you put a general-purpose AI system (or118 another AI system) into a product under your own name/trademark. Treated119 as provider for the product.120121**Dual-role flag.** If the user substantially modifies a vendor system122(fine-tunes on their own data, changes the intended purpose, rebrands),123they may become a **provider** of the modified system even if they started124as a deployer. Call this out when they describe any modification beyond125configuration. `[verify against current AI Act text — Article 25, provider126obligations and substantial modification]`127128Write the role. Write `role_basis` in one sentence.129130### Step 2: Tier131132> **What does the system do, and does the use case fall into a regulated133> category?**134135Check in order:136137**A. Article 5 prohibited practices.** `[verify against current AI Act138text — Article 5]`139140Summaries, not definitive text:141- Subliminal or deceptive techniques materially distorting behavior142- Exploiting vulnerabilities (age, disability, socio-economic status) to143 materially distort behavior144- Social scoring by public authorities leading to detrimental treatment145- Real-time remote biometric ID in publicly accessible spaces for law146 enforcement (narrow exceptions)147- Biometric categorization inferring race, political opinions, union148 membership, religious or philosophical beliefs, sex life, or sexual149 orientation150- Emotion recognition in the workplace or education (medical and safety151 exceptions)152- Facial image database scraping from the internet or CCTV153- Predictive policing based solely on personality traits154155If matched → tier is `prohibited`. Flag the use case as stop and route to156the governance team's prohibited-practice workflow.157158**B. Annex III high-risk areas.** `[verify against current AI Act text —159Annex III]`160161Summaries:1621. Biometric identification and categorization1632. Critical infrastructure (digital infrastructure, road traffic, supply of164 water / gas / heating / electricity)1653. Education and vocational training (access, evaluation, proctoring,166 monitoring prohibited behavior)1674. Employment, worker management, self-employment access — recruitment,168 selection, promotion, termination, task allocation, monitoring, performance1695. Essential private and public services (public benefits, credit scoring170 for individuals, risk assessment and pricing for life/health insurance,171 emergency dispatch)1726. Law enforcement (risk assessment, polygraphs, deepfake detection,173 reliability of evidence, profiling)1747. Migration, asylum, border control (risk assessment, travel document175 verification, examination of applications)1768. Administration of justice and democratic processes (research and177 interpretation, influencing elections)178179If matched → tier is `high_risk`. Note the Annex III area and subsection.180181**C. GPAI.** `[verify against current AI Act text — Article 51 and182surrounding]`183184- **GPAI:** model trained on broad data at scale, designed for generality,185 capable of competently performing a wide range of distinct tasks.186- **GPAI + systemic risk:** cumulative compute > 10^25 FLOPs, or designated187 by the Commission.188189**D. Limited risk.** Chatbots interacting with natural persons, deepfakes,190emotion recognition and biometric categorization systems outside Article 5191scope — transparency obligations apply.192193**E. Minimal risk.** Everything else.194195Write the tier. Write `tier_basis` in one sentence, citing the article or196Annex entry that matched, tagged `[verify against current AI Act text]`.197198### Step 3: Recommendations199200Offer three next steps:2011. "Want me to walk through obligations for this system? I'll do it in202 conversation — I don't derive them from a table."2032. "Want to run `/ai-governance-legal:aia-generation` to produce a full204 impact assessment?"2053. "Want to set a next review date? I'll add it to the inventory."206207## Record format208209```yaml210systems:211 - id: sys-001212 name: "Resume screening tool"213 owner: "HR / Jamie"214 description: "Filters inbound CVs against job criteria"215 status: in_production # planned | in_development | in_production | deprecated216 eu_nexus: true # deployed, offered, or affects people in the EU/EEA217 role: deployer # provider | deployer | importer | distributor | authorized_rep | product_manufacturer218 role_basis: "We license from VendorX and deploy internally [verify against current AI Act text]"219 tier: high_risk # prohibited | high_risk | limited | minimal | gpai | gpai_systemic220 tier_basis: "Annex III(4)(a) — employment, recruitment selection [verify against current AI Act text]"221 obligations_assessed: false222 obligations_note: "To assess: as deployer of a high-risk system — human oversight, input data quality, monitoring, record-keeping, informing workers, FRIA if public body/service — see Article 26 [verify against current AI Act text]"223 next_review: "2026-08-01"224 review_trigger: "on substantial modification or annually"225 created: "2026-05-11"226 updated: "2026-05-11"227```228229## Why this skill does NOT auto-derive obligations230231The inventory stores role, tier, and the basis for each. It does NOT232contain a hardcoded role × tier → obligations table.233234When the user asks "what are my obligations for System X?", the skill235does the analysis **in conversation**, tagged `[verify]`, and routes to236`/ai-governance-legal:aia-generation` for the formal impact assessment237if needed.238239This is deliberate:240- Article mapping is complex and the AI Act is phasing in through 2027.241- Confident-and-wrong on a compliance obligation ends up in a board memo.242- The inventory is a registry for the lawyer. The lawyer owns the243 obligation analysis.244245## Guardrails246247- **Never classify silently.** The classification walk-through must be248 visible; do not auto-classify from a system description.249- **`[verify]` tags stay.** They are not hedging — they are the point.250 Do not strip them in outputs.251- **Flag substantial modification.** Whenever a system is modified beyond252 configuration, prompt the user to re-run `/ai-inventory classify` —253 modification can change role.254- **Don't declare obligations from a table.** If asked, do the analysis255 in conversation and route to `/aia-generation` for anything that needs256 a formal record.