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.

71

Quality

89%

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

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 body for a simple CLI skill: entirely lean, fully executable command examples covering the common cases, and clearly organized sections with no filler. Non-obvious behaviors (pagination via page token, single --type limit, price-level encoding) are captured as terse notes exactly where they belong.

DimensionReasoningScore

Conciseness

The body is lean and efficient with zero padding — every line is either an install command, a config variable, an executable example, or a non-obvious behavioral note ('Type filter sends only the first --type value'). Nothing explains concepts Claude already knows, matching the 5 anchor exactly.

5 / 5

Actionability

All guidance is fully executable, copy-paste-ready CLI commands that cover the common cases: search with flags ('goplaces search "coffee" --open-now --min-rating 4 --limit 5'), location bias, pagination, resolve, details with reviews, and JSON output. This matches the 5 anchor with no gaps.

5 / 5

Workflow Clarity

This is a simple, single-purpose skill (query the Places API), and the single action is unambiguous with a sensible Install → Config → Common commands → Notes progression, so the simple-skill exception applies. There are no destructive or batch operations, so no validation checkpoints are required.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references, and the content is well-organized into clearly labeled sections (Install, Config, Common commands, Notes), which per the rubric guideline earns a 5. Nothing that belongs in a separate file is inlined.

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 strong description that names a specific tool and four concrete capabilities with an explicit 'Use for...' clause. The main weakness is that the trigger guidance describes output modes rather than the natural situations or phrasings that should activate the skill.

Suggestions

Rewrite the 'Use for' clause around concrete trigger situations and user phrasings, e.g., 'Use when the user asks to find nearby places, look up a business or address, or check place details like ratings, hours, or reviews.'

Add natural synonyms and variations to the trigger terms, such as 'nearby', 'local businesses', 'points of interest', or 'find a place', so the skill fires on common user wordings.

Mention location-biased/area search in the capability list (e.g., 'search with location bias and radius') since it is a documented command and closes the coverage gap against the top specificity anchor.

DimensionReasoningScore

Specificity

Names the domain ('Google Places API (New) via the goplaces CLI') and four concrete actions ('text search, place details, resolve, and reviews'), matching the 'several specific actions; minor gaps in coverage' anchor. It falls short of the 5 anchor because common capabilities like nearby or location-biased search are not mentioned, and it is above the 3 anchor since more than 1-2 actions are enumerated.

4 / 5

Completeness

Both 'what' and 'when' are present: the description states the actions and includes an explicit trigger clause ('Use for human-friendly place lookup or JSON output for scripts'), matching the 4 anchor. It does not reach 5 because the 'when' clause describes output modes rather than concrete trigger situations a user would voice (e.g., 'when the user asks to find nearby places or check place reviews').

4 / 5

Trigger Term Quality

Includes good natural keywords users would say — 'place lookup', 'reviews', 'text search', 'JSON' — matching the 'good keyword coverage; a few natural terms missing' anchor. Common user phrasings like 'nearby', 'local businesses', 'find a restaurant', or 'points of interest' are absent, keeping it below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

'Google Places API (New) via the goplaces CLI' plus specific subcommands create a clear niche with distinct triggers and minimal overlap with other skills, matching the 5 anchor exactly. It is not a 4 because no closely related skill would plausibly collide with this uniquely named CLI and API.

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.

Validation — 13 / 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
Bitterbot-AI/bitterbot-desktop
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.