CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dora

Expert DORA (Regulation (EU) 2022/2554 — Digital Operational Resilience Act) compliance advisor for EU financial entities. Use this skill whenever a user asks about DORA compliance, ICT risk management frameworks, ICT incident classification or reporting, threat-led penetration testing (TLPT), ICT third-party risk management, Register of Information, contractual provisions with ICT providers, ICT concentration risk, oversight of critical ICT third-party service providers (CTPPs), or any DORA RTS/ITS obligation. Also trigger for: "DORA gap analysis", "DORA readiness", "Art. 6 ICT risk framework", "Art. 17 incident reporting", "Art. 26 TLPT", "Art. 28 third-party policy", "Art. 30 contractual provisions", "Register of Information CIR 2024/2956", "critical TPSP designation", "DORA vs NIS2", "DORA simplified framework", or EBA/ESMA/EIOPA digital resilience guidance.

Quality

92%

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

82%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 strong, well-organized compliance skill body: highly actionable output formats, rule-based behavioral guidance, phased gap-analysis tables, and a properly wired one-level-deep reference bundle. The main weaknesses are token duplication between the inline chapter walkthroughs and article-reference.md, and the absence of explicit verification checkpoints in the gap-analysis workflow.

Suggestions

Condense the Chapter II–V article-by-article walkthroughs (Art. 5–16, 17–23, 24–27, 28–44 sections) into chapter-level summaries with key articles and common gaps only, pointing to references/article-reference.md for per-article detail — this would remove the main duplication and cut the body's token cost substantially.

Add an explicit step sequence and verification loop to the gap-analysis workflow (e.g., Step 0: confirm entity scope and simplified-framework eligibility against CDR (EU) 2024/1774; final step: verify Register of Information completeness against CIR (EU) 2024/2956 mandatory fields before delivering conclusions).

Consider moving the dated 'Status Update — September 2026' items (CTPP designations, CSSF 26/915, ESA incident statistics) into a dated reference file or keeping them clearly quarantined, so the evergreen body stays lean and time-sensitive facts are updated in one place.

DimensionReasoningScore

Conciseness

The body is dense with regulation specifics Claude cannot reliably know ("Art. 28(4)(a)-(f)", "CDR (EU) 2024/1772", "Initial (4h) → Intermediate (72h) → Final (1 month)") presented almost entirely as compact tables and bullets — efficient, with no concept padding, so above anchor 3. But it is not anchor 5 ('every token earns its place'): the ~200-line Chapter II–V article walkthroughs substantially duplicate references/article-reference.md ('All 64 DORA articles with obligation summaries'), which is more than 'minor instances' of trimmable content.

4 / 5

Actionability

Concrete, executable guidance throughout: the 'How to Respond' table specifies exact output formats per task ("Table: DORA Article | Obligation Summary | Status | Evidence Needed | Gap Notes"), Foundational Rules give directives that can be followed directly ("If unsure whether the simplified framework applies: Default to the full Chapter II framework (Art. 6-14)"), and the gap-analysis tables enumerate evidence and common gaps per obligation. Per the rubric's scoring notes, an instruction-only skill with this level of specific, case-covering guidance merits the top anchor; not anchor 4, which allows 'minor gaps'.

5 / 5

Workflow Clarity

Sequences are present and mostly checkpointed: gap analysis proceeds in ordered Phases 1-4, TLPT is a 7-step numbered process (scope → threat intelligence → red team → remediation → notification → attestation → mutual recognition), and decision safeguards exist ("Default to the full Chapter II framework", "Verify vendor subsidiary status now"). It falls short of anchor 5 because the primary gap-analysis workflow has no explicit verification step on its outputs (e.g., validating Register completeness against CIR 2024/2956 fields) and no feedback/re-check loop; it is above anchor 3 since checkpoints are not merely implicit.

4 / 5

Progressive Disclosure

All four referenced files exist (references/rts-its-guide.md, article-reference.md, third-party-risk.md, incident-classification.md), are one level deep with no nested references, and are clearly signaled both inline ("See references/rts-its-guide.md for the full list") and in a dedicated 'Reference Files' section with descriptions. Good structure per anchor 4; it does not reach anchor 5 ('content appropriately split') because the body inlines substantial article-by-article detail that also lives in references/article-reference.md, making SKILL.md more than an overview.

4 / 5

Total

17

/

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 exemplary description: it states the skill's role and audience concisely, defines explicit 'use when' triggers covering all major DORA domains, and adds a rich list of natural trigger phrases including article-level and regulation-number variants. It is long but every clause is trigger-relevant with no fluff or over-claims.

DimensionReasoningScore

Specificity

Quotes: "Expert DORA (Regulation (EU) 2022/2554...) compliance advisor for EU financial entities" plus concrete capability areas "ICT incident classification or reporting, threat-led penetration testing (TLPT)", "Register of Information", "contractual provisions with ICT providers", "oversight of critical ICT third-party service providers (CTPPs)". This matches the anchor-5 example (multiple specific concrete capabilities, comprehensive coverage): all major DORA topic areas across its nine chapters are named, so it is not anchor 4, which requires 'minor gaps in coverage'.

5 / 5

Completeness

Explicitly answers 'what' ("Expert DORA... compliance advisor for EU financial entities") and 'when' ("Use this skill whenever a user asks about DORA compliance, ICT risk management frameworks, ..." plus "Also trigger for: 'DORA gap analysis', 'DORA readiness', ..."). Both are present with concrete trigger phrases, exactly the anchor-5 structure; anchor 4 would require the 'when' to be less explicit or specific, which it is not. Uses third-person/declarative voice throughout, so no voice penalty applies.

5 / 5

Trigger Term Quality

Quotes: "DORA compliance", "DORA gap analysis", "DORA readiness", "Art. 17 incident reporting", "Art. 30 contractual provisions", "DORA vs NIS2", "DORA simplified framework", "EBA/ESMA/EIOPA digital resilience guidance" — these are natural phrases a compliance/risk professional would actually say, with synonyms and regulation numbers ("Register of Information CIR 2024/2956"). Coverage exceeds the anchor-5 example (PDFs, forms, .pdf); not anchor 4, which expects 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

Clear niche (EU DORA financial-sector regulation) with distinct, DORA-specific triggers; it even preempts the nearest overlap by naming "DORA vs NIS2" as a deliberate trigger rather than a confusion risk. Minimal conflict with generic compliance or security skills, matching anchor 5's 'clear niche with distinct triggers'; not anchor 4, since no meaningful overlap risk with closely related skills is identified.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (530 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

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

Path

plugins/dora/skills/dora/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.