CtrlK
BlogDocsLog inGet started
Tessl Logo

defi-protocol-templates

Implement DeFi protocols with production-ready templates for staking, AMMs, governance, and lending systems. Use when building decentralized finance applications or smart contract protocols.

88

1.26x
Quality

Does it follow best practices?

Impact

100%

1.26x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable thanks to complete, executable contract templates and is well-organized by section, but it is token-heavy from inlining five full contracts, lacks a sequenced workflow with validation checkpoints for risky financial operations, and its referenced bundle files are missing.

Suggestions

Move the full contract implementations into the referenced assets/*.sol and references/*.md files (which currently do not exist) and keep only the key structure and a short snippet per protocol inline in SKILL.md.

Add a short 'Build & verify' workflow with explicit checkpoints — e.g., compile, run tests, and confirm reentrancy/repayment invariants before deployment — given these are destructive financial contracts.

Create the referenced bundle files or remove the dangling links so the 'Resources' navigation actually resolves.

DimensionReasoningScore

Conciseness

Prose is lean and free of concept-explanation fluff, but ~450 lines of five full Solidity contracts inlined in SKILL.md is heavy token usage; the contracts could be externalized to the referenced asset files with only key snippets retained, so it could be tightened.

2 / 3

Actionability

Five complete, executable Solidity contracts (StakingRewards, SimpleAMM, GovernanceToken/Governor, FlashLoanProvider) are provided copy-paste ready with imports and constructors, matching the level-3 anchor for fully executable code.

3 / 3

Workflow Clarity

'When to Use', 'Best Practices', and 'Common DeFi Patterns' provide structure, but there is no sequenced build/deploy/test workflow and no validation checkpoints for these destructive financial contracts, which caps the score per the feedback-loop guidance.

2 / 3

Progressive Disclosure

Sections and clearly signaled one-level-deep references (references/*.md, assets/*.sol) show the right intent, but the referenced bundle files do not exist and full contracts are inlined rather than split out, so navigation is undermined and content that should be separate is inline.

2 / 3

Total

9

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that concisely states concrete capabilities and provides an explicit 'Use when' trigger covering both domain and intent. It hits every completeness and distinctiveness criterion with no fluff.

DimensionReasoningScore

Specificity

Names concrete actions ('Implement DeFi protocols with production-ready templates') and enumerates multiple specific concrete capabilities (staking, AMMs, governance, lending), matching the level-3 anchor for listing several specific actions.

3 / 3

Completeness

Explicitly answers 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'), matching the level-3 anchor with an explicit 'Use when...' clause.

3 / 3

Trigger Term Quality

Natural terms a developer would say are well covered — 'DeFi protocols', 'staking', 'AMMs', 'governance', 'lending', 'decentralized finance applications', 'smart contract protocols' — with no jargon-only or generic phrasing.

3 / 3

Distinctiveness Conflict Risk

The DeFi/smart-contract niche with distinct triggers (staking, AMMs, governance, lending) is clearly delimited and unlikely to fire for unrelated skills, matching the level-3 anchor.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 9 missing

Warning

Total

15

/

16

Passed

Repository
Dicklesworthstone/pi_agent_rust
Reviewed

Table of Contents

Is this your skill?

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.