MCPInstall

ai-transparency-reqs

Implements AI transparency requirements under EU AI Act Arts. 13-14 and GDPR Arts. 13-14. Covers user notification of AI interaction, system capability disclosure, limitation documentation, and meaningful information about automated logic. Keywords: AI transparency, EU AI Act, GDPR notification, explainability, automated decision.

Installs
46
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/mukul975/privacy-data-protection-skills --skill ai-transparency-reqs
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads ai-transparency-reqs automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

AI Transparency Requirements

Overview

AI transparency operates at the intersection of two regulatory frameworks: the GDPR's data subject information rights (Arts. 13-14) and the EU AI Act's transparency obligations (Arts. 13-14, 50). Together they require controllers and deployers to provide meaningful, accessible information about AI system capabilities, limitations, decision logic, and personal data processing. This skill implements the combined transparency framework, addressing both the technical explainability challenge of complex ML models and the legal obligation to communicate AI processing in plain language to affected individuals.

GDPR Transparency for AI Systems

Art. 13-14 Information Requirements Applied to AI

When personal data is processed by AI systems, data subjects must receive:

Information ElementGDPR ArticleAI-Specific Application
Purposes of processingArt. 13(1)(c) / 14(1)(c)Specific AI use case, not generic "service improvement"
Lawful basisArt. 13(1)(c) / 14(1)(c)The basis for AI training and for AI inference separately
Legitimate interestArt. 13(1)(d) / 14(2)(b)The specific interest served by AI processing
RecipientsArt. 13(1)(e) / 14(1)(e)AI infrastructure providers, model hosting services
International transfersArt. 13(1)(f) / 14(1)(f)Where AI processing occurs (training and inference locations)
Retention periodArt. 13(2)(a) / 14(2)(a)Training data retention, inference log retention, model lifecycle
Data subject rightsArt. 13(2)(b) / 14(2)(c)Including AI-specific rights: explanation, contestation, human review
Automated decision-makingArt. 13(2)(f) / 14(2)(g)Meaningful information about logic, significance, and envisaged consequences
Source of dataArt. 14(2)(f)Training data sources (categories, not necessarily individual sources)

Art. 13(2)(f) / 14(2)(g) — Meaningful Information About Automated Logic

This is the most challenging transparency requirement for AI systems. The EDPB and Article 29 Working Party have clarified:

What "meaningful information about the logic involved" requires:

  1. System-level explanation: General description of how the AI system works — what factors are considered, what methodology is used, how the model was trained
  2. Purpose and context: Why the AI system is used and what role its output plays in decisions
  3. Key variables: The main data points or features that influence the AI output, without requiring disclosure of proprietary algorithms
  4. Decision criteria: How the model output translates into a decision (e.g., score thresholds, classification categories)
  5. Significance: What the decision means for the data subject in practical terms
  6. Consequences: The potential effects (both intended and foreseeable) of the AI-driven decision

What it does not require:

  • Full disclosure of source code or model weights
  • Mathematical description of the algorithm
  • Proprietary trade secrets (but this does not exempt from meaningful explanation)
  • Explanation of individual model predictions in real-time (though this may be required under Art. 22)

Layered Approach to AI Transparency

The EDPB recommends a layered transparency approach:

LayerContentDelivery
Layer 1: Initial noticeAI is used in processing; general purpose; link to full informationAt point of interaction (banner, tooltip, notification)
Layer 2: SummaryAI system description, key data used, decision logic summary, rights availablePrivacy notice section, AI information page
Layer 3: Detailed informationFull technical description, training data categories, fairness measures, accuracy metrics, limitationsSupplementary documentation, upon request
Layer 4: Individual explanationSpecific factors influencing a particular decision, appeal mechanismUpon request or automatically for significant decisions

EU AI Act Transparency Obligations

Art. 13 — Transparency and Provision of Information to Deployers (High-Risk)

High-risk AI systems (Annex III) must be designed and developed to ensure:

