Deploy ERC20 tokens with Uniswap V4 pools on Base, Ethereum, Arbitrum
79
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/clanker/SKILL.mdQuality
Discovery
54%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description has strong domain-specific terminology that would help with skill selection in blockchain contexts, and its specificity to Uniswap V4 and named chains creates clear distinctiveness. However, it critically lacks a 'Use when...' clause and only describes a single action (deploy) rather than the full range of capabilities.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'Use when the user wants to launch a token, create a liquidity pool, or deploy to Base/Ethereum/Arbitrum'
Expand the action list to include related capabilities such as 'configure initial liquidity', 'set token parameters', or 'verify contracts'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (ERC20 tokens, Uniswap V4 pools) and a single action (deploy), but doesn't list multiple concrete actions like 'configure liquidity', 'set token parameters', or 'manage pool settings'. | 2 / 3 |
Completeness | Only answers 'what' (deploy tokens with pools on specific chains) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'ERC20', 'tokens', 'Uniswap V4', 'pools', 'Base', 'Ethereum', 'Arbitrum', 'deploy'. These are terms crypto developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining ERC20 deployment with Uniswap V4 pools on named chains. Unlikely to conflict with generic blockchain or token skills due to the specific protocol and chain mentions. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that efficiently documents a token deployment CLI. It excels at conciseness and actionability with clear command syntax and progressive examples. The main gap is the lack of explicit validation checkpoints and error handling guidance for what are inherently risky blockchain operations.
Suggestions
Add a validation workflow section showing how to verify deployment success (e.g., check transaction hash, verify contract on explorer, confirm LP creation)
Include error recovery guidance for common failure scenarios (insufficient gas, RPC errors, failed transactions)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what tokens, IPFS, or Uniswap are. Every section delivers actionable information without padding. | 3 / 3 |
Actionability | Provides complete, copy-paste ready commands with clear syntax. Examples progress from simple to complex, covering all major use cases with specific flags and values. | 3 / 3 |
Workflow Clarity | Commands are well-organized by category, and 'simulate before deploy' is mentioned in best practices. However, there's no explicit validation workflow or error recovery guidance for failed deployments or transaction issues. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear sections (Setup, Commands, Options, Examples, Chains, Config, Fees, Best Practices). For a skill of this scope, the single-file organization is appropriate with logical groupings. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
2a8c94e
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.