agentsclimarketplace

Hive defi research

Skill hive-intel/hive-skills/skills/hive-defi-research

Installable Hive Intelligence agent skills for crypto MCP setup, discovery, and research workflows.

Install
npx -y skills add hive-intel/hive-skills --skill hive-defi-research

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use this skill when the user asks about DeFi protocol metrics — TVL, fees, revenue, yields, APY, stablecoin supply, bridge volume, or chain-level DeFi totals — or wants protocols compared ("Aave vs Compound", "top protocols by TVL", "best stablecoin yields"). Use it whenever the answer needs current protocol-level numbers. For token prices and venue data use hive-market-research; for a specific pool's depth use hive-dex-pool-analysis.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.4 KB, as published. Nobody here has run it

hive-defi-research — DeFi Protocol Analysis

Answer protocol, TVL, fee, revenue, yield, stablecoin, bridge, and chain-level DeFi questions with like-for-like, timestamped metrics.

Task toolset and identifiers

Toolset: defi_protocol_analysis (confirm against hive://toolsets if routing fails).

  • Required: protocol name/slug or chain.
  • Optional: time window, metric type, yield pool, stablecoin, bridge.

Ask for a protocol slug, or choose a provider-supported slug only when the user clearly named the protocol.

Procedure

  1. Resolve the protocol slug or chain name.
  2. Call search_tools for protocol, TVL, fee/revenue, yield, stablecoin, bridge, or chain-metric capabilities.
  3. Call get_api_endpoint_schema for each endpoint before calling it.
  4. Pull only the metrics the question needs.
  5. Compare protocols only with like-for-like metrics and timestamps, and state when a metric is unavailable or stale.

Bounded calls

  • Limit protocol lists and yield pools.
  • Avoid comparing TVL snapshots from different dates without a caveat.
  • Mark missing fee/yield/stablecoin metrics instead of omitting them.

Worked example

User: "Compare Aave and Compound — TVL and fees, which one actually earns more?"

  1. search_tools → {"query": "protocol tvl fees revenue defi", "limit": 5}
  2. get_api_endpoint_schema for the protocol-metric endpoints returned, then invoke_api_endpoint once per protocol slug with schema-valid arguments.
  3. Normalize: same metric definitions, same window, same timestamps.
  4. Summarize the comparison in a table, with provider and fetched_at per metric, using the report template.

Report template

## Summary
[Protocol or chain DeFi read in one or two sentences.]

## Calls made
- Toolset: defi_protocol_analysis
- Endpoint(s): [exact endpoint names]
- Identifiers: [protocol slugs, chains, metric filters]

## Evidence
- TVL: [value + as-of]
- Fees/revenue: [value + window]
- Yields/stablecoins/bridges: [if requested]
- Provenance: [provider, fetched_at, runtime status per call]

## Caveats
[Unavailable metrics, stale snapshots, methodology differences.]

## Next action
[Compare peers, inspect a yield pool, or add token/pool diligence — only if needed.]

Gotchas

  • TVL, revenue, and fees answer different questions — do not substitute one for another.
  • High APY without liquidity/risk context is not a recommendation.
  • Provider methodology can differ across chains and protocols.

Runtime status handling

Treat unreliable or temporarily unavailable DeFi endpoints as degraded. Do not silently omit a metric; mark it unavailable with the runtime status.

Hand-offs

  • Token price/market questions → hive-market-research.
  • One pool's depth and trades → hive-dex-pool-analysis.
  • Protocol token safety → hive-token-diligence or hive-security-risk.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.