The body is mostly efficient with concrete sections, but the Google/Bing distinction and the "supplement, not replace, hreflang/LocalBusiness" point are repeated across the intro, Quick Reference, Explain, and Code Review, and the Explain section restates points already covered. It is above level 1 (no padding about basic concepts Claude already knows) but could be tightened to reach level 3.

It provides copy-paste-ready HTML in Fix and explicit, specific validation rules in Check (ISO 3166-1/3166-2 codes, lat;lon format, ICBM matching geo.position), giving concrete executable guidance rather than vague direction.

This is a simple single-task skill with a clear, well-organized Check → Fix → Code Review flow and numbered verification points; per the simple-skills note it qualifies for level 3, and no destructive/batch feedback-loop cap applies.

The body is under 50 lines, well-organized into sections, and points to a single real one-level-deep bundle file (references/rule.md, verified to exist) for full details, matching the clear-overview-with-well-signaled-reference anchor.

The description names the domain ("locally-focused or regionally-targeted pages") and a single concrete action ("auditing ... for geo targeting signals"), but does not enumerate multiple specific actions the way the level-3 anchor expects. It is above level 1 because a concrete action and domain are named, but stops short of listing several distinct actions.

It contains an explicit "Use when ..." trigger clause and states what the skill does (audits pages for geo targeting signals), answering both what and when; the Google/Bing scoping note adds useful context. It is not capped at 2 because explicit trigger guidance is present.

It surfaces natural terms a user would actually say when needing this skill — "locally-focused", "regionally-targeted pages", "geo targeting signals", "Bing", "regional search engines", and "meta tags" — giving good coverage rather than the thin single-phrase level-2 example.

The geo-meta / Bing / regional-search-engine niche is distinct, and the explicit note that these tags have no documented effect on Google carves it away from general local-SEO or hreflang skills, making conflicts unlikely.