AD claw402
Professional market data and AI APIs via x402 micropayments — no API key, no signup, no subscription. Pay per call with USDC on Base. 215+ endpoints across 12 provider groups: crypto market data (CoinAnk derivatives analytics, nofxos.ai AI signals, CoinMarketCap quotes/listings/DEX/MCP), US stocks & options (Alpaca, Polygon, Alpha Vantage), China A-shares (Tushare), forex & global time-series (Twelve Data), and AI inference (GPT-4o, Claude, DeepSeek V3/Reasoner, Qwen3-Max/Plus/Turbo/Flash/Coder/VL, embeddings, DALL-E). One wallet, instant access to any paid API — no registration ever required.
As a process D 49/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 11979 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 49/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 40Execution cost. Instruction body is 11979 tokens: crowds the task out of the window
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 50 steps
- 100Consistency. Name and required fields are in place
- 100Running it twice. No mutating operations
- low 10 top-level sections: this looks like several domains in one skill
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
- -215 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 600: enough signal without eating the budget
- +4Structure: 66 headings
- +3Step-by-step instructions: 50 items
- +4Has examples (16 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.