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 - Getting aerial flyover videos of an address - Getting solar/rooftop insights and imagery for a building 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" - "aerial view", "flyover video", "solar potential", "rooftop" Use `npx agentcash@latest fetch` for Google Maps endpoints. Choose partial ($0.02) vs full ($0.05-0.08) based on data needs.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable commands and well-sequenced workflows, and it is reasonably token-efficient. Its main weakness is progressive disclosure: it references non-existent rule files and inlines substantial reference material that belongs in separate bundle files.

Suggestions

Create the referenced rules/getting-started.md and rules/partial-vs-full.md files (or remove the broken links), so signaled references resolve to real bundle files.

Move the Common Place Types and Response Data field listings into a separate reference file linked from the body, keeping SKILL.md as a lean overview.

De-duplicate the Workflows section so it references the per-endpoint examples above instead of repeating identical fetch commands.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with no concept over-explanation, but the Workflows section repeats commands already shown in per-endpoint sections (e.g. the text-search and place-details fetch calls), which is minor redundancy that could be trimmed. Not a 5 because some tokens duplicate earlier examples.	4 / 5
Actionability	Fully executable, copy-paste-ready `npx agentcash@latest fetch` commands with real URLs, complete JSON bodies, and parameters annotated with constraints (e.g. 'radius in meters, max 50000', '1-5').	5 / 5
Workflow Clarity	Workflows use sequenced checklists ('Find Businesses in Area', 'Compare Places with Reviews') and the aerial-view section includes a poll-until-active feedback loop. Not a 5 because read/search operations lack explicit verification checkpoints, though they are non-destructive so no cap applies.	4 / 5
Progressive Disclosure	Structure and section headers are clear and references are signaled as markdown links, but the referenced files (rules/getting-started.md, rules/partial-vs-full.md) do not exist in any bundle directory, and bulk reference material (Common Place Types, Response Data, the full endpoint table) is inlined rather than split out.	3 / 5
	Total	16 / 20 Passed

Description

100%Weight 40%Scale 1-5

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 a strong, third-person statement of capability with an explicit USE FOR list and a dedicated TRIGGERS section full of natural phrases. It clearly answers both what the skill does and when to use it with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across distinct capabilities — 'Finding businesses by name or type', 'Getting aerial flyover videos of an address', 'Getting solar/rooftop insights and imagery for a building' — with comprehensive coverage of search, details, aerial, and solar.	5 / 5
Completeness	Explicitly answers both 'what' (the USE FOR capability list) and 'when' (a dedicated TRIGGERS block with concrete trigger phrases), satisfying the top anchor.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage including synonyms and variations: '"find", "search for", "locate", "nearby"', '"restaurants near", "hotels in"', '"aerial view", "flyover video", "solar potential"'.	5 / 5
Distinctiveness Conflict Risk	Clear niche — 'Search for places, businesses, and locations using Google Maps APIs via x402' — with distinct, domain-specific triggers and minimal overlap with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning
relative_links	Relative link issues: 2 missing	Warning

	Total	14 / 16 Passed

Repository: Merit-Systems/agentcash-skills
Path: skills/local-search/SKILL.md
Commit: 3d657b7

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.