CtrlK
BlogDocsLog inGet started
Tessl Logo

website-search

Use when applies to sites with internal site search functionality. Use when optimizing branded search result appearance or adding structured data for the first time.

57

Quality

66%

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/website-search/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 content is a concise, well-structured overview that assumes Claude's competence and delegates detail to a single real reference file. The main gap is the absence of a complete copy-paste JSON-LD example inline, which keeps actionability just short of fully executable.

DimensionReasoningScore

Conciseness

The body is lean and efficient with no padding or explanation of concepts Claude already knows (e.g., it never explains what JSON-LD or schema is); every section earns its place, matching the 'Lean and efficient' anchor.

5 / 5

Actionability

Concrete guidance is present via specific field names ("@type": "WebSite", SearchAction, target, "query-input": "required name=search_term_string", {search_term_string} placeholder), but there is no complete copy-paste code block inline — the full example is delegated to references — so it is 'mostly executable' rather than fully copy-paste ready.

4 / 5

Workflow Clarity

The Check, Fix, Explain, and Code Review sections form a clear sequenced workflow, and verification of the final page output is mentioned, but explicit validation checkpoints are only lightly signaled, matching 'clear sequence with most checkpoints present; minor validation gaps.'

4 / 5

Progressive Disclosure

The body is a concise overview with a single well-signaled, one-level-deep reference to references/rule.md (verified to exist), giving clear navigation appropriate for a simple skill.

5 / 5

Total

18

/

20

Passed

Description

47%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 provides clear trigger guidance for when to use the skill but omits any statement of what the skill actually does, leaving the 'what' half of completeness unaddressed. Trigger terms and distinctiveness are solid.

Suggestions

Add a concise 'what' clause stating the concrete action, e.g. 'Adds WebSite JSON-LD schema with a SearchAction to enable Google's Sitelinks Searchbox.'

Lead with the action before the triggers so the description reads as 'Adds WebSite SearchAction JSON-LD schema. Use when...' to satisfy both what and when.

Include a natural synonym such as 'JSON-LD' or 'Sitelinks Searchbox' to round out trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ("internal site search functionality", "branded search result appearance", "structured data") but never states a concrete action the skill performs; there are no verbs like add, generate, or validate, matching the anchor 'Names the domain but actions are minimal or generic.'

2 / 5

Completeness

Two explicit "Use when..." clauses answer 'when', but there is no clear 'what' — the description never says what the skill does, fitting the anchor 'only when is present without what'.

2 / 5

Trigger Term Quality

Phrases like "internal site search functionality", "branded search result appearance", and "structured data" are natural terms a user would say, giving good coverage, though a few common synonyms are missing so it is not a 5.

4 / 5

Distinctiveness Conflict Risk

The niche (Sitelinks Searchbox / WebSite SearchAction structured data) is fairly distinct with clear triggers and only minor overlap risk with general SEO or structured-data skills.

4 / 5

Total

12

/

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
thedaviddias/Front-End-Checklist
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.