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. Use PROACTIVELY for legal documentation, compliance texts, or regulatory requirements.

58

Quality

67%

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

46%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 well-organized and scoped to a single domain, but it leans on generic boilerplate and abstract directives rather than concrete, executable legal-drafting guidance, and the workflow lacks validation checkpoints. Tightening the filler and adding specific clause templates or drafting patterns would materially raise the score.

Suggestions

Replace the generic 'Instructions' boilerplate with concrete drafting guidance specific to legal documents — e.g., required GDPR clauses, required TOS sections, or a document scaffold template.

Add a validation/feedback step to the 'Approach' workflow (e.g., 'Verify each mandatory disclosure is present against the regulation's checklist before finalizing').

Remove the templated 'Use this skill when' / 'Do not use this skill when' filler that does not add legal-specific value beyond the frontmatter description.

DimensionReasoningScore

Conciseness

Mostly list-based and reasonably tight, but the templated 'Use this skill when' / 'Do not use this skill when' / generic 'Instructions' boilerplate ('Clarify goals, constraints, and required inputs...') is padding that adds nothing Claude does not already know.

3 / 5

Actionability

Guidance is high-level and abstract — 'Include all mandatory disclosures and clauses', 'Structure documents with logical sections' — with no clause templates, document scaffolding, or concrete drafting patterns, leaving Claude without the specifics needed to execute.

2 / 5

Workflow Clarity

The numbered 'Approach' gives a rough six-step sequence (identify jurisdictions, draft, structure, flag for review) but has no validation checkpoints or feedback loops, and the disclaimer/flag step is only weakly a verification gate.

3 / 5

Progressive Disclosure

A single self-contained SKILL.md with clearly labeled sections (Focus Areas, Approach, Key Regulations, Output) and no nested references; organization is good though the inline regulation/focus lists slightly exceed what a lean overview needs.

4 / 5

Total

12

/

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, concrete description that names specific legal document types and regulations, answers both what and when explicitly, and stays in proper third-person voice. The main gap is trigger-term synonym coverage, which keeps it just below the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete drafting actions across document types — 'Draft privacy policies, terms of service, disclaimers, and legal notices' and 'Creates GDPR-compliant texts, cookie policies, and data processing agreements' — giving comprehensive coverage rather than vague abstraction.

5 / 5

Completeness

Explicitly answers both 'what' ('Draft... Creates...') and 'when' ('Use PROACTIVELY for legal documentation, compliance texts, or regulatory requirements') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural keywords users would actually say ('privacy policies', 'terms of service', 'disclaimers', 'cookie policies', 'GDPR', 'compliance texts'), though a few common synonyms ('terms and conditions', 'TOS', 'privacy notice') are missing and 'Use PROACTIVELY' is directive phrasing rather than a pure natural trigger.

4 / 5

Distinctiveness Conflict Risk

The legal-documentation / compliance niche is well-scoped and clearly distinguishable, with only minor overlap risk against a generic 'compliance' or 'writing' skill.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
rmyndharis/antigravity-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.