local-places
Search for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.
70
66%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/local-places/SKILL.mdQuality
Discovery
40%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 identifies a clear niche (Google Places API proxy search) with reasonable specificity about the domain, but lacks explicit trigger guidance ('Use when...') and misses common natural language terms users would employ when looking for places. It would benefit from expanded trigger terms and a clear 'when to use' clause.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to find nearby restaurants, cafes, shops, or other local businesses, or asks about places in a specific area.'
Include more natural trigger terms users would say, such as 'find nearby', 'local businesses', 'points of interest', 'location search', 'what's near me', or 'look up a place'.
List additional concrete actions beyond 'search', such as 'retrieve place details, ratings, reviews, hours, and location coordinates'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (place search) and mentions examples like 'restaurants, cafes', and specifies the mechanism (Google Places API proxy on localhost), but doesn't list multiple concrete actions beyond 'search for places'. | 2 / 3 |
Completeness | Describes what it does (search for places via Google Places API proxy) but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric should cap completeness at 2, and the 'when' is entirely missing, placing it at 1. | 1 / 3 |
Trigger Term Quality | Includes some natural keywords like 'restaurants', 'cafes', 'places', and 'Google Places API', but misses common variations users might say such as 'find nearby', 'local businesses', 'directions', 'reviews', 'location search', or 'points of interest'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of Google Places API, proxy on localhost, and place search creates a clear niche that is unlikely to conflict with other skills. The technical specificity of the API and proxy mechanism makes it distinctly identifiable. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that provides clear, actionable guidance for using a local Places API proxy. The content is concise, with executable curl examples and specific filter constraints. The conversation flow section adds valuable behavioral guidance for Claude. Minor improvement could come from slightly better progressive disclosure if the skill grows, but at its current size the inline approach is acceptable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. No unnecessary explanations of what APIs are or how curl works. Every section earns its place with concrete, relevant information. The tagline is slightly decorative but negligible. | 3 / 3 |
Actionability | Fully executable curl commands with complete request bodies, headers, and realistic example data. Setup instructions are copy-paste ready. Filter constraints are specific with exact value ranges. | 3 / 3 |
Workflow Clarity | Clear two-step flow (resolve → search) is well-sequenced. The Conversation Flow section provides explicit decision logic for handling ambiguous inputs. Step 1 includes a health check before proceeding. For an API proxy skill, the workflow is appropriately structured with clear sequencing. | 3 / 3 |
Progressive Disclosure | Content is well-organized into logical sections (Setup, Quick Start, Conversation Flow, Filters, Response Format), but everything is inline in a single file. The filter constraints and response format sections could potentially be referenced separately, though the total length is reasonable enough that this is a minor issue. | 2 / 3 |
Total | 11 / 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
- deepgram/dglabs-deepclaw
- Commit
ec8d4f8
- 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.