CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

legal-advisor

Draft privacy policies, terms of service, disclaimers, and legal notices. Creates GDPR-compliant texts, cookie policies, and data processing agreements. Use for legal documentation, compliance texts, or regulatory requirements.

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/legal-advisor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 a well-organized but generic persona-style overview: it names the right focus areas and regulations and mandates a verbatim disclaimer, yet provides little executable, clause-level guidance and no explicit validation of drafted documents. It also contains circular use/don't-use filler and boilerplate instructions that add tokens without information.

Suggestions

Replace the circular "Use this skill when" / "Do not use this skill when" bullets and generic Instructions bullets with concrete drafting guidance, e.g., the mandatory GDPR clauses (lawful basis, data subject rights, retention) or a section skeleton for a privacy policy.

Add an explicit validation checkpoint to the Approach workflow, such as "After drafting, verify every mandatory disclosure for each identified jurisdiction is present before delivering the document."

Move per-regulation compliance checklists and mandatory-clause lists into reference files (e.g., references/gdpr-checklist.md) and link them one level deep from the body, keeping SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The core lists (Focus Areas, Approach, Output) are lean, but the body includes circular filler ("Working on legal advisor tasks or workflows", "The task is unrelated to legal advisor"), generic Instructions bullets ("Apply relevant best practices and validate outcomes"), and regulations annotated with knowledge Claude already has ("GDPR (European Union)"). This is anchor 3 ("mostly efficient but includes some unnecessary explanation") rather than 2, since padding does not dominate the content.

3 / 5

Actionability

Some guidance is concrete — the verbatim disclaimer text, named regulations, and a specified Output list — but there are no clause-level requirements, document templates, or skeletons; the Approach steps ("Identify applicable jurisdictions", "Include all mandatory disclosures") are high-level. This fits anchor 3 ("some concrete guidance but incomplete; missing key details") rather than 4.

3 / 5

Workflow Clarity

The Approach section provides a clear 6-step sequence, but validation checkpoints are implicit at best ("Flag areas requiring specific legal review") with no step verifying completeness or regulatory coverage of the drafted document. This matches anchor 3 ("sequence present but checkpoints missing or implicit"); it is not 4 because no explicit verification step exists, and not 2 because the sequence itself is coherent.

3 / 5

Progressive Disclosure

Sections are well-organized with clear headers and the skill is compact (~50 lines) with no bundle files to reference. However, per-regulation compliance checklists and mandatory clause lists are bulk detail that belongs in one-level-deep reference files, which are absent — anchor 4 ("good structure; minor organization gaps") rather than 5.

4 / 5

Total

13

/

20

Passed

Description

88%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 that clearly states concrete capabilities and includes an explicit "Use for..." trigger clause, covering the legal-documentation niche comprehensively. Keyword coverage and distinctiveness are good but not maximal, missing common synonyms and using broad compliance phrases that create minor overlap risk.

DimensionReasoningScore

Specificity

"Draft privacy policies, terms of service, disclaimers, and legal notices. Creates GDPR-compliant texts, cookie policies, and data processing agreements" lists multiple specific concrete deliverables with comprehensive coverage of the legal-documentation niche, matching the anchor-5 example's breadth. It is not 4 because there are no obvious gaps in coverage within the stated domain.

5 / 5

Completeness

It explicitly answers "what" (drafts privacy policies, terms of service, disclaimers, notices, GDPR-compliant texts, cookie policies, DPAs) and "when" ("Use for legal documentation, compliance texts, or regulatory requirements"), with concrete trigger categories. Anchor 4 would require the when-clause to be noticeably less explicit; here both parts are clearly and explicitly stated.

5 / 5

Trigger Term Quality

Natural keywords like "privacy policies", "terms of service", "GDPR", "cookie policies", and "compliance" are present, but common variations users say ("terms and conditions", "ToS", "EULA", "CCPA") are missing. This fits anchor 4 ("good keyword coverage; a few natural terms missing") rather than 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The named document types (privacy policy, ToS, DPA, cookie policy) form a clear niche, but the broad when-clause phrases "regulatory requirements" and "compliance texts" could overlap with other compliance-domain skills (e.g., finance or healthcare compliance). This is anchor 4 ("mostly distinct; minor overlap risk") rather than 5's minimal conflict risk.

4 / 5

Total

18

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

rmyndharis/antigravity-skills

Path

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