Works with
Packaged from the source skill for Claude, Codex and 4 more.
About this skill
NIS2 Readiness helps an organization structure the information needed for a readiness review. It includes local utilities for entity scope, incident timelines, security-measure assessments and possible overlap between cyber-related regimes. Inputs are supplied CSV or JSON records, and outputs are findings for human review.
Use this skill when
- Entity records need a first-pass scope review with missing size or sector information made explicit.
- An incident log needs consistent event times and a clear list of open reporting questions.
- A security-measure inventory needs evidence gaps and responsible owners rather than an unsupported claim of compliance.
What it can do
The scripts inspect entity profiles, calculate rule-based incident timeline findings, map assessment rows to the packaged measure list and identify questions about overlapping regimes. Examples and runbook references show the expected record shapes. They do not file reports or change systems.
The packaged logic is an aid to preparation. National implementation, designation decisions, current official rules and case-specific facts require qualified review. A routing result is not a binding legal opinion, and a completed checklist is not certification. Verify all inputs and applicability with the responsible authority or specialist, especially during a live incident. Keep sensitive incident data within an authorized environment.
Typical workflows
- Clarify scope: provide sector, entity size and jurisdiction details; use the output to locate evidence gaps and questions needing a specialist decision.
- Prepare an incident record: reconcile detection and awareness times, inspect generated timeline findings and assign reporting responsibility without submitting automatically.
- Review measures: complete the assessment with actual evidence, distinguish absent controls from unassessed rows and track follow-up ownership.
What is inside the skill
Section headings from the original SKILL.md (about 597 words of instructions). Read the full text in the source repository before installing.
- Workflow
- The gates block on (exit 4)
- Hard rules
- Scripts
- References and assets
Bundled files
assets/assessment.example.csvassets/entities.example.csvassets/incident_runbook.mdassets/incidents.example.csvassets/profile.example.jsonreferences/article21_measures.mdreferences/incident_reporting_article23.mdreferences/scope_and_registration.mdscripts/art21_gap_check.pyscripts/eu_cyber_regime_router.pyscripts/nis2_incident_clock.pyscripts/nis2_scope_classifier.pyLICENSE
Example prompts
- Use these entity records to prepare a NIS2 scope-review worksheet. Show the inputs used for each result, flag missing size or jurisdiction evidence and list the questions our compliance lead must resolve.
- Review this redacted incident timeline with the packaged routing and clock tools. Identify parallel reporting questions and conflicting timestamps, without filing anything or treating the result as legal advice.
- Assess this security-measure inventory against the packaged checklist. Separate unmet from unassessed items and request concrete evidence and an owner for each finding rather than labeling the organization compliant.
How to install Nis2 Readiness
Claude Packaged
- Download the Claude package from the skill page. The ZIP contains one folder named after the skill, with SKILL.md and any bundled reference files.
- For Claude Code, unpack the folder into ~/.claude/skills/ to use it in every project, or into .claude/skills/ inside a repository to share it with your team.
- For Claude apps, upload the ZIP in the Skills section of the capabilities settings.
- Start a new session and describe the task in your own words. Claude picks the skill when the request matches its description.
Codex Packaged
- Download the Codex package. The ZIP contains one folder named after the skill, with SKILL.md and bundled resources.
- Unpack the complete folder into .agents/skills/ inside your repository, or into ~/.agents/skills/ for personal use. Preserve its relative reference-file paths.
- Start a new Codex session and invoke the skill by name or with $skill-name, or describe a matching task.
- AGENTS.md is separate project guidance. The ZIP does not generate or modify that file.
GPT Packaged
- Download the GPT package from the skill page.
- Create or edit a custom GPT (or a ChatGPT project) and paste the contents of SKILL.md into the instructions field.
- Upload the bundled reference files as knowledge so the GPT can consult them.
- Test with one of the example prompts from the skill page and adjust the instructions if your use case differs.
Gemini Packaged
- Download the Gemini package from the skill page.
- For a project, unpack the complete folder into .gemini/skills/ or .agents/skills/. For personal use, use ~/.gemini/skills/ or ~/.agents/skills/.
- Run /skills reload in Gemini CLI, then /skills list to check discovery. There is no need to paste the skill into GEMINI.md.
- Test a matching task and verify the referenced tools and files are available.
Cursor Packaged
- Download the Cursor package from the skill page.
- Unpack the complete skill folder into .cursor/skills/ or .agents/skills/ in your project. For personal local use, ~/.cursor/skills/ and ~/.agents/skills/ are also supported.
- Start a new Cursor session. Type / in Agent chat and select the skill name, or describe a matching task.
- Commit the skill folder and resources for team use. Personal local skills are not automatically available to remote agents or automation runs.
OpenCode Packaged
- Download the OpenCode package from the skill page.
- Unpack the complete folder into .opencode/skills/ in your project, or ~/.config/opencode/skills/ for personal use. OpenCode also supports .agents/skills/ and .claude/skills/ compatibility locations.
- Keep supporting files at their original relative paths. AGENTS.md is separate project-wide guidance and is not generated by this ZIP.
- Start OpenCode in the project and test a matching task with the model and permissions you use.
Permissions & security
Inspect the source, license and declared permissions before use. Read the scripts before running them. Review method
Nis2 Readiness FAQ
What does the Nis2 Readiness skill do?
Prepare NIS2-oriented entity, incident and security-measure reviews from local records. Includes a multi-regime routing aid and gap reports, with authority and legal interpretation left to qualified reviewers.
Which AI agents can use Nis2 Readiness?
Packages for Claude, Codex and 4 more are built from the same source instructions.
How do I install Nis2 Readiness in Claude?
Download the Claude package from the skill page. The ZIP contains one folder named after the skill, with SKILL.md and any bundled reference files. For Claude Code, unpack the folder into ~/.claude/skills/ to use it in every project, or into .claude/skills/ inside a repository to share it with your team.
Who made Nis2 Readiness and what is the license?
Nis2 Readiness is published by Alireza Rezvani under the MIT license. The source is https://github.com/alirezarezvani/claude-skills/tree/main/ra-qm-team/nis2-readiness/skills/nis2-readiness. The catalog keeps the original attribution.
What permissions does Nis2 Readiness need?
Declared permissions: read project files, write generated skill files. Risk level: low. Check the scripts in the source before running them.