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

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/terms-of-service/SKILL.md

Quality

Content

78%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, lean overview that delegates detail to a single real reference file, with concrete actionable Check/Fix/Explain steps. The main gap is the absence of explicit verification checkpoints and any inline example, leaving it just below top marks on workflow clarity and actionability.

Suggestions

Add an explicit Verify step (e.g., confirm the footer link resolves, appears on interior pages, and the registration checkbox is required) to strengthen workflow clarity.

Inline one short footer/checkbox snippet or a verification command so the body is self-sufficient for the common case, complementing the reference.

Trim the opening explanatory sentence on what ToS protect, since the reference already covers the 'why it matters' rationale.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-sectioned with no padding over basic concepts; the brief opening paragraph on ToS purpose is the only mild over-explanation, fitting 'efficient; minor instances that could be trimmed' rather than the fully lean 5.	4 / 5
Actionability	Gives concrete, specific guidance ('Check whether the website footer contains a link to a Terms of Service page', 'add an explicit acceptance checkbox during registration'); per the instruction-skill note code absence is not penalized, but it falls just short of 5 since copy-paste examples live in the reference rather than the body.	4 / 5
Workflow Clarity	Check -> Fix -> Explain -> Code Review sections provide a clear sequence for a simple single-purpose skill, but there are no explicit validation checkpoints, matching 'clear sequence with most checkpoints present; minor validation gaps' rather than the checkpoint-rich 5.	4 / 5
Progressive Disclosure	The body is a concise overview with a clearly signaled one-level-deep reference ('see references/rule.md'), and rule.md exists and holds the detailed implementation; this matches 'clear overview with well-signaled one-level-deep references'.	5 / 5
	Total	17 / 20 Passed

Description

66%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-oriented, and clearly distinct, with an explicit 'Use when' clause and a well-scoped niche. It could improve by listing more concrete review actions and adding common ToS synonyms ('ToS', 'Terms and Conditions').

Suggestions

Add concrete review actions (e.g., 'verify the footer link resolves, check it appears on interior pages, confirm a registration acceptance checkbox exists') to lift specificity.

Include common synonyms users say — 'Terms of Service (ToS)', 'Terms and Conditions', 'Terms of Use' — to broaden trigger term coverage.

State the 'what' as an explicit third-person capability before the 'Use when' clause (e.g., 'Reviews footer Terms of Service link visibility and signup acceptance. Use when...').

Dimension	Reasoning	Score
Specificity	Names the ToS-link-visibility domain and a single concrete review action ('reviewing whether a website or web application has a visible Terms of Service link accessible from every page'), matching the 'names domain and 1-2 concrete actions' anchor; it does not enumerate several specific actions so it stays below 4.	3 / 5
Completeness	Provides an explicit 'Use when...' trigger and an implicit but clear 'what' (reviewing ToS link visibility); the 'when' is explicit while the 'what' could be stated more directly, matching 'both what and when; when could be more explicit' rather than the fully explicit 5.	4 / 5
Trigger Term Quality	Includes natural terms a user would say ('website or web application', 'Terms of Service link') but omits common synonyms such as 'ToS', 'Terms and Conditions', or 'Terms of Use', fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Targets a clear, narrow niche (footer ToS link visibility across all pages) with distinct triggers and minimal overlap risk with other skills, matching the 'clear niche with distinct triggers' anchor.	5 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/terms-of-service/SKILL.md
Commit: 30756a7

Reviewed: 13 days ago

Table of Contents

Discovery Implementation Validation

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.