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.
92
92%
Does it follow best practices?
Impact
97%
3.88xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
85%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description that clearly identifies the tool, API, and specific capabilities (text search, place details, resolve, reviews). It includes a 'Use for' clause that provides trigger guidance. The main weakness is that trigger terms lean technical rather than matching natural user language—users are more likely to say 'find nearby restaurants' or 'look up a business' than 'text search' or 'resolve'.
Suggestions
Add natural user-facing trigger terms like 'find places', 'nearby businesses', 'restaurant lookup', 'location info', or 'business reviews' to improve discoverability from typical user queries.
| 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 | Answers both what ('Query Google Places API via goplaces CLI for text search, place details, resolve, and reviews') and when ('Use for human-friendly place lookup or JSON output for scripts'). The 'Use for' clause serves as an explicit trigger guidance. | 3 / 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 | 11 / 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 file that maximizes information density while remaining clear and actionable. It covers installation, configuration, all major commands with realistic examples, and relevant edge-case notes—all in minimal space. No improvements needed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line earns its place. No unnecessary explanations of what Google Places API is or how CLIs work. Assumes Claude's competence throughout. | 3 / 3 |
Actionability | Provides fully executable, copy-paste-ready commands covering all major use cases (search, resolve, details, pagination, JSON output, geo-biasing). Specific flags and values are shown. | 3 / 3 |
Workflow Clarity | This is a simple, single-purpose CLI skill with no multi-step or destructive operations. Each command is unambiguous and self-contained, which is appropriate for a lookup 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 |
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 | |
ec8d4f8
Table of Contents
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.