CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nap-consistency

Use when auditing a local business website for local SEO. Applies to any business that has a physical address and wants to appear in local search results or Google Maps.

Quality

70%

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/nap-consistency/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 skill is well-structured with good progressive disclosure to a real references/rule.md file and actionable audit/fix guidance with concrete inconsistency examples. It is dragged down by significant redundancy — duplicate Check/Code Review sections and a concept-explanation section Claude does not need — plus a missing post-fix verification step and the confusing "canonical-url format" wording.

Suggestions

Merge the 'Code Review' section into 'Check' — they are the same procedure written twice — and drop or compress 'Explain' and 'Quick Reference', since the NAP ranking-factor rationale is standard SEO knowledge already stated in the intro.

Fix the copy-paste error "a single canonical-url format" (appears in the Fix section) to read "a single canonical NAP format", so the instruction is not confused with URL canonicalization.

Add a validation step after the fix, e.g., "Re-scan the site and confirm every occurrence (including JSON-LD) now matches the canonical format exactly before finishing", to close the batch-update feedback loop.

DimensionReasoningScore

Conciseness

Several sections are padded or duplicated: "Code Review" restates "Check" almost verbatim ("Extract all instances of the business name, street address, and phone number... Compare each instance for exact formatting consistency" vs "Search the site for all instances of... Compare each occurrence for exact consistency"), the "Quick Reference" bullets restate the intro/Check/Fix, and "Explain" re-explains the same local-SEO ranking-factor concept already covered in the opening paragraph — knowledge Claude already has. This matches "noticeably verbose; several unnecessary explanations or padded sections" rather than anchor 3, because roughly a third of the body could be deleted with no information loss.

2 / 5

Actionability

Concrete, specific guidance with real examples: "(e.g., 'St.' vs 'Street', '555-1234' vs '(555) 123-4567')" for comparison, and a fix that enumerates exact targets — "Update all pages, footer, contact page, about page, and structured data to match exactly". Not anchor 5 because there is no executable mechanism for finding all occurrences (e.g., a search command or extraction snippet), and the instruction "Standardise all NAP occurrences to a single canonical-url format" is confusing — a copy-paste error where "canonical NAP format" was meant.

4 / 5

Workflow Clarity

A rough Check → Fix sequence is present ("Search the site for all instances..." then "Standardise all NAP occurrences...") but there is no verification step after the batch update of all pages and structured data, and the near-duplicate "Check"/"Code Review" sections blur which procedure to follow. Per the batch-operation cap (site-wide page updates with no validate/re-check loop), this cannot exceed 3, matching "sequence present but checkpoints missing or implicit".

3 / 5

Progressive Disclosure

The short body is a clean overview with well-organized sections and one clearly signaled, one-level-deep reference — "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — and the file references/rule.md actually exists and itself contains no second-level references. This matches "clear overview with well-signaled one-level-deep references; easy navigation".

5 / 5

Total

14

/

20

Passed

Description

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

A solid description in third person with an explicit, well-scoped 'Use when...' trigger clause and natural local-SEO keywords. Its main weakness is that the 'what' stays at the level of "auditing for local SEO" without naming the concrete check (NAP consistency), which also weakens distinctiveness against sibling local-SEO skills.

DimensionReasoningScore

Specificity

"auditing a local business website for local SEO" names a clear domain with one concrete action, matching "names domain and 1-2 concrete actions, but not comprehensive" — it never states what is actually checked (NAP: name, address, phone). It is above anchor 2 ("actions are minimal or generic", e.g. "Processes PDF files") because the audit target and purpose are concretely scoped, but below anchor 4 because no specific audit activities are enumerated.

3 / 5

Completeness

Both parts are explicit: 'what' is "auditing a local business website for local SEO" and 'when' is a full "Use when..." clause plus "Applies to any business that has a physical address and wants to appear in local search results or Google Maps." Not anchor 5 because the 'what' is thin — it says "auditing" but not what the audit inspects — whereas the anchor-5 example enumerates concrete actions ("Extract text and tables from PDF files, fill forms, merge documents").

4 / 5

Trigger Term Quality

Natural terms are present — "local business website", "local SEO", "local search results", "Google Maps", "physical address" — phrasing a user doing local SEO work would naturally say. Not anchor 5 because common synonyms the skill itself relies on are missing: "NAP", "Name Address Phone", "citations", "Google Business Profile", "local listings".

4 / 5

Distinctiveness Conflict Risk

The niche is specific — auditing local business websites for local SEO with Maps/local-search triggers — so it is "mostly distinct" with only minor overlap risk against closely related sibling skills (e.g., a LocalBusiness structured-data or general SEO-audit skill). Not anchor 5 because the description never mentions NAP/name-address-phone, the one term that would make its scope unambiguous versus adjacent local-SEO skills.

4 / 5

Total

15

/

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/nap-consistency/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.