agentleFS
tradingstrategy-aitradingstrategy-ai/web3-ethereum-defi/.claude/skills/add-vault-abi-methods/SKILL.md

add-vault-abi-methods

Skill834 starsChanged 3 days agoMITView on GitHub

Expose vault smart contract ABI methods in the vault class

  • Reads credentials

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the task also changes public vault descriptions or notes, read and follow the shared description writing style.

    line 10
  2. Very specific:

    Check folder eth_defi/abi for already downloded ABI files

    line 40
  3. Distinctive:

    Check if the ABI files we are similar.

    line 41
  4. Distinctive:

    Write the test using Anvil mainnet fork based method

    line 65
  5. Very specific:

    Use the latest block number for the named chain, use get-block-number skill if needed for the test case

    line 66
  6. Distinctive:

    Run all vault tests with the command:

    line 74

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Add vault ABI methods

This is a skill description to add smart contract

If the task also changes public vault descriptions or notes, read and follow the shared description writing style. The guide applies to public copy; keep method and ABI details in technical documentation.

Inputs

  1. Vault protocol name
  2. Smart contract address and a blockchain as a blockchain explorer link
  3. What methods to cover

Vault classes

Vault protocol classes can be found in eth_defi/erc_4626/vault_protocol folder. Each vault protocol has its own class. There are 40+ protocols. Some protocol share classes and extend other protocols.

Smart contracts

Each vault class wraps a JSON-RPC calls to an Ethereum smart contract. These smart contracts are described by ABI files in eth_defi/abi folder.

Step 1) Identify the proxy class

Identify the proxy class used for the vault protocol.

  • Identify the proxy class under eth_defi/erc_4626/vault_protocol folder.
  • The protocol might not have a proxy class. In this case report this and abort.

Step 2) Identify ABI file

Identify ABI file we should use for the task.

  • Check folder eth_defi/abi for already downloded ABI files
  • Check if the ABI files we are similar. If they are not, summarise the differences and ask the user how to proceed, then stop.

Step 3) Add a ABI file loading to the vault protocol proxy class

See YearnV3Vault.vault_contract property as an example.

Step 4) Find methods relevant for the task

  • Read ABI file
  • Read protocol documentation
  • Identify relevant smart contract methods

Step 5) Create accessor methods

See IPORVault.get_performance_fee() method as an example.

  • How to call the smart contract
  • How to interpret the result

Step 6) Write test case

See test_ipor_fee test case as an example.

  • Write the test using Anvil mainnet fork based method
  • Use the latest block number for the named chain, use get-block-number skill if needed for the test case
  • Run it
  • Fix potential issues

Step 7) Check regression

See we did not break anything by accident.

Run all vault tests with the command:

source .local-test.env && poetry run pytest -n auto -k vault_protocol

Step 8) Report results to back

Finish with clean-up-for-pr at the outermost task's review handoff.

  • Findings on how the smart contract functions operate and how the results are translated
  • Created files
  • Created accessor methods

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.