CtrlK
BlogDocsLog inGet started
Tessl Logo

maps

Geocode, POIs, routes, timezones via OpenStreetMap/OSRM.

57

Quality

68%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/productivity/maps/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 well-structured, highly actionable CLI skill body with executable examples for all 8 commands and a verification section; only minor conciseness and organization trimming keep it from top marks.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence (no 'what is geocoding' padding), but the supersedes paragraph restates frontmatter metadata and the 46-item category list is light bulk, keeping it just below a 5.

4 / 5

Actionability

Every command ships copy-paste-ready bash with concrete arguments and a shared $MAPS variable, plus a Verification section with expected output — fully executable and covering the common cases.

5 / 5

Workflow Clarity

Sequencing is clear for the multi-step cases (area → bbox, Telegram pin → nearby) and a Verification checkpoint exists; it is a read-only CLI skill so the destructive/batch cap does not apply, but there are no explicit error-recovery feedback loops, holding it at 4.

4 / 5

Progressive Disclosure

Structure is clean with well-labeled sections and a single one-level-deep bundle reference (scripts/maps_client.py) signaled by path; the inlined 46-category list is the minor gap that keeps it from a 5.

4 / 5

Total

17

/

20

Passed

Description

53%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 tight, third-person description with a clear niche, but it omits explicit 'when to use' guidance and leans on technical nouns over natural trigger phrases, capping completeness and trigger coverage at 3.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants coordinates, nearby places, driving/walking routes, or timezone info for a location' to lift completeness above 3.

Surface natural user phrases — 'nearby', 'directions', 'distance', 'find places near me' — alongside the technical terms (geocode, POIs) for fuller trigger coverage.

Rephrase capabilities as concrete verbs ('Geocode place names, find nearby POIs, compute routes, look up timezones') rather than a terse noun list to broaden action specificity.

DimensionReasoningScore

Specificity

"Geocode, POIs, routes, timezones via OpenStreetMap/OSRM" names the domain and several capability areas, but only "Geocode" is a verb; the rest are terse nouns, so it lands at 'names domain and 1-2 concrete actions, not comprehensive' rather than a fuller action list.

3 / 5

Completeness

The 'what' is clear (geocoding, POIs, routes, timezones) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

It surfaces relevant keywords (geocode, POIs, routes, timezones) but misses the natural phrases users actually say — 'nearby', 'directions', 'distance', 'restaurants near me' — so coverage is partial rather than comprehensive.

3 / 5

Distinctiveness Conflict Risk

The OSM/OSRM-scoped maps/geocoding niche is clearly distinct with minimal conflict risk, though the terseness keeps it just short of the fully-trigger-anchored 5 example.

4 / 5

Total

13

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository
NousResearch/hermes-agent
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.