CtrlK
BlogDocsLog inGet started
Tessl Logo

gog-maps

Google Maps operations through gog.

54

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/gog-maps/SKILL.md
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.

The body is an exemplary lean skill page: concise, executable, and well-structured, with explicit safety guards and clear pointers to per-command contracts. Its only weakness is that write/delete workflows rely on confirm-and-dry-run guidance rather than a concrete validate-then-retry loop.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: a brief orientation line, a three-command safe-start block, a tight flag list, a compact command table, and a closing 'don't guess syntax' pointer — every token earns its place with no padding or basic-concept explanation.

5 / 5

Actionability

It gives copy-paste-ready executable commands (`gog auth list --check --json --no-input`, `gog schema maps --json`) and a concrete command table, but per-command flags and example invocations are deferred to `--help`/`schema` rather than shown inline — a minor gap keeping it just below fully executable.

4 / 5

Workflow Clarity

A clear safe-start sequence (auth → schema → readonly help) plus explicit pre-write validation (confirm account/object/mutation, use --dry-run, --readonly for non-mutating tasks) gives most checkpoints; it is not a 5 because there is no structured validate→fix→retry feedback loop for write/delete operations.

4 / 5

Progressive Disclosure

For an under-50-line single-purpose skill, the body is well-organized into clearly signaled sections (Safe start, Commands) and correctly pushes detail to one level deep via `gog maps <command> --help` and `gog schema maps … --json` plus a cross-reference to `../gog/SKILL.md`; no bundle files exist to verify inline.

5 / 5

Total

18

/

20

Passed

Description

36%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 correctly names the domain and the governing tool but is too terse: 'operations' is abstract, concrete capabilities are absent, and no usage triggers are given. It avoids fluff and stays third-person, but lacks the actionable specificity and trigger guidance that mark a strong description.

Suggestions

Replace the abstract 'operations' with concrete capabilities, e.g. 'Get directions, compute travel distance and duration matrices, geocode addresses, search Places, and reverse-geocode coordinates via gog.'

Add a usage trigger clause, e.g. 'Use when the user asks about Google Maps directions, distances, geocoding, or Places lookups.'

Include natural synonyms a user would say (directions, distance matrix, geocode, Places) to raise trigger-term coverage.

DimensionReasoningScore

Specificity

The description is 'Google Maps operations through gog.' — it names the domain (Google Maps) but states only the abstract action 'operations' with no concrete capability verbs (e.g. directions, geocoding, places), matching the 'entirely vague; no concrete actions' anchor.

1 / 5

Completeness

It conveys a clear 'what' (Google Maps operations via gog) but provides no 'Use when…' clause or equivalent trigger guidance, so the 'when' is entirely missing — the rubric caps completeness at 3 when such guidance is absent.

3 / 5

Trigger Term Quality

'Google Maps operations' supplies one natural keyword ('Google Maps') but omits the common phrases a user would say (directions, geocode, places, distance matrix, reverse-geocode) and any file/extension variants, fitting 'one or two generic keywords; missing the natural phrases'.

2 / 5

Distinctiveness Conflict Risk

'Google Maps operations through gog' carves a clear niche tied to a specific service and tool, with only minor overlap risk against a sibling Google/gog skill; not a 5 because the generic 'operations' leaves trigger specificity slightly loose.

4 / 5

Total

10

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
openclaw/gogcli
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.