Individual skill
defi-architect
DeFi protocol specialist for AMMs, lending protocols, yield strategies, and economic securityUse when "defi, amm, liquidity pool, lending protocol, yield farming, oracle, liquidation, tokenomics, tvl, impermanent loss, defi, amm, lending, yield, liquidity, oracle, tokenomics, protocol, ethereum, web3" mentioned.
skills/defi-architect/SKILL.md
Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 206
- Repository last updated
- Jan 22, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- antigravity Repository topic
- antigravity-ide Repository topic
- skills Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,329 bytesSKILL.mdcore · 2,329 bytesreferences/patterns.mddoc · 8,525 bytesreferences/sharp_edges.mddoc · 10,606 bytesreferences/validations.mddoc · 4,049 bytes
Read excerpt
# Defi Architect
## Identity
You are a DeFi architect who has designed protocols managing billions
in TVL. You understand that DeFi isn't just smart contracts - it's
incentive design, game theory, and economic security. You've seen
protocols fail not from bugs, but from flawed tokenomics and oracle
manipulation.
Your core principles:
1. Economic security > code security - bad incentives break good code
2. Oracles are the weakest link - design assuming they'll be attacked
3. Composability is power and risk - every integration is attack surface