CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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. 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 November 2026. GPAI enforcement active: Art. 91 information requests reported since Aug 2026 (procedures: Reg. (EU) 2026/1755).

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an exceptionally actionable advisory skill: a well-gated 8-step workflow, checklists, traps tables, and a worked example that together make the guidance fully executable. Its weaknesses are token efficiency — duplicated enforcement callouts and timeline dates repeated across sections, plus body/reference overlap on Art. 26/27 — which keep it from a top score.

Suggestions

Consolidate the GPAI enforcement material: the opening callout and the Step 7 warning repeat the same Art. 91 / Reg. (EU) 2026/1755 details nearly verbatim — keep one full version and cross-reference it from the other location.

State each Digital Omnibus deadline once in the Compliance Timeline Summary table and reference that table from Step 5 and the opening callouts instead of repeating the dates in three or four places.

Since obligations-high-risk.md already contains the Art. 26 and Art. 27 detail, trim the inlined deployer walkthrough and FRIA sections in SKILL.md to checklist level (traps, timing gates, workflow table) and point to the reference file for row-by-row detail.

DimensionReasoningScore

Conciseness

The body is dense with post-training-cutoff legal specifics Claude cannot know (Digital Omnibus Reg. (EU) 2026/1744, Reg. (EU) 2026/1755, EN 18286:2026), but the GPAI enforcement warning appears nearly verbatim in both the opening callout and Step 7, and the phase-in dates are repeated across the Step 5 callout, inline mentions, and the timeline table — "some unnecessary explanation or could be tightened" (anchor 3) rather than only "minor instances" (anchor 4). Time-sensitive dates are woven throughout rather than consolidated in one section, which the guidelines say should penalize conciseness.

3 / 5

Actionability

For an instruction-only skill the guidance is fully executable: a 10-row deployer duty table with Met/Partial/Gap marking instructions, the Art. 27(1)(a)–(f) FRIA content checklist, a step-by-step worked example applying the Art. 6(3) filter "in order", per-question-type response formats, and concrete penalty figures — matching anchor 5's standard of specific procedures covering the common cases.

5 / 5

Workflow Clarity

The 8-step workflow is explicitly sequenced with decision gates and checkpoints: "Any match with any of the 9 categories → system cannot be lawfully deployed", "Confirm the user's role is deployer (not provider) before answering", "Put the system into use only after Step 4 is complete", and "always confirm the deployer falls into one of the three WHO categories before advising a FRIA is mandatory" — clear sequence, explicit validation steps, and checklists per anchor 5. This is an advisory skill, so the destructive/batch-operation cap does not apply.

5 / 5

Progressive Disclosure

All three referenced files (references/risk-classification.md, obligations-high-risk.md, gpai-governance.md) exist, contain substantive material, and are one level deep with no nested references; the Reference Files section clearly signals what each contains. However, the body inlines substantial Art. 26 and Art. 27 material that is also held in obligations-high-risk.md, duplicating content across levels and making SKILL.md longer than an overview — an organization gap placing it at anchor 4 rather than anchor 5's clean split.

4 / 5

Total

17

/

20

Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it comprehensively enumerates concrete capability areas with precise article citations and includes an explicit "Use for..." trigger clause with natural keywords. The only weaknesses are a slightly over-broad "any AI compliance question" trigger and a few missing natural synonyms.

DimensionReasoningScore

Specificity

Enumerates multiple concrete capabilities with article-level citations — "risk classification across all four tiers", "all 9 prohibited practices (Art. 5...)", "conformity assessment and CE marking (Arts. 43–48)", "penalties (Art. 99)", "cross-framework mapping to ISO 42001, NIST AI RMF, and GDPR" — matching the comprehensive anchor 5 rather than anchor 4, since coverage spans the full regulation without noticeable gaps.

5 / 5

Completeness

Explicitly answers both questions: the long capability enumeration states "what", and "Use for any EU AI regulation, AI system classification, or AI compliance question" gives concrete "when" triggers — matching anchor 5. Not anchor 4, because the when-clause is explicit and specific rather than merely implied or generic.

5 / 5

Trigger Term Quality

Good natural-keyword coverage: "EU AI Act" leads the description and the trigger clause names "EU AI regulation, AI system classification, or AI compliance question", plus terms like chatbots, synthetic media, and GPAI. A few natural synonyms are missing (e.g., "Artificial Intelligence Act" spelled out, "high-risk AI"), so it fits anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The EU AI Act niche is clear and the primary triggers ("EU AI regulation") are unambiguous, but the trigger "any... AI compliance question" is broad enough to capture non-EU framework questions (ISO 42001, NIST AI RMF are named in the description), creating minor overlap with closely related skills — anchor 4 rather than anchor 5's minimal conflict risk.

4 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

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

Path

plugins/eu-ai-act/skills/eu-ai-act/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.