categorise-vault-strategy

Assign evidence-based strategy tags to DeFi vaults and maintain address-to-tag mappings.

823|187|Updated Jan 30, 2022
One-click install
npx skills add https://github.com/tradingstrategy-ai/web3-ethereum-defi --skill categorise-vault-strategy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: categorise-vault-strategy
Source: https://github.com/tradingstrategy-ai/web3-ethereum-defi/tree/main/.claude/skills/categorise-vault-strategy
Command: npx skills add https://github.com/tradingstrategy-ai/web3-ethereum-defi --skill categorise-vault-strategy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Classifying DeFi vault investment strategies consistently is hard: tags must be grounded in documented evidence, stored in the right protocol adapter mapping, and wired into the correct data path without breaking existing resolvers. This Skill standardizes that workflow for ERC-4626 VaultBase adapters and native perpetual DEX vault exports.

Core Features & Use Cases

  • Evidence-based tagging: Selects tags from eth_defi.vault.strategy_tag.StrategyTag only when official documentation supports them, leaving unverifiable vaults unmapped.
  • Adapter-aware mapping: Creates or updates tags.py files for ERC-4626 protocol adapters and native perpetual DEX integrations (ApeX, Hyperliquid, GRVT, Hibachi, Lighter) with documented comment blocks.
  • Wiring and testing: Connects mappings to get_strategy_tags() resolvers, adds focused no-RPC tests, and schedules the production metadata migration.
  • Use Case: When adding a new RWA lending vault to a Morpho-style adapter, use this Skill to research the strategy, add the lowercase address entry with rwa and rwa_lending tags, wire the resolver, and post migration instructions on the pull request.

Quick Start

Use the categorise-vault-strategy skill to classify the vault at address 0x... on its chain and update the protocol's tags.py mapping.

Frequently Asked Questions about categorise-vault-strategy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I classify a DeFi vault's investment strategy?

Resolve the vault's chain and lowercase contract address, read its adapter description and official protocol documentation, then assign every supported StrategyTag the documented strategy warrants. Record the entry in the protocol's tags.py with a comment citing the decision sources.

How do I add strategy tags to an ERC-4626 vault adapter?

Create or update eth_defi/erc_4626/vault_protocol/{slug}/tags.py with a STRATEGY_TAGS dict keyed by lowercase address strings, then wire the vault class's get_strategy_tags method to call lookup_strategy_tags with that mapping.

Does this workflow handle Hyperliquid or GRVT vaults?

Yes, native perpetual DEX integrations like ApeX, Hyperliquid, GRVT, Hibachi, and Lighter use eth_defi/{slug}/tags.py with string keys, since their vault IDs or synthetic addresses are not EVM addresses. Their resolver normally adds the perpetual_futures tag by default.

What happens when a vault's strategy is not documented?

Leave the address out of the mapping so get_strategy_tags returns None, meaning the information is missing. Use the unknown tag only when research explicitly establishes the strategy is unknown, never infer tags from token symbols or marketing.

Should I update the local vault metadata pickle after tagging?

No, do not update the local vault-metadata-db.pickle during development. Post the production migration instructions as a pull request comment so the operator runs the dry run and migration only after the code is merged and deployed.