RequirementDescription
InterpretabilitySystem design enables deployers to interpret outputs and use them appropriately
Instructions for useDetailed documentation of capabilities, limitations, intended purpose, foreseeable misuse
Performance metricsAccuracy levels, robustness metrics, known limitations for specific groups
Human oversight infoDescription of human oversight measures and how to implement them
Input data specsDescription of input data the system was designed to process
Training data descriptionRelevant information about training data including provenance and preprocessing

Art. 14 — Human Oversight (High-Risk)

High-risk AI systems must be designed to enable effective human oversight:

  • Clear indication of AI system outputs and confidence levels
  • Ability to correctly interpret AI outputs in context
  • Ability to override or reverse AI decisions
  • Ability to intervene or stop the system ("stop button")
  • Awareness of automation bias risk

Art. 50 — Transparency for Specific AI Systems

AI System TypeTransparency Obligation
AI interacting with personsInform that they are interacting with an AI system (unless obvious from context)
Emotion recognition / biometric categorisationInform about the system's operation and process personal data in compliance with GDPR
AI-generated or manipulated content (deepfakes)Label content as AI-generated in a machine-readable format
AI-generated text on matters of public interestDisclose that the text has been artificially generated or manipulated

Art. 50(1) — AI Interaction Notification

Controllers must inform natural persons that they are interacting with an AI system. This applies to:

  • Chatbots and virtual assistants
  • AI-powered customer service systems
  • Automated email or message generation
  • AI-driven recommendation systems with direct user interface
  • Voice-based AI assistants

Exceptions: where it is obvious from the circumstances and context that the person is interacting with AI (e.g., a robot in a factory setting).

AI Transparency Documentation Framework

Model Card Requirements

For each deployed AI model, maintain a model card containing:

SectionContent
Model overviewName, version, type, developer, deployment date
Intended useSpecific purpose, target users, deployment context
Out-of-scope useUses the model is not designed for; foreseeable misuse
Training data summaryData sources (categories), volume, temporal range, geographic scope, known biases
Performance metricsAccuracy, precision, recall, F1 by relevant subgroup; fairness metrics
LimitationsKnown failure modes, demographic performance disparities, edge cases
Privacy propertiesDifferential privacy applied (epsilon), membership inference test results, training data extraction risk
Human oversightLevel of oversight required, reviewer qualifications, override procedures
Update historyRetraining dates, data updates, performance changes

AI System Transparency Register

Organisations operating multiple AI systems should maintain a central register:

FieldDescription
System IDUnique identifier
System nameHuman-readable name
AI Act classificationUnacceptable / High / Limited / Minimal
PurposeSpecific processing purpose
Data subjects affectedCategories and estimated numbers
Personal data processedAt training and inference
Decision authorityAI decision-support vs. automated decision
Transparency measuresNotification, explanation, documentation
DeployerInternal / External deployment
Registration dateEU AI Act database registration (if high-risk)

Explainability Techniques for Compliance

Global Explainability (System-Level)

Techniques for providing Art. 13(2)(f) "meaningful information about the logic":

TechniqueBest ForLimitation
Feature importance (SHAP, LIME)Identifying key variablesMay oversimplify complex interactions
Decision rules extractionConverting model logic to human-readable rulesLoss of accuracy for complex models
Partial dependence plotsShowing how features affect predictionsAssumes feature independence
Counterfactual explanationsShowing what change would lead to different outcomeComputationally expensive for many features
Attention visualisationTransformer models — showing what the model focuses onAttention does not always equal importance

Local Explainability (Individual Decision)

For Art. 22 right to explanation of individual decisions:

TechniqueDescriptionUse Case
LIMELocal Interpretable Model-agnostic ExplanationsAny model — approximate local behaviour with interpretable model
SHAP valuesShapley Additive Explanations for individual predictionsFeature contribution to specific prediction
Counterfactual"You were denied because X; if X were Y, outcome would be different"Credit, hiring, insurance decisions
AnchorsSufficient conditions for a predictionRule-based explanation of individual case
Concept-basedHigh-level concepts that influenced the decisionWhen features are not directly interpretable

