AB fetch-evm-logs
Scaffold and fetch event logs from any EVM smart contract via RPC (eth_getLogs + ABI parse). Works on any EVM-compatible chain/contract (Ethereum, L2s, custom chains) given chainId + address + RPC. Trigger when the user asks to get, pull, fetch, sync, or download contract event logs / 合约日志 / 事件日志 / eth_getLogs — e.g.「帮我获取某个 EVM 合约的日志」 「帮我拉取智能合约的日志」「fetch logs for this contract」「get Transfer events from 0x…」. Also when they give chainId + contractAddress and want on-chain events. Discovers ABI from public sources or accepts user-provided ABI, lists events, asks which to fetch, then runs s1/s2. Pull + parse only — not for stats/analytics (use evm-log-stats).
Scaffold and fetch event logs from any EVM smart contract via RPC (ethgetLogs + ABI parse).
As a process B 71/100 · Nearly there — weak spots: 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 · 0
✓ No critical or high findings
Files scanned: 0. 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 71/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 1 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 19 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1416 tokens
- 100Progress reporting. Reports progress
- 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
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 664: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 19 items
- +3Output format is stated explicitly
- +4Has examples (11 code blocks)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 94.