add-vault-note
Skill834 starsChanged 3 days agoMITView on GitHub
Add a note to specific vault
In this repository23 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-curatorSkill
- add-stablecoinSkill
- add-vault-abi-methodsSkill
- 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
- find-new-curatorsSkill
- fix-sphinx-docsSkill
- get-block-numberSkill
- Identify vault protocolSkill
- maintain-curatorsSkill
- make-releaseSkill
- monthly-vault-reportSkill
- more-vaultsSkill
- post-process-logoSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 7 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Read and follow the shared description writing style before writing or editing public vault notes or handwritten descriptions.
- Distinctive: line 15
Before starting, gather the following information from the user:
- Distinctive: line 26
Use search to find the record
- Distinctive: line 28
Don't try to open the JSON file, as it is too large
- Very specific: line 36
Add the vault address VAULT_FLAGS_AND_NOTES
- Distinctive: line 38
If the address already exist ask for user input
- Distinctive: line 39
Make sure the address is lowercased
- Very specific: line 42
If the user explicitly did not tell you to use any flag, set flag to None
- Very specific: line 43
If the user is unsure whether the vault should be flagged, or AI-assisted research does not reach the same conclusion every time, use …
- Distinctive: line 70
Run ruff to make sure Python code is formatted.
≈ “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
Add vault note
This skill adds a human-readable note to a specific vault in the database.
Read and follow the shared description writing style before writing or editing public vault notes or handwritten descriptions.
Required inputs
Before starting, gather the following information from the user:
- Vault smart contract address - The address of an example vault contract on a blockchain
- Message: A human readable message
- Flags (optional): Flags from
VaultFlagenum - if not given set toNone
1. Resolve vault name
Can be resolved from https://top-defi-vaults.tradingstrategy.ai/top_vaults_by_chain.json JSON file
- It's a list of JSON object records
- Use search to find the record
- Extract its name
- Don't try to open the JSON file, as it is too large
Alternatively use check-vault-onchain.py.
2. Edit the flag.py
The vault notes are stored in ``eth_defi/vault/flag.py`.
Add the vault address VAULT_FLAGS_AND_NOTES
- If the address already exist ask for user input
- Make sure the address is lowercased
- For the message create a Python constant like other messages have in
flag.py - Set the message and flag in the dictionary
- If the user explicitly did not tell you to use any flag, set flag to
None - If the user is unsure whether the vault should be flagged, or AI-assisted
research does not reach the same conclusion every time, use
VaultFlag.review_needed. It does not blacklist the vault; its note tells readers the vault is under review. For a review a person asks for, use theREVIEW_NEEDED_MANUALmessage constant. The check-specific constantsREVIEW_NEEDED_OFF_MARKET_COLLATERAL,REVIEW_NEEDED_EXIT_LIQUIDITYandREVIEW_NEEDED_DATA_QUALITYsay the automated investability checks did not agree, so use them only for findings of the vault report investability check. Record in the comment block what is uncertain and what a reviewer should check to decide - Add an extensive line comment above the entry, as the Instructions for adding entries in the
flag.pymodule docstring require: the vault name, protocol and chain, the date, what is wrong and why this flag, and canonical source URLs (the tradingstrategy.ai vault page, the block explorer page, and any announcement or incident report). A bare address or a name-only comment is not enough
Persisted metadata refresh
New or changed flags require a numbered refresh of existing rows: export reads
the stored _flags and does not recompute them from the manual table. Only
note-only changes can rely on the current manual notes being resolved during
export; document when that makes a migration unnecessary. Cached descriptions
and other persisted fields also need a numbered repair when they must be
refreshed. Follow the migration documentation
and use the reviewed chain/address and fields in a new script.
Standalone fix-*.py and migrate-*.py repairs are legacy format and must
not be created or run for this task. Use the unified runner and include its
production run reminder; do not mutate the local database during authoring.
3. Format code
Run ruff to make sure Python code is formatted.
4. Open PR
Finish with clean-up-for-pr at the outermost task's review handoff.
- Open a pull request.
- This is not a feature pull request - no need to add changelog entry
- Prefix the pull request "notes" instead of "feat"
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.

