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
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 97%
↑ 3.88xAgent success when using this skill
Validation for skill structure
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 effectively communicates specific capabilities and identifies a clear technical niche with the goplaces CLI and Google Places API. However, it lacks natural user trigger terms (people searching for places rarely say 'Google Places API') and the 'Use for' clause describes output formats rather than when Claude should choose this skill over others.
Suggestions
Add natural trigger terms users would say, such as 'find nearby restaurants', 'business hours', 'location info', 'place reviews', or 'search for places'
Rewrite the 'Use for' clause to specify trigger scenarios: 'Use when the user asks to find places, look up business details, get reviews, or search for locations'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'text search, place details, resolve, and reviews' - these are distinct, actionable capabilities that clearly describe what the skill does. | 3 / 3 |
Completeness | Clearly answers 'what' (query Google Places API for search, details, resolve, reviews) but the 'when' clause ('Use for human-friendly place lookup or JSON output') describes output format rather than explicit trigger scenarios when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes some relevant terms like 'Google Places API', 'place lookup', 'goplaces CLI', but missing common user variations like 'find restaurants', 'nearby places', 'business info', 'location search', or 'maps'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche with 'Google Places API', 'goplaces CLI' - unlikely to conflict with other skills due to the specific tool and API mentioned. | 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, well-crafted skill that exemplifies token efficiency. It provides all necessary information for using the goplaces CLI without any padding or unnecessary explanation. The command examples cover the full range of common use cases with clear, executable syntax.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what Google Places API is or how CLIs work. Every line provides actionable information. | 3 / 3 |
Actionability | Provides complete, copy-paste ready commands for all common use cases. Installation, configuration, and usage examples are all concrete and executable. | 3 / 3 |
Workflow Clarity | This is a simple, single-purpose CLI skill. Each command is self-contained and unambiguous. No multi-step workflows requiring validation checkpoints. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized into logical sections (Install, Config, Common commands, Notes). | 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 | |
- 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.