CtrlK
BlogDocsLog inGet started
Tessl Logo

legal-advisor

Draft privacy policies, terms of service, disclaimers, and legal notices. Creates GDPR-compliant texts, cookie policies, and data processing agreements.

52

Quality

58%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/legal-advisor/SKILL.md

The canonical home for this skill is legal-advisor in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

50%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 body is concise and well-sectioned but stays at a high level: it lacks concrete document templates or clause examples, has no validation/review loop in its workflow, and references a playbook file that does not exist on disk.

Suggestions

Add at least one concrete artifact — a skeleton privacy-policy or ToS template with placeholder clauses — to make guidance executable rather than descriptive.

Fix or remove the dangling 'resources/implementation-playbook.md' reference; either ship the file or move the detail inline with a real pointer.

Insert an explicit validation/review checkpoint in the Approach (e.g., 'Cross-check mandatory disclosures against the regulation checklist before finalizing').

DimensionReasoningScore

Conciseness

Mostly list-driven and efficient with no over-explanation of regulations Claude already knows; a few generic filler bullets ('Apply relevant best practices and validate outcomes', the 'You are a legal advisor...' line) keep it just below 5.

4 / 5

Actionability

Provides high-level checklists of what to include but no executable templates, clause skeletons, or concrete examples; the single concrete pointer ('open resources/implementation-playbook.md') targets a file that does not exist, leaving only minimal concrete guidance.

2 / 5

Workflow Clarity

A coherent numbered Approach sequence (identify jurisdictions, draft, structure, flag for review) is present, but it has no validation checkpoints or review feedback loops for the document-generation process.

3 / 5

Progressive Disclosure

Sections are reasonably organized, but the one external reference (resources/implementation-playbook.md) is a broken/dangling path with no bundle directory present, and dense regulation/clause lists that would benefit from a separate reference remain inline.

3 / 5

Total

12

/

20

Passed

Description

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

The description is specific and well-targeted to a legal-compliance niche, with strong natural trigger terms and clear concrete outputs. Its main weakness is the absence of any 'Use when' trigger guidance, which caps completeness.

Suggestions

Add a 'Use when...' clause naming concrete user triggers, e.g. 'Use when drafting privacy policies, terms of service, or GDPR/CCPA compliance documents.'

Expand the action vocabulary beyond 'Draft'/'Creates' (e.g., review, update, audit) to push specificity toward comprehensive.

Include common synonyms and abbreviations (ToS, T&Cs, privacy notice, DPA) to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Names several concrete outputs ('privacy policies, terms of service, disclaimers, and legal notices' plus 'GDPR-compliant texts, cookie policies, and data processing agreements'), matching the 'several specific actions; minor gaps' anchor; falls short of 5 because only two verbs (Draft, Creates) carry the action set.

4 / 5

Completeness

Clear concrete 'what' but entirely missing a 'when'/'Use when' clause; per guidelines, missing explicit trigger guidance caps completeness at 3 rather than 2 because the 'what' is specific.

3 / 5

Trigger Term Quality

Strong natural terms (privacy policies, terms of service, disclaimers, GDPR, cookie policies, DPA) users would actually say; not 5 because synonyms (ToS, T&Cs, privacy notice) and a 'Use when' trigger phrase are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear legal-document niche with distinct triggers (GDPR, DPA, cookie policies); minor residual breadth around 'legal notices'/'disclaimers' keeps it just below 5.

4 / 5

Total

15

/

20

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
administrakt0r/AI-Agents-Safe-Coding-Skills
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.