CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

penny-web-search

Real-time web search and structured local-business/Places search using PennyAPI over x402. Use for fresh web results, recent facts, current events, research, verification, fact checking, and for finding businesses, restaurants, stores, services, local leads, addresses, ratings, phone numbers, websites, and coordinates. Penny costs $0.004 per call on Base USDC.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is penny-web-search in ayoubsalem-spec/penny-web-search-skill

SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

A well-structured, actionable skill body with concrete endpoints, parameter specs, and JSON examples, plus appropriate validation and a feedback loop for the paid operation. The main weaknesses are redundancy (price repeated, Routing/Selection-rule overlap) and the lack of a complete runnable x402 retry example.

Suggestions

State the $0.004 price once (e.g., in the Service block) and reference it elsewhere rather than repeating it in the header, Service, and Payment behavior sections.

Merge the 'Routing' and 'Selection rule' sections — both describe when to use Web Search vs Places — into a single decision section to remove duplication.

Add one complete end-to-end example showing the initial 402 challenge and the x402 payment-capability retry, so the payment flow is executable rather than only described.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete endpoints and parameters, but the $0.004 price is restated three times (header, Service block, Payment behavior) and the 'Routing' and 'Selection rule' sections largely duplicate each other on when to use web search vs Places.

3 / 5

Actionability

Provides concrete endpoints, parameter constraints (limit 1–10, num 1–10), and copy-paste-ready POST JSON bodies for both capabilities; minor gap is the absence of a runnable example showing the x402 402-challenge retry flow end-to-end.

4 / 5

Workflow Clarity

Clear paid-call workflow with explicit validation ('Before authorizing payment, verify... the quoted price does not exceed $0.004') and a feedback loop ('If a paid request has an ambiguous failure, inspect its payment/result state before attempting another paid call'); not a 5 because steps are prose imperatives rather than a numbered checklist.

4 / 5

Progressive Disclosure

Well-organized into clear single-level sections (Routing, Service, Penny Web Search, Penny Places, Payment behavior, Selection rule) with no nested references; slightly above the simple-skill line and the redundant sections could be consolidated, so not a 5.

4 / 5

Total

15

/

20

Passed

Description

96%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.

A strong description that clearly states the two capabilities and the trigger conditions, with rich natural-language trigger terms and an explicit 'Use for' clause. Minor overlap risk with generic web-search skills on the research/current-events triggers keeps distinctiveness just below the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities across two distinct services — 'web search' and 'structured local-business/Places search' — plus comprehensive output types ('businesses, restaurants, stores, services, local leads, addresses, ratings, phone numbers, websites, and coordinates').

5 / 5

Completeness

Explicitly answers both 'what' ('Real-time web search and structured local-business/Places search using PennyAPI over x402') and 'when' ('Use for fresh web results, recent facts... and for finding businesses...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-language triggers users actually say — 'fresh web results, recent facts, current events, research, verification, fact checking' and 'finding businesses, restaurants, stores, services, local leads' — with good synonym coverage.

5 / 5

Distinctiveness Conflict Risk

Mostly distinct niche (PennyAPI over x402, paid places search), but the broad web-research triggers ('research, fact checking, current events') create minor overlap risk with generic web-search skills; not a 5 because of that overlap.

4 / 5

Total

19

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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

14

/

16

Passed

Repository

ayoubsalem-spec/penny-web-search-skill

Path

penny-web-search/SKILL.md

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.