CtrlK
BlogDocsLog inGet started
Tessl Logo

802-regulations-dora

Use when reviewing, designing, or modifying Java enterprise systems that may support financial entities, critical ICT services, third-party ICT provider integrations, or operational resilience obligations under DORA. This should trigger for requests such as Review a Java platform for DORA ICT risk controls; Design operational resilience evidence for a financial service; Add incident, continuity, backup, recovery, or third-party ICT controls; Assess resilience testing and monitoring before production release. Part of Plinth Toolkit

67

Quality

81%

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

81%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.

Well-architected reference skill: lean overview, concrete bundle-backed workflow with gating checkpoints, and clean one-level-deep progressive disclosure. Slight conciseness trimming and an explicit validation feedback loop would push it to the top anchor.

Suggestions

Tighten the repeated scope/constraint enumerations (e.g., the Scope and When-to-use lists overlap the description) to reduce redundancy and token cost.

Add an explicit validate-fix-retry feedback loop in the workflow (e.g., re-run questionnaire gaps / re-validate evidence before finalizing the report) to reach the top workflow_clarity anchor.

Consider collapsing the duplicated reference links at the end (Reference section repeats the two references/ links already introduced above) into a single navigation block.

DimensionReasoningScore

Conciseness

Generally lean overview that assumes Claude's competence and avoids re-explaining DORA basics, with some enumerative constraint lists and repeated scope statements that could be tightened further.

4 / 5

Actionability

Provides concrete executable guidance via a numbered workflow referencing real bundle files (questionnaire, report template, chapters summary) and specific review artifacts to inspect, with only minor gaps in inline examples.

4 / 5

Workflow Clarity

A clear six-step sequence with explicit checkpoints (e.g., 'Do not proceed ... until all 20 questions have an evidence-backed answer or an Unknown marker') and secret-redaction gates; not quite a full validate-fix-retry feedback loop, hence just below 5.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview pointing to four real, one-level-deep references (chapters summary, engineering examples, questionnaire, report template) with clearly signaled links and well-organized sections.

5 / 5

Total

17

/

20

Passed

Description

82%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.

A strong, well-structured description with clear 'Use when' triggers and concrete review actions tied to a distinct regulatory niche. Minor room to add a few more natural synonyms and broaden the concrete-action list.

DimensionReasoningScore

Specificity

Names the domain (DORA, financial entities, ICT services, third-party providers) and several concrete review actions (review ICT risk controls, design resilience evidence, add incident/continuity/backup controls, assess resilience testing), though it is more enumerative than truly comprehensive in concrete capabilities.

4 / 5

Completeness

Explicitly answers both 'what' (review/design/modify Java enterprise systems supporting financial entities and operational resilience) and 'when' with concrete 'Use when...' trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Good natural trigger phrases a user would actually say ('Review a Java platform for DORA ICT risk controls', 'Design operational resilience evidence'); a few common synonyms or variants are missing but coverage is strong.

4 / 5

Distinctiveness Conflict Risk

The DORA / financial-entity / ICT-resilience niche is distinct from most skills; minor overlap risk with general compliance or security skills, but trigger phrasing is specific.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 6 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository
jabrena/plinth
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.