Agent skill

806 Regulations Eu Data Act

by jabrena in jabrena/plinth

A skill your agent uses when reviewing, designing, or modifying Java enterprise systems that expose, exchange, store, process, export, or port data across users, businesses, connected products…

Apache-2.0Auto-check passedData & Analytics

Install 806 Regulations Eu Data Act

skills CLI
$ npx skills add jabrena/plinth --skill 806-regulations-eu-data-act -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jabrena/plinth 806-regulations-eu-data-act --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/806-regulations-eu-data-act .claude/skills/806-regulations-eu-data-act && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
806-regulations-eu-data-act
GitHub stars
447
Token cost
~3k tokens
SKILL.md length
1,247 words
Files
4 (incl. references, assets)
Skills in repo
124
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when reviewing, designing, or modifying Java enterprise systems that expose, exchange, store, process, export, or port data across users, businesses, connected products…

  • Modifying Java enterprise systems that expose
  • SKILL.md covers Scope, EU Data Act Engineering Review, Constraints and When to use this skill, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Port data across users

What it does

806 Regulations Eu Data Act is an agent skill from jabrena/plinth. Use when reviewing, designing, or modifying Java enterprise systems that expose, exchange, store, process, export, or port data across users, businesses, connected products, cloud providers, APIs, event streams, AI data pipelines, data spaces, or SaaS platforms and need EU Data Act engineering controls. This should trigger for requests such as Review a Java platform for EU Data Act controls; Design data access and portability evidence; Add data-sharing request workflows, export formats, interoperability…

Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files and assets (for example `assets/reports/806-eu-data-act-engineering-review-report-template.md`, `references/806-regulations-eu-data-act-chapters-summary.md` and `references/806-regulations-eu-data-act-engineering-examples.md`).

It sits in Data & Analytics, covering Data pipelines and ETL. It works with Java. The repository describes itself as: Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers. The licence is Apache-2.0.

When your agent uses it

  • Modifying Java enterprise systems that expose
  • Port data across users
  • Connected products
  • Cloud providers

Example prompts

  • “/806-regulations-eu-data-act”

What it can do on your machine

Read from SKILL.md and the folder at commit dca88dc. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • eur-lex.europa.eu

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

806 Regulations Eu Data Act loads about 3k tokens when it runs, and up to ~14k if it reads all its reference files. Until then it costs about 182 tokens; SKILL.md has 1,247 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~182
When it runs · the whole SKILL.md, loaded when a task matches
~3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~14k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jabrena/plinth at commit dca88dc, republished under its Apache-2.0 licence (© jabrena). 1,247 words, ~3,038 tokens.

Download SKILL.mdSave it as .claude/skills/806-regulations-eu-data-act/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
806-regulations-eu-data-act
description
Use when reviewing, designing, or modifying Java enterprise systems that expose, exchange, store, process, export, or port data across users, businesses, connected products, cloud providers, APIs, event streams, AI data pipelines, data spaces, or SaaS platforms and need EU Data Act engineering controls. This should trigger for requests such as Review a Java platform for EU Data Act controls; Design data access and portability evidence; Add data-sharing request workflows, export formats, interoperability, metadata, audit logs, cloud-switching support, non-personal data safeguards, or trade-secret handoffs; Assess Data Act engineering readiness before production release. Part of Plinth Toolkit
license
Apache-2.0
metadata.author
Juan Antonio Breña Moral
metadata.version
0.19.0

EU Data Act Regulation for Java Enterprise Data Access and Portability Engineering

Use this Skill to review Java enterprise applications, SaaS platforms, APIs, data pipelines, connected-product integrations, event-driven systems, data spaces, and cloud services that may require EU Data Act-aware engineering controls.

Apply this Skill to determine what engineering controls, operational evidence, and owner handoffs are needed before a system exposes data access, data-sharing, export, portability, interoperability, cloud-switching, non-personal data, or data-processing-service workflows.

This Skill is not legal advice. It helps Java engineers, architects, tech leads, platform teams, data-governance teams, and reviewers identify where Data Act concerns may apply and how to translate those concerns into enterprise architecture controls such as data inventories, access authorization, user and recipient request workflows, machine-readable export formats, metadata, API quality of service, audit logs, cloud-switching support, interoperability evidence, non-personal data safeguards, trade-secret or sensitive-data handoff, contract evidence, and operational controls for data access requests.

The purpose of this Skill is to increase awareness of potential gaps in the system and create engineering evidence for qualified review. The response produced by this Skill does not represent legal advice, a legal opinion, or a final regulatory determination.

The main question is:

When does a Java enterprise system require EU Data Act-aware data access, sharing, portability, interoperability, or cloud-switching controls, and what should developers build differently?

External reference: Regulation (EU) 2023/2854 Data Act.

