SKILLEMALL.ai

AB use-smart-contract-platform

Deploy, import, interact with, and monitor smart contracts using Circle Smart Contract Platform APIs. Supports bytecode deployment, template contracts (ERC-20/721/1155/Airdrop), ABI-based read/write calls, and webhook event monitoring. Keywords: contract deployment, smart contract, ABI interactions, template contracts, event monitoring, contract webhooks, bytecode, ERC-1155, ERC-20, ERC-721.

ClawHub Agent Skills author: Madelyn v0.1.0 MIT-0 7 files body ≈ 2 452 tokens Open the sourceclawhub.ai analyzed 4 d ago

As a process B 74/100 · Nearly there — weak spots: result and completion, running it twice

IntegrationInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
99
Quality 40%
76
Run on models
none yet
Process rating
B
74/100
Nearly there
Result and completion w 14
0
Running it twice w 4
30
When it triggers w 12
50
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Secrets in code secret-high-entropy-token references/deploy-bytecode.md:48
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    const bytecode = "0xPA…ERE";
    quoted

Files scanned: 7. 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 74/100

  • 0Result and completion. Does not say what the result is
  • 30Running it twice. 39 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Tools and files. No external tools needed
  • 100Steps. 49 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2452 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 394: enough signal without eating the budget
  • +4Structure: 30 headings
  • +3Step-by-step instructions: 49 items
  • +4Has examples (5 code blocks)
  • +4Reference files are cited in the instructions (5 of 5)

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

External checks

ClawHub: clean
This skill is a disclosed smart-contract helper, but users must handle Circle credentials and blockchain transactions carefully.
LLM: benign (high) · VirusTotal: · 29 May 2026