К основному содержанию
скилл CX Codex

807-regulations-eu-digital-services-act — скилл для Claude Code

Скилл 807-regulations-eu-digital-services-act помогает проверять Java-системы на инженерные контроли для DSA: модерацию, жалобы, рекомендации, рекламу и прозрачность.

Apache-2.0 215 установок ★ 465 обновлён 2026-10-21

Установить в Claude Code · Через Skills CLI (Vercel) Все способы и платформы ↓
npx skills add jabrena/plinth --skill 807-regulations-eu-digital-services-act -a claude-code
Открыть на GitHub

Что делает 807-regulations-eu-digital-services-act

Скилл разбирает Java-системы, которые поддерживают посреднические сервисы, хостинг, онлайн-платформы, маркетплейсы, модерацию контента, рекомендации или рекламу. Он помогает найти, какие данные и процессы нужны для аудита решений, уведомлений пользователей, жалоб, апелляций и отчётности по прозрачности.

В проверку входят журналы решений модерации, состояние рабочих процессов, причины решений, отслеживание уведомлений и ответов, контроль рекомендаций и рекламы, защита несовершеннолетних, оценка рисков и безопасная наблюдаемость. Скилл рассчитан на Java-сервисы, включая Spring Boot и Quarkus. Он не заменяет юридическую оценку: классификацию сервиса, статус VLOP или VLOSE и регуляторные выводы нужно передать юристам и ответственным командам.

Какие задачи решает

  • проверить Java-платформу на контроли DSA
  • спроектировать обработку уведомлений и апелляций
  • зафиксировать причины решений модерации
  • собрать доказательства прозрачности рекомендаций и рекламы
  • подготовить данные для оценки системных рисков

Примеры запросов агенту

  • Проверь Java-платформу и найди пробелы в контролях DSA.
  • Спроектируй для этого сервиса процессы уведомлений, жалоб и апелляций.
  • Покажи, какие журналы и данные нужны для аудита модерации, рекомендаций и рекламы.

Как установить 807-regulations-eu-digital-services-act

1Через Skills CLI (Vercel)

npx skills add jabrena/plinth --skill 807-regulations-eu-digital-services-act -a claude-code

2Вручную: положить файлы

~/.claude/skills/807-regulations-eu-digital-services-act/SKILL.md

Папка скилла целиком; для одного проекта — .claude/skills/807-regulations-eu-digital-services-act/

По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов

Вопросы о 807-regulations-eu-digital-services-act

Как установить 807-regulations-eu-digital-services-act в Claude Code?

Выполните npx skills add jabrena/plinth --skill 807-regulations-eu-digital-services-act -a claude-code, затем проверьте файл ~/.claude/skills/807-regulations-eu-digital-services-act/SKILL.md.

Что делает 807-regulations-eu-digital-services-act?

Скилл помогает проектировать и проверять инженерные контроли DSA в Java-системах: модерацию, уведомления, апелляции, рекомендации, рекламу, прозрачность и аудит.

Заменяет ли скилл юридическую проверку?

Нет. Он формирует инженерные точки контроля и эскалации, а классификацию сервиса, статус VLOP или VLOSE и регуляторные выводы оставляет юридическим и ответственным командам.

Исходный текст

SKILL.md · Apache-2.0
---
name: 807-regulations-eu-digital-services-act
description: 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, moderation, audit, researcher access, or privacy-safe observability evidence; Assess online-platform transparency controls before production release. Part of Plinth Toolkit
license: Apache-2.0
metadata:
  author: Juan Antonio Breña Moral
  version: 0.19.0
---
# EU Digital Services Act Regulation for Java Online Platform Engineering

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](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32022R2065).

Digital Services Act chapters summary reference: [Digital Services Act chapters summary](references/807-regulations-eu-digital-services-act-chapters-summary.md).

Java engineering examples reference: [Digital Services Act engineering examples](references/807-regulations-eu-digital-services-act-engineering-examples.md).

Report template asset: [Digital Services Act engineering review report template](assets/reports/807-eu-digital-services-act-engineering-review-report-template.md).

## Scope

This Skill applies to:

- Java systems that may provide intermediary services, hosting services, online platforms, online marketplaces, or online interfaces where users, traders, or third parties provide content, products, services, or information
- Spring Boot, Quarkus, Micronaut, and framework-agnostic Java services with notice-and-action, content moderation, statement-of-reasons, trusted flagger, complaint, appeal, or out-of-court dispute evidence requirements
- Search, ranking, recommendation, feed, catalog ordering, personalization, advertising, ad repository, trader traceability, transparency reporting, user controls, and minor-protection workflows
- Very large online platform or very large online search engine evidence where applicable, including systemic risk assessment, mitigation, crisis response, independent audit, compliance function, data access, vetted researcher access, and transparency reporting
- Privacy-safe observability, incident escalation, moderation audit logging, user notification, workflow state, data access control, retention, and evidence reconstruction for platform governance

## Digital Services Act Engineering Review

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:

- Which user, trader, platform, marketplace, hosting, recommendation, advertising, complaint, or moderation workflows are in scope
- Which content or product decisions are made, why they are made, which policy or order drove them, who can appeal them, and how decisions are audited
- Which notices, orders, complaints, appeals, trusted flagger reports, and out-of-court dispute outcomes can be tracked end to end
- Which recommender, ranking, advertising, user-control, minor-protection, trader-traceability, and transparency-reporting evidence exists
- Which risk assessment, mitigation, audit, data access, researcher access, incident escalation, and privacy-safe observability evidence is available where VLOP or VLOSE concerns may apply

## Constraints

Translate Digital Services Act concerns into engineering controls for Java enterprise systems. Do not provide legal advice or replace review by legal, compliance, trust-and-safety, privacy, security, product, risk, audit, research-access, or executive accountability owners.

- **NOT LEGAL ADVICE**: Frame findings as online platform engineering controls and escalation points; recommend qualified review for intermediary classification, platform classification, VLOP or VLOSE status, illegal-content determinations, advertising or recommender interpretation, audit or researcher access duties, systemic-risk conclusions, and regulatory interpretation
- **SCOPE FIRST**: Identify whether the Java system supports an intermediary service, hosting service, online platform, online marketplace, online search engine, recommender system, advertising workflow, or VLOP/VLOSE evidence flow before recommending controls
- **MODERATION EVIDENCE**: Require traceable content decision audit logs, statement-of-reasons data, moderation workflow state, affected user notification, policy references, authority order references, and appeal eligibility where applicable
- **NOTICE AND RESPONSE TRACKING**: Verify notice intake, validation, deduplication, triage, action, response, redress, trusted flagger handling, and misuse protections are auditable end to end
- **TRANSPARENCY CONTROLS**: Review transparency reporting, recommender and ranking explanation evidence, ad transparency metadata, user-facing controls, trader traceability, and online interface design evidence
- **USER REDRESS**: Verify complaint, appeal, out-of-court dispute, reinstatement, and support workflows preserve state, deadlines, reasons, evidence, and owner handoffs
- **SYSTEMIC RISK WHERE APPLICABLE**: For potential VLOP or VLOSE scope, require risk assessment, mitigation, crisis response, independent audit, compliance function, data access, vetted researcher access, and transparency evidence
- **PRIVACY-SAFE OBSERVABILITY**: Preserve platform governance evidence without exposing secrets, credentials, personal data, illegal-content details, sensitive user reports, researcher data, or moderation training data unnecessarily
- **RELATIONSHIP TO OTHER RULES**: Use GDPR, AI Act, DORA, NIS2, Data Act, or sector guidance together with this Skill when the same system crosses privacy, AI, cybersecurity, resilience, data access, or platform governance boundaries

## When to use this skill

- Review a Java online platform for Digital Services Act controls
- Design notice-and-action, content moderation, complaint, appeal, or transparency reporting workflows
- Add recommender explanation, ranking controls, advertising transparency metadata, trader traceability, or user controls
- Assess VLOP, VLOSE, audit, researcher access, systemic risk, or crisis-response evidence before production release
- Check whether Java platform logs, metrics, traces, and dashboards preserve DSA evidence without exposing sensitive data

## Workflow

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

Read `references/807-regulations-eu-digital-services-act-chapters-summary.md`, `references/807-regulations-eu-digital-services-act-engineering-examples.md`, and `assets/reports/807-eu-digital-services-act-engineering-review-report-template.md` in that order. Use the chapters summary for Digital Services Act chapter, article, scope, liability, due diligence, transparency, online platform, marketplace, VLOP/VLOSE, supervision, enforcement, and owner-handoff context. Use the engineering examples for Java control patterns such as content decision audit logs, moderation workflow state, notice intake and response tracking, recommender and ranking explanation evidence, ad 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. Do not start implementation review until the chapters summary, examples reference, and report template are understood.

2. **Classify the platform scope**

Identify service context, possible intermediary-service signals, hosting signals, online-platform or marketplace signals, online search or recommender signals, advertising workflows, trader interactions, user-generated content, terms and policy owners, content moderation decisions, user-redress paths, active-recipient evidence, VLOP/VLOSE indicators, deployment geography, data stores, observability systems, and governance owners. Escalate unclear intermediary or platform classification, VLOP/VLOSE status, illegal-content interpretation, advertising or recommender interpretation, audit or researcher access duties, systemic-risk conclusions, and regulatory interpretation to legal, compliance, trust-and-safety, privacy, security, product, risk, audit, research-access, or executive accountability owners.

3. **Review implementation and platform evidence**

Review Java code, configuration, controllers, DTOs, moderation services, policy engines, workflow state machines, persistence models, message schemas, search or ranking code, recommender configuration, ad delivery metadata, user-control settings, complaint and appeal records, transparency reporting jobs, logs, metrics, traces, audit exports, runbooks, tests, deployment workflows, and provider documentation. Check for gaps between claimed DSA controls and reviewable evidence.

4. **Recommend engineering controls**

Map Digital Services Act concerns to engineering actions: scope inventory, content decision audit logs, notice-and-action tracking, statement-of-reasons records, moderation workflow state, trusted flagger routing, misuse protections, complaint and appeal workflows, recommender explanation evidence, ranking controls, user controls, ad transparency metadata, trader traceability, transparency reporting, minor-protection controls, privacy-safe observability, incident escalation, and VLOP/VLOSE risk, audit, and researcher-access evidence where applicable.

5. **Generate review report and owner handoffs**

Use `assets/reports/807-eu-digital-services-act-engineering-review-report-template.md` to produce a concise engineering review with scope, evidence reviewed, Digital Services 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 intermediary classification, platform classification, VLOP/VLOSE status, illegal-content determinations, advertising or recommender interpretation, audit or researcher access duties, systemic-risk conclusions, and regulatory interpretation require qualified owner review.

## Reference

For detailed guidance, examples, and constraints, see:

- [references/807-regulations-eu-digital-services-act-chapters-summary.md](references/807-regulations-eu-digital-services-act-chapters-summary.md)
- [references/807-regulations-eu-digital-services-act-engineering-examples.md](references/807-regulations-eu-digital-services-act-engineering-examples.md)

© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth

Похожие скиллы

Все скиллы по теме «Бэкенд и API» →
mcp-eu-ai-act ark-forge Сервер сканирует код проекта на соответствие требованиям EU AI Act и GDPR. Он находит библиотеки ИИ и оценивает документацию по статьям регламента. CX Codex +1 ★ 12звёзд репо eu-ai-act-reviewer bencium Скилл eu-ai-act-reviewer просматривает пользовательские сценарии, публичный контент и код на предмет возможных требований EU AI Act. Это поиск проблем, а не юридическое заключение. CX Codex +1 1 000установок EU AI Act Compliance lexbeam-software MCP-сервер EU AI Act Compliance классифицирует AI-системы по EU AI Act, проверяет обязанности и сроки. Подходит для разбора рисков, штрафов и требований к документации. CX Codex +1 502установок langchain4j-ai-services-patterns giuseppe-trisciuoglio Скилл langchain4j-ai-services-patterns для Claude Code строит декларативные типобезопасные AI-сервисы на Java через интерфейсы с аннотациями, память и инструменты. CX Codex +1 3 900установок eu-ai-act jgsystemsconsulting Скилл eu-ai-act для Claude Code разбирает требования Акта ЕС об искусственном интеллекте. Подключается к вопросам о классификации ИИ-систем, обязанностях участников и оценке соответствия. CX Codex +1 ★ 93звёзд репо compliance-team-eu-ai-act Alireza Rezvani Плагин compliance-team-eu-ai-act для Claude Code классифицирует ИИ-системы по EU AI Act, планирует оценку соответствия и формирует матрицу обязанностей. ★ 30 251звёзд репо

Из того же набора123

Весь набор →
152-java-performance-gatling Скилл 152-java-performance-gatling настраивает нагрузочное тестирование Gatling в Maven-проекте на Java: зависимости, плагин, симуляции и запуск через ./mvnw gatling:test. CX Codex +1 219установок 004-commands-installation Скилл 004-commands-installation интерактивно переносит встроенные команды проекта из ресурсов Plinth Toolkit в выбранный каталог ассистента. CX Codex +1 219установок 005-agents-installation Скилл 005-agents-installation копирует встроенные определения субагентов в выбранный каталог проекта. Он пригодится, когда нужно подготовить .claude/agents или другую поддерживаемую папку. CX Codex +1 219установок 705-technologies-nosql-mongodb Скилл 705-technologies-nosql-mongodb для Claude Code охватывает MongoDB независимо от Spring Boot, Quarkus или Micronaut. Включается при работе со схемами документов, индексами, агрегациями и транзакциями. CX Codex +1 216установок 316-frameworks-spring-mongodb-migrations-mongock Скилл 316-frameworks-spring-mongodb-migrations-mongock для Claude Code добавляет и проверяет миграции Mongock в приложениях Spring Boot. Он включается при настройке или ревью миграций MongoDB. CX Codex +1 215установок 400-frameworks-quarkus-create-project Скилл 400-frameworks-quarkus-create-project для Claude Code создаёт Maven-проект на Quarkus 3.x через Quarkus CLI и инструменты SDKMAN. Создаёт проект нового сервиса с заданными координатами и расширениями. CX Codex +1 215установок 804-regulations-eu-nis2 Скилл 804-regulations-eu-nis2 для проверки Java-приложений на соответствие требованиям директивы NIS2 к киберустойчивости критически важных сервисов. Анализирует готовую инвентаризацию, не трогая код и логи. CX Codex +1 215установок 808-regulations-eu-digital-markets-act Скилл 808-regulations-eu-digital-markets-act помогает проверять корпоративные Java-системы на соответствие требованиям закона ЕС о цифровых рынках (DMA). CX Codex +1 213установок

Спонсоры проекта

Компании, которые помогают держать аналитику открытой