CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

73%

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

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 lean, well-structured overview with a concrete Check/Fix workflow specifying exact schema properties, and a properly signaled one-level reference to references/rule.md for the full code example. Weaknesses are minor: a bit of motivational padding in the intro and a vague post-fix verification step.

DimensionReasoningScore

Conciseness

The ~45-line body is efficient with concrete property names and no concept tutorials, but the intro sentence "reducing friction for brand-aware users and increasing the click-through quality from branded queries" is motivational padding that could be trimmed. Fits anchor 4 (efficient with minor trimmable instances); not 5 due to that padding, not 3 because the excess is limited to one or two phrases.

4 / 5

Actionability

The Fix section specifies exact properties ("Set `url` to the canonical-url homepage URL... `target` pointing to your search results URL with `{search_term_string}` placeholder, and `query-input` as `required name=search_term_string`") and Check gives a concrete detection recipe. Not 5 because the body contains no copy-paste JSON-LD example (deferred to references/rule.md); not 3 because the property-level guidance is concrete and executable, not pseudocode.

4 / 5

Workflow Clarity

A clear Check → Fix → Explain/Code Review sequence: check the homepage for an existing WebSite/SearchAction block, add it if missing, then verify output. Not 5 because the post-fix verification step is vague ("describe how to verify the final page output") with no explicit re-validation loop (e.g., re-run the check or use a Rich Results test); not 3 because a concrete pre-fix check exists and the sequence is unambiguous.

4 / 5

Progressive Disclosure

A short, well-organized overview body with clear section headers and a single, well-signaled one-level-deep reference — "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — which was verified to exist as a real bundle file. Matches the simple-skill exception and anchor 5: clear overview, content appropriately split, easy navigation.

5 / 5

Total

17

/

20

Passed

Description

57%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 explicit trigger clauses with decent natural keywords, but the first sentence is grammatically broken ("Use when applies to sites..."), the core capability (adding WebSite SearchAction schema for the Sitelinks Searchbox) is never stated, and the generic "adding structured data" trigger risks conflicts with other schema skills. It reads as trigger-only guidance with the "what" left implicit.

Suggestions

State the "what" explicitly, e.g. "Adds and verifies WebSite schema with SearchAction JSON-LD to enable Google's Sitelinks Searchbox for branded queries" before the "Use when" clauses.

Fix the garbled first sentence ("Use when applies to sites with internal site search functionality") to a natural trigger such as "Use when the site has internal search functionality".

Add distinct trigger synonyms — "schema markup", "SEO", "sitelinks searchbox", "JSON-LD" — and narrow "adding structured data for the first time" to search-specific schema so it does not fire for unrelated schema tasks.

DimensionReasoningScore

Specificity

Names the domain and 1-2 concrete actions ("optimizing branded search result appearance", "adding structured data") but never mentions the specific artifacts (WebSite schema, SearchAction, Sitelinks Searchbox, JSON-LD), so coverage is not comprehensive. Fits anchor 3 rather than 4 because the actions are generic; not 2 because it goes beyond naming the domain alone.

3 / 5

Completeness

The "when" is explicit (two "Use when..." clauses), but the "what" is only weakly implied — the description never states the skill adds WebSite SearchAction schema for the Sitelinks Searchbox. Not 4 because anchor 4 requires both a clear what and when; not 2 because the trigger clauses do convey an implicit what ("adding structured data").

3 / 5

Trigger Term Quality

Good natural keyword coverage: "internal site search", "branded search result", "structured data" are phrases users would say. Missing a few common variations ("schema markup", "SEO", "sitelinks searchbox", "JSON-LD"), placing it at anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

"Use when... adding structured data for the first time" would plausibly trigger for any structured-data task (Organization, Breadcrumb, Product schema), creating real overlap with sibling SEO schema skills. Not 4 because the overlap risk is more than minor; not 2 because the site-search and branded-result framing keeps it reasonably scoped.

3 / 5

Total

13

/

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/website-search/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.