CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

60

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%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill uses good progressive disclosure with a verified one-level reference and sectioned content, but the body suffers from redundant Check/Code Review sections, prose-only guidance, and a workflow lacking explicit verification checkpoints. Tightening duplication and adding a sequenced audit-with-verify flow would raise the weaker dimensions.

Suggestions

Remove the near-duplicate 'Code Review' section (it repeats 'Check') and trim the conceptual 'Explain' section to cut redundant tokens.

Add a numbered audit workflow (extract → compare → standardize → update all pages → verify) with an explicit verification checkpoint, since updating every page is a batch operation.

Provide concrete executable tooling (e.g., a site-wide grep/search command or a small script) instead of prose instructions so the Check/Code Review steps are copy-paste ready.

DimensionReasoningScore

Conciseness

The body is mostly lean and sectioned, but the 'Code Review' section nearly duplicates 'Check' and the 'Explain' section restates local-SEO concepts Claude already knows, so it could be tightened.

2 / 3

Actionability

Concrete fields and locations to check are specified, but guidance stays in prose with no executable command or script, and 'Report any differences' is vague, leaving it short of copy-paste-ready.

2 / 3

Workflow Clarity

An implied Check→Fix sequence exists, but steps are not numbered and there is no explicit validation checkpoint despite 'Fix' being a batch update across all pages, which caps clarity at 2.

2 / 3

Progressive Disclosure

The body is a concise overview that clearly signals a single one-level-deep reference ('see references/rule.md'), which exists and does not nest further, giving clean navigation.

3 / 3

Total

9

/

12

Passed

Description

82%

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 is well-structured with an explicit 'Use when...' trigger and natural search terms, clearly answering both what and when. It is held back only by listing a single action and some overlap risk with adjacent local-SEO skills.

DimensionReasoningScore

Specificity

Names the domain ('local business website', 'local SEO') and a single concrete action ('auditing'), but does not list multiple specific actions, so it falls short of the top anchor.

2 / 3

Completeness

Opens with an explicit 'Use when...' clause for the trigger and states what it does ('auditing a local business website for local SEO'), satisfying both what and when.

3 / 3

Trigger Term Quality

Includes natural terms a user would say ('local SEO', 'local business website', 'local search results', 'Google Maps'), giving good coverage of likely trigger phrasing.

3 / 3

Distinctiveness Conflict Risk

The local-SEO/physical-address niche is specific, but it could overlap with sibling local-SEO rules (e.g., LocalBusiness schema, Google Business Profile) referenced elsewhere.

2 / 3

Total

10

/

12

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.