CtrlK
BlogDocsLog inGet started
Tessl Logo

regulatory-audit-generator

Builds compliance checklists for business scenarios involving GDPR, PIPL, or advertising/data laws. Outputs a structured checklist with check items, legal basis, risk levels, and actionable recommendations. Triggered by requests like "run a compliance check," "GDPR/PIPL compliance," "pre-launch review," "privacy impact assessment (PIA/DPIA)," or asking if a feature is compliant.

64

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/regulatory-audit-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A thorough, well-structured instruction skill with strong actionability and a clear SOP, held back by inlining a large reference volume in SKILL.md and some over-explanation. Splitting regulation tables into bundle reference files and tightening prose would raise it.

Suggestions

Move the detailed regulation tables (Sections 1 and 3) into separate reference files under ./references/ and link to them from SKILL.md to improve progressive disclosure.

Trim explanatory restatement of regulatory scope and basic concepts that Claude already knows to improve conciseness.

Add a worked end-to-end example (filled checklist for one scenario) to push actionability from concrete-template to fully executable.

DimensionReasoningScore

Conciseness

The 200-line body is mostly efficient reference material (tables of regulations, check items, risk criteria), but includes some over-explanation Claude already knows (e.g., defining that minors are a user group, restating regulatory scope) and could be tightened throughout.

3 / 5

Actionability

Provides concrete, copy-ready guidance: explicit IF-rules for selecting regulations, a markdown checklist output template, and detailed per-scenario check items with article citations; minor gaps are the placeholder 'YYYY-MM-DD' and bracketed fields rather than fully worked examples.

4 / 5

Workflow Clarity

A clear four-step SOP (gather info → identify regulations → generate checklist → output priorities) with a P0–P3 prioritization table, plus a directive to proactively ask follow-ups rather than assume; lacks an explicit validate/retry feedback loop, though this skill is advisory rather than destructive.

4 / 5

Progressive Disclosure

Well-organized into numbered sections, but everything is inlined in SKILL.md with no bundle files or one-level-deep references — the large regulation/check-item tables could be split into separate reference files, and the only 'References' section lists external laws rather than skill bundle navigation.

3 / 5

Total

14

/

20

Passed

Description

91%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, specific description that clearly states capabilities and provides explicit trigger phrases for when to invoke the skill. Minor room only for additional trigger synonyms.

DimensionReasoningScore

Specificity

Names the domain (compliance checklists for GDPR/PIPL/advertising laws) and multiple concrete outputs — 'structured checklist with check items, legal basis, risk levels, and actionable recommendations' — giving comprehensive coverage of capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (builds structured compliance checklists with check items, legal basis, risk levels, recommendations) and 'when' via concrete 'Triggered by requests like...' trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ('run a compliance check', 'GDPR/PIPL compliance', 'pre-launch review', 'privacy impact assessment (PIA/DPIA)', 'is a feature compliant'), but lacks synonyms/file-extension-style variants and a few common phrasings.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (regulatory compliance checklist generation for named law families) with distinctive triggers unlikely to fire for unrelated skills.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
zebbern/claude-code-guide
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.