Menu
Identify an unknown vault protocol based on its smart contract address
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Add support for a new ERC-4626 vault protocol. Use when the user wants to integrate a new vault protocol like IPOR, Plutus, Morpho, etc. Requires vault smart contract address, protocol name, and protocol slug as inputs.
Audit curator feeder YAML files for stale Twitter, LinkedIn, RSS and website error markers, decide whether each error is real, then clear false positives, repoint renamed handles/links, or tombstone dead entities — leaving a dated audit comment on every entry touched.
Add a new stablecoin or staked/derivative stablecoin to feed metadata, classification sets, rich metadata YAML and logos. Use when the user wants a stablecoin symbol (e.g. a vault denomination token) to be recognised by is_stablecoin_like() and shown on the site.
Add a new vault curator to feed metadata and curator detection. Use when the user wants to add a verified curator, protocol-managed curator, or curator alias discovered from vault data.
Identify missing vault curators from vault databases and suggest curator feeder YAML entries
Check all stablecoin YAML files for Twitter activity and domain availability, adding a checks section to each file
| name | Identify vault protocol |
| description | Identify an unknown vault protocol based on its smart contract address |
This skill attempts to identify a vault protocol based on its smart contract source.
If there a named deployer address for the smart contract, save it as a clue as well. The "deployer" word in the name is not part of the protocol name.
Get it from the blockchain explorer.
If you cannot get the smart contract source code, abort.
The deployer name is the strongest indicator of the protocol name if available.
Do two separate searches on Github public repositories.
Try to identify the main repository where the contract development happens.
Use Github MCP tool.
If it looks like the protocol is using smart contracts from someone else, then make a note of this "Smart contracts are developed int the project X and protocol Y is using them." In this case we are interested in protocol Y in the further steps.
If there is a separation between who owns the smart contract and who is the deployer, then follow the deployer clue for the next steps.
Same search steos as above but do web search.
IGNORE ALL RESULTS ON TRADING STRATEGY WEBSITE AND ETH_DEFI REPOSITORY, AS WE CANNOT REFLECT BACK TO OURSELVES.
Same search steos as above but do web search.
If it looks like there are is a good match for some protocol we have not yet listed
If the search results from the earlier steps do not give good results, then ask for the human input what to attempt next.
Check the protocol website, documentation site and web search for smart contract audits.
For web search, use keywords
Also if there is a sepearate developer, do another search with use keywords
Usually audit reports are available as PDF or report-like web page.
Gather hints about the protocol fee structure in
Give bullet points output that contains:
The output format should be a Markdown block.
docs/protocol-research/{protocol name slugged}-{vault address}.md.