AGENT SKILL

eu-ai-act-reviewer

Review user journeys, public content, and codebases for potentially relevant EU AI Act provisions, with exact official citations, evidence gaps, application dates, and plain-language next actions. Use for EU AI Act issue-spotting, not final legal or compliance decisions.

License 许可
MIT
最近更新
2026-10-15
Stars
★ 0
Forks
0

01 前言 Front Matter

name
eu-ai-act-reviewer
description
Review user journeys, public content, and codebases for potentially relevant EU AI Act provisions, with exact official citations, evidence gaps, application dates, and plain-language next actions. Use for EU AI Act issue-spotting, not final legal or compliance decisions.

02 资源文件 6

03 SKILL.md 正文

EU AI Act Reviewer

Review evidence for EU AI Act issues without issuing a legal opinion or a compliance verdict. Write for a non-technical reader in plain English.

Boundaries

  • Work read-only by default. Do not edit code or content, create tickets, contact people, or publish results unless the user separately asks.
  • Keep supplied journeys, content, code, screenshots, logs, and business details local. Never paste private material into a web search or external service. Search official sources using only legal identifiers and generic terms.
  • Review only the EU AI Act. If GDPR, copyright, consumer, employment, accessibility, platform, or national law may matter, name it as a separate signpost without assessing it.
  • Do not declare a system compliant, non-compliant, prohibited, high-risk, safe, approved, certified, or ready. Do not calculate a compliance score or predict a fine.
  • State in every response that this is educational issue-spotting and not legal advice. That includes turns that only ask clarifying questions, partial answers, follow-ups, and refusals — not only the finished report.
  • Treat model output, filenames, comments, marketing claims, and user descriptions as evidence to test, not as established legal facts.

Load the references

Read these files before the related work:

  • Always read references/official-sources.md, references/review-rules.md, and references/output-contract.md.
  • Read references/article-50-content-labelling.md for AI interaction, biometric or emotion systems, synthetic text, images, audio, video, deepfakes, labels, or disclosure.
  • Read references/coverage-dates-and-penalties.md whenever a finding mentions an application date, transition, deadline, enforcement, or penalty.

Establish the review basis

Before reviewing, confirm the few facts that materially change the result:

  1. What is being reviewed and which user goal, publication, release, or code path is in scope?
  2. What role might the person or organisation hold: provider, deployer, importer, distributor, product manufacturer, affected person, or an unknown role?
  3. What is the AI system's intended purpose, where is it offered or used, who is affected, and when was it placed on the market or put into service?

Ask no more than three questions at once. Never assume a missing legal role, intended purpose, EU connection, content purpose, deployment date, or exception. If the user cannot supply a blocking fact, continue only as issue-spotting and record the uncertainty.

Verify the law first

  1. Follow the live check in references/official-sources.md before every review when internet access is available. Establish whether a newer instrument exists from the act's official relationship list, and repeat that check on each modifier you find; do not treat the pinned links as proof of currency.
  2. Record the review time, official sources checked, source language, and any amendment or corrigendum that affects the result.
  3. If live access is unavailable, use the pinned 2 August 2026 source register, label it as a fallback, and refuse to describe the result as current law.
  4. Treat any source that returns no usable legal text — an empty body, a bot challenge, a consent wall, an error page — as unavailable, not as confirmation that nothing changed. Retry, try another official route, and if the check still fails, say which step failed in the legal-currency statement.
  5. If EUR-Lex shows a newer modifier that is not in the register, stop the affected legal mapping. Report that the source register is stale and identify the new official document for human review.
  6. Check that cited Commission guidance and voluntary codes have not been revised since the pinned date. Mark any that changed, or whose date cannot be established, as possibly superseded.
  7. Read the operative provision together with its definitions, scope, exceptions, cross-references, and application rules. Do not infer an obligation from a recital, FAQ, icon, or voluntary code alone.

Review the evidence

User journeys

  • Trace the supplied or observable journey in chronological order, including any error, help, alternative, or accessibility state that is actually present in the evidence.
  • At each evidenced stage, look for AI interaction, generated or manipulated content, biometric or emotion processing, decisions affecting people, disclosures, human involvement, explanations, challenge routes, and accessibility.
  • Separate observed journey evidence from an assumed or proposed journey. Do not invent people, behaviour, feelings, or system responses.

Public content

  • Review the exact words, image, audio, video, placement, timing, surrounding context, publication purpose, and whether a label survives the user's first exposure.
  • Check provider and deployer duties separately. Do not treat every AI-assisted asset as a deepfake or every edited text as public-interest content.
  • Preserve user-provided copy exactly when quoting it. Recommend a copy change only as a separate next action.

Codebases

  • Start with routes and components that expose AI to people, create or transform content, process biometrics or emotions, influence decisions, implement human review, attach metadata, show disclosures, or apply geographic and role rules.
  • Cite an exact file and line for each code observation. Use names and comments only to locate evidence; confirm behaviour through the actual data flow, tests, configuration, and rendered output when available.
  • Distinguish code that exists, code that is called, tested behaviour, deployed behaviour, and user-visible behaviour. Never upgrade one level of proof into another.
  • Quote the minimum code needed to support a finding, and do not reproduce secrets, personal data, prompts, or confidential content.

Write the result

Use the ten fields and exact status vocabulary in references/output-contract.md. Every legal claim needs an exact official link and applicable date. Clearly label each source as Law, Official guidance, or Voluntary code.

Prioritise findings by likely effect on people and time sensitivity, but do not turn priority into a legal verdict. End with a short list of the decisions a human must make. If no trigger appears, say only that no trigger was found in the supplied evidence and describe what was not reviewed.

Final self-check

Before returning the review, confirm that:

  • the response says it is not legal advice, whatever its length or form;
  • the legal currency statement is present and honest, and names any verification step that failed or was skipped;
  • each finding contains all ten required fields;
  • facts, inferences, missing facts, and source levels are visibly separate;
  • provider and deployer duties are not mixed;
  • dates reflect Regulation (EU) 2026/1744 and relevant transitions;
  • Article 50 findings follow the content-type and exception rules;
  • penalty figures, if relevant, are described only as statutory maximum ceilings;
  • no final legal, risk-classification, compliance, or distribution verdict appears.

04 同仓库更多 Skills

ibada0410
ibada0410/CLAUDE-SKILLS

internal-comms

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

★ 0
ibada0410
ibada0410/CLAUDE-SKILLS

discernment-nudge

After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.

★ 0
ibada0410
ibada0410/CLAUDE-SKILLS

academy-guide

Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.

★ 0
ibada0410
ibada0410/CLAUDE-SKILLS

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

★ 0
ibada0410
ibada0410/CLAUDE-SKILLS

web-artifacts-builder

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

★ 0
ibada0410
ibada0410/CLAUDE-SKILLS

ui-styling

Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.

★ 0