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.
86
83%
Does it follow best practices?
Impact
97%
3.88xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
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 is strong on specificity and distinctiveness, clearly naming the tool, API, and supported operations. However, it lacks an explicit 'Use when...' clause with natural user trigger terms (e.g., 'find nearby restaurants', 'look up a business'), which limits its completeness and trigger term quality for skill selection scenarios.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to find places, look up businesses, get reviews, or search for locations via Google Places.'
Include more natural user-facing trigger terms like 'find a restaurant', 'nearby places', 'business lookup', 'location search', or 'Google Maps' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'text search, place details, resolve, and reviews' via a named CLI tool ('goplaces'). Also specifies output modes: 'human-friendly place lookup or JSON output for scripts.' | 3 / 3 |
Completeness | The 'what' is well-covered (query Google Places API via goplaces CLI for specific operations). However, there is no explicit 'Use when...' clause — 'Use for human-friendly place lookup or JSON output' partially implies when, but doesn't clearly state trigger conditions like 'when the user asks about places, businesses, or locations'. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'Google Places API', 'goplaces CLI', 'text search', 'place details', 'reviews', and 'JSON output', but misses common natural user phrases like 'find a restaurant', 'nearby places', 'location search', 'business info', or 'maps'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive: references a specific CLI tool ('goplaces'), a specific API ('Google Places API (New)'), and specific operations (text search, place details, resolve, reviews). Unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
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 that provides exactly what Claude needs to use the goplaces CLI effectively. It's concise, fully actionable with real command examples, and well-structured for a single-purpose tool. No improvements needed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line earns its place. No explanation of what Google Places API is, no unnecessary context. Assumes Claude knows how CLIs work and jumps straight to install, config, and commands. | 3 / 3 |
Actionability | All commands are concrete, copy-paste ready with realistic flags and arguments. Covers search, resolve, details, pagination, and JSON output with specific examples. | 3 / 3 |
Workflow Clarity | This is a simple, single-purpose CLI skill with no multi-step destructive operations. The commands are unambiguous and the workflow (install → config → use) is clear from the structure. No validation gaps for this type of 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 logical sections (Install, Config, Common commands, Notes). No bundle files are needed. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
72%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
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.