add-curator

Adds vault curator metadata, feed YAML files, and detection patterns to the eth_defi repository.

823|187|Updated Jan 30, 2022
One-click install
npx skills add https://github.com/tradingstrategy-ai/web3-ethereum-defi --skill add-curator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-curator
Source: https://github.com/tradingstrategy-ai/web3-ethereum-defi/tree/main/.claude/skills/add-curator
Command: npx skills add https://github.com/tradingstrategy-ai/web3-ethereum-defi --skill add-curator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adding a new vault curator to the web3-ethereum-defi repository requires coordinated edits across feed YAML files, curator detection logic in Python, logo assets, and strategy tags, which is error-prone when done manually.

Core Features & Use Cases

  • Feed File Creation: Generates curator YAML files under eth_defi/data/feeds/curators with verified short and long descriptions, social links, and evidence links, or alias files pointing to canonical feeders.
  • Detection Wiring: Updates CURATOR_NAME_PATTERNS, PROTOCOL_CURATED_SLUGS, and identify_curator() in eth_defi/vault/curator.py so vaults are attributed to the new curator.
  • Verification Workflow: Runs curator inventory scripts, targeted pytest tests, ruff checks, and schema validation to confirm the integration loads correctly.
  • Use Case: When vault data reveals a new organisation acting as a curator (e.g., discovered via the find-new-curators skill), use this Skill to register it with proper naming policy, sources, logos, and detection rules.

Quick Start

Add the curator 'Example Capital' as a new verified vault curator with its feed file, detection patterns, and logo.

Frequently Asked Questions about add-curator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new vault curator to eth_defi?

Create a YAML file under eth_defi/data/feeds/curators with feeder-id, name, role, descriptions, and evidence links, then update CURATOR_NAME_PATTERNS or protocol-curator constants in eth_defi/vault/curator.py. Verify with the curator inventory script and targeted pytest runs.

How do I handle a curator that already exists as a protocol feeder?

Create an alias YAML with canonical-feeder-id pointing to the existing protocol or stablecoin feeder instead of duplicating feed sources. Add curator-specific identity and description metadata, and reuse the canonical feeder's logo unless the curator has a distinct brand.

What naming rules apply when adding curator records?

Use one clean organisation-level brand name without legal, regional, or affiliate suffixes, and keep a single canonical slug for international entities. Create separate records only for genuinely independent organisations, preserving exact legal names in protocol-specific mapping fields.

When should I add entries to CURATOR_NAME_PATTERNS?

Add patterns only for verified vault-name variants, short names, acronyms, or product names; usually the YAML name field alone is sufficient. Avoid generic single-word patterns unless checked against the vault dataset for false positives.

How do I verify a curator addition works correctly?

Run the print-existing-curators.py inventory script, targeted pytest tests for identify_curator and CURATOR_NAME_PATTERNS, and ruff format/check on edited Python files. Also validate that all curator YAML files load through load_feeder_metadata with descriptions present.