CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/risk-acceptance-decision-author

Build-an-X workflow that produces a structured risk-acceptance decision document - for risks the team has decided to accept (rather than mitigate / transfer / avoid). Walks the author through the ISO 31000 risk-acceptance criteria (rationale, sign-off, scope, review trigger, exit conditions), captures stakeholder approval, and links to the originating risk register entry. Output is a Markdown decision artefact that lives alongside the risk register and provides audit-defensible justification for the team's acceptance choice. Use when a risk register entry's Strategy column is set to Accept, or an already-accepted risk comes up for its scheduled re-review, an audit, or a post-incident look-back.

79

Quality

99%

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

Overview
Quality
Evals
Security
Files

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, multi-step instruction skill: lean and concrete, with exact authority matrices, quantified rationale guidance, and a real referenced examples file. It earns top marks on every dimension with only trivial editorial tightening possible.

DimensionReasoningScore

Conciseness

The body is information-dense — four purpose-built tables and concrete matrices instead of prose — and never explains concepts Claude already knows; the only mildly editorial touches (Overview motivation, 'The hardest part.') are minimal and clarify purpose rather than pad.

3 / 3

Actionability

Concrete and copy-ready throughout: an exact score-to-authority matrix (1-5/6-9/10-14/15-19/20-25), a quantified rationale table, a named ordered document-section list in Step 5, and filled markdown templates for the register entry, decisions index, and annual review log.

3 / 3

Workflow Clarity

Seven steps are clearly sequenced with explicit requirement gates (Step 3 'Two questions need explicit answers', Step 4 'At minimum: time + score-change trigger') and an Anti-patterns table that functions as a review checklist; no destructive/batch validation gap applies to document authoring.

3 / 3

Progressive Disclosure

Core workflow lives inline while the two filled examples are offloaded to a single one-level-deep, clearly signaled reference (references/example-decisions.md), which exists in the bundle; navigation is easy and the split is appropriate.

3 / 3

Total

12

/

12

Passed

Description

100%

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 description: specific actions, natural trigger terms, an explicit 'Use when' clause covering what and when, and a distinct niche. It closely matches the score-3 anchors on every dimension.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'produces a structured risk-acceptance decision document', 'Walks the author through the ISO 31000 risk-acceptance criteria (rationale, sign-off, scope, review trigger, exit conditions)', 'captures stakeholder approval', 'links to the originating risk register entry' — matching the score-3 anchor; third-person voice is used throughout.

3 / 3

Completeness

Clearly answers both 'what' (produces/walks/captures/links/output artefact) and 'when' via an explicit 'Use when...' clause with multiple triggers, so it is not capped at 2.

3 / 3

Trigger Term Quality

The 'Use when' clause surfaces natural domain terms a practitioner would say — 'risk register entry's Strategy column is set to Accept', 'scheduled re-review', 'audit', 'post-incident look-back' — giving good coverage rather than jargon-only phrasing.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — an acceptance decision artefact for the Accept strategy — with distinct triggers that separate it from the sibling register/matrix builder skills, making mis-triggering unlikely.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents