CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

legal-risk-assessment

Assess and classify legal risks using a severity-by-likelihood framework with escalation criteria. Use when evaluating contract risk, assessing deal exposure, classifying issues by severity, or determining whether a matter needs senior counsel or outside legal review.

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

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

The framework itself is excellent — specific, quantitative, and immediately usable, with a documentation standard that makes outputs reproducible. Weaknesses are structural: the assessment workflow is implied rather than explicitly sequenced with validation checkpoints, the single 260-line file inlines content that belongs in reference files, and there is localized redundancy (duplicated matrix, restated characteristics).

Suggestions

Add an explicit numbered assessment workflow (e.g., 1. Gather facts → 2. Rate severity against the table, citing the matching anchor → 3. Rate likelihood → 4. Compute and map the score to a level → 5. Apply that level's action list → 6. Document via the memo template) with a checkpoint that re-verifies each rating against the anchor descriptions.

Split the Documentation Standards (memo template and risk-register entry) and the When to Escalate to Outside Counsel sections into reference files (e.g., references/memo-format.md, references/escalation.md), keeping SKILL.md as a concise overview of the matrix, levels, and actions.

Trim the redundant ASCII risk matrix (the Severity x Likelihood multiplication is trivial) and collapse the per-level 'Characteristics' bullets, which restate the severity table, into the level headers or examples.

DimensionReasoningScore

Conciseness

Mostly efficient — the severity/likelihood tables, action lists, and memo template earn their tokens and assume legal competence (no explaining what a contract or NDA is). However, the ASCII risk matrix is redundant with the trivial "Risk Score = Severity x Likelihood" formula, and each level's "Characteristics" bullets largely restate the severity table, so there is more than minor trimming to be done. Not 4 because the redundancy is noticeable rather than minor; not 2 because the padding is localized and most sections are dense and useful.

3 / 5

Actionability

For an instruction-only skill the guidance is fully executable: quantified severity thresholds ("< 1% of relevant contract/deal value", "1-5%", "5-25%", "> 25%"), a copy-paste-ready memo template with ten numbered sections, a complete risk-register field table, and concrete per-level action lists plus worked example scenarios at each risk level. Meets the 5 anchor's standard of specific examples covering common cases.

5 / 5

Workflow Clarity

The operational sequence (rate severity via table → rate likelihood via table → compute score → look up level → apply that level's recommended actions → document via memo template) is present but only implicit in the section ordering and memo template; no explicit step enumeration or validation checkpoint exists (e.g., re-checking a rating against the anchor descriptions). This is not a destructive/batch skill, so no cap applies, but it sits at the 3 anchor (sequence present, checkpoints implicit) rather than 4, which requires a clearly enumerated sequence with most checkpoints explicit.

3 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), so the ~260-line body is a single monolith with good internal headers. The memo template, risk-register format, and outside-counsel selection criteria are self-contained chunks that clearly belong in separate reference files. Good structure, but content that should be separate is inline — matching the 3 anchor; not 2 because organization and navigation within the file are solid.

3 / 5

Total

14

/

20

Passed

Description

87%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 description: concrete actions, an explicit and well-phrased 'Use when' clause covering several natural trigger scenarios, and a clearly bounded legal-risk niche. The only gaps are a few missing synonyms (litigation, regulatory, compliance) and no mention of the documentation deliverables.

DimensionReasoningScore

Specificity

"Assess and classify legal risks using a severity-by-likelihood framework with escalation criteria" names the domain and several concrete actions (assess, classify, apply the severity-by-likelihood framework, determine escalation). Not 5 because it omits the documentation capability (risk memo, risk register) that the skill body treats as a core deliverable.

4 / 5

Completeness

It explicitly answers both questions: the "what" is "Assess and classify legal risks using a severity-by-likelihood framework with escalation criteria" and the "when" is a full "Use when..." clause with four concrete trigger phrases. Matches the 5 anchor and exceeds the 4 anchor, whose "when" is less specific.

5 / 5

Trigger Term Quality

"evaluating contract risk, assessing deal exposure, classifying issues by severity, or determining whether a matter needs senior counsel or outside legal review" gives good coverage of natural legal-team phrasing. Not 5 because common variations users would say — litigation, regulatory inquiry, compliance, NDA, risk register — are absent.

4 / 5

Distinctiveness Conflict Risk

The legal-risk niche is clear and triggers (contract risk, deal exposure, senior counsel, outside legal review) are domain-specific, so overlap with non-legal skills is minimal. It is written in third person with no voice penalty.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

anthropics/knowledge-work-plugins

Path

legal/skills/legal-risk-assessment/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.