defi-registry-manager

Update DeFi registry entries across frontend, Rust core, server, and admin tooling.

1|Updated Jan 4, 2026

Search Tags:#automation #tokens #protocols #dex #registry-management #defi-registry

Ready to run

npx skills add https://github.com/BarisSozen/claude --skill defi-registry-manager

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: defi-registry-manager
Source: https://github.com/BarisSozen/claude/tree/main/.claude/skills/defi-registry-manager
Command: npx skills add https://github.com/BarisSozen/claude --skill defi-registry-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The DeFi registry is spread across multiple codebases and often requires coordinated updates when tokens, protocols, chains, networks, or RPC endpoints change. This Skill provides a centralized workflow to streamline expansions and keep data consistent.

Core Features & Use Cases

Identify registry type (token, protocol, chain, or network) and determine the corresponding changes.
Follow a concise four-step checklist to ensure all affected files are updated in frontend, core, server, and admin tooling.
Validate changes across repositories to reduce registry drift and ensure data integrity.

Quick Start

Identify the registry type (token, protocol, chain, or network), follow the appropriate checklist, update all impacted files across codebases, and run the validation to ensure consistency.

Frequently Asked Questions about defi-registry-manager

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

FAQPage Schema

How do I update a DeFi registry across multiple repositories when adding new tokens or chains?▼

To update a DeFi registry across multiple repositories, identify the registry type (token, protocol, chain, or network), follow the specific checklist for that type, update all related files across frontend, Rust core, server, and admin tooling, and run validation checks to ensure data consistency.

What is the best way to synchronize DEX and protocol configurations across frontend and Rust core codebases?▼

The best way to synchronize configurations across codebases is using an automated four-step workflow: identify the registry type, apply the corresponding checklist, update all impacted files including RPC endpoints, and validate changes to eliminate registry drift.

Why does DeFi registry drift occur when adding new network endpoints and RPC configurations?▼

DeFi registry drift occurs because the registry is spread across multiple codebases requiring coordinated updates; without a centralized workflow to enforce file updates and validation across frontend, server, and core, data becomes inconsistent.

Does this registry automation workflow support adding new DEXes and token addresses across admin tooling and server repositories?▼

Yes, this registry automation workflow supports adding new DEXes, token addresses, and network endpoints by enforcing a four-step checklist that updates all affected files across frontend, Rust core, server, and admin tooling repositories.

How do I validate changes to ensure consistency after updating DeFi protocols and chains?▼

To validate changes after updating DeFi protocols and chains, you must run the final validation step in the four-step workflow, which checks all updated files across the multiple repositories to ensure data integrity and eliminate registry drift.

Can I use this skill to add new network endpoints and RPC configurations to a Rust core repository?▼

Yes, you can use this skill to add new network endpoints and RPC configurations because the workflow explicitly handles Rust core, frontend, server, and admin tooling files to ensure synchronized updates across all codebases.