CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nis2

EU NIS2 Directive (Directive (EU) 2022/2555) compliance advisor for essential and important entities: entity classification, Art. 21 risk management measures, Art. 23 incident reporting timelines (24h/72h/1 month), Art. 20 governance obligations, supply chain security (Art. 21(2)(d); coordinated risk assessments Art. 22), gap assessments, policy drafting, ISO 27001 alignment, and penalty exposure analysis. Also covers Commission Implementing Regulation (EU) 2024/2690, the technical/methodological sub-requirements for Art. 21(2) and the significant-incident thresholds binding on DNS/cloud/data-centre/MSP/MSSP/trust-service and other digital entities. Use for NIS2 readiness, transposition questions, ENISA technical implementation guidance, significant-incident thresholds, supervisory differences between essential and important entities, and cross-border coordination.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A high-quality, audit-usable compliance skill body: precise citations, exact thresholds, worked examples, and templates make it directly actionable, and the three reference files are real, well-signaled, and one level deep. The main improvement levers are trimming/offloading the Section 6 national transposition detail into a reference file and tightening a few dense passages, which would lift both conciseness and progressive disclosure to the top anchor.

Suggestions

Move the Member-State transposition detail (Netherlands Cbw/Stb. 2026 187, Austrian NISG 2026, Poland/Portugal dates, CJEU referral IP/26/1499) into a references/transposition-status.md file, keeping only the '24 of 27 transposed' summary, the verification advice, and a read-trigger in SKILL.md — this shortens the body and gives the time-sensitive content a natural home.

Add a read-trigger line for the transposition reference in the 'Reference Files' section, mirroring the pattern already used for the other three files, so national-status questions route to it explicitly.

Tighten a few dense passages (e.g., the SaaS classification note and the Netherlands paragraph) to plain threshold statements; the parenthetical legal citations they carry are already available in the reference files.

DimensionReasoningScore

Conciseness

The body is dense and fact-specific throughout (exact thresholds like '≥250 employees, OR annual turnover >€50M AND balance sheet >€43M', precise article citations, penalty figures) and avoids explaining concepts Claude already knows. However, there are minor instances that could be trimmed or offloaded: Section 6's national transposition detail ('Stb. 2026, 187', 'over 8,000 organisations in 18 sectors', Austrian NISG promulgation numbers) is heavier than SKILL.md needs, matching the 4 anchor ('efficient; minor instances of over-explanation that could be trimmed') rather than the 5 anchor where every token earns its place in the overview.

4 / 5

Actionability

For an instruction-only skill the guidance is fully executable: a task-to-output-format routing table, a four-step classification workflow with exact size thresholds and a worked DSO example ('200 employees and €50M turnover... does NOT exceed the large ceiling'), a deadline-computation table with a concrete ransomware timeline ('Monday 09:00 → early warning by Tuesday 09:00'), and a gap-assessment template specifying evidence to request per Art. 21(2) measure. This matches the 5 anchor's 'specific examples cover the common cases' — well above the 4 anchor's 'minor gaps', since even the penalty table instructs applying 'the entity's actual figures'.

5 / 5

Workflow Clarity

Multi-step processes are clearly sequenced with checkpoints: classification runs Steps 1–4 with an anti-skip guard ('Misclassification is the most common and costly NIS2 error... Always run all three steps'), a worked example that functions as a validation anchor ('State both the default and the designation caveat'), and explicit consequence mapping; the incident workflow computes every deadline 'from the moment of awareness' with a table and a worked example; the gap assessment closes with a prioritization roadmap ('quick wins ≤30 days; structural ≤6 months'). Checklists and self-check instructions match the 5 anchor; the operations are advisory, so destructive/batch validation caps do not apply.

5 / 5

Progressive Disclosure

Structure is good: a dedicated 'Reference Files' section lists all three existing one-level-deep references with per-file descriptions and an explicit read-trigger ('Read the relevant reference file when the user asks for detailed control implementation guidance...'). It falls short of the 5 anchor because the SKILL.md body itself runs ~150 lines and inlines content that could live in a reference — notably the Section 6 transposition-status detail (Dutch/Austrian/Polish/Portuguese specifics) has no corresponding reference file — matching the 4 anchor's 'most content is appropriately placed... minor organization gaps'.

4 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An excellent description: it names the exact legal instrument, enumerates comprehensive and concrete capability areas with precise article references, and closes with an explicit 'Use for' trigger clause covering the natural phrasings a user would employ. The only conceivable critique is density (it packs a lot into three sentences), but there is no padded or vague language — every clause carries a distinct capability or trigger.

DimensionReasoningScore

Specificity

The description lists many concrete, distinct capabilities — 'entity classification, Art. 21 risk management measures, Art. 23 incident reporting timelines (24h/72h/1 month), Art. 20 governance obligations, supply chain security... gap assessments, policy drafting, ISO 27001 alignment, and penalty exposure analysis' — which is comprehensive coverage of the domain, matching the 5 anchor ('multiple specific concrete actions; comprehensive coverage') rather than the 4 anchor's 'minor gaps in coverage'.

5 / 5

Completeness

It explicitly answers both questions: what ('EU NIS2 Directive... compliance advisor for essential and important entities: entity classification... penalty exposure analysis') and when ('Use for NIS2 readiness, transposition questions, ENISA technical implementation guidance, significant-incident thresholds, supervisory differences... and cross-border coordination'). This is the 5 anchor verbatim in structure — clear 'what' plus a concrete 'Use for' trigger clause — and clearly above the 4 anchor where the 'when' is only partially explicit.

5 / 5

Trigger Term Quality

Natural trigger phrases a user would actually say are well covered: 'NIS2 readiness', 'transposition questions', 'ENISA technical implementation guidance', 'significant-incident thresholds', 'supervisory differences between essential and important entities', plus synonyms such as 'Directive (EU) 2022/2555' and the entity-tier names. This matches the 5 anchor's 'comprehensive coverage of natural terms including synonyms'; the 4 anchor ('a few natural terms missing') would require identifiable common user phrasings to be absent, and none are.

5 / 5

Distinctiveness Conflict Risk

The niche is unambiguous — the EU NIS2 Directive, named with its official number '(Directive (EU) 2022/2555)' and its implementing regulation — so it would not trigger for adjacent skills (GDPR, DORA, general cybersecurity or compliance skills). It matches the 5 anchor ('clear niche with distinct triggers; minimal conflict risk') and is well above the 4 anchor's 'minor overlap risk with closely related skills'.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Sushegaad/Claude-Skills-Governance-Risk-and-Compliance

Path

plugins/nis2/skills/nis2/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.