CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gog-maps

Google Maps through gog. Use for Maps place search, place details, directions, and geocoding.

Quality

83%

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

86%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 lean, generated command-reference skill that respects the token budget, provides executable safe-start commands, a clear command table, and explicit write-safety checkpoints. Its only notable gaps are the absence of example invocations for the maps commands themselves and any output-validation feedback loop.

DimensionReasoningScore

Conciseness

Every line earns its place: a two-sentence intro pointing to the parent skill, a three-command safe-start block, a five-row command table, and terse safety bullets — no concept explanations, no padding, and it assumes Claude's competence throughout.

5 / 5

Actionability

The safe-start block ("gog auth list --check --json --no-input", "gog schema maps --json") is copy-paste ready and the command table is concrete, but no example invocations with arguments are shown for the maps commands themselves, deferring instead to "--help" and "gog schema".

4 / 5

Workflow Clarity

The safe-start sequence is clear with explicit checkpoints for risky operations ("--dry-run before supported writes", "Confirm the exact account, object, and mutation before any write or delete"), but there are no feedback loops or output-validation steps, and write-safety detail is deferred to the parent skill.

4 / 5

Progressive Disclosure

A ~30-line overview with well-organized sections whose only reference is a clearly signaled, one-level-deep pointer ("Read `../gog/SKILL.md` first for shared auth, output, safety, and live-write rules"), with per-command details appropriately delegated to CLI help and schema output.

5 / 5

Total

18

/

20

Passed

Description

75%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 concise, concrete description that names the tool, domain, and four specific capabilities with an explicit "Use for" trigger clause. It stops short of comprehensive capability coverage (distance and reverse-geocode absent) and lacks user-mention trigger phrasing and synonyms, holding most dimensions at 4.

Suggestions

Cover the full command surface: add "distance matrix" and "reverse-geocode" to the capability list so the description matches the body's command table (specificity, completeness).

Add user-mention trigger phrasing, e.g. "Use when the user asks for directions, place searches, or converting addresses to coordinates", to make the when-clause explicit and capture natural synonyms like "address" and "coordinates" (completeness, trigger_term_quality).

DimensionReasoningScore

Specificity

Lists four concrete actions — "Maps place search, place details, directions, and geocoding" — but omits "distance" and "reverse-geocode" which appear in the body's command table, so coverage has minor gaps rather than being comprehensive.

4 / 5

Completeness

Both parts are explicit — what ("Google Maps through gog") and when ("Use for Maps place search, place details, directions, and geocoding") — but the when-clause lists capabilities rather than user-trigger phrasing, so it could be more explicit and specific.

4 / 5

Trigger Term Quality

Natural terms like "Google Maps", "directions", and "geocoding" are present, but common user phrasings such as "address", "coordinates", "distance", or "nearby" are missing — good keyword coverage with a few natural terms absent.

4 / 5

Distinctiveness Conflict Risk

"Google Maps through gog" carves out a clear niche with distinct triggers, but generic terms like "geocoding" and "directions" create minor overlap risk with other geo/navigation skills.

4 / 5

Total

16

/

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

openclaw/gogcli

Path

.agents/skills/gog-maps/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.