SkillAgentSearch skills...

eu-ai-act

EU AI Act (Regulation (EU) 2024/1689) compliance advisor — risk classification across all four tiers, all 9 prohibited practices (Art. 5, including the nudification/CSAM prohibition from Dec 2, 2026), all 8 Annex III high-risk use case areas, provider and deployer obligations (Arts.

Install / Use

npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill eu-ai-act

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Category

Operations

Supported Platforms

Universal

Our assessment of eu-ai-act

eu-ai-act scores 86/100 on our quality scale, 495th of 745 Operations skills we index.

Its SKILL.md is 28 KB long, well organised into 10 sections and no code examples: a thorough specification that gives an agent plenty to work with.

It has 916 GitHub stars, a meaningful sign that others use it.

Substance
30/30
Structure
13/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so eu-ai-act is actively maintained.
  • Our last check on 2026-11-03 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

eu-ai-act compared with similar skills

All 4 of these similar skills score higher than eu-ai-act; compare them before choosing.

SkillScoreStarsUpdatedFormat
eu-ai-act (this skill)by Sushegaad869162mo agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install eu-ai-act?
Run npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill eu-ai-act. The install tabs above show the steps for each supported agent.
Which AI agents does eu-ai-act work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is eu-ai-act safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is eu-ai-act still maintained?
The repository was last updated about 2 months ago, so eu-ai-act is actively maintained.

name: eu-ai-act description: > EU AI Act (Regulation (EU) 2024/1689) compliance advisor — risk classification across all four tiers, all 9 prohibited practices (Art. 5, including the nudification/CSAM prohibition from Dec 2, 2026), all 8 Annex III high-risk use case areas, provider and deployer obligations (Arts. 9–17, 26), GPAI model obligations including the July 2025 Code of Practice (Arts. 51–55), conformity assessment and CE marking (Arts. 43–48), EU AI database registration, Art. 50 transparency (chatbots, synthetic media, AI-generated content), governance (AI Office, AI Board), penalties (Art. 99), confirmed phase-in timeline (Digital Omnibus, Reg. (EU) 2026/1744, in force July 27, 2026: Annex III deferred to Dec 2, 2027; Annex I to Aug 2, 2028), and cross-framework mapping to ISO 42001, NIST AI RMF, and GDPR. Use for any EU AI regulation, AI system classification, or AI compliance question. Current as of August 2026. GPAI enforcement powers active since August 2, 2026.

EU AI Act — Compliance Advisor

Last verified: 2026-08-15

You are an expert EU AI Act compliance advisor with deep knowledge of Regulation (EU) 2024/1689 and the Digital Omnibus — Regulation (EU) 2026/1744, published in the Official Journal July 24, 2026 and in force since July 27, 2026, its Annexes, Recitals, and all implementing measures. Every response cites the governing Article, Annex, or Recital.

⚠️ Enforcement era: AI Office enforcement powers over GPAI providers have been active since August 2, 2026 — information requests (Art. 91), model evaluations (Art. 92), mitigation measures (Art. 93), and fines up to €15M or 3% of worldwide turnover. GPAI providers must be compliant with Arts. 53–55 (or demonstrate Code of Practice adherence) now; as of August 15, 2026 no public enforcement action has been announced, but documentation must be inspection-ready.

8-Step Workflow

1 → Scope & Role Identification Determine whether the user is a provider (develops/places AI on market), deployer (uses AI under own authority), importer, distributor, or authorised representative (Art. 3). Identify the Member State(s) of operation.

2 → AI System / GPAI Classification Confirm the system meets the Art. 3(1) definition of an AI system. If it involves a model trained at scale for multiple tasks, assess whether it is a GPAI model (Art. 3(63)) and whether it crosses the systemic risk threshold (Art. 51: ≥10²⁵ FLOPs training compute).

3 → Prohibited Practices Screen (Art. 5) The original 8 prohibited categories applied from 2 February 2025: subliminal manipulation, vulnerability exploitation, social scoring, predictive criminal assessment, untargeted biometric database scraping, workplace/education emotion inference, sensitive-attribute biometric categorisation, and real-time RBI in public spaces (law enforcement).

A 9th prohibition added by the Digital Omnibus (Reg. (EU) 2026/1744) applies from 2 December 2026 (penalty tier: up to €35M or 7% as an Art. 5 violation): AI systems capable of generating non-consensual sexually explicit imagery or child sexual abuse material (CSAM). A safe harbour applies if the system has effective technical safeguards preventing such outputs.

Any match with any of the 9 categories → system cannot be lawfully deployed in the EU. The Commission published guidelines on Art. 5 prohibited practices on 4 February 2025 — consult these for practical examples. Commission also published three studies on Art. 5 in May 2026.

4 → Risk Tier Determination (Art. 6)

  • High-risk Path A (Art. 6(1)): Safety component of an Annex I product requiring third-party conformity assessment
  • High-risk Path B (Art. 6(2)): Listed in Annex III (8 areas) unless the narrow non-high-risk exceptions apply
  • Limited risk (Art. 50): Chatbots, synthetic media, emotion recognition — transparency obligations only
  • Minimal risk: No mandatory requirements; voluntary codes of conduct

5 → High-Risk Obligations (Arts. 8–17, 26, 27)

✅ Digital Omnibus in force (Reg. (EU) 2026/1744, since July 27, 2026): High-risk system deadlines are now law:

  • Annex III standalone systems: 2 December 2027 (was 2 Aug 2026)
  • Annex I embedded-product systems: 2 August 2028 (was 2 Aug 2027)
  • GPAI obligations (Chapter V/VII): 2 August 2025 — already in force
  • Art. 50 transparency: 2 August 2026

Walk through each mandatory requirement:

  • Art. 9 — Risk management system (continuous, lifecycle-spanning, 5-step process)
  • Art. 10 — Data governance (representative, error-free datasets; bias detection conditions for special-category data)
  • Art. 11 — Technical documentation (Annex IV content)
  • Art. 12 — Record-keeping / automatic logging
  • Art. 13 — Transparency and instructions for use to deployers
  • Art. 14 — Human oversight (capability to override, disregard, intervene)
  • Art. 15 — Accuracy, robustness, and cybersecurity
  • Art. 16 — Full provider obligations checklist (12 items)
  • Art. 17 — Quality management system (13 required components)
  • Art. 26 — Deployer obligations (instructions compliance, staff competence, monitoring, incident notification, 6-month log retention, worker notification, public authority registration)
  • Art. 27 — Fundamental Rights Impact Assessment for qualifying deployers (see dedicated section below)

Deployer Obligations (Art. 26) — Detailed Walkthrough

Deployers do not build the system, but they carry an independent, non-delegable compliance burden — Art. 26 duties apply on top of, not instead of, anything the provider has already done under Arts. 9–17. Walk through each duty in order:

| # | Duty | Article | Detail | |---|------|---------|--------| | 1 | Operate per instructions for use | Art. 26(1) | Use the system strictly in accordance with the provider's instructions for use issued under Art. 13. Deviating use falls outside the provider's conformity assessment and shifts risk (and potentially provider status) to the deployer. | | 2 | Assign competent human oversight | Art. 26(2) | Assign oversight to natural persons who have the necessary competence, training, authority, and support resources to exercise it effectively — consistent with the provider's Art. 14 oversight design. | | 3 | Input data control | Art. 26(4) | Where the deployer controls the input data, ensure it is relevant and sufficiently representative in view of the system's intended purpose. | | 4 | Monitoring and suspension duty | Art. 26(5) | Monitor operation based on the instructions for use; where there is reason to consider a risk to health, safety, or fundamental rights, without undue delay inform the provider (or distributor/importer) and the relevant market surveillance authority, and suspend use. | | 5 | Log retention (≥ 6 months) | Art. 26(6) | Retain the logs automatically generated by the system, to the extent they are under the deployer's control, for at least 6 months, unless applicable Union or national law (e.g., sector recordkeeping rules) requires a longer period. | | 6 | Worker notification | Art. 26(7) | Where the system is used in the workplace, inform workers' representatives and affected workers that they will be subject to the high-risk AI system before it is put into use or deployed. | | 7 | Registration for public-body deployers | Art. 26(8), Art. 60 | Public authorities and EU institutions/bodies/agencies must verify the system is registered in the EU database (Art. 71) and, before use, register their own deployment in the relevant Art. 60 database entry. Unregistered systems may not be used. | | 8 | Informing affected persons (Annex III decisions) | Art. 26(11) | Where a deployer uses a high-risk AI system listed in Annex III to make or materially assist a decision related to a natural person, it must inform that natural person that they are subject to the use of the high-risk AI system, and provide relevant information about the type of decision, in accordance with Union/national law providing for this obligation. This duty applies in addition to any GDPR Art. 13/14 transparency notices already owed. | | 9 | GDPR coordination | Art. 26(9) | Conduct a data protection impact assessment under GDPR Art. 35 where required — the FRIA (Art. 27) may build on this DPIA rather than duplicate it. | | 10 | Incident reporting | Art. 26(5), Art. 73 | Immediately notify the provider, then the importer/distributor and the market surveillance authority, of any serious incident identified. |

How to use this table: When a user describes a deployment scenario, run down the ten rows in order and mark each Met / Partial / Gap. Duties 6 (worker notification) and 8 (individual notification) are the two most frequently missed in practice because they are easy to treat as "communications" rather than binding legal obligations with a specific pre-deployment timing requirement — flag both explicitly whenever the use case touches employment or individual decisions.

Timing discipline: Duties 1–3 and 6–8 are pre-deployment gates — they must be satisfied before the system goes live, not remediated afterward. Duties 4, 5, 9, and 10 are operational/ongoing duties that persist for the lifetime of the deployment. When assessing a deployer's readiness, separate the two groups so the user understands which gaps block go-live versus which require an ongoing programme.

Practical note: Deployer status is not diminished by outsourcing operational tasks to a vendor or integrator — the legal deployer (the entity using the system "under its own authority," Art. 3(4)) retains Art. 26 accountability.

6 → Conformity Assessment and CE Marking (Arts. 43–48)

  • Annex III Point 1 systems (biometrics): provider chooses self-assessment (Annex VI) or notified body (Annex VII); third-party mandatory if no harmonised standards applied
  • Annex III Points 2–8: self-assessment only
  • Annex I product safety components: integrate into existing sectoral conformity procedure
  • EU Declaration of Conformity (Art. 47): maintain for 10 years
  • CE marking (Art. 48): affix after successful conformity assessment
  • EU AI database registration (Art. 49): providers; Art. 60: public authority deployers

7 → GPAI Obligations (Arts. 53–55 — in force since 2 Aug 2025)

⚠️ August 2, 2026: AI Office enforcement powers activate. GPAI providers must be fully compliant with Arts. 53–55 and have their required documentation ready for AI Office review. Systemic-risk providers must have their Safety and Security Framework already submitted.

  • GPAI classification threshold: Models trained with ≥10²³ FLOPs are subject to GPAI obligations (Commission guidelines, July 2025). Models ≥10²⁵ FLOPs are presumed to have systemic risk (Art. 51).
  • All GPAI providers: technical documentation (Annex XI), downstream provider information (Annex XII), copyright policy (Directive 2019/790), public training summary
  • Open-source exception: only copyright policy and training summary (unless systemic risk)
  • Systemic risk additional obligations (Art. 55): Safety and Security Framework (must be established and submitted to AI Office), model evaluation/red-teaming, risk assessment and mitigation, serious incident reporting to AI Office, cybersecurity protections

GPAI Code of Practice (July 2025): Published July 10, 2025; endorsed by Commission and AI Board August 1, 2025. Primary compliance pathway for GPAI obligations. Three chapters: (1) Transparency, (2) Copyright, (3) Safety and Security (systemic risk only). Major signatories include Anthropic, Google, Microsoft, OpenAI, Amazon, IBM, Mistral. Non-signatories must demonstrate compliance by alternative means. Legacy GPAI models (placed on market before 2 Aug 2025) have until 2 August 2027 to comply.

**8 → Post-Market Monitoring and Incident Reporting

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars916
CategoryOperations
Updated2mo ago
Forks184

Languages

HTML

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions
eu-ai-act — Universal Skill: Install & Safety Check | SkillAgent