CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

physical-address

Use when auditing local business websites, e-commerce sites, or any site where a physical presence affects trust or local search visibility.

Quality

69%

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/physical-address/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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, actionable audit skill: the Check → Fix → Code Review flow is unambiguous, verification criteria are specific, and detailed implementation is correctly deferred to a real, one-level-deep reference file. Its main weakness is redundancy — the Check and Code Review sections repeat the same address-completeness criteria almost verbatim, and Explain reiterates the intro's rationale.

Suggestions

Merge the Code Review section into Check (or reduce it to a one-line pointer) to eliminate the near-verbatim duplication of the address-completeness criteria.

Trim the Explain section to only the non-obvious detail (NAP/Google Business Profile consistency suppressing local rankings), since the trust and local-SEO rationale is already stated in the intro.

DimensionReasoningScore

Conciseness

The body is short and free of concept-teaching, but the Check section ("Check the contact page and footer for a visible physical address. Verify the address is complete (street, city, state/region, postal code, country)") and the Code Review section ("Check the contact page and footer for visible address text. Verify the address includes: street number and name, city, state/region, postal code, and country") are near-verbatim duplicates, and Explain restates the intro's trust/local-SEO rationale. This fits "Mostly efficient but includes some unnecessary explanation or could be tightened" — not 2 because there is no library-tutorial or concept padding, and not 4 because the Check/Code Review duplication is a genuine, noticeable redundancy.

3 / 5

Actionability

Guidance is concrete and executable: "Wrap it in an <address> HTML element. Ensure the address exactly matches the address in your LocalBusiness JSON-LD schema and your Google Business Profile" and "Flag if no address is found on either contact page or footer" give exact checks, fix steps, and a flag condition. It is not 5 because copy-paste-ready markup (the <address> snippet or JSON-LD example) lives only in references/rule.md rather than the body, and not 3 because the instructions are specific and complete, not high-level hints.

4 / 5

Workflow Clarity

This is a simple, single-purpose skill and the single action is unambiguous: Check defines exactly what to verify (address completeness, <address> element, schema markup), Fix defines the remediation, and Code Review supplies the verification checkpoint "Flag if no address is found on either contact page or footer" plus the exact-match cross-reference. Per the rubric's simple-skill exception this earns a 5; no destructive or batch operations exist that would cap it at 3, and the audit sequence is coherent rather than gappy (not 4).

5 / 5

Progressive Disclosure

The ~35-line body is organized into clear Quick Reference/Check/Fix/Explain/Code Review sections with a single, well-signaled reference — "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — and that file exists (references/rule.md, 114 lines) with no nested references inside it, so the bundle is exactly one level deep. It is not 4 because there are no organization gaps: the pointer is explicit about what the reference contains and everything else is appropriately inline.

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 is a well-formed trigger clause with natural keywords, but it answers only "when" and never "what" — the skill's actual actions (verify address presence/completeness, check <address> markup, ensure schema/Google Business Profile consistency) are entirely unstated, leaving completeness and specificity weak. Prepending one sentence of concrete actions would fix both dimensions at once.

Suggestions

Add a 'what' statement before the trigger clause, e.g., "Verifies a complete physical business address is displayed and marked up with LocalBusiness/PostalAddress schema. Use when auditing..."

DimensionReasoningScore

Specificity

The description names a specific domain — "auditing local business websites, e-commerce sites, or any site where a physical presence affects trust or local search visibility" — but enumerates no concrete actions the skill performs (e.g., verify an address, check schema markup, review a contact page). This matches the anchor "Names the domain but actions are minimal or generic"; it is not 3 because no 1-2 concrete actions are stated, and not 1 because the domain is specific rather than entirely vague.

2 / 5

Completeness

The description is entirely a "when" clause ("Use when auditing local business websites...") and never states what the skill does — displaying/verifying a physical business address is nowhere mentioned. This fits the anchor "only 'when' is present without 'what'"; it is not 3 because that anchor requires a clear "what" which is absent, and not 1 because the "when" is explicit and fairly detailed rather than extremely vague.

2 / 5

Trigger Term Quality

Natural phrases a user would say are present: "auditing local business websites", "e-commerce sites", "physical presence", "trust", "local search visibility". This is good keyword coverage with a few natural terms missing ("local SEO", "NAP consistency", "business address", "contact page"), matching the anchor "Good keyword coverage; a few natural terms missing" — not 5 because those common synonyms are absent, and not 3 because coverage spans both the trust and local-visibility phrasings rather than a few generic keywords.

4 / 5

Distinctiveness Conflict Risk

The local-business/local-search-visibility niche gives it distinct triggers compared to generic skills, matching "Mostly distinct; minor overlap risk with closely related skills". It is not 5 because the broad phrase "any site where a physical presence affects trust" could overlap with other SEO/trust audit skills (e.g., contact-info or schema-markup rules), and not 3 because the local-search framing is specific enough to mostly avoid collisions.

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

Path

skills/physical-address/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.