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, which limits its completeness and discoverability when users phrase requests in everyday language (e.g., 'find restaurants near me').
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to find places, look up business details, read reviews, or search for locations via Google Places.'
Include more natural trigger terms users would say, such as 'find a restaurant', 'nearby places', 'business hours', 'location search', or 'maps'.
| 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 text search, details, resolve, reviews). 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 'Use when the user asks about places, businesses, or locations.' | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'Google Places API', 'place lookup', 'reviews', 'text search', and 'goplaces CLI', but misses common natural user terms 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, actionable, and well-structured with concrete commands covering all major use cases. No improvements needed for a skill of this scope.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line earns its place. No explanation of what Google Places API is, no unnecessary context. Assumes Claude knows how to use CLIs and APIs. Extremely lean. | 3 / 3 |
Actionability | Provides concrete, copy-paste-ready commands for every operation (search, resolve, details, pagination, JSON output). 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 destructive operations. Each command is a standalone action with clear syntax. The single-action nature makes the workflow unambiguous. | 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) that are easy to scan. | 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
- Hung-Reo/hungreo-openclaw
- Commit
a5bf5e0
- 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.