CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

55

Quality

63%

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-sequenced audit workflow with genuinely concrete specifics (title pattern, 300-word threshold, exact schema properties) and an appropriately split one-level reference verified to exist. The only notable weakness is mild duplication of the doorway-page rationale between the intro and Quick Reference.

DimensionReasoningScore

Conciseness

The body is tight and imperative ('Create individual pages for each city/region served', 'at least 300 words of unique content'), but the doorway-page warning is stated twice — in the intro ('thin, templated location pages are penalised by Google as doorway pages') and again in a Quick Reference bullet ('Avoid creating identical pages per location... (doorway pages)'). This matches 'Efficient; minor instances of over-explanation that could be trimmed'; not 5 because of that duplication, not 3 because there is no substantive padding.

4 / 5

Actionability

Concrete, specific guidance: 'unique title targeting `[Service] in [City]`', 'LocalBusiness schema with `areaServed`', 'Flag pages that appear to be thin templated clones'. Matches 'Mostly executable guidance... with minor gaps'; not 5 because copy-paste material (the JSON-LD markup example, URL structure) is deferred to the reference rather than inline, not 3 because there is no pseudocode or missing key detail.

4 / 5

Workflow Clarity

A clear Check -> Fix -> Explain -> Code Review sequence with checkpoints ('Verify each page has unique content beyond just swapping city names', 'describe how to verify the final page output'). Matches 'Clear sequence with most checkpoints present; minor validation gaps'; not 5 because the explicit validation steps themselves live in references/rule.md, not in the body.

4 / 5

Progressive Disclosure

The ~35-line body is a well-organized overview (Quick Reference, Check, Fix, Explain, Code Review) that defers detail through a clearly signaled, verified one-level-deep reference ('see `references/rule.md`' — a real file holding the code example, per-page checklist, URL structure, and verification steps). Matches 'Clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation'.

5 / 5

Total

17

/

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 gives two specific 'when' triggers but never states what the skill does, and the opening phrase 'Use when applies to' is ungrammatical. Trigger-term coverage and niche distinctiveness are good, yet the absent 'what' keeps completeness and specificity low.

Suggestions

Add an explicit 'what' clause before the triggers, e.g. 'Audits and creates service-area pages with unique local content and LocalBusiness `areaServed` schema. Use when...' so the description answers both what the skill does and when to use it.

State the concrete capabilities in the description itself (audit for thin templated location pages, add `areaServed` structured data, generate locally unique per-city content) instead of only naming the domain.

Include the natural trigger phrases users would actually say — 'service area pages', 'location pages', 'city pages' — which are currently missing despite being the skill's core subject, and fix the garbled 'Use when applies to' opening.

DimensionReasoningScore

Specificity

The description names the domain concretely ('service businesses (plumbers, lawyers, consultants)', 'local SEO strategy', 'brick-and-mortar locations') but states no capability of the skill itself — 'applies to' and 'planning' describe applicability, not actions. Matches 'Names the domain but actions are minimal or generic'; not 1 (the domain is concrete, not vague) and not 3 (no concrete actions like 'audits' or 'creates service-area pages' are listed).

2 / 5

Completeness

Both sentences are 'when' clauses ('Use when applies to...', 'Use when planning...') and no 'what' is ever stated — the skill's function (auditing/creating service-area pages) is absent, and the opening clause is garbled. Matches 'only when is present without what'; not 1 because the 'when' guidance is specific rather than extremely vague, not 3 because a clear 'what' is entirely missing.

2 / 5

Trigger Term Quality

Good natural-term coverage: 'plumbers, lawyers, consultants', 'local SEO', 'serving multiple regions', 'brick-and-mortar locations'. Matches 'Good keyword coverage; a few natural terms missing'; not 5 because central synonyms users would say ('service area' — the skill's own name — 'location pages', 'city') are absent, not 3 because coverage goes well beyond a single keyword.

4 / 5

Distinctiveness Conflict Risk

Qualifiers like 'service businesses (plumbers, lawyers, consultants)' and 'without brick-and-mortar locations in every city' carve a distinct niche away from general SEO skills. Matches 'Mostly distinct; minor overlap risk with closely related skills'; not 5 because 'planning local SEO strategy' is broad enough to trigger for general local-SEO or storefront local-business requests.

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.

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
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.