Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jabrena/808-regulations-eu-digital-markets-act
Use when reviewing, designing, or modifying Java enterprise systems that may support EU Digital Markets Act gatekeeper-platform concerns, core platform services, interoperability, business-user data access, consent-dependent data combination, ranking, self-preferencing, advertising transparency, or anti-circumvention controls. This should trigger for requests such as Review a Java platform for DMA controls; Design interoperability and business-user data access evidence; Add ranking, consent, pre
Passed 19 of 22 test cases with the skill, and 13 of 22 without it.
and 8 more in the full report
8 fixed11 passed either way1 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
We operate a Java advertising analytics pipeline and portal that provides reports to business merchants and combines user interaction data across services. Could you assess our API contracts, export workflows, and consent mechanisms for DMA compliance? Output an engineering assessment report that outlines the scope of data flows, evidence analyzed, identified compliance gaps, concrete technical controls needed, and a release decision recommendation.
| Checked | Without skill | With skill |
|---|---|---|
| The report states that combining user data across services requires explicit opt-in consent under DMA Article 5(2). | Passed | Passed |
| The report requires providing daily access to ad performance metrics and pricing data free of charge. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this Skill to review Java enterprise applications, platform APIs, marketplaces, app stores, advertising systems, ranking systems, identity services, browser or operating-system integrations, messaging interoperability, business-user portals, data access APIs, analytics pipelines, CI/CD workflows, or operational tooling that may support Digital Markets Act (DMA) gatekeeper-platform obligations.
Apply this Skill to determine what engineering controls, compliance evidence, and escalation paths are needed before a system is released, connected to production platform data, exposed to business users, or used to operate a core platform service.
This Skill is not legal advice. It helps Java engineers, architects, tech leads, platform teams, product teams, and reviewers identify when DMA concerns may apply and how to translate gatekeeper-platform expectations into enterprise architecture controls such as interoperability interfaces, business-user data access APIs, consent and preference evidence, ranking and self-preferencing audit signals, advertising transparency evidence, app-store or marketplace access controls, anti-circumvention guardrails, observability, change control, documentation, and compliance evidence handoff.
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, a gatekeeper designation, a core platform service classification, or a final regulatory determination.
The main question is:
When does a Java enterprise platform require DMA-aware gatekeeper controls, and what should developers build differently?
External reference: Digital Markets Act Regulation (EU) 2022/1925.
Digital Markets Act chapters summary reference: DMA chapters summary.
Java engineering examples reference: DMA engineering examples.
Report template asset: DMA engineering review report template.
This Skill applies to:
Treat gatekeeper designation, core platform service scope, obligation applicability, consent interpretation, self-preferencing assessments, fair and reasonable access terms, suspension or exemption requests, and regulatory interpretation as governance decisions for legal, compliance, platform governance, product, privacy, security, risk, competition, and executive accountability owners.
Engineering teams should still create evidence that makes those decisions reviewable:
test cases passed, vs 13 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.