Enforcement Precedents

  • Garante v. OpenAI (2023): Required transparency about AI training data processing, model capabilities, and limitations — privacy notice deemed insufficient for AI system transparency.
  • CNIL v. Clearview AI (SAN-2022-019, 2022): EUR 20M fine — complete absence of transparency about facial recognition AI processing; data subjects had no notice their images were scraped and processed.
  • Austrian DPA v. CRIF (DSB-D213.636, 2023): Credit scoring AI — insufficient explanation of automated decision-making logic per Art. 13(2)(f); data subject received only a score without meaningful information about factors.
  • Dutch DPA v. Tax Authority (SyRI, 2020): Court found algorithmic fraud detection lacked transparency — citizens could not understand how the system assessed them, violating right to private life.
  • AEPD v. CaixaBank (PS/00421/2020, 2021): EUR 6M fine — automated credit decision-making without adequate transparency about the logic involved and significance for data subjects.

Integration Points

  • ai-automated-decisions: Art. 22 explanation requirements integrate with transparency obligations
  • ai-dpia: Transparency assessment is part of DPIA necessity and proportionality analysis
  • ai-act-high-risk-docs: Art. 13 AI Act documentation requirements overlap with transparency framework
  • ai-deployment-checklist: Pre-deployment transparency validation is a checklist item

FAQ

What does the ai-transparency-reqs skill do?

Implements AI transparency requirements under EU AI Act Arts. 13-14 and GDPR Arts. 13-14. Covers user notification of AI interaction, system capability disclosure, limitation documentation, and meaningful information about automated logic. Keywords: AI transparency, EU AI Act, GDPR notification, explainability, automated decision.

How do I install ai-transparency-reqs?

Run npx skills add https://github.com/mukul975/privacy-data-protection-skills --skill ai-transparency-reqs in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/ai-transparency-reqs/ (personal) or .claude/skills/ai-transparency-reqs/ (project).

Which AI agents can use ai-transparency-reqs?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is ai-transparency-reqs safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains ai-transparency-reqs?

It is published by mukul975 in mukul975/privacy-data-protection-skills. It has 46 recorded installs.

More from mukul975/privacy-data-protection-skills

View all →

brazil-lgpd

mukul975/privacy-data-protection-skills

Open the skill to read its SKILL.md instructions.

61 installs

analytics-cookie-consent

mukul975/privacy-data-protection-skills

Managing consent for analytics cookies and implementing privacy-preserving measurement. Covers GA4 privacy configuration, consent mode fallback behavior, aggregate reporting alternatives, and cookieless measurement approaches.

Data & Databases56 installs

audit-report-writing

mukul975/privacy-data-protection-skills

Open the skill to read its SKILL.md instructions.

Docs & Writing50 installs

gdpr-compliance-audit

mukul975/privacy-data-protection-skills

Open the skill to read its SKILL.md instructions.

Security48 installs

conducting-gdpr-dpia

mukul975/privacy-data-protection-skills

Open the skill to read its SKILL.md instructions.

48 installs

backup-retention-erasure

mukul975/privacy-data-protection-skills

Open the skill to read its SKILL.md instructions.

47 installs

Popular docs & writing skills

View category →

grill-with-docs

mattpocock/skills

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

Docs & Writing1.2M installs

lark-markdown

open.feishu.cn

飞书 Markdown:查看、创建、上传、编辑和比较飞书中的原生 Markdown 文件。当用户要操作飞书 Markdown 文件,或比较其远端版本及本地草稿时使用。纯本地 Markdown 文件操作不触发本 skill。不负责将 Markdown 导入为飞书在线文档,也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。

Docs & Writing778.7K installs

writing-beats

mattpocock/skills

Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.

Docs & Writing490.7K installs

writing-shape

mattpocock/skills

Writing, exploit: shape raw material into an article, paragraph by paragraph.

Docs & Writing490.2K installs

writing-fragments

mattpocock/skills

Writing, explore: mine raw fragments, no structure yet.

Docs & Writing489.6K installs

writing-for-agents

mattpocock/skills

Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

Docs & Writing479.3K installs