Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lawve-ai/eu-ai-act-transparency-assessor-oliver-schmidt-prietz
Assesses which of the Art. 50(1)-(5) transparency obligations of the EU AI Act apply to a given AI system's provider or deployer, grounded in the final Code of Practice on Transparency of AI-Generated Content (June 2026) and the Commission's draft Art. 50 Guidelines. Covers AI-chatbot disclosure, deepfake and synthetic-content marking/watermarking, emotion-recognition and biometric-categorisation notices, the machine-readable marking duty, the obviousness exceptions, and the implementation timel
Passed 20 of 22 test cases with the skill, and 8 of 22 without it.
and 17 more in the full report
12 fixed8 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
When does the Code of Practice obligation requiring watermark detection tools to support cross-provider interoperability become effective?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies February 2, 2027 as the effective date for the Code of Practice watermark detection interoperability obligation. | Missed | Passed |
The instructions your model reads when the skill loads.
Identify which Article 50 transparency duties (Regulation (EU) 2024/1689) apply to a system, decide
what must be implemented and by when, and produce a formal mini-report plus a per-obligation
compliance checklist. Works standalone, or ingests a prior classifier ASSESSMENT CONTEXT block.
Important: This skill provides structured Art. 50 transparency guidance based on the EU AI Act (Regulation (EU) 2024/1689), the final Code of Practice on Transparency of AI-Generated Content (10 Jun 2026), and the Commission's draft Art. 50 Guidelines (8 May 2026). It is not legal advice; final decisions need qualified counsel, and only the CJEU can authoritatively interpret Art. 50. • Penalty band: non-compliance is Tier 2 — up to EUR 15,000,000 or 3% of worldwide annual turnover (Art. 99(4)(g); €750k for EU bodies). Not the €35M / 7% band (that is Art. 5 prohibited practices). • Dates: Art. 50 applies from 2 August 2026 (Chapter IV general application — not the 2 Aug 2025 tranche). The 50(2) legacy-system marking grace to 2 December 2026 is now adopted — the Digital Omnibus cleared the European Parliament (Jun 2026) and the Council (final green light, 29 Jun 2026) and is awaiting OJ publication ("shortly"; in force the 3rd day after). Treat 2 Dec 2026 as near-settled; only until the OJ text appears does the statutory 2 Aug 2026 date formally still govern legacy systems. Recommend a quick live OJ / law-tracker check. • Soft law: the Code of Practice is final but voluntary and under adequacy assessment (still pending) — adherence is not conclusive evidence of compliance. The Commission Guidelines are still draft (8 May 2026; consultation closed 3 Jun 2026). See references/sources.md for the live source manifest and uncertainty tiers.
Before intake, offer the user a route — do not default straight to the full report:
How deep do you need to go? 1. Quick triage — a yes/no on which duties bite and the earliest deadline (a few questions, a short answer). 2. Full assessment — the formal mini-report + per-obligation checklist + portable compliance block. 3. Implementation plan — what product / legal / engineering actually has to build, per triggered duty.
test cases passed, vs 8 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.