CtrlK
BlogDocsLog inGet started
Tessl Logo

tos-clause-scanner

Audit Terms of Service, user agreements, and privacy policies for consumer risks, producing a structured report that flags unfair clauses, data traps, and liability issues. Trigger when a user asks to review, audit, or analyze a ToS, privacy policy, or user agreement, or mentions specific concerns like auto-renewal or data authorization.

72

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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-structured, actionable instruction set with a clear workflow and copy-paste report template. Its main weaknesses are mild verbosity in a few reference sections and only implicit validation checkpoints in the audit workflow.

Suggestions

Add an explicit validation step to the workflow (e.g., 'Verify all seven risk categories were scanned before finalizing the report') to strengthen workflow_clarity toward 5.

Tighten or trim the Quick Start example prompts and the regulatory-reference list to reduce token overhead without losing the actionable core.

Consider externalizing the detailed industry-specific risks (section 5) and full regulatory framework (section 4) into a reference file to improve progressive_disclosure and reduce inline length.

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids explaining concepts Claude already knows, but a few sections (example prompts, the full regulatory list, industry-specific risks) could be tightened without losing value.

4 / 5

Actionability

As an instruction-only skill it provides highly actionable guidance—specific risk patterns, per-category review checklists, a copy-paste-ready report template, and concrete evaluation dimensions—covering the common audit cases.

5 / 5

Workflow Clarity

The audit workflow is clearly sequenced (read full text, scan categories, analyze, sort, append action items) with an explicit cross-check step and citation requirement, though explicit validation checkpoints (e.g., confirm all categories covered) are only implicit.

4 / 5

Progressive Disclosure

Content is well-organized into clearly numbered sections with no broken or deeply nested references; since no bundle files exist, the self-contained inline content (regulatory framework, industry risks) is reasonably placed, though some could be externalized.

4 / 5

Total

17

/

20

Passed

Description

92%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, trigger-rich, and fully answers both what the skill does and when to use it, occupying a clear niche with low conflict risk. Its only minor gap is slightly less exhaustive keyword/synonym coverage.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions—auditing for consumer risks, producing a structured report, and flagging unfair clauses, data traps, and liability issues—matching the comprehensive-coverage anchor.

5 / 5

Completeness

It explicitly answers both 'what' (audit ToS/privacy policies, flag unfair clauses/data traps/liability) and 'when' ('Trigger when a user asks to review, audit, or analyze...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

It surfaces natural trigger terms users would say ('review, audit, or analyze a ToS, privacy policy, or user agreement') plus specific concerns (auto-renewal, data authorization), but a few common synonyms/extensions are absent.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (consumer-side ToS/privacy-policy auditing) with distinct triggers, making overlap with unrelated skills unlikely.

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.