local-search
Search for places, businesses, and locations using Google Maps APIs via x402. USE FOR: - Finding businesses by name or type - Searching nearby places - Getting detailed place information (address, hours, reviews) - Finding restaurants, stores, services in an area - Getting business ratings and reviews TRIGGERS: - "find", "search for", "locate", "nearby" - "restaurants near", "hotels in", "stores around" - "business details", "opening hours", "reviews for" - "places in", "what's near", "directions to" Use `npx agentcash fetch` for Google Maps endpoints. Choose partial ($0.02) vs full ($0.05-0.08) based on data needs.
Install with Tessl CLI
npx tessl i github:Merit-Systems/agentcash-skills --skill local-search95
Does it follow best practices?
Validation for skill structure
Discovery
100%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 well-structured skill description that excels across all dimensions. It provides specific capabilities, comprehensive trigger terms that match natural user language, explicit 'USE FOR' and 'TRIGGERS' sections that clearly answer what and when, and a distinct focus on Google Maps place search that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Finding businesses by name or type', 'Searching nearby places', 'Getting detailed place information (address, hours, reviews)', 'Finding restaurants, stores, services', 'Getting business ratings and reviews'. | 3 / 3 |
Completeness | Clearly answers both what (search for places, businesses, locations via Google Maps APIs) and when (explicit TRIGGERS section with natural language patterns like 'find', 'nearby', 'restaurants near'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural user terms including 'find', 'search for', 'nearby', 'restaurants near', 'hotels in', 'opening hours', 'reviews for', 'what's near', 'directions to' - these are phrases users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on Google Maps place/business search with distinct triggers around location-based queries. The mention of 'x402' and 'agentcash' further distinguishes it from generic search skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%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-structured, actionable skill with excellent conciseness and clear progressive disclosure. The quick reference table and executable examples make it immediately useful. The main weakness is the lack of error handling guidance and validation checkpoints in the workflows, which would help Claude recover from failed API calls or empty results.
Suggestions
Add error handling guidance to workflows (e.g., what to do when search returns no results, how to handle invalid placeIds)
Include a validation step in workflows to verify API responses before proceeding (e.g., check that results array is non-empty)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting only necessary information without explaining concepts Claude already knows. Tables, code examples, and lists are used effectively to maximize information density. | 3 / 3 |
Actionability | All examples are fully executable bash commands with complete JSON payloads. Parameters are clearly documented, and the code is copy-paste ready with realistic values. | 3 / 3 |
Workflow Clarity | Workflows are presented with checklists and clear sequences, but lack explicit validation/error handling steps. No guidance on what to do if a search returns no results or if an API call fails. | 2 / 3 |
Progressive Disclosure | Content is well-organized with a quick reference table upfront, clear section headers, and appropriate references to external files (getting-started.md, partial-vs-full.md) that are one level deep and clearly signaled. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.