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.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/defi-protocol-templates/SKILL.md

Quality

Content

46%Weight 40%Scale 1-5

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

The body delivers genuinely actionable, executable Solidity templates for four DeFi primitives, but it is let down by inlining full contracts that its own Resources section says should be external files (which are absent), generic boilerplate instructions, and no real validation workflow for deploying financially destructive contracts.

Suggestions

Move the four full Solidity contracts into the referenced assets/*.sol files (which currently do not exist) and keep SKILL.md as a concise overview with short excerpts and clear links.

Replace the generic "Instructions" bullets with a concrete deployment workflow: write tests, run fuzzing, validate with a checker, then audit — with explicit verify/fix/retry checkpoints.

Provide an inline lending template or explicitly note it lives in assets/lending-protocol.sol so every domain named in the description has executable coverage.

Dimension	Reasoning	Score
Conciseness	The body inlines four complete Solidity contracts (~400 lines) that the Resources section itself says should live in assets/*.sol, plus generic filler like "Clarify goals, constraints, and required inputs" and "Apply relevant best practices and validate outcomes", making it noticeably verbose with padded sections.	2 / 5
Actionability	The staking, AMM, governance, and flash-loan contracts are full, copy-paste-ready executable Solidity, but the lending domain (named in the description and 'Use this skill when') has no inline implementation, leaving a minor coverage gap.	4 / 5
Workflow Clarity	"Instructions" gives only a rough generic 3-step sequence (clarify goals, apply best practices, validate outcomes) with no concrete validation checkpoints for deploying high-risk financial contracts, and the cap for missing validation in destructive/batch operations holds it at 3.	3 / 5
Progressive Disclosure	The Resources section clearly signals one-level-deep references, but the referenced references/ and assets/ files do not exist in the bundle and the bulk contract content that belongs in those files is inlined directly in SKILL.md, matching the 'content that clearly belongs in separate files is inlined' anchor.	2 / 5
	Total	11 / 20 Passed

Description

83%Weight 40%Scale 1-5

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, well-structured description that concretely names its DeFi sub-domains and pairs a clear 'what' with an explicit 'Use when' trigger. It could be sharpened by varying the action verbs and adding a few common DeFi synonyms (yield farming, flash loans) to broaden trigger coverage.

Suggestions

Vary the action language beyond 'implement ... with templates' (e.g., 'deploy', 'customize', 'audit') to surface more distinct capabilities.

Add high-traffic DeFi terms like 'yield farming', 'liquidity pools', and 'flash loans' to the trigger clause so the description matches the body's full scope.

Tighten 'smart contract protocols' to a more DeFi-specific trigger to reduce overlap with generic smart-contract skills.

Dimension	Reasoning	Score
Specificity	"Implement DeFi protocols with production-ready templates for staking, AMMs, governance, and lending systems" names multiple specific DeFi sub-domains with a concrete action, but relies on a single verb (implement) across domains rather than listing multiple distinct actions, so it sits just below the comprehensive 5 anchor.	4 / 5
Completeness	It explicitly states 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 concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	"building decentralized finance applications or smart contract protocols" plus staking/AMMs/governance/lending give good natural keyword coverage, but common variants like yield farming, liquidity pools, and flash loans that the body covers are missing from the description.	4 / 5
Distinctiveness Conflict Risk	The DeFi template niche is mostly distinct with clear triggers, but the broad phrase "smart contract protocols" creates minor overlap risk with general smart-contract development skills.	4 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 9 missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/defi-protocol-templates/SKILL.md
Commit: 3eff4af

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.