add-vault-protocol

Adding a new ERC-4626 vault protocol requires generating a protocol-specific vault class, updating feature enums, implementing detection probes, and creating ABI metadata. This skill automates that end-to-end scaffolding, tests, and documentation.

Scaffolding a vault protocol integration requires the vault address, protocol name, slug, chain, and explorer. The workflow uses these inputs to automatically generate ABI code, risk and fee stubs, and test templates.

Automated vault detection uses classification probes to identify specific ERC-4626 protocol features. The skill implements these probes alongside feature enum updates to correctly route and instantiate new vault classes.

Yes, the vault protocol integration workflow accepts chain and explorer parameters as inputs, allowing you to onboard ERC-4626 vaults across different networks like IPOR, Plutus, or Morpho into your library.

The best way to generate tests and docs for a new vault protocol is using an automated workflow that creates documentation stubs and test templates to validate detection and integration directly from the provided vault address.