CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

terms-of-service

Use when reviewing whether a website or web application has a visible Terms of Service link accessible from every page.

Quality

72%

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/terms-of-service/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 overview with concrete, actionable check/fix guidance and a clean single-file reference that is appropriately one level deep. Its weaknesses are mild padding — the legal-background intro and the generic Code Review boilerplate — which keep conciseness below the top tier.

Suggestions

Trim the opening paragraph to one short clause (or drop it) — the legal rationale for ToS is background Claude already knows and is repeated in references/rule.md's 'Why It Matters' section.

Rewrite or drop the Code Review boilerplate; as written, 'server config, headers' is irrelevant to a footer link check — instead give the concrete review target (inspect the rendered footer on interior pages, verify the registration form's acceptance checkbox) or point to references/rule.md for it.

Inline one tiny example of the expected footer markup or the acceptance checkbox so the Check step has a concrete thing to look for without leaving SKILL.md.

DimensionReasoningScore

Conciseness

The body is compact and mostly earns its tokens (Quick Reference bullets on enforceability and clickwrap are genuinely additive), but the opening legal primer ("limiting liability, establishing jurisdiction, setting rules for user conduct...") explains background Claude does not need, and the Code Review section's generic boilerplate ("server config, headers, forms, and integration points") is filler. This sits at 'mostly efficient but includes some unnecessary explanation', below level 4's 'minor instances of over-explanation'.

3 / 5

Actionability

The Check and Fix sections give concrete, executable instruction ("Check whether the website footer contains a link to a Terms of Service page. Verify the link is present on all pages including interior pages... add an explicit acceptance checkbox during registration"), which per the scoring notes is the right bar for an instruction-only skill. It falls short of level 5 only because no inline example of what to look for (e.g., a sample footer snippet) or verification method is given.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is clear and the Code Review section includes a verification checkpoint ("verify them against the effective production-like response"), so this is above level 3. It misses level 5 because the Code Review section drifts — "server config, headers, forms, and integration points" do not map cleanly to a footer link check, leaving the sequence slightly incoherent at its final step.

4 / 5

Progressive Disclosure

The body is a small, well-organized overview with section headers, and it cleanly points to a single one-level-deep reference that exists in the bundle ("For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`"). The bundle contains exactly that one file, so navigation is trivial and matches the 'clear overview with well-signaled one-level-deep references' anchor.

5 / 5

Total

16

/

20

Passed

Description

62%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 has a clear, explicit trigger and a distinct niche (ToS link discoverability), but it only communicates a single review action and omits natural synonyms like "ToS", "terms and conditions", and "footer". It is serviceable but below the bar set by the good examples, which state capabilities separately from the trigger.

Suggestions

State the what separately from the when — e.g., 'Reviews the site footer for a Terms of Service link on every page and checks for an explicit acceptance step during signup. Use when auditing a website or when the user mentions ToS, terms and conditions, or legal links in the footer.'

Add natural trigger synonyms — 'ToS', 'terms and conditions', 'terms of use', 'footer' — to widen keyword coverage.

Mention the related checks the skill covers (acceptance checkbox, stable terms URL) so the capability list is not limited to link visibility alone.

DimensionReasoningScore

Specificity

The description names the domain and one concrete action — "reviewing whether a website or web application has a visible Terms of Service link accessible from every page" — but lists no other capabilities (fix, explain, review guidance). It matches the 'names domain and 1-2 concrete actions' anchor, not level 4 which expects several specific actions.

3 / 5

Completeness

The explicit "Use when..." trigger is present and the what (reviewing ToS link visibility on every page) is discernible, but the what is embedded in the trigger clause rather than stated as its own capability statement, and it covers only the check. Level 5 requires both what and when clearly and explicitly stated with concrete trigger phrases.

4 / 5

Trigger Term Quality

Relevant keywords are present ("Terms of Service", "website", "web application", "link", "every page") but common variations users would naturally say are missing — "ToS", "terms and conditions", "footer". This is 'some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

"Terms of Service" carves out a clear niche distinct from generic skills, but the phrasing overlaps with sibling footer-link checklist rules (e.g., privacy policy link checks), so it is 'mostly distinct; minor overlap risk with closely related skills' rather than fully distinct.

4 / 5

Total

14

/

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

thedaviddias/Front-End-Checklist

Path

skills/terms-of-service/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.