BD clanker
Deploy ERC20 tokens on Base using Clanker SDK. Create tokens with built-in Uniswap V4 liquidity pools. Supports Base mainnet and Sepolia testnet. Requires PRIVATE_KEY in config.
Deploy ERC20 tokens on Base using Clanker SDK.
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenscripts/deploy.py:56High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"address": "0xE8…3a9",
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/deploy.py:60High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"locker": "0x63…496",
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/deploy.py:61High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"vault": "0x8E…F6C",
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/deploy.py:62High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"airdrop": "0xf6…1E0",
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/deploy.py:63High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"devbuy": "0x13…0be",
quoted
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 49/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
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web, python) that frontmatter does not declare
- 85Steps. 39 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1620 tokens
- 100Running it twice. Mutating operations check current state
- 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 (7 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
- -41 reference files, but SKILL.md never points to them: the model will not open them
- -32 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 177: enough signal without eating the budget
- +4Structure: 26 headings
- +3Step-by-step instructions: 39 items
- +4Has examples (14 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.