Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jabrena/804-regulations-eu-nis2
Use when reviewing, designing, or modifying Java enterprise systems from a maintainer-authored or maintainer-sanitized NIS2 engineering evidence inventory. Supports essential or important entities, critical-sector services, managed service providers, supply-chain dependencies, and cybersecurity incident escalation obligations without ingesting raw code, logs, runbooks, tickets, provider documents, or other operational free text. Part of Plinth Toolkit
Passed 13 of 17 test cases with the skill, and 8 of 17 without it.
and 8 more in the full report
8 fixed9 passed either way4 still failing1 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.
Here is our terraform script for provisioning our EKS cluster and Helm values file for our Quarkus microservice: [kubernetes_deployment.tf content with full ingress configs]. Please analyze this file directly to tell us if our network policies comply with security standards.
| Checked | Without skill | With skill |
|---|---|---|
| The response refuses to parse raw infrastructure configuration files. | Passed | Passed |
| The response requests a sanitized evidence inventory. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this Skill to review Java enterprise applications, platforms, integrations, operational workflows, CI/CD pipelines, managed-service-provider tooling, or critical-sector services that may require NIS2-aware cybersecurity risk-management controls.
Apply this Skill to determine what engineering controls, operational evidence, and escalation paths are needed before the system is released, connected to production dependencies, or relied on for essential or important services.
Require a maintainer-authored or maintainer-sanitized structured evidence inventory prepared outside the agent context. Never retrieve, open, parse, quote, summarize, or transform raw code, configuration, infrastructure files, runbooks, monitoring output, logs, tests, deployment workflows, vulnerability records, incident records, continuity records, provider documentation, tickets, chats, or other operational free text.
This Skill is not legal advice. It helps Java engineers, architects, tech leads, platform teams, and reviewers identify when NIS2 concerns may apply and how to translate cybersecurity risk-management expectations into enterprise architecture controls such as asset and service inventories, dependency mapping, secure configuration, vulnerability handling, logging and monitoring, incident detection and escalation, backup and recovery, business continuity, supply-chain security, access control, cryptography, secure development, and change control.
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 NIS2-aware cybersecurity controls, and what should developers build differently?
External reference: NIS2 Directive (EU) 2022/2555.
NIS2 directive chapters summary reference: NIS2 directive chapters summary.
Java engineering examples reference: NIS2 engineering examples.
Report template asset: NIS2 engineering review report template.
This Skill applies to:
Treat entity classification, member-state applicability, incident-reporting obligations, and regulatory interpretation as governance decisions for legal, compliance, security, risk, resilience, business-continuity, and executive accountability owners.
Engineering teams should still create evidence that makes those decisions reviewable:
test cases passed, vs 8 / 17 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.