CtrlK
BlogDocsLog inGet started
Tessl Logo

gog-maps

Google Maps operations through gog.

65

Quality

78%

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

100%

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 model of lean, actionable, well-structured guidance: concrete commands, a clear safe-start workflow with explicit write-safety checkpoints, and a single clearly-signaled one-level reference to the shared parent skill. It assumes Claude's intelligence and wastes no tokens.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: a brief safe-start block, a compact command table, and terse flag guidance, with no padded explanation of what Google Maps is or how APIs work. Every token earns its place.

3 / 3

Actionability

It provides concrete, executable commands (e.g. `gog auth list --check --json --no-input`, `gog --readonly --account user@example.com maps --help`), specific flags, a command table, and clear discovery guidance via `--help` and `schema ... --json`. The guidance is copy-paste ready.

3 / 3

Workflow Clarity

The Safe start section gives a clear discovery sequence, and writes are gated by explicit checkpoints — confirm account/object/mutation before writes/deletes and use `--dry-run` before supported writes. For a simple command-wrapper skill the workflow is unambiguous with explicit safety validation.

3 / 3

Progressive Disclosure

The skill is under 50 lines with well-organized sections and no local bundle files; its only reference is the one-level-deep `../gog/SKILL.md`, clearly signaled with "Read ... first". Navigation is easy and references are not nested.

3 / 3

Total

12

/

12

Passed

Description

57%

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 concise, third-person, and clearly niched to Google Maps via the gog tool, but it is vague on specific capabilities and lacks any explicit use-trigger guidance. It reads as a competent but minimal declaration rather than a discovery-optimized trigger.

Suggestions

Replace the vague word "operations" with concrete actions, e.g. "Get directions, geocode addresses, search places, and compute distances through gog."

Add an explicit trigger clause such as "Use when the user asks about Google Maps, directions, routes, geocoding, or nearby places."

Include common natural term variations (maps, routes, directions, geocoding) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The phrase "Google Maps operations through gog" names the concrete domain and tool but relies on the vague word "operations" rather than listing specific actions (e.g. directions, geocode, places). It is above a 1 because the domain is concrete, but below a 3 because no concrete actions are enumerated.

2 / 3

Completeness

It states what the skill does (Google Maps operations via gog) but provides no "Use when…" trigger or equivalent guidance for when Claude should invoke it. Per the judging guideline, a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

"Google Maps" is a natural term users would say, but the description omits common variations and intents such as directions, routes, geocoding, or distance. It has some relevant keywords but lacks coverage, matching the level-2 anchor.

2 / 3

Distinctiveness Conflict Risk

"Google Maps operations through gog" carves out a clear, specific niche tied to a distinct tool, making it unlikely to trigger for unrelated skills.

3 / 3

Total

9

/

12

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.