SKILLEMALL.ai
GitHub ↗ RU Sign in

BC polygon-agent-cli

Complete Polygon agent CLI. Session-based smart contract wallets (Sequence), token ops (send/swap/bridge/deposit via Trails), ERC-8004 on-chain identity + reputation, x402 micropayments. Single CLI entry point, AES-256-GCM encrypted storage.

ClawHub Agent Skills author: JamesLawton v1.0.4 2 files body ≈ 2 701 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

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

IntegrationAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
97
Quality 40%
72
Run on models
none yet
Process rating
C
61/100
Has gaps
Result and completion w 14
0
When it triggers w 12
20
Consistency w 8
40
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 · 3

✓ No critical or high findings

Medium and low: 3
  • low Secrets in code secret-high-entropy-token QUICKSTART.md:86
    High-entropy token-like string (may be an id, hash or a credential)
    --contract 0xAB…7ca
  • low Secrets in code secret-high-entropy-token SKILL.md:134
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    - IdentityRegistry: `0x80…432`
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:135
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    - ReputationRegistry: `0x80…b63`
    quoted

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

  • 0Result and completion. Does not say what the result is
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (polygon-agent-cli) differs from the folder (polygon-agents-cli)
  • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 18 steps
  • 100Failures and branches. 2 branches, has a failure section
  • 100Execution cost. Instruction body is 2701 tokens
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • low 11 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (5 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
  • +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 241: enough signal without eating the budget
  • +4Structure: 18 headings
  • +3Step-by-step instructions: 18 items
  • +4Has examples (10 code blocks)

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

External checks

ClawHub: suspicious
This skill is a coherent Polygon wallet helper, but it gives agents sensitive crypto-wallet authority and relies on a public callback tunnel, downloaded helper binary, and temporary session files that users should review carefully.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026