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.

70

Quality

86%

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

72%

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-structured and highly actionable with concrete risk patterns, checklists, and a complete report template. Its main weakness is verbosity in the reference-style sections and the absence of an explicit completion-validation step in the workflow.

Suggestions

Add an explicit validation step to the workflow (e.g., 'Before outputting, confirm all seven risk categories were scanned and every finding quotes original text') to raise workflow_clarity.

Condense §4 (regulatory framework) and §5 (industry-specific risks) into tighter reference lists or move them to a separate reference file to improve token efficiency.

DimensionReasoningScore

Conciseness

The body is substantive domain content (risk patterns, checklists, report template) with no Claude-already-knows padding, but at ~280 lines the regulatory reference list (§4) and industry-specific risk catalog (§5) lean encyclopedic and could be tightened, matching the "mostly efficient but could be tightened" anchor rather than fully lean.

2 / 3

Actionability

It gives concrete, specific guidance — per-category risk patterns, review checklists, and a near copy-paste-ready report output template with plain-language explanation principles — so an instruction-only skill here meets the fully actionable anchor.

3 / 3

Workflow Clarity

Sequenced workflows exist (§2.1 four-step input processing, §6.2 five-step workflow) with defined evaluation dimensions, but there is no explicit validation checkpoint confirming all seven categories were covered or the report is complete before output, leaving it at the steps-listed-but-checkpoints-implicit level.

2 / 3

Progressive Disclosure

It is a single self-contained SKILL.md with no bundle files and no nested references, but is well organized into clearly numbered sections, which the rubric scores at 3 for skills with no need for external references.

3 / 3

Total

10

/

12

Passed

Description

100%

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, third-person, and explicitly pairs a concrete capability statement with a natural trigger clause. It avoids vagueness and reads as a clear, distinct skill. No changes needed.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Audit Terms of Service... producing a structured report that flags unfair clauses, data traps, and liability issues" — and uses correct third-person voice, matching the score-3 anchor for listing several specific concrete actions.

3 / 3

Completeness

It clearly answers both "what" (audit ToS/privacy policies and produce a structured risk report) and "when" via the explicit "Trigger when a user asks to review, audit, or analyze..." clause, satisfying the score-3 anchor.

3 / 3

Trigger Term Quality

It surfaces natural user phrasings ("review, audit, or analyze a ToS, privacy policy, or user agreement") plus concrete concerns ("auto-renewal or data authorization"), giving good coverage of terms users would actually say.

3 / 3

Distinctiveness Conflict Risk

The consumer-side ToS/privacy-policy auditing niche with distinct triggers (ToS, privacy policy, auto-renewal, data authorization) is unlikely to overlap with unrelated skills, matching the score-3 clear-niche anchor.

3 / 3

Total

12

/

12

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.