EU Data Act chapters summary reference: EU Data Act chapters summary.

Java engineering examples reference: EU Data Act engineering examples.

Report template asset: EU Data Act engineering review report template.

Scope

This Skill applies to:

  • Java systems that expose, exchange, store, process, export, port, or derive data through REST APIs, GraphQL APIs, Kafka topics, batch exports, object storage, data lakes, SaaS APIs, data spaces, connected-product integrations, or cloud services
  • Spring Boot, Quarkus, Micronaut, and framework-agnostic Java services with user-facing data access, third-party sharing, export, portability, interoperability, cloud-switching, or non-personal data governance requirements
  • Systems with data holder, user, data recipient, third-party recipient, public-sector exceptional-need, data processing service, data-space participant, smart-contract, or provider-switching signals
  • Data access request workflows, authorization checks, consent and entitlement evidence, API quality-of-service records, export jobs, schema registries, metadata catalogs, audit logs, retention and deletion controls, and provider exit runbooks
  • Product data, related service data, exportable data, metadata, non-personal data, mixed personal and non-personal datasets, trade secrets, commercially sensitive data, cloud customer data, and data-sharing agreements

EU Data Act Engineering Review

Treat applicability, data holder status, user entitlement, data recipient role, public-sector exceptional need, trade-secret decisions, contract interpretation, cloud-switching obligations, international access restrictions, and regulatory interpretation as governance decisions for legal, compliance, privacy, data governance, security, product, procurement, cloud, risk, and business owners.

Engineering teams should still create evidence that makes those decisions reviewable:

  • Which products, services, APIs, event streams, datasets, exports, data stores, cloud services, and providers are in scope
  • Which product data, related service data, exportable data, metadata, personal data, non-personal data, trade secrets, or commercially sensitive data can be accessed or shared
  • Which users, data holders, data recipients, third parties, cloud customers, public-sector requesters, and provider owners participate in data workflows
  • Which authorization, entitlement, purpose limitation, audit, request, refusal, suspension, deletion, and handoff evidence exists
  • Which portability APIs, machine-readable formats, metadata, schemas, quality-of-service expectations, interoperability controls, and switching runbooks are implemented
  • Which unresolved legal, contractual, trade-secret, personal-data, international-transfer, or public-sector request questions require qualified owner review

Constraints

Translate EU Data Act concerns into engineering controls for Java enterprise systems. Do not provide legal advice or replace review by legal, compliance, privacy, data governance, security, product, procurement, cloud, risk, or business owners.

  • NOT LEGAL ADVICE: Frame findings as data access, portability, interoperability, cloud-switching, and operational engineering controls; recommend qualified review for applicability, roles, contracts, trade secrets, cloud-switching obligations, and regulatory interpretation
  • SCOPE FIRST: Identify whether the system has connected-product, related-service, data holder, user, data recipient, third-party sharing, public-sector exceptional-need, data-processing-service, data-space, or smart-contract signals before recommending controls
  • DATA INVENTORY: Require traceable inventories for datasets, metadata, APIs, Kafka topics, object stores, exports, data products, data owners, processors, recipients, and provider systems
  • ACCESS AUTHORIZATION: Verify entitlement, authentication, authorization, purpose, request origin, recipient role, least privilege, revocation, refusal, suspension, deletion, and audit evidence for data access requests
  • PORTABILITY AND INTEROPERABILITY: Review machine-readable export formats, API contracts, schemas, metadata, quality-of-service evidence, bulk download, real-time access where technically feasible, standards, and provider switching support
  • NON-PERSONAL DATA SAFEGUARDS: Preserve non-personal data controls, mixed-dataset separation, confidentiality, international governmental access safeguards, and security during access, transfer, export, and switching
  • TRADE SECRET HANDOFF: Do not decide trade-secret disclosure boundaries; identify trade-secret or commercially sensitive data and route confidentiality measures, refusals, suspensions, or exceptions to qualified owners
  • CONTRACT AND CLOUD SWITCHING EVIDENCE: Review data-sharing terms, access terms, compensation evidence, provider exit information, exportable data registers, switching runbooks, continuity controls, and erasure evidence
  • OPERATIONAL REQUEST CONTROLS: Require observable request intake, SLA handling, identity checks, approvals, audit logs, evidence-safe logging, dispute or complaint routing, support runbooks, and release gates for data access workflows
Show full SKILL.md (427 more words)Show less

When to use this skill

  • Review a Java platform for EU Data Act controls
  • Design data access and portability evidence for a Java service
  • Add data-sharing request workflows, export formats, metadata, audit logs, interoperability, or cloud-switching support
  • Assess Data Act engineering readiness before production release
  • Check whether Java APIs, Kafka topics, cloud services, or data products support Data Act-aware owner handoffs

Workflow

  1. Read regulation chapters summary, engineering examples, and report template

Read references/806-regulations-eu-data-act-chapters-summary.md, references/806-regulations-eu-data-act-engineering-examples.md, and assets/reports/806-eu-data-act-engineering-review-report-template.md in that order. Use the chapters summary for Data Act chapter, article, data access, portability, cloud-switching, interoperability, enforcement, and owner-handoff context. Use the engineering examples for Java control patterns such as data inventory, access authorization, portability APIs, export formats, metadata, audit logs, cloud-switching evidence, non-personal data safeguards, trade-secret handoffs, data-sharing request workflows, contract evidence, and operational controls. Do not start implementation review until the chapters summary, examples reference, and report template are understood.

  1. Classify the data access and portability scope

Identify service context, possible connected-product or related-service signals, data holder signals, user and recipient roles, public-sector exceptional-need signals, cloud or data-processing-service signals, data-space or smart-contract signals, system owner, data owner, privacy owner, security owner, product owner, provider owner, deployment environments, datasets, metadata, APIs, event streams, data stores, exports, retention, and provider-switching pathways. Escalate unclear applicability, data holder status, user entitlement, data recipient role, trade-secret decisions, contract interpretation, cloud-switching obligations, international access restrictions, or regulatory interpretation to qualified owners.

  1. Review implementation and operational evidence

Review Java code, API contracts, DTOs, serializers, schema registries, Kafka contracts, batch exports, object storage layouts, metadata catalogs, access-control rules, request workflows, audit logs, privacy controls, tests, runbooks, cloud contracts, provider exit documentation, support workflows, monitoring, and release evidence. Check for gaps between claimed controls and reviewable evidence.

  1. Recommend engineering controls

Map Data Act concerns to engineering actions: data inventory, role and entitlement evidence, request intake, purpose and authorization checks, machine-readable exports, metadata and schema publication, bulk or real-time API access where technically feasible, audit logging, evidence-safe support operations, non-personal data safeguards, mixed-dataset privacy handoff, trade-secret confidentiality measures, data-sharing terms, cloud-switching runbooks, interoperability standards, erasure controls, and release gates.

  1. Generate review report and owner handoffs

Use assets/reports/806-eu-data-act-engineering-review-report-template.md to produce a concise engineering review with scope, evidence reviewed, Data Act risk signals, potential violation or non-compliance signals, engineering gaps, recommended controls, owner handoffs, residual risks, release decision, and validation steps. State explicitly that legal applicability, data holder/user/recipient roles, trade-secret decisions, contract interpretation, cloud-switching obligations, international access restrictions, and regulatory interpretation require qualified owner review.

Reference

For detailed guidance, examples, and constraints, see:

© jabrena, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references, assets) in skills/806-regulations-eu-data-act of jabrena/plinth.

  • SKILL.md
  • assets/reports/806-eu-data-act-engineering-review-report-template.md
  • references/806-regulations-eu-data-act-chapters-summary.md
  • references/806-regulations-eu-data-act-engineering-examples.md

Open the folder on GitHubat commit dca88dc

Compare with similar skills

806 Regulations Eu Data Act next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

806 Regulations Eu Data Act compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
806 Regulations Eu Data Act this skilljabrena/plinth447—~3kAutomated safety check: PassApache-2.0
Authoring Java SDK Tasksastronomer/agents451—~2.6kAutomated safety check: PassApache-2.0
Authoring Language SDK Tasksastronomer/agents451—~1.8kAutomated safety check: PassApache-2.0
Configuring Airflow Language Sdksastronomer/agents451—~2.3kAutomated safety check: NotesApache-2.0
Deploying Java SDK Bundlesastronomer/agents451—~2.8kAutomated safety check: NotesApache-2.0
Azure Messagingmicrosoft/GitHub-Copilot-for-Azure2551 repos~821Automated safety check: PassMIT

Similar skills

  • Authoring Java SDK Tasks

    astronomer/agents

    Writes Airflow task logic in Java, Kotlin, or any JVM language using the Airflow Java SDK.

    451 GitHub stars~2.6k tokensUpdated 3 days ago
    Data & AnalyticsAuto-check passed
  • The language-neutral foundation for Airflow language SDKs — implement task logic in a non-Python language while the DAG stays in Python.

    451 GitHub stars~1.8k tokensUpdated 3 days ago
    Data & AnalyticsAuto-check passed
  • Configures Airflow to run language SDK tasks (Java, Go, and future native SDKs) — register a coordinator, map a queue to it, ensure the runtime/artifact on workers, and tune coordinator options.

    451 GitHub stars~2.3k tokensUpdated 3 days ago
    Data & AnalyticsAuto-check: notes
  • Builds and deploys compiled Airflow Java SDK bundles so workers can run them.

    451 GitHub stars~2.8k tokensUpdated 3 days ago
    Data & AnalyticsAuto-check: notes
  • Azure Messaging

    microsoft/GitHub-Copilot-for-Azure

    Official

    Troubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus.

    255 GitHub starsUsed in 1 repo~821 tokens
    Data & AnalyticsAuto-check passed
  • Azure Eventhub Java

    microsoft/skills

    Official

    Build real-time streaming applications with Azure Event Hubs SDK for Java.

    3.1k GitHub starsUsed in 5 repos~2.8k tokens
    Backend & APIsAuto-check passed

More from jabrena/plinth

All 124 skills in this repo
  • A skill your agent uses when you need to add or review fuzz testing for Java APIs with CATS — including contract-driven negative testing, malformed payload validation, boundary input exploration, CI…

    447 GitHub stars~874 tokensUpdated 3 days ago
    Auto-check passed
  • A skill your agent uses when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, UML Deployment Diagrams…

    447 GitHub stars~3.1k tokensUpdated 3 days ago
    Auto-check passed
  • A skill your agent uses when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning…

    447 GitHub stars~3.2k tokensUpdated 3 days ago
    Auto-check passed
  • A skill your agent uses when you need to set up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template, configuring load tests with…

    447 GitHub stars~842 tokensUpdated 3 days ago
    Auto-check passed
  • A skill your agent uses when you need to set up Java application profiling to detect and measure performance issues — including trusted preinstalled async-profiler v4.x setup, problem-driven…

    447 GitHub stars~903 tokensUpdated 3 days ago
    Auto-check passed
  • A skill your agent uses when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the…

    447 GitHub stars~697 tokensUpdated 3 days ago
    Auto-check passed

Works with

Questions about 806 Regulations Eu Data Act

What does 806 Regulations Eu Data Act do?

A skill your agent uses when reviewing, designing, or modifying Java enterprise systems that expose, exchange, store, process, export, or port data across users, businesses, connected products…. 806 Regulations Eu Data Act is an agent skill from jabrena/plinth. Use when reviewing, designing, or modifying Java enterprise systems that expose, exchange, store, process, export, or port data across users, businesses, connected products, cloud providers, APIs, event streams, AI data pipelines, data spaces, or SaaS platforms and need EU Data Act engineering controls.

When should I use 806 Regulations Eu Data Act?

806 Regulations Eu Data Act fits situations like: modifying Java enterprise systems that expose; port data across users; connected products; cloud providers.

How do I install 806 Regulations Eu Data Act in Claude Code?

Run `npx skills add jabrena/plinth --skill 806-regulations-eu-data-act -a claude-code`. Or copy the skill folder (skills/806-regulations-eu-data-act in jabrena/plinth) into .claude/skills/806-regulations-eu-data-act in your project. Claude Code loads it when a task matches its description.

How do I install 806 Regulations Eu Data Act in Codex?

Run `npx skills add jabrena/plinth --skill 806-regulations-eu-data-act -a codex`. Or copy the skill folder (skills/806-regulations-eu-data-act in jabrena/plinth) into .agents/skills/806-regulations-eu-data-act in your project. Codex loads it when a task matches its description.

Can I use 806 Regulations Eu Data Act in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jabrena/plinth --skill 806-regulations-eu-data-act -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/806-regulations-eu-data-act, .gemini/skills/806-regulations-eu-data-act, .github/skills/806-regulations-eu-data-act and .opencode/skills/806-regulations-eu-data-act in your project.

What does 806 Regulations Eu Data Act need to run?

SKILL.md names no scripts, command-line tools or credentials: 806 Regulations Eu Data Act is instructions for the agent only.

Does 806 Regulations Eu Data Act access the network?

SKILL.md names 1 domain. As links in the text: eur-lex.europa.eu. This is read from the text; nothing was executed.

Is 806 Regulations Eu Data Act safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does 806 Regulations Eu Data Act use?

806 Regulations Eu Data Act is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does 806 Regulations Eu Data Act use?

About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 11k tokens, read only when the agent opens those files.

What are the alternatives to 806 Regulations Eu Data Act?

Skills that share tags, products or a category with 806 Regulations Eu Data Act: Authoring Java SDK Tasks (astronomer/agents, 451 stars), Authoring Language SDK Tasks (astronomer/agents, 451 stars), Configuring Airflow Language Sdks (astronomer/agents, 451 stars) and Deploying Java SDK Bundles (astronomer/agents, 451 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains 806 Regulations Eu Data Act?

jabrena (a GitHub user) maintains it in jabrena/plinth, which has 447 GitHub stars. The repository holds 124 skills in this directory. The repository was last updated on October 7, 2026.

Source: jabrena/plinth on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.