CtrlK
BlogDocsLog inGet started
Tessl Logo

local-seo

Audit a Google Business Profile, compare it to local competitors, and map Maps visibility around a location.

68

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 concise, highly actionable, well-sequenced workflow with strong guardrails — the main weakness is that everything lives in one file with no progressive disclosure via reference files.

Suggestions

Move the per-tool API detail (the 'OpenSEO MCP tools' section) into a references file and link to it, keeping SKILL.md as a concise overview.

Consider a separate references doc for the output-format/table guidance so the workflow stays lean.

Add clearly signaled, one-level-deep reference links (e.g. See TOOLS.md) to lift progressive disclosure.

DimensionReasoningScore

Conciseness

Lean and efficient throughout; assumes Claude's competence, never explains what Maps/GBP is, and every line carries actionable information.

5 / 5

Actionability

Fully executable guidance — concrete tool names, specific parameters (minRating, isClaimed: false, 3x3 vs 5x5), exact thresholds (>5 locations → ask), and cid/place_id matching rules.

5 / 5

Workflow Clarity

An 8-step sequenced workflow with explicit validation checkpoints for paid/batch operations (check research log before spending credits, confirm coordinate before grid) and a prioritization rule.

5 / 5

Progressive Disclosure

Well-organized into sections, but with no bundle files all content is inline in a single SKILL.md rather than split into one-level-deep references.

3 / 5

Total

18

/

20

Passed

Description

71%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 specific and covers concrete actions well, but lacks an explicit 'Use when…' trigger clause, which caps completeness. Adding natural trigger phrases like 'Use when auditing local SEO or Google Maps rankings' would lift both completeness and trigger-term quality.

Suggestions

Add a 'Use when…' clause naming the trigger scenarios (e.g. local SEO audits, Google Maps ranking, local pack visibility) to satisfy the completeness requirement.

Include synonyms users naturally say — 'local SEO', 'local pack', 'GBP' — to broaden trigger-term coverage.

Briefly state when NOT to use it (national organic work) in the description to sharpen distinctiveness from sibling skills.

DimensionReasoningScore

Specificity

Lists three concrete, comprehensive actions — 'Audit a Google Business Profile, compare it to local competitors, and map Maps visibility' — fully covering the skill's domain.

5 / 5

Completeness

Has a clear 'what' but no explicit 'Use when…' clause, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Includes natural terms ('Google Business Profile', 'local competitors', 'Maps visibility') but misses common synonyms like 'local SEO', 'local pack', or 'GBP'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear GBP/Maps niche with distinct triggers; minor overlap risk with sibling SEO skills like competitor-analysis.

4 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
every-app/open-seo
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.