Skip to content

alirezarezvani/claude-skills / ra-qm-team/skills/nis2-readiness

nis2-readiness

Verified

Use when a cyberattack, ransomware or outage hits a hospital, utility, transport, digital-infrastructure or other EU company and it must report under NIS2 (Directive 2022/2555) or the German NIS2UmsuCG/BSIG - 24h early warning, 72h notification, one-month final report. Also for whether a company is an essential or important entity, BSI registration, management-board liability and training (Article 20), an Article 21 gap analysis, or one incident that also triggers DORA, CRA or GDPR reports. Four deterministic scripts with cited articles.

assets/incident_runbook.md

View on GitHub
# NIS2 significant incident runbook

Fill the standing part once; copy the per-incident part for each incident.
Deadlines: Directive (EU) 2022/2555 Art 23(4); Germany BSIG §32.

## Standing set-up

| Item | Value |
|---|---|
| Category (essential / important) and Member State of jurisdiction (Art 26) | |
| CSIRT or authority and reporting channel (Germany: BSI portal) | |
| Registration done? date and reference (Art 27; BSIG §33) | |
| Digital provider under 2024/2690? (DNS, TLD, cloud, DC, CDN, MSP, MSSP, marketplace, search, social, trust) | |
| Also under DORA, CRA or GDPR? (run `eu_cyber_regime_router.py`) | |
| Who decides significance (name, deputy) | |
| Who submits (name, deputy) | |
| Who informs recipients of the service (Art 23(1)) | |

## Per incident

| Step | Time (with offset) | Who | Note |
|---|---|---|---|
| Detected | | | |
| Aware (significant incident with reasonable certainty) | | | starts all clocks |
| Significance decided | | | criteria met (Art 23(3) or 2024/2690 Art 3) |
| Early warning sent | | | due aware + 24 h; malicious? cross-border? |
| Recipients informed | | | without undue delay |
| Notification sent | | | due aware + 72 h (24 h trust services) |
| Intermediate report (if requested) | | | |
| Final or progress report sent | | | due notification + 1 month |
| Handling concluded | | | final due 1 month after, if a progress report was sent |

Then run:

```bash
python scripts/nis2_incident_clock.py --incidents incidents.csv
```
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 323kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall