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

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/physical-address/SKILL.md

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 body is well-structured with a clear overview and a properly signaled single reference file, achieving good progressive disclosure. Its main weaknesses are duplicated check instructions, an Explain section that over-justifies known concepts, and the absence of a concrete markup/schema example and a verify-after-fix step.

Suggestions

Merge the Check and Code Review sections (they repeat the same verification list) and trim the Explain rationale to only the non-obvious LocalBusiness/Google Business Profile matching point, reducing redundancy.

Add a short copy-paste example of an <address> element with matching LocalBusiness PostalAddress JSON-LD to make the Fix fully actionable.

Add an explicit post-fix verification step (re-check that the visible address, JSON-LD, and Google Business Profile all match exactly) to give the Check→Fix flow a clear validation checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with bulleted Quick Reference and short sections, but the Check and Code Review sections repeat nearly identical verification instructions and the Explain section restates widely-known trust/SEO rationale, fitting the 'mostly efficient but could be tightened' anchor rather than the every-token-earns-its-place level 3.	2 / 3
Actionability	Guidance is concrete (specify street/city/state/postal/country, wrap in <address>, match LocalBusiness JSON-LD and Google Business Profile exactly), but no example <address> markup or JSON-LD snippet is provided, leaving it at 'some concrete guidance but incomplete / missing key details' rather than copy-paste ready level 3.	2 / 3
Workflow Clarity	A Check-then-Fix sequence is present and the Check section acts as a verification checklist, but there is no explicit validate-after-fix step or feedback loop, matching the 'steps listed but validation checkpoints missing or implicit' anchor.	2 / 3
Progressive Disclosure	SKILL.md is a concise overview that clearly signals a single one-level-deep reference ("see references/rule.md"), and that file exists, matching the 'clear overview with well-signaled one-level-deep references' anchor.	3 / 3
	Total	9 / 12 Passed

Description

50%

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 clear, well-formed trigger clause with a defined niche, but it functions almost entirely as a "when" statement and never names the skill's concrete capability (displaying/verifying a physical address). Adding an explicit "what" and the core keyword "address" would lift specificity, completeness, and trigger-term quality together.

Suggestions

Lead with the concrete action before the trigger, e.g. "Verifies and displays a physical business address with LocalBusiness schema. Use when auditing..." to make the "what" explicit and raise specificity and completeness.

Include the central keyword "address" plus natural variants ("NAP", "contact page", "LocalBusiness schema", "Google Business Profile") in the trigger clause to improve trigger-term coverage.

Tighten the trigger to the actual scope (contact-page/footer address + schema matching) so it is less likely to overlap with generic SEO-audit skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ("local business websites, e-commerce sites") and a general action ("auditing") but lists no concrete capabilities such as verifying or displaying an address, so it sits at the 'names domain and some actions, but not comprehensive' anchor rather than the multi-action level 3.	2 / 3
Completeness	The "Use when..." clause answers "when" explicitly and clearly, but "what does this do" is only implied through the word "auditing" rather than stated, so it does not reach the explicit both-what-and-when level 3.	2 / 3
Trigger Term Quality	Natural terms like "local business", "e-commerce", and "local search visibility" appear, but the central keyword "address" (and common variants like "NAP" or "LocalBusiness schema") is absent, leaving coverage with relevant keywords but missing common variations.	2 / 3
Distinctiveness Conflict Risk	The physical-presence/local-SEO niche is somewhat specific, yet the broad phrasing "auditing local business websites... or any site where a physical presence affects trust" could overlap with general SEO-audit or trust-review skills, matching the 'somewhat specific but could still overlap' anchor.	2 / 3
	Total	8 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/physical-address/SKILL.md
Commit: 48405aa

Reviewed: about 7 hours ago

Table of Contents

Discovery Implementation Validation

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.