CtrlK
BlogDocsLog inGet started
Tessl Logo

policy-diff

Diff a specific regulatory change against the indexed policy library. Use when a reg has changed and you need to know which policies it touches and what the gap is, when the user says "diff this reg against our policies", "which policy does this affect", or "gap analysis", or when reg-feed-watcher hands off a material item.

72

Quality

88%

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

77%Weight 40%Scale 1-3

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

A strong, actionable regulatory-diff workflow with clear sequencing and validation checkpoints, weakened only by some rhetorical verbosity and a monolithic structure that could split templates into references.

Suggestions

Trim the moralizing framing in 'Scope integrity' (e.g., 'looks like concealment in discovery') to the operative instruction; the banner + routing rule already carry the point.

Extract the Step 3 diff block, the negative-finding paragraph, and the full Output template into a referenced file (e.g., templates.md) to reduce the monolithic body and improve progressive disclosure.

Collapse the repeated citation/source-tagging guidance (Step 1 source attribution vs. the closing verify block) into a single canonical statement to save tokens.

DimensionReasoningScore

Conciseness

Mostly lean and instruction-dense with no domain-concept padding, but some rhetorical framing ('looks like concealment in discovery', 'the difference between we scoped the review and we hid the problem') could be trimmed.

2 / 3

Actionability

Provides copy-paste-ready output templates, exact banner strings ('⚠️ RULE STATUS UNVERIFIED'), precise routing tags (status_verified: false), and concrete fallback messages — fully actionable instruction guidance.

3 / 3

Workflow Clarity

Clear Step 0–4 sequence with explicit validation checkpoints (rule-in-force verification, no-silent-supplement stop-and-ask, scope-limitation propagation) and downstream feedback loops.

3 / 3

Progressive Disclosure

Well-organized with clear headers, but the ~200-line skill is monolithic — output templates and branch logic are all inline with no offloading to reference files.

2 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 highly specific, well-triggered description that clearly separates what the skill does from when to invoke it, with natural quoted user phrases and a clear niche. Among the strongest descriptions on the rubric.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Diff a specific regulatory change against the indexed policy library' and 'know which policies it touches and what the gap is' — rather than vague language.

3 / 3

Completeness

Clearly states what it does (diff a reg against the policy library for gap analysis) and when to use it via an explicit 'Use when...' clause with concrete triggers.

3 / 3

Trigger Term Quality

Quotes natural user utterances verbatim ('diff this reg against our policies', 'which policy does this affect', 'gap analysis') plus the reg-feed-watcher handoff trigger, covering terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The regulatory-change-vs-policy-library niche and its distinct handoff/utterance triggers are unlikely to conflict with or misfire against other skills.

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
anthropics/claude-for-legal
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.