CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

geo-meta

Use when auditing locally-focused or regionally-targeted pages for geo targeting signals, particularly on sites targeting audiences through Bing or regional search engines. Note that these meta tags have no documented effect on Google's ranking.

Quality

78%

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/geo-meta/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A tight, highly actionable audit skill: concrete checks with format examples, copy-paste-ready fix code, and a properly signaled one-level-deep reference. The only real weakness is redundancy — the Google/Bing caveat and the 'supplement, not replace' guidance each repeat three to four times across the short body.

Suggestions

State the 'not used by Google, may be read by Bing' and 'supplement, not replace, hreflang/LocalBusiness' caveats once (e.g. in the intro or Quick Reference) and cut the duplicates from the Explain section.

Trim or merge the Explain section into the intro, since it mostly restates the Quick Reference and adds little actionable content.

Fold the Code Review section's format checks into the Check section to avoid repeating the same ISO 3166-2 and lat;long validation twice.

DimensionReasoningScore

Conciseness

The Check, Fix, and Code Review sections are lean and concrete, but the 'supplement, not replace, hreflang/LocalBusiness' caveat is repeated in the intro, Quick Reference, and Explain sections, and 'not used by Google' appears four times across a ~54-line body. Mostly efficient, but the repetition and the largely conceptual Explain section could be trimmed.

3 / 5

Actionability

Fully executable guidance: a copy-paste-ready HTML block with concrete values, exact tag names, explicit format examples ('US-CA', 'GB-ENG', '37.7749;-122.4194'), consistency requirements between geo.position and ICBM, and specific flag criteria in Code Review.

5 / 5

Workflow Clarity

A clear Check → Fix → Code Review audit flow with validation built into the Check step (format verification with examples). It falls short of anchor 5 because the steps are not sequenced as an explicit workflow with a re-verify loop after fixes, though the single-purpose audit is unambiguous.

4 / 5

Progressive Disclosure

A well-sectioned overview (Quick Reference, Check, Fix, Explain, Code Review) that points to a real, clearly signaled, one-level-deep reference ('see references/rule.md', verified to exist at 133 lines) for full implementation details. Content is appropriately split and easy to navigate.

5 / 5

Total

17

/

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 well-scoped description with a clear 'Use when' trigger, strong natural keywords, and a distinctive Bing/geo-targeting niche. Its main weakness is that the 'what' stays abstract — it names the audit purpose but not the concrete actions or the specific meta tags involved.

Suggestions

Name the concrete actions and artifacts, e.g. 'Checks for and adds geo meta tags (geo.region, geo.placename, geo.position) and validates their ISO 3166-2 and lat;long formats' — this would lift both specificity and completeness.

Use 'geo meta tags' or 'meta tags' explicitly as a trigger term instead of only 'geo targeting signals', since users auditing pages would naturally say 'geo meta tags' or 'local SEO'.

Optionally state what the skill does on failure/practice (check, fix, and review guidance) to make the 'what' as explicit as the 'when'.

DimensionReasoningScore

Specificity

Names the domain ('geo targeting signals', 'locally-focused or regionally-targeted pages') and one concrete action ('auditing... for geo targeting signals'), but does not list several specific actions such as which meta tags are checked or fixed. It exceeds anchor 2 because the action is concrete rather than generic, but falls short of anchor 4's several specific actions.

3 / 5

Completeness

Both 'what' ('auditing... pages for geo targeting signals') and an explicit 'when' clause ('Use when auditing locally-focused or regionally-targeted pages... through Bing or regional search engines') are present, with a useful Google caveat. Not 5 because the 'what' is indirect — it never explicitly names the meta tags the skill checks or fixes.

4 / 5

Trigger Term Quality

Good natural keyword coverage: 'auditing', 'geo targeting signals', 'locally-focused', 'regionally-targeted', 'Bing', 'regional search engines'. A few natural terms are missing — 'meta tags' appears only as the indirect 'these meta tags', and variations like 'geo meta tags' or 'local SEO' are absent, so it does not reach anchor 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (geo targeting signals for Bing and regional search engines) that is mostly distinct from other skills, with only minor overlap risk against broader local-SEO or hreflang-related audit 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/geo-meta/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.