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

88%

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

SKILL.md
Quality
Evals
Security

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.

A well-structured, actionable body that assumes Claude's competence and organizes a paid-API skill cleanly. The main gaps are minor redundancy in restating endpoints/price and the lack of a full end-to-end HTTP payment example and an explicit sequenced workflow.

Suggestions

Add one complete end-to-end HTTP/curl example showing the 402 challenge response and the retried paid request, so the payment handshake is copy-paste ready.

Dedupe the endpoint URLs and the $0.004 price — state each once in the Service section and reference it from Routing and the per-endpoint sections.

Restate the payment behavior as a short numbered sequence (1. expect 402 → 2. verify PennyAPI + price ≤ $0.004 → 3. sign via x402 capability and retry → 4. on ambiguous failure, inspect state before retrying) to make the workflow explicit.

DimensionReasoningScore

Conciseness

Lean overall and assumes Claude's knowledge of x402/USDC/Base, but endpoints and the $0.004 price are restated across the Routing, Service, and Payment behavior sections, leaving minor redundancy that could be trimmed.

4 / 5

Actionability

Concrete endpoints, typed input parameters (limit 1–10, num default 5), and copy-paste JSON bodies are provided, but no complete end-to-end HTTP example showing the 402 challenge → payment → retry handshake, leaving a minor gap.

4 / 5

Workflow Clarity

The payment flow includes explicit validation checkpoints (verify PennyAPI, price ≤ $0.004) and a feedback loop (ambiguous failure → inspect state before retrying), but the steps are presented as prose rather than a crisp sequenced checklist.

4 / 5

Progressive Disclosure

A single-purpose, self-contained skill with cleanly sectioned headers (Routing, Service, Web Search, Places, Payment behavior, Selection rule), easy navigation, and no nested or buried references; the simple-skill exception applies.

5 / 5

Total

17

/

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, specific description that clearly states both what the skill does and when to use it, with rich natural trigger terms. The only weakness is that several research/verification triggers are broad enough to compete with general web-search skills.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'Real-time web search', 'structured local-business/Places search', and an enumerated set of outputs (ratings, addresses, phone numbers, websites, coordinates) — giving comprehensive coverage in third-person form.

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... and for finding businesses...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-language terms a user would actually say: 'fresh web results, recent facts, current events, research, verification, fact checking' plus 'businesses, restaurants, stores, services, local leads', with synonyms across both capabilities.

5 / 5

Distinctiveness Conflict Risk

The PennyAPI/x402/Base-USDC niche is distinct, but broad triggers like 'current events, research, fact checking, verification' overlap with generic web-search and research skills, leaving minor conflict risk.

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

skills/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.