CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

local-business

Use when auditing a local business website's structured data. Applies to any business that serves customers at a physical location or specific geographic area.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/local-business/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 well-structured overview with strong progressive disclosure: it defers code examples and framework guidance to a real, substantive references/rule.md and keeps only the essentials inline. Its weaknesses are redundancy — the required-field list appears four times, with Check and Code Review nearly duplicating each other — and explanation of LocalBusiness-schema basics that Claude already knows.

Suggestions

Merge the 'Check' and 'Code Review' sections, which repeat nearly identical detection criteria and required-field lists.

Drop or compress the 'Explain' section and the intro paragraph, which duplicate each other in stating what LocalBusiness schema does (knowledge Claude already has).

State the required-field list once (e.g., in Quick Reference) and reference it from the other sections instead of restating it.

DimensionReasoningScore

Conciseness

The body is compact overall, but the required-properties list is repeated across Quick Reference, Check, Fix, and Code Review (e.g., 'Verify the required properties are present: name, address with PostalAddress, telephone, and url' vs. the near-identical Code Review list), and both the intro paragraph and the Explain section restate what LocalBusiness schema does — knowledge Claude already has. It is not a 2 because each section is terse with no heavy padding, and not a 4 because the Check/Code Review duplication and the Explain section are genuinely trimmable.

3 / 5

Actionability

The Fix section gives a complete, executable spec — 'Add a <script type='application/ld+json'> block ... Include: @context, @type, name, address (with streetAddress, addressLocality, addressRegion, postalCode, addressCountry), telephone, url, openingHours, and geo' — and both Check and Code Review name a concrete validation tool (Google's Rich Results Test). It is not a 5 because the body itself contains no copy-paste-ready JSON-LD example (code is deferred to references/rule.md), and not a 3 because the guidance is specific and complete rather than high-level hints or pseudocode.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review section order implies a clear check/add/validate sequence, and the validation checkpoint ('Validate with Google's Rich Results Test') is present in both Check and Code Review. It is not a 5 because the sequence is implied by section order rather than stated and there is no explicit re-validate-after-fixing feedback loop, and not a 3 because a validation tool is named and the single action (add LocalBusiness JSON-LD) is unambiguous.

4 / 5

Progressive Disclosure

The body is a lean overview with clear sections and a single, well-signaled, one-level-deep reference — 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — and that file exists and carries the bulk detail (full JSON-LD examples, property tables, sub-type list, Next.js implementation, validation, exceptions). This matches the anchor for a clear overview with appropriately split content and easy navigation.

5 / 5

Total

16

/

20

Passed

Description

62%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 is short, in third person, and has an explicit 'Use when...' trigger with a clear applicability statement, so both what and when are answered. Its main gaps are thin action coverage (a single verb, 'auditing') and missing the technical synonyms (LocalBusiness schema, JSON-LD, local SEO) a user would most plausibly say when needing this skill.

Suggestions

Add the core technical trigger terms users would actually say: 'LocalBusiness schema', 'JSON-LD', 'schema markup', and 'local SEO'.

Expand the 'what' beyond the single action 'auditing' — e.g., 'checks required LocalBusiness properties (name, address, telephone) and adds/repairs JSON-LD markup'.

Broaden the trigger scenarios beyond auditing to include when the user asks to add or fix local business schema on a site.

DimensionReasoningScore

Specificity

Names the domain ('local business website's structured data') and one concrete action ('auditing'), matching the anchor for domain plus 1-2 concrete actions but not comprehensive. It is not a 4 because only a single action is listed rather than several specific actions, and not a 2 because 'auditing a local business website's structured data' is concrete rather than generic.

3 / 5

Completeness

Both parts are explicitly present: what ('auditing a local business website's structured data') and when ('Use when auditing...', plus 'Applies to any business that serves customers at a physical location or specific geographic area'). It is not a 5 because the 'what' is a single unenumerated action and the trigger covers only the auditing scenario, and not a 3 because 'when' is explicit, not weakly implied.

4 / 5

Trigger Term Quality

'local business', 'structured data', 'physical location', and 'geographic area' are relevant natural keywords, but common variations users would actually say are missing: 'LocalBusiness schema', 'JSON-LD', 'schema markup', 'local SEO'. It is not a 4 because those core synonyms are absent, and not a 2 because the included keywords are genuinely natural, not generic filler.

3 / 5

Distinctiveness Conflict Risk

'Local business website's structured data' carves a clear niche distinct from most skills, matching 'mostly distinct; minor overlap risk'. It is not a 5 because the broader 'structured data' territory could overlap with sibling schema-markup/SEO skills (e.g., product or article schema), and not a 3 because 'local business' is a specific, well-bounded trigger.

4 / 5

Total

14

/

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/local-business/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.