SKILLEMALL.ai
GitHub ↗ RU Sign in

CC tx-explain

Decode any Base transaction into a plain-English story - method, token movements, swaps/approvals, counterparties, and suspicious-approval flags. Keyless via Base RPC + Etherscan v2.

aeonfun/aeon Agent Skills author: aeonfun 1 file body ≈ 1 022 tokens Open the sourcegithub.com↗ analyzed 79 min ago

Decode any Base transaction into a plain-English story - method, token movements, swaps/approvals, counterparties, and suspicious-approval flags.

As a process C 50/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

Proceduretype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
86/100
safety, quality, tests
Safety 60%
96
Quality 40%
72
Run on models
none yet
Process rating
C
50/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • 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 Exfiltration net-credential-use SKILL.md:25
    Credential used in a network call (verify the destination is the intended service) (detector / deny-list definition)
    - `ETHERSCAN_API_KEY` — optional, used only to fetch a verified ABI for richer decoding. Appended to the URL as `&apikey=…` via `./secretcurl`'s `{ETHERSCAN_API_KEY}` placeholder (never a bare `$SECRE
    detector
  • low Exfiltration net-credential-use SKILL.md:43
    Credential used in a network call (verify the destination is the intended service) (quoted — discussed, not commanded)
    Take the first 4 bytes of `input` (the selector). Recognize common selectors directly; otherwise fetch the `to` contract's verified ABI via Etherscan v2 (`module=contract&action=getabi`) — keyless wor
    quoted
  • low Exfiltration net-credential-use SKILL.md:48
    Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)
    ./secretcurl -m 10 -s "https://api.etherscan.io/v2/api?chainid=8453&module=…&action=…&address=…" | jq -r '.result'
    vendor-host
  • low Exfiltration net-credential-use SKILL.md:105
    Credential used in a network call (verify the destination is the intended service) (detector / deny-list definition)
    Base RPC is public and keyless; Etherscan v2's optional key is appended as `&apikey=…` via `./secretcurl`'s `{ETHERSCAN_API_KEY}` placeholder (never a bare `$SECRET`, never a header). Both are plain H
    detector

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 50/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 4 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 100Steps. 8 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1022 tokens
  • 100Progress reporting. Reports progress
  • 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 182: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 8 items
  • +4Has examples (4 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.