AD sato-hub
Query Sato Hub, the scored, daily-rebuilt index of onchain-agent tooling (frameworks, MCP servers, wallets, x402 and stablecoin payment rails, ERC-8004 identity, trading venues, agent skills) plus measured agent-economy numbers and Agent Passports. Use for questions about what to build a crypto agent from, which tools support a chain or standard, whether a crypto-agent project is real, maintained and open source, or for a citable on-chain adoption figure. Read-only, keyless, via the hosted MCP server at https://satohub.ai/api/mcp or a bundled curl script.
Query Sato Hub, the scored, daily-rebuilt index of onchain-agent tooling (frameworks, MCP servers, wallets, x402 and stablecoin payment rails, ERC-8004…
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenreferences/examples.md:206High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)scripts/query.sh preflight '{"token":"0x1b…Bcb","chain":"Base","response_format":"json"}'fixturequoted -
low Secrets in code
secret-high-entropy-tokenreferences/examples.md:228High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)scripts/query.sh route_swap '{"chain":"Solana","token_in":"EPjF…t1v","token_out":"So11…112","amount":"1000000","response_format":fixturequoted
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 43/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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 11 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 100Steps. 39 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2451 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +1No license
- +2Single-language instructions
- +3Description length 561: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 39 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.