CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

service-area

Use when applies to service businesses (plumbers, lawyers, consultants) serving multiple regions. Use when planning local SEO strategy for businesses without brick-and-mortar locations in every city.

Quality

68%

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/service-area/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 audit/fix guide with concrete, actionable specifics and an appropriately delegated one-level-deep reference file. Its main weaknesses are repetition of the doorway-page and areaServed guidance across sections and verification directions that stop short of explicit validation checkpoints.

Suggestions

State the doorway-page warning and areaServed schema guidance once (e.g., in Quick Reference) and have Check/Fix reference them rather than restate them, to trim repeated tokens.

Add an explicit validation checkpoint to the Fix workflow, e.g., "After publishing, verify the LocalBusiness/areaServed structured data with Google's Rich Results Test and spot-check each page for unique content".

DimensionReasoningScore

Conciseness

The body is lean with no explanations of concepts Claude already knows, but key facts repeat: the doorway-page warning appears in the intro ("thin, templated location pages are penalised by Google as doorway pages"), Quick Reference ("Avoid creating identical pages per location that differ only in the city name (doorway pages)"), and Check ("Flag pages that appear to be thin templated clones"), and the areaServed schema guidance appears in Quick Reference, Check, and Fix. Efficient with minor trimmable repetition — anchor 4.

4 / 5

Actionability

Concrete, executable guidance throughout: "Use `LocalBusiness` schema with `areaServed`", "unique title targeting `[Service] in [City]`", "at least 300 words of unique content", "nearby landmarks, local case studies, region-specific FAQs". As an instruction-only skill the absence of inline code is acceptable, but the guidance stops short of copy-paste-ready examples (code lives in references/rule.md), so anchor 4 rather than 5.

4 / 5

Workflow Clarity

A coherent Check → Fix → Explain → Code Review sequence covers audit, remediation, and code-level review, and the Code Review section directs verification ("describe how to verify the final page output"). However, explicit validation checkpoints (e.g., how to confirm schema validity or unique content per page) are not spelled out in the body — anchor 4, not 5.

4 / 5

Progressive Disclosure

A clear under-50-line overview with a single well-signaled, one-level-deep reference: "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — the file exists and contains the JSON-LD code example, per-page checklist, and verification steps. Content is appropriately split between overview body and detailed reference — anchor 5.

5 / 5

Total

17

/

20

Passed

Description

43%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 strong, explicit trigger guidance with natural keywords for the service-area/local-SEO niche. However, it states only "when" conditions — the skill's actual capabilities (creating/auditing service-area pages, LocalBusiness schema with areaServed, doorway-page detection) are never mentioned, which caps completeness and specificity and leaves moderate conflict risk with sibling local-SEO skills.

Suggestions

Add a leading 'what' clause naming concrete capabilities, e.g., "Creates and audits service-area pages for service businesses serving multiple regions, including LocalBusiness schema with areaServed and doorway-page detection", before the 'Use when' triggers.

Include the skill's concrete artifact names ("service area pages", "location pages", "LocalBusiness schema", "areaServed") as trigger terms to improve specificity and findability.

Sharpen the differentiator from general local-SEO/storefront skills, e.g., explicitly scope to businesses with no physical location in the cities they serve.

DimensionReasoningScore

Specificity

The description concretely names the domain ("service businesses (plumbers, lawyers, consultants) serving multiple regions", "local SEO strategy") but states no actions at all — nothing about creating or auditing service-area pages, LocalBusiness schema, or doorway-page checks. This matches anchor 2 ("names the domain but actions are minimal or generic"): not 1 because the domain is specifically identified, not 3 because no concrete actions are listed.

2 / 5

Completeness

Two explicit trigger clauses are present ("Use when applies to service businesses...", "Use when planning local SEO strategy..."), but no "what" whatsoever — the skill's capabilities are never stated. This matches anchor 2 ("only 'when' is present without 'what'"): not 3, which requires a clear "what", and the missing-"when" cap of 3 does not apply since trigger guidance is explicit.

2 / 5

Trigger Term Quality

Good natural keyword coverage: "service businesses", "plumbers, lawyers, consultants", "multiple regions", "local SEO", "brick-and-mortar locations". Common variations like "service area pages", "location pages", "city pages", or "geo-modified queries" are missing, so it falls just short of the comprehensive synonym-level coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The clause "businesses without brick-and-mortar locations in every city" carves out a service-area niche, but the skill would still trigger alongside sibling local-SEO skills (e.g., local-business schema or Google Business Profile skills) for a query like "local SEO for a plumber". Somewhat specific with residual overlap risk — anchor 3; the differentiator is partial and the missing "what" statement provides no further disambiguation.

3 / 5

Total

11

/

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/service-area/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.