Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jabrena/807-regulations-eu-digital-services-act
Use when reviewing, designing, or modifying Java enterprise systems that may support intermediary services, hosting services, online platforms, marketplaces, content moderation, recommender systems, advertising delivery, complaint workflows, transparency reporting, or systemic-risk evidence under the EU Digital Services Act. This should trigger for requests such as Review a Java online platform for DSA controls; Design notice-and-action or appeal workflows; Add recommender, ad transparency, mode
Passed 19 of 22 test cases with the skill, and 13 of 22 without it.
and 3 more in the full report
6 fixed13 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
We use a machine learning ranking engine in Java to generate personalized user feeds. Our team currently logs only the final recommended item IDs without storing the main ranking parameters, personalization flags, or option toggles given to users. Assess this logging practice and recommend necessary technical controls.
| Checked | Without skill | With skill |
|---|---|---|
| Requirement to log primary ranking parameters used to determine feed ordering. | Passed | Passed |
| Requirement for user controls enabling modifications to main recommender parameters. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this Skill to review Java enterprise applications, online platforms, marketplaces, hosting services, content moderation tools, recommender systems, advertising systems, complaint workflows, transparency reporting pipelines, operational dashboards, or audit evidence that may require Digital Services Act-aware engineering controls.
Apply this Skill to determine what engineering controls, operational evidence, and escalation paths are needed before a Java system is released, connected to production traffic, used for online platform operations, or relied on for content moderation, recommender, advertising, complaint, or systemic-risk workflows.
This Skill is not legal advice. It helps Java engineers, architects, tech leads, platform teams, trust-and-safety teams, and reviewers identify when Digital Services Act concerns may apply and how to translate online platform expectations into enterprise architecture controls such as content decision audit logs, moderation workflow state, notice intake and response tracking, recommender and ranking explanation evidence, advertising transparency metadata, user controls, complaint and appeal workflows, risk assessment evidence, incident escalation, data access for auditors or researchers where applicable, and privacy-safe observability.
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 Digital Services Act-aware online platform controls, and what should developers build differently?
External reference: Regulation (EU) 2022/2065 Digital Services Act.
Digital Services Act chapters summary reference: Digital Services Act chapters summary.
Java engineering examples reference: Digital Services Act engineering examples.
Report template asset: Digital Services Act engineering review report template.
This Skill applies to:
Treat intermediary classification, hosting or online-platform classification, very-large-online-platform or very-large-online-search-engine scope, illegal-content policy, advertising or recommender interpretation, audit or researcher access duties, systemic-risk conclusions, and regulatory interpretation as governance decisions for legal, compliance, trust-and-safety, privacy, security, product, risk, 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.