galleon-defi-data
DeFi data
Make market and protocol evidence usable without confusing an aggregator observation with an executable quote, a wallet balance, or an authorization to trade.
Start with the requested task
Read task examples and user configuration for a completed example and recovery path. Apply only the workflow stages needed by the current request. Reuse supplied preferences and compatible tools; ask only for missing terms that affect this task. Public explanation or comparison does not require transaction fields. Keep any existing authorization within its exact scope.
Connect the right source
For a first public price check, start with the diagnostic workflow and its known Bitcoin connectivity example. For analysis, start with the user's existing official provider connection and resolve the requested identity before querying. Do not configure additional providers just because they appear below.
Use provider setup when enabling access or choosing between CoinGecko market/onchain data, DefiLlama protocol/yield data, and public API fallbacks. For crypto projects, narratives and event research, use the AIXBT workflow. Reuse official MCP or SDK clients already present. Discover current tool schemas: advertised tool counts and names can lag the running server. Record unavailable capabilities separately from working ones.
CoinGecko has a public keyless MCP path. DefiLlama's official MCP requires an API subscription and OAuth; its public REST endpoints are a distinct free surface. Credentials and plan enrollment are user-owned. Installing this skill grants neither spending authority nor permission to change an existing client's authentication.
Our name is galleon-defi-data; DefiLlama also publishes a different skill named defi-data. Keep their identities distinct if the user wants both.