agentleFS
tradingstrategy-aitradingstrategy-ai/web3-ethereum-defi/.claude/skills/identify-vault-protocol/SKILL.md

Identify vault protocol

Skill830 starsChanged 10 days agoMITView on GitHub

Identify an unknown vault protocol based on its smart contract address

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If there a named deployer address for the smart contract, save it as a clue as well.

    line 16
  2. Distinctive:

    If you cannot get the smart contract source code, abort.

    line 20
  3. Distinctive:

    Do two separate searches on Github public repositories.

    line 26
  4. Distinctive:

    Use Github MCP tool.

    line 34
  5. Distinctive:

    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.

    line 38
  6. Distinctive:

    Search the DefiLlama adapters Github repository for clues using the smart contract address

    line 52
  7. Distinctive:

    If it looks like there are is a good match for some protocol we have not yet listed

    line 56
  8. Distinctive:

    If the search results from the earlier steps do not give good results, then ask for the human input what to attempt next.

    line 63
  9. Distinctive:

    Check the protocol website, documentation site and web search for smart contract audits.

    line 67
  10. Distinctive:

    Write a free-form note with links for the human to research further

    line 85
  11. Distinctive:

    If the smart cotract is developed by someone else, name the developer and link the developer Github repository

    line 102

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Identify vault protocol

This skill attempts to identify a vault protocol based on its smart contract source.

Required inputs

  1. Chain and smart contract address: Given as an explorer link

Step 1. Get the smart contract source code and deployer name

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.

Step 2. Github search for the smart contract keyword and adress

Do two separate searches on Github public repositories.

  • Deployer name
  • One for the smart contract contract address and smart contract address only
  • One for the smart contract name and smart contract name only

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.

Step 3: Web search for the smart contract keyword

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.

Step 4: Twitter search

Same search steos as above but do web search.

Step 5: DefiLLama adapters

Step 6: Check web properties of a protocol

If it looks like there are is a good match for some protocol we have not yet listed

  • Try to find its homepage
  • Try to find its Twitter
  • Try to find its documentation link
  • Try to find a page on the protocol website which allows you to deposit the page. Usually called "app", "vaults", "strategies", "markets", "earn", "staking" or similar and is linkned from homepage.

If the search results from the earlier steps do not give good results, then ask for the human input what to attempt next.

Step 7: Audit reports

Check the protocol website, documentation site and web search for smart contract audits.

For web search, use keywords

  • {protocol name} and audit and Solidity

Also if there is a sepearate developer, do another search with use keywords

  • {developer name} and audit and Solidity

Usually audit reports are available as PDF or report-like web page.

Step 8: Gather fee information

Gather hints about the protocol fee structure in

  • The vault smart contract, or other related smart contracts in the Github repository
  • Protocol homepage
  • Write a free-form note with links for the human to research further

Analyse

Give bullet points output that contains:

  • Chain
  • Address
  • Explorer link
  • Protocol name
  • Web page
  • Github repository
  • Documentation link
  • DefiLLama link (if available)
  • Link to audit documents
  • Fee information
  • Notes
  • If the smart cotract is developed by someone else, name the developer and link the developer Github repository

The output format should be a Markdown block.

  • Display the output in the chat
  • Save the result in docs/protocol-research/{protocol name slugged}-{vault address}.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.