find-new-curators
Skill834 starsChanged 3 days agoMITView on GitHub
Identify missing vault curators from vault databases and suggest curator feeder YAML entries
- Reads credentials
In this repository23 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-curatorSkill
- add-stablecoinSkill
- add-vault-abi-methodsSkill
- add-vault-noteSkill
- add-vault-protocolSkill
- categorise-vault-strategySkill
- check-stablecoinsSkill
- check-top-list-vaultsSkill
- check-vault-onchainSkill
- clean-up-for-prSkill
- document-curator-incidentSkill
- extract-project-logoSkill
- extract-test-setSkill
- extract-vault-protocol-logoSkill
- fix-sphinx-docsSkill
- get-block-numberSkill
- Identify vault protocolSkill
- maintain-curatorsSkill
- make-releaseSkill
- monthly-vault-reportSkill
- more-vaultsSkill
- post-process-logoSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
31 rules. About 0 are common, 20 are distinctive, and 11 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈20
Distinctive · estimate
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when asked to discover new vault curators, improve curator coverage, or audit whether vaults in generic protocols are …
- Distinctive: line 14
Before starting, clarify the scope if the user did not provide it:
- Distinctive: line 20
If the user asks for "all", inspect the local data sources that are present and report any missing databases instead of failing the whole …
- Distinctive: line 24
Start by printing the existing machine-readable curator list:
- Very specific: line 43
Treat eth_defi/data/feeds/curators/ as the source of truth for code paths.
- Distinctive: line 47
Use the narrowest available source for the protocols in scope.
- Very specific: line 51
Read scripts/erc-4626/README-vault-scripts.md before running pipeline scripts.
- Distinctive: line 77
Use cached data if present.
- Distinctive: line 81
Use the native DuckDB databases when present:
- Very specific: line 94
Prefer DuckDB SQL for exploration.
- Distinctive: line 98
Run the current curator matcher before inventing new names:
- Very specific: line 134
Avoid single-word matches unless the word is distinctive and verified externally.
- Distinctive: line 158
Do not add a candidate if the only evidence is a protocol name, token name, or an unverified social handle.
- Distinctive: line 164
Check whether the protocol is already covered by:
- Distinctive: line 173
all vaults for a protocol are operated by the protocol itself
- Distinctive: line 177
When the same organisation already has a protocol or stablecoin feeder, prefer an alias curator YAML:
- Very specific: line 186
When the protocol itself needs curator classification, update eth_defi/vault/curator.py rather than adding a fake third-party curator.
- Very specific: line 192
Search the repo first: rg -n "{name}|{slug}" eth_defi/data eth_defi/vault docs scripts tests.
- Distinctive: line 193
Check whether a protocol, stablecoin, or curator YAML already represents the organisation.
- Distinctive: line 194
Verify the official website and social links.
- Distinctive: line 195
Check whether RSS exists; if not, leave it out rather than adding a dead URL.
- Distinctive: line 198
If web information is needed, use authoritative project pages first.
- Distinctive: line 202
When reporting only, use a compact table:
- Distinctive: line 207
Use these type values:
- Distinctive: line 215
When making code/data changes:
- Very specific: line 217
add or update eth_defi/data/feeds/curators/{slug}.yaml
- Very specific: line 218
add evidence links under other-links when a protocol forum, documentation page, or vault launch post proves the curator role
- Very specific: line 220
update eth_defi/vault/curator.py only for classification/name-pattern changes
- Distinctive: line 221
add tests when changing curator classification behaviour
- Very specific: line 222
update eth_defi/data/curators.md only if requested or if the new curator belongs in the human reference list
- Very specific: line 238
If tests/vault/test_curator.py does not exist, search for curator tests and run the closest focused test file instead.
≈ “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.
Files
Find new curators
Use this skill when asked to discover new vault curators, improve curator coverage, or audit whether vaults in generic protocols are missing curator metadata.
The goal is to produce a reviewed shortlist of curator candidates, not to blindly add every unknown string found in vault names.
Required inputs
Before starting, clarify the scope if the user did not provide it:
- Protocols: Which vault protocols to inspect, e.g. Morpho, Euler, IPOR Fusion, Lagoon Finance, Hyperliquid, GRVT, Lighter, Hibachi, or all.
- Data source: Local pipeline data in
~/.tradingstrategy/vaults, production R2 metadata, or a specific DuckDB/parquet file. - Output: Candidate report only, or also create new
eth_defi/data/feeds/curators/*.yamlfiles.
If the user asks for "all", inspect the local data sources that are present and report any missing databases instead of failing the whole task.
1. Print existing curators
Start by printing the existing machine-readable curator list:
poetry run python .claude/skills/find-new-curators/scripts/print-existing-curators.pyUseful environment variables:
FEEDS_DIR=eth_defi/data/feeds poetry run python .claude/skills/find-new-curators/scripts/print-existing-curators.py
INCLUDE_ALIASES=false poetry run python .claude/skills/find-new-curators/scripts/print-existing-curators.pyAlso inspect the human reference list:
sed -n '1,140p' eth_defi/data/curators.mdTreat eth_defi/data/feeds/curators/ as the source of truth for code paths. eth_defi/data/curators.md is useful background and should be updated only when the user asks for documentation changes or the new curator is strategically important.
2. Load vault data
Use the narrowest available source for the protocols in scope.
ERC-4626 and generic vault protocols
Read scripts/erc-4626/README-vault-scripts.md before running pipeline scripts.
Usual local files live under:
~/.tradingstrategy/vaults/vault-metadata-db.pickle~/.tradingstrategy/vaults/vault-prices-1h-cleaned.parquet~/.tradingstrategy/vaults/top_vaults_by_chain.json
For Morpho, Euler, IPOR Fusion, Lagoon Finance, and other ERC-4626-like protocols, prefer the metadata database or exported top vault JSON over live chain calls. Pull columns or fields that contain:
- chain id
- vault address
- vault name
- vault token symbol
- protocol slug or protocol name
- TVL or assets under management
- existing curator slug, if present
- any offchain description or manager metadata
Lagoon Finance
Lagoon curator data can come from offchain metadata fetched from app.lagoon.finance/api/vault. See:
eth_defi/erc_4626/vault_protocol/lagoon/offchain_metadata.pytests/lagoon/test_lagoon_metadata.py
Use cached data if present. If fetching live data, be explicit that GitHub Actions/datacentre IPs may receive failures.
Hyperliquid, GRVT, Lighter, and native vaults
Use the native DuckDB databases when present:
~/.tradingstrategy/vaults/hyperliquid-vaults.duckdb~/.tradingstrategy/vaults/grvt-vaults.duckdb~/.tradingstrategy/vaults/lighter-pools.duckdb- other native vault databases added by the current repo, e.g. Hibachi
Relevant references:
scripts/hyperliquid/README-hyperliquid-vaults.mdscripts/grvt/README-grvt-vaults.mdscripts/lighter/README-lighter-vaults.md
Prefer DuckDB SQL for exploration. Use Pandas DataFrame output in notebooks and tabulate.tabulate() in scripts.
3. Identify curator candidates
Run the current curator matcher before inventing new names:
eth_defi.vault.curator.identify_curator()eth_defi.vault.curator.CURATOR_NAME_PATTERNSeth_defi.vault.curator.PROTOCOL_CURATED_SLUGSeth_defi.vault.curator.ALL_PROTOCOL_CURATOR_SLUGS
Then inspect unmatched or low-confidence vaults by protocol and TVL.
Good candidate signals:
- A repeated proper noun appears across multiple vault names or symbols.
- A vault name includes a known asset manager, risk manager, trading firm, or strategy operator.
- A native vault description names a manager or company.
- A protocol UI/API has a curator, manager, allocator, owner, guardian, trader, or strategy operator field.
- The candidate has a real website, X/Twitter profile, LinkedIn company profile, or RSS/blog source.
Weak candidate signals:
- Generic strategy words like "core", "prime", "stable", "yield", "max", "bluechip", "delta neutral", or "basis".
- Asset names, token symbols, chain names, or collateral names.
- Protocol-owned vault labels, unless these should become protocol-managed curators.
- One-off vault names with no external identity and low TVL.
4. Use name heuristics
Extract possible curator names from vault names with conservative heuristics.
Patterns worth checking:
- Prefix before asset or strategy suffix, e.g.
Gauntlet USDC Core->Gauntlet. - Brand inside compound names, e.g.
RE7 Morpho USDC->RE7. - Known company suffixes, e.g.
Capital,Labs,Finance,Strategies,Risk,Digital,Technologies. - Native vault manager fields, e.g. GRVT
manager_name. - Offchain descriptions with phrases like "managed by", "curated by", "operated by", "strategy by", "vault by", "led by".
Avoid single-word matches unless the word is distinctive and verified externally. If the match needs a short alias, add it to CURATOR_NAME_PATTERNS only after checking for false positives across the vault dataset.
5. Suggest generic protocol curators
For generic vault protocols, report candidates as third-party curators when the protocol is infrastructure and vaults are operated by outside parties.
Typical examples:
- Morpho vault curators
- Euler vault curators
- IPOR Fusion curators
- Lagoon Finance curators
- vault managers in native marketplace protocols
For each candidate, include:
- proposed slug
- display name
- evidence vaults with chain id, address, name, and TVL
- matched heuristic
- website/Twitter/LinkedIn/RSS if found
- whether to add a full source-bearing YAML or only a name pattern for an existing curator
- confidence: high, medium, or low
Do not add a candidate if the only evidence is a protocol name, token name, or an unverified social handle.
6. Suggest protocol-managed curators
Some vaults are managed by the protocol itself and should not be treated as external curators.
Check whether the protocol is already covered by:
PROTOCOL_CURATED_SLUGSfor protocols where all vaults are protocol-managedALL_PROTOCOL_CURATOR_SLUGSfor protocols with specific system vaults- address constants such as Hyperliquid system vaults and Lighter system pools
- curator alias YAML files with
canonical-feeder-idpointing to a protocol or stablecoin feeder
Suggest protocol-managed curators when:
- all vaults for a protocol are operated by the protocol itself
- a protocol has official system vaults mixed with third-party vaults
- a stablecoin/protocol issuer also acts as the curator for its staked or yield vaults
When the same organisation already has a protocol or stablecoin feeder, prefer an alias curator YAML:
feeder-id: spark
name: Spark
role: curator
canonical-feeder-id: sparkWhen the protocol itself needs curator classification, update eth_defi/vault/curator.py rather than adding a fake third-party curator.
7. Verify candidates
For every proposed curator:
- Search the repo first:
rg -n "{name}|{slug}" eth_defi/data eth_defi/vault docs scripts tests. - Check whether a protocol, stablecoin, or curator YAML already represents the organisation.
- Verify the official website and social links.
- Check whether RSS exists; if not, leave it out rather than adding a dead URL.
- Confirm the candidate appears in vault data, not just in marketing copy.
If web information is needed, use authoritative project pages first. For X/Twitter and LinkedIn, prefer links from the official website footer or docs.
8. Output format
When reporting only, use a compact table:
| Candidate | Type | Confidence | Evidence | Suggested action |
Use these type values:
third-party curatorprotocol-managed curatoralias curatorname-pattern updatereject
When making code/data changes:
- add or update
eth_defi/data/feeds/curators/{slug}.yaml - add evidence links under
other-linkswhen a protocol forum, documentation page, or vault launch post proves the curator role - update
eth_defi/vault/curator.pyonly for classification/name-pattern changes - add tests when changing curator classification behaviour
- update
eth_defi/data/curators.mdonly if requested or if the new curator belongs in the human reference list
9. Run checks
For data-only YAML changes, at minimum run:
poetry run python .claude/skills/find-new-curators/scripts/print-existing-curators.pyFor curator classification changes, run focused tests:
source .local-test.env && poetry run pytest tests/feed/test_canonical_feeder.py tests/vault/test_curator.pyIf tests/vault/test_curator.py does not exist, search for curator tests and run the closest focused test file instead.
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
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.

