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.

3.88x

Quality

83%

Does it follow best practices?

Impact

97%

3.88x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is an excellent, lean skill file that provides exactly what Claude needs to use the goplaces CLI effectively. It assumes Claude's competence, provides concrete executable examples for all major commands, and organizes information into scannable sections. No improvements needed.

Dimension	Reasoning	Score
Conciseness	Every line earns its place. No explanation of what Google Places API is, no unnecessary context. Lean sections with just the essential info Claude needs.	3 / 3
Actionability	Provides concrete, copy-paste-ready commands for every operation (search, resolve, details, pagination, bias). Includes specific flags and example values that are immediately executable.	3 / 3
Workflow Clarity	This is a simple, single-purpose CLI skill with no multi-step or destructive operations. The commands are unambiguous and self-contained, which is appropriate for a lookup/query tool.	3 / 3
Progressive Disclosure	For a simple CLI skill under 50 lines with no need for external references, the content is well-organized into clear sections (Install, Config, Common commands, Notes) that are easy to scan.	3 / 3
	Total	12 / 12 Passed

Description

67%

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 does a good job identifying the specific tool (goplaces CLI) and concrete capabilities (text search, place details, resolve, reviews), making it distinctive. However, it leans toward technical terminology and misses natural user trigger terms like 'find a place', 'restaurant nearby', or 'business reviews'. The 'when to use' guidance is present but could be more explicit with user-facing scenarios.

Suggestions

Add natural user-facing trigger terms like 'find a place', 'nearby restaurants', 'business info', 'location lookup', or 'Google Maps' to improve discoverability.

Strengthen the 'Use when...' clause with explicit trigger scenarios, e.g., 'Use when the user asks to find places, look up business details, read reviews, or needs Google Places data.'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'text search, place details, resolve, and reviews' — these are distinct, named capabilities rather than vague language.	3 / 3
Completeness	The 'what' is well-covered (query Google Places API via goplaces CLI for text search, place details, resolve, reviews). The 'when' is partially addressed with 'Use for human-friendly place lookup or JSON output for scripts' but lacks explicit trigger guidance like 'Use when the user asks about...' with natural trigger scenarios.	2 / 3
Trigger Term Quality	Includes relevant terms like 'Google Places API', 'goplaces CLI', 'text search', 'place details', 'reviews', and 'place lookup', but misses common user-facing variations like 'find a restaurant', 'nearby places', 'location search', 'maps', or 'business info' that users would naturally say.	2 / 3
Distinctiveness Conflict Risk	Very distinct niche — specifically targets the goplaces CLI and Google Places API (New), which is unlikely to conflict with other skills. The tool name and API are clearly identified.	3 / 3
	Total	10 / 12 Passed

Validation

72%

Warnings & errors only

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

Validation — 8 / 11 Passed

Validation for skill structure

Criteria	Description	Result
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	8 / 11 Passed

Repository: deepgram/dglabs-deepclaw
Commit: ec8d4f8

Reviewed: about 1 month ago

Table of Contents

Discovery Implementation Validation

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.