CtrlK
BlogDocsLog inGet started
Tessl Logo

goplaces

Query Google Places API (New) via the goplaces CLI for text search, place details, resolve, and reviews. Use for human-friendly place lookup or JSON output for scripts.

90

3.88x
Quality

89%

Does it follow best practices?

Impact

97%

3.88x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is goplaces in Hung-Reo/hungreo-openclaw

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

An exemplary lean CLI reference: token-efficient, fully executable commands covering common cases, well-organized sections, and useful gotchas without any padding. No external references are needed or missing.

DimensionReasoningScore

Conciseness

Lean and well-organized with no padding or explanation of concepts Claude already knows; every line (config, commands, gotchas) earns its place. Re-reading the 4 anchor, there are no unnecessary explanations to trim, so 5 fits.

5 / 5

Actionability

Fully executable, copy-paste-ready commands with real flags and realistic arguments cover the common cases (search, bias, pagination, resolve, details, json). The only placeholder is <place_id>, which is standard and clearly a parameter.

5 / 5

Workflow Clarity

A simple single-purpose read-only CLI skill whose usage is unambiguous via the Common commands list; the destructive/batch cap does not apply since all operations are read-only API queries. Per the simple-skill exception, the clear command inventory warrants 5.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external references (no references/scripts/assets bundle files exist), and content is cleanly split into well-organized sections (Install, Config, Common commands, Notes). Per the under-50-lines guidance, this earns 5.

5 / 5

Total

20

/

20

Passed

Description

78%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, third-person description that names a clear niche and several concrete operations, with an explicit 'Use for...' trigger clause. Main weakness is the trigger guidance being terse and missing common natural synonyms.

Suggestions

Broaden trigger terms with natural phrases users say, e.g. 'Use when finding nearby places, looking up restaurants/cafes, or resolving place names to IDs'.

Mention the file extension or output context for scripts more explicitly, e.g. 'for piping place JSON into scripts'.

Consider noting autocomplete/nearby support if the CLI offers it, to round out capability coverage.

DimensionReasoningScore

Specificity

Names the domain (Google Places API) and the tool (goplaces CLI) and lists several concrete actions — 'text search, place details, resolve, and reviews' — with only minor coverage gaps (e.g. no autocomplete). Not a 5 because coverage is not exhaustive of the API surface.

4 / 5

Completeness

It answers 'what' (query Places API via goplaces for the four operations) and 'when' ('Use for human-friendly place lookup or JSON output for scripts'), but the 'when' is terse and could be more explicit about specific trigger scenarios. Has both, so above the 3 cap; not a 5 because the trigger guidance lacks concrete phrases.

4 / 5

Trigger Term Quality

Natural terms like 'place lookup', 'place details', 'reviews', and 'JSON output' appear, but common synonyms users might say ('nearby', 'find restaurants/cafes', 'POI', 'maps') are missing. Good coverage but a few natural phrases absent, so not a 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Google Places API via the specific goplaces CLI) with distinct triggers and minimal overlap risk with other skills. Re-reading the 4 anchor, this is more sharply targeted than 'minor overlap risk', so 5 fits.

5 / 5

Total

17

/

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
trpc-group/trpc-agent-go
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.