SKILLEMALL.ai
GitHub ↗ RU Sign in

CC moltnode-chain-reader

Read 31 blockchains over keyless JSON-RPC with MoltNode (balances, blocks, contract calls) and get Chord swap quotes with an unsigned transaction and simulation.

The skillemall take

Promises to read 31 blockchains via keyless JSON-RPC, fetch balances and call contracts, plus Chord swap quotes with unsigned transactions. One instruction file, 1096 tokens, no scripts. Never ran on models, no sandbox testing.

Quality scores 80, but process only 59 — logic is there, execution stumbles. Two medium-level findings mean bugs that won't break it outright. Safety at 94 is solid. Works with Claude and Hermes. Install if you specifically need MoltNode and Chord integration and don't mind debugging on your own.

sickn33/agentic-awesome-skills Hermes author: sickn33 MIT 1 file body ≈ 1 096 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Read 31 blockchains over keyless JSON-RPC with MoltNode (balances, blocks, contract calls) and get Chord swap quotes with an unsigned transaction and…

As a process C 59/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice

IntegrationAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code Hermes Agent
JSON
Technical rating
C
88/100
safety, quality, tests
Safety 60%
94
Quality 40%
80
Run on models
none yet
Process rating
C
59/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Risky intent medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The purpose itself is risky: wallets, browser password stores, offensive security. Even an honest implementation gives the agent access to things that cost money.

For the author

Explain in the description why the access is needed and how it is limited; add tests that show refusals on dangerous requests.

How to improve

  1. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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 · 2

✓ No critical or high findings

Medium and low: 2
  • medium Risky intent intent-wallet-secrets SKILL.md:74
    Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target
    - Never ask for, store, print or send a private key or seed phrase. Signing happens in the user's own wallet or a signer they control.
  • low Secrets in code secret-high-entropy-token SKILL.md:48
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    {"jsonrpc":"2.0","id":1,"method":"eth_getBalance","params":["0xd8…045","latest"]}
    quoted

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

Against the Agent Skills spec

  • warning description-long-hermes description is 161 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • note frontmatter-key unknown frontmatter key "risk"
  • note frontmatter-key unknown frontmatter key "source"
  • note frontmatter-key unknown frontmatter key "source_repo"
  • note frontmatter-key unknown frontmatter key "source_type"
  • note frontmatter-key unknown frontmatter key "date_added"
  • note frontmatter-key unknown frontmatter key "tools"
  • note frontmatter-key unknown frontmatter key "license_source"

Process rating: all ten parameters 59/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 3 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 23 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1096 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low The response is described with custom markup (6 tags): a typed call is more reliable

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
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Description length 161: enough signal without eating the budget
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 23 items
  • +4Has examples (3 code blocks)
  • +1License stated

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