AB erc20-tokenomics-builder
ERC20 token launch readiness toolkit. Use when designing or auditing tokenomics for a new token project — includes VestingWallet setup (OpenZeppelin), allocation table generation, cliff/vesting schedule modeling, investor documentation, Uniswap v2/v3 liquidity math, and token distribution analysis. Triggers on: token launch, tokenomics design, vesting schedule, token allocation, SAFT/token sale docs, liquidity bootstrapping, Uniswap pool setup, token supply modeling. NOT for: already-deployed token audits (use solidity-audit-precheck), DeFi position tracking (use defi-position-tracker), or general smart contract upgrades.
As a process B 71/100 · Nearly there — weak spots: inputs and preconditions, failures and branches, running it twice
How to improve
- 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 · 0
✓ No critical or high findings
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: ERC20 token launch readiness toolkit. Use when designing or auditi… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 71/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 3 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 29 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1471 tokens
- 100Progress reporting. Reports progress
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
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 629: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 29 items
- +3Output format is stated explicitly
- +4Has examples (6 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.