Implement DeFi protocols with production-ready templates for staking, AMMs, governance, and lending systems. Use when building decentralized finance applications or smart contract protocols.
Install with Tessl CLI
npx tessl i github:wshobson/agents --skill defi-protocol-templatesOverall
score
71%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 100%
↑ 1.25xAgent success when using this skill
Validation for skill structure
Discovery
85%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description that clearly defines its DeFi-specific domain with concrete protocol types and includes explicit 'Use when' guidance. The main weakness is moderate trigger term coverage - while it captures core DeFi terminology, it misses some common user phrases and related concepts that could improve skill selection accuracy.
Suggestions
Expand trigger terms to include common variations like 'yield farming', 'liquidity pools', 'token swaps', 'DAO', 'Solidity', or 'Web3' that users might naturally mention
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'staking, AMMs, governance, and lending systems' along with 'production-ready templates' - these are specific DeFi protocol types rather than vague abstractions. | 3 / 3 |
Completeness | Clearly answers both what ('Implement DeFi protocols with production-ready templates for staking, AMMs, governance, and lending systems') and when ('Use when building decentralized finance applications or smart contract protocols') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes good domain terms like 'DeFi', 'staking', 'AMMs', 'governance', 'lending', and 'smart contract protocols', but missing common variations users might say like 'yield farming', 'liquidity pools', 'token swaps', 'DAO', or 'Solidity'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche in DeFi/blockchain space with distinct triggers like 'staking', 'AMMs', 'governance', 'lending systems', and 'smart contract protocols' - unlikely to conflict with general coding or document skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
52%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels at providing production-ready, executable DeFi contract templates with complete implementations. However, it critically lacks deployment and testing workflows with validation checkpoints, which is especially important for financial smart contracts where errors can be catastrophic. The content is somewhat verbose with sections Claude doesn't need, and the large code blocks would benefit from being split into referenced files.
Suggestions
Add a deployment workflow section with explicit steps: compile -> run tests -> deploy to testnet -> verify contract -> security audit -> deploy to mainnet, with validation checkpoints at each stage
Move the full contract implementations to referenced files (e.g., assets/staking-contract.sol) and keep only key snippets or interface summaries in the main SKILL.md
Remove the 'When to Use This Skill' and generic 'Best Practices' sections - Claude can infer use cases and already knows standard security practices
Add testing examples showing how to validate each contract type before deployment (e.g., Foundry/Hardhat test snippets)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill provides substantial code templates which are valuable, but includes some unnecessary sections like 'When to Use This Skill' that Claude can infer, and the 'Best Practices' section contains generic advice Claude already knows. The code itself is appropriately dense. | 2 / 3 |
Actionability | Excellent actionability with complete, executable Solidity contracts for staking, AMM, governance, and flash loans. All code is copy-paste ready with proper imports, events, and full implementations rather than pseudocode. | 3 / 3 |
Workflow Clarity | No deployment workflow, testing sequence, or validation steps are provided. For DeFi protocols involving financial operations, missing critical steps like 'compile -> test -> deploy to testnet -> verify -> audit -> mainnet' and no validation checkpoints for these high-risk contracts is a significant gap. | 1 / 3 |
Progressive Disclosure | References to external files are listed in the Resources section, but the main content is a monolithic wall of code (~400 lines). The code templates could be split into separate files with the SKILL.md providing overview and navigation. Structure exists but organization could be improved. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
88%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 Passed | |
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.