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 a place', 'look up a business', 'restaurant nearby'), 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 using Google Places.'
Include more natural user-facing trigger terms such as 'find a restaurant', 'nearby places', 'business details', 'location search', or '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 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 'when the user asks about places, locations, or businesses'. | 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, concise skill that provides exactly the information Claude needs to use the goplaces CLI effectively. It assumes Claude's competence, provides concrete executable commands, and is well-organized into scannable sections. The notes section adds genuinely useful non-obvious details (price level scale, type filter limitation).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Every line provides new, non-obvious information (install source, env vars, CLI flags with realistic examples). No unnecessary explanation of what Google Places API is or how CLIs work. | 3 / 3 |
Actionability | All commands are copy-paste ready with realistic arguments. Covers the main use cases (search, resolve, details, JSON output, pagination, geo-biasing) with concrete flag examples that Claude can directly adapt. | 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 tool that performs read-only API queries. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with a single-purpose CLI tool, the content is well-organized into logical sections (install, config, commands, notes) without needing 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
- trpc-group/trpc-agent-go
- Commit
09cce3e
- 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.