AC 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. TRIGGERS: search the web, current information, latest, recent, up-to-date, verify online, fact check, research, web results, breaking developments, find businesses, local businesses, restaurants near, coffee shops, stores near, services near, nearby businesses, local leads, business phone, business website, business ratings, business address, places, coordinates.
Real-time web search and structured local-business/Places search using PennyAPI over x402.
As a process C 55/100 · Has gaps — weak spots: result and completion, inputs and preconditions, progress reporting
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 55/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 26 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 769 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +2Single-language instructions
- +3Description length 728: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 26 items
- +4Has examples (7 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.