eu-ai-act-compliance
Skill2 starsChanged 13 days agoMITView on GitHub
EU AI Act compliance logging and requirements. Use this skill when ensuring transparency, human oversight, and record-keeping per Regulation (EU) 2024/1689 — even if they just say "add compliance logging" or "make sure this is EU AI Act compliant". Not for security-code-auditor, privacy-first.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- cookieMonsterDev/agents-skillstheir own version, first seen Nov 1, 2026
- DirtyBeastAfterTheToad/EU-AI-Act-Compliance-Codebase-Audit-Skilltheir own version, first seen Oct 13, 2026
- legalithm-org/legalithmtheir own version, first seen Aug 4, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- cookieMonsterDev/agents-skills★ 7same name
- legalithm-org/legalithm★ 1same name
- DirtyBeastAfterTheToad/EU-AI-Act-Compliance-Codebase-Audit-Skill★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository63 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/avoid-ai-writing/AGENTS.mdAGENTS.md
- .agents/skills/do-web-doc-resolver/AGENTS.mdAGENTS.md
- .agents/skills/skill-evaluator/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms-full.txtllms.txt
- llms.txtllms.txt
- accessibility-auditorSkill
- agent-browserSkill
- agentic-abstentionSkill
- agents-mdSkill
- api-design-firstSkill
- architecture-diagramSkill
- avoid-ai-writingSkill
- cicd-pipelineSkill
- cloudflare-worker-apiSkill
- codacySkill
- codeberg-apiSkill
- code-review-assistantSkill
- css-render-performanceSkill
- database-devopsSkill
- debuggerSkill
- delegateSkill
- dependency-upgradesSkill
- dist-channel-selectionSkill
- docs-hookSkill
- document-rendering-and-locatorsSkill
- dogfoodSkill
- dora-reportSkill
- do-web-doc-resolverSkill
- durable-objectsSkill
- git-github-workflowSkill
- goap-agentSkill
- implementerSkill
- intent-classifierSkill
- iterative-refinementSkill
- jules-delegatorSkill
- learnSkill
- lifecycle-managementSkill
- local-context-sanitizationSkill
- memory-contextSkill
- migration-refactoringSkill
- nested-build-isolationSkill
- privacy-firstSkill
- progressive-deliverySkill
- pwa-offline-syncSkill
- reader-ui-uxSkill
- readme-best-practicesSkill
- secrets-managementSkill
- secure-invite-and-accessSkill
- security-code-auditorSkill
- shell-script-qualitySkill
- skill-creatorSkill
- skill-evaluatorSkill
- static-analysisSkill
- testing-strategySkill
- test-runnerSkill
- triz-solverSkill
- turso-dbSkill
- The first 60 shown.
The file
Files
EU AI Act Compliance
When to Use
- User asks to ensure EU AI Act compliance for logging or transparency
- Need to implement human oversight or record-keeping per Regulation (EU) 2024/1689
- Even if they just say "add compliance logging" or "make sure this is EU AI Act compliant"
Quick Start
import { AIActLogger } from "./eu-ai-act-compliance";
const logger = new AIActLogger({
systemId: "<PROJECT_ID>",
providerName: "<ORG_NAME>",
riskClassification: "limited_risk",
});
await logger.logOperation({
operation: "ai_inference",
inputData: { source: "user_request", hash: "sha256:abc123..." },
outputData: { result: "example_result", confidence: 0.85 },
humanOversight: { reviewerId: "user_123", decision: "approved", timestamp: new Date().toISOString() },
});Core Concepts
| Concept | Article | Description |
| Automatic Logging | Art. 12 | Record events over system lifetime |
| Transparency | Art. 50 | Disclose AI interaction to users |
| Human Oversight | Art. 14 | Enable human intervention |
| Data Governance | Art. 10 | Document training/validation data |
| Retention | Art. 19 | Keep logs minimum 6 months |
Risk Classification
Limited Risk (Article 50)
Systems interacting with natural persons must:
- Disclose AI interaction at first contact (Art. 50.1).
- Mark synthetic content as AI-generated (Art. 50.2).
High Risk (Chapter III, Articles 8-17)
Systems in Annex III (recruitment, credit scoring, etc.) require:
- Risk management (Art. 9) & Data governance (Art. 10).
- Technical documentation (Art. 11) & Automatic logging (Art. 12).
- Human oversight design (Art. 14) & CE marking (Art. 48).
Logging Requirements (Article 12)
interface AIActLogEntry {
timestamp: string; // ISO 8601
systemId: string;
operation: string;
inputData: { source: string; hash: string; description: string };
outputData: { result: string; confidence?: number; explanation?: string };
humanOversight?: { reviewerId: string; decision: "approved" | "rejected" | "modified"; timestamp: string };
retentionUntil: string; // Min 6 months
}Compliance Checklist
- AI interaction disclosure implemented (Art. 50.1).
- Synthetic content marking enabled (Art. 50.2).
- Provider contact information published.
- High-risk: Risk management & Data governance documented.
- High-risk: Automatic logging & 6-month retention configured.
References
references/eu-ai-act-articles.md- Key article analysis
See Also
security-code-auditor— General security auditsprivacy-first— Email/personal data prevention
Rationalizations
| Rationalization | Reality |
| "Small change, no logging." | AI interactions fall under transparency (Art. 50). |
| "Oversight later." | Oversight-by-design is mandatory for high-risk (Art. 14). |
Red Flags
- Deploying without interaction disclosure.
- High-risk systems without automated record-keeping.
Voice & Context
- Default:
professional+blog - Reference:
voice-profilesskill for definitions and auto-detection.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

