CtrlK
BlogDocsLog inGet started
Tessl Logo

reg-gap-analysis

Diff a new AI regulation or guidance against your current governance posture — surfaces gaps, priorities, and a remediation plan with owners and deadlines. Use when an AI regulation moves (or you learn about one you missed), or when user says "new reg just dropped", "does [regulation] affect us", "gap analysis for EU AI Act", "compliance check against [AI law or guidance]", or pastes regulatory text.

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

Low

Low-risk findings worth noting

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.

The body is a well-structured, highly actionable regulatory gap-analysis workflow with concrete templates and explicit verification protocols. Its main weaknesses are a duplicated research-guidance section and a monolithic single-file layout that underuses progressive disclosure.

Suggestions

Consolidate the overlapping "Research first, then workflow" and "Research the regulation before building the gap analysis" sections into one to remove redundancy.

Move the source-attribution-tiering and citation-tagging block into a references/ file (e.g. CITATION-TIERING.md) and link to it from the body to improve progressive disclosure.

Tighten the Purpose and Integration sections, which restate motivation already conveyed by the description.

DimensionReasoningScore

Conciseness

Mostly substantive and assumes Claude's competence (no generic explanations of what regulation is), but the "Research first, then workflow" and "Research the regulation before building the gap analysis" sections substantially overlap, and the long inline source-attribution-tiering block could be tightened. Not score 3 because of the duplicated research guidance; not score 1 because most tokens earn their place and no basic concepts are over-explained.

2 / 3

Actionability

Provides copy-paste-ready templates — the requirements table, the per-requirement diff markdown block with defined fields, and the remediation-plan table with owner/due/status columns — plus a concrete category taxonomy and citation-tagging scheme. Not score 2 because the guidance is fully specified and executable rather than pseudocode or abstract.

3 / 3

Workflow Clarity

Clear five-step sequence (scope → extract → diff → prioritize → remediation) with an explicit scoping gate ("If not, one line and done") and verification checkpoints (verify currency, no-silent-supplement protocol that loops back to the user, cite-check before relying). Not score 2 because explicit validation/feedback checkpoints are present rather than implicit.

3 / 3

Progressive Disclosure

Well-organized into clearly headed sections, but the ~230-line body is monolithic with no bundle files (references/scripts/assets absent) and long inline blocks (source attribution tiering, research guidance) that could be split into one-level-deep references. Not score 3 because content that would benefit from being separate is inline; not score 1 because sections are clearly signaled and navigable rather than a disorganized wall.

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.

The description is specific, trigger-rich, complete, and distinctive, written in clean third-person voice. It surfaces concrete actions and natural-language triggers a user would actually say.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Diff a new AI regulation or guidance against your current governance posture", "surfaces gaps, priorities, and a remediation plan with owners and deadlines" — matching the highest anchor. Not score 2 because it goes beyond naming a domain to enumerating specific operations.

3 / 3

Completeness

Explicitly answers both what (diff, surface gaps, remediation plan with owners/deadlines) and when via a clear "Use when..." clause with concrete triggers. Not score 2 because the 'when' is explicit and multi-pronged, not merely implied.

3 / 3

Trigger Term Quality

Quotes natural phrases users would actually say — "new reg just dropped", "does [regulation] affect us", "gap analysis for EU AI Act", "compliance check against [AI law or guidance]" — giving good coverage of natural terms. Not score 2 because it provides multiple realistic verbatim triggers rather than just topical keywords.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (AI regulation gap analysis against governance posture) with distinctive regulatory-specific triggers unlikely to fire for unrelated skills. Not score 2 because the scope and triggers are specific enough to avoid overlap with general compliance or governance 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.