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 falls short on trigger term quality by missing natural user language (e.g., 'find nearby places', 'business reviews', 'location info') and on completeness by lacking an explicit 'Use when...' clause with concrete trigger scenarios.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to find places, look up business details, get reviews, or search for locations via Google Places.'
Include more natural user-facing trigger terms like 'find nearby', 'restaurant', 'business info', 'location search', 'Google Maps places' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'text search, place details, resolve, and reviews' along with the specific tool ('goplaces CLI') and API ('Google Places API (New)'). | 3 / 3 |
Completeness | The 'what' is well covered (query Google Places API via goplaces CLI for text search, details, resolve, reviews). The 'when' is only weakly implied with 'Use for human-friendly place lookup or JSON output for scripts' — this lacks an explicit 'Use when...' clause with clear trigger scenarios. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'Google Places', 'place lookup', 'reviews', 'text search', but misses common user terms like 'nearby restaurants', 'find places', 'location search', 'business info', or 'maps'. Users rarely say 'resolve' or 'goplaces CLI' naturally. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche: specifically targets Google Places API via a named CLI tool ('goplaces'). Unlikely to conflict with other skills due to the specific API and tool references. | 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, concise skill that provides all necessary information for using the goplaces CLI without any wasted tokens. The commands are concrete and copy-paste ready, covering the full range of functionality. The organization is clean and appropriate for the skill's scope.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Every line provides new, non-obvious information (install source, env vars, CLI flags with examples). No unnecessary explanation of what Google Places API is or how CLIs work. | 3 / 3 |
Actionability | Provides fully copy-paste ready commands covering all major use cases (search, resolve, details, pagination, JSON output, geo-biasing). Specific flags and example values are included. | 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 query-only tool. | 3 / 3 |
Progressive Disclosure | For a simple CLI skill under 50 lines, the content is well-organized into logical sections (install, config, commands, notes) with no need for external references. Structure is clean and 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
- qsimeon/openclaw-engaging
- Commit
4467e04
- 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.