AC graph-advocate
Route any blockchain data question to the right Graph Protocol service. Returns live data from 15,500+ subgraphs, Token API (EVM/Solana/TON + Polymarket + Hyperliquid), x402 payment analytics, cross-venue prediction-market spreads (Polymarket ↔ Limitless, Polymarket ↔ Kalshi), and protocol-specific MCP packages. Trigger keywords: subgraph, token, balance, holder, swap, pool, TVL, DeFi, NFT, Aave, Uniswap, Polymarket, Limitless, Kalshi, prediction market spread, arbitrage, Hyperliquid, perps, ENS, governance, x402, onchain data, blockchain.
Route any blockchain data question to the right Graph Protocol service.
As a process C 57/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, running it twice
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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Secrets in code
secret-high-entropy-tokenreferences/token-api.md:15High-entropy token-like string (may be an id, hash or a credential)| USDC | 0xA0…B48 | 0x83…913 |
-
low Secrets in code
secret-high-entropy-tokenreferences/token-api.md:16High-entropy token-like string (may be an id, hash or a credential)| WETH | 0xC0…Cc2 | 0x42…006 |
-
low Secrets in code
secret-high-entropy-tokenreferences/token-api.md:17High-entropy token-like string (may be an id, hash or a credential)| USDT | 0xdA…ec7 | — |
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:226High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)Payments are received by Ampersend smart account `0x0F…C86`.
quoted
Files scanned: 9. 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 57/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 11 mutating operations with no state check
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (web, node) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 4065 tokens
- 100Steps. 35 steps
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 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)
- +1No license
- +2Single-language instructions
- +3Description length 545: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 35 items
- +3Output format is stated explicitly
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (6 of 6)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.