← LeaderboardThe Skill Leaderboard

dora-readiness

Use when a bank, payment or e-money institution, investment firm, insurer, crypto-asset service provider or fund manager in the EU faces DORA (Regulation 2022/2554, Digital Operational Resilience Act) - is an ICT outage or cyber incident major, when the initial (4h/24h), intermediate (72h) and final reports are due, weekends included; the register of information; ICT or cloud contracts missing audit rights, exit plans or other Article 30 terms; scope and the simplified framework for small firms. Not for DORA DevOps metrics. Three deterministic scripts with cited articles.

Published by alirezarezvani ↗alirezarezvani/claude-skills

Try your first task

A source-grounded starter task has not been verified for this skill yet.

SKILL.md

name: dora-readinessdescription: Use when a bank, payment or e-money institution, investment firm, insurer, crypto-asset service provider or fund manager in the EU faces DORA (Regulation 2022/2554, Digital Operational Resilience Act) - is an ICT outage or cyber incident major, when the initial (4h/24h), intermediate (72h) and final reports are due, weekends included; the register of information; ICT or cloud contracts missing audit rights, exit plans or other Article 30 terms; scope and the simplified framework for small firms. Not for DORA DevOps metrics. Three deterministic scripts with cited articles.argument-hint: "[entities CSV | ICT incident log CSV | register of information CSV]"license: MITmetadata:   version: 1.0.0  build_pattern: "Three deterministic stdlib scripts with blocking exit codes (Art 2 scope + simplified framework + CTPP check, major-incident classifier with the RTS 2025/301 clock, register of information and Art 30 contract check); rules from Regulation (EU) 2022/2554, Delegated Regulations (EU) 2024/1772 and 2025/301, Implementing Regulation (EU) 2024/2956"  distinct_from: "nis2-readiness (non-financial entities; DORA is lex specialis); vpe-advisor (DORA DevOps delivery metrics, a different DORA); information-security-manager-iso27001 (management system); cra-readiness (products)"

DORA Readiness

Portability: 3 stdlib scripts, no network, nothing submitted anywhere. Fill CSVs, run, keep the output as evidence. Not legal advice. Your competent authority supervises; national transposition choices (e.g. CSIRT copies) vary.

DORA has applied since 17 January 2025 to 20 types of financial entity and to the ICT providers that serve them. Supervisors first asked for two things: the register of information and major-incident reports. Teams fail in predictable ways: they classify on gut feeling instead of the RTS thresholds, start the 4-hour clock at awareness instead of at classification, miss recurring incidents that are major together, and sign cloud contracts for critical functions with no audit right or exit plan.

Workflow

# 1 - Scope: full regime, simplified (Art 16), excluded, or ICT provider?
python scripts/dora_scope_check.py --entities assets/entities.example.csv
# 2 - Incidents: which are major, which report is due, is any overdue?
python scripts/dora_incident_classifier.py --incidents assets/incidents.example.csv --entity credit-institution
# 3 - Third parties: does the register and every contract hold up?
python scripts/register_of_information_check.py --register assets/register.example.csv

Run step 2 first whenever an ICT incident is live. --list-types, --list-exemptions, --list-simplified and --list-terms print the Art 2 entity types, exclusions, Art 16 cases and the Art 30 contract terms.

How an incident becomes major (RTS 2024/1772 Art 8)

It affects critical services (Art 6) and either a successful malicious unauthorised access that may cause data loss, or two of: clients (>10%,

100 000, >30% counterparts, >10% transactions, or relevant clients), reputation, duration (>24 h, or >2 h down on a critical function), two Member States, data impact, economic loss >EUR 100 000. Incidents with the same root cause, at least twice in six months, that meet this together are one major incident (Art 8(2)).

The gates block on (exit 4)

  1. An entity type DORA does not list, or no type at all (Art 2(1)).
  2. A report past its deadline: initial 4 h after classification and no later than 24 h after awareness; intermediate 72 h after the initial; final one month after the last intermediate (RTS 2025/301 Art 5).
  3. A contract for a critical or important function missing an Art 30(3) term or an exit plan (Art 28(8)), or a contract never assessed for criticality.

Hard rules

  • Classify against the thresholds, write the classification time down. It starts the 4-hour clock.
  • Weekend relief is narrow. Noon of the next working day applies, but not to initial and intermediate reports of credit institutions, CCPs, trading venues or NIS2-identified entities (Art 5(5)): pass --entity.
  • Late still owes the report, and the warning. Tell the authority before a deadline passes (Art 5(3)).
  • Clients hear from you. If their financial interests are hit, inform them without undue delay (DORA Art 19(3)).
  • Microenterprises and Art 16 entities skip the recurring check, not the reporting.
  • Never submit for the user. The scripts prepare; a named person files with the competent authority.

Scripts

ScriptRoleExit codes
scripts/dora_scope_check.pyEntity type (Art 2(1)(a)-(u)), exclusions (Art 2(3)), simplified framework (Art 16), microenterprise, NIS2 overlap, CTPP (Arts 31-35)0 · 2 findings · 3 bad input · 4 unplaced
scripts/dora_incident_classifier.pyArt 6/8/9 classification, recurring incidents, initial / intermediate / final deadlines, weekend rule, client notice0 on time · 2 open · 3 · 4 overdue
scripts/register_of_information_check.pyLEI, criticality, Art 30(2) and 30(3) terms, exit plan (Art 28(8)), risk assessment (Art 28(4)), concentration and third country (Art 29)0 clean · 2 gaps · 3 · 4 blocked

All support --help, --sample and --output json.

References and assets

dora-readiness by alirezarezvani · The Skill Leaderboard