hive-intelligence 1.1.0 → 1.1.3

package/agent-skills/packs/hive-security-risk/evals/evals.json

@@ -0,0 +1,27 @@
+{
+  "skill_name": "hive-security-risk",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Is it safe to approve this spender for my ERC-20 token?",
+      "expected_output": "Uses security_risk, asks for chain/token/owner/spender if missing, checks approval risk, and avoids signing guidance until risk is resolved.",
+      "files": [],
+      "assertions": [
+        "Chooses security_risk.",
+        "Requests missing approval identifiers.",
+        "Does not tell the user to sign while risk is unresolved."
+      ]
+    },
+    {
+      "id": 2,
+      "prompt": "Check whether this dApp URL and contract look phishing-related before I connect my wallet.",
+      "expected_output": "Routes to dApp/address/phishing checks, reports severity/evidence/remediation, and caveats missing provider data.",
+      "files": [],
+      "assertions": [
+        "Includes phishing or dApp risk checks.",
+        "Reports severity and evidence.",
+        "Provides remediation or next action."
+      ]
+    }
+  ]
+}

package/agent-skills/packs/hive-security-risk/references/workflow.md

@@ -0,0 +1,46 @@
+# Security Risk Workflow
+
+Use this reference for token, address, approval, dApp, phishing, contract, and
+transaction simulation risk.
+
+## Required identifiers
+
+- Chain/network.
+- One or more of: token contract, wallet address, spender address, dApp URL,
+  contract address, or transaction payload.
+
+Ask for missing chain and actor details before approval or simulation checks.
+Never invent a spender, owner, calldata, or URL.
+
+## Tool selection order
+
+1. Identify the risk object: token, address, approval, dApp, contract, or
+   transaction.
+2. Use `search_tools` for the matching security/risk endpoints.
+3. Inspect schemas before invocation.
+4. Run the narrowest risk check first.
+5. Add simulation or approval analysis only when the required payload/owner
+   details exist.
+
+## Bounded calls
+
+- Keep risk checks scoped to the provided contract, address, or payload.
+- Avoid broad scans unless the user explicitly asks for an audit.
+- Use severity and evidence rather than unsupported certainty.
+
+## Report template
+
+- Summary: risk level and safest recommendation.
+- Calls made: endpoints, chain, risk object, identifiers.
+- Evidence: flags, simulation results, approval exposure, source/freshness.
+- Caveats: missing payload, incomplete provider coverage, degraded/rate-limited
+  provider.
+- Next action: revoke approval, avoid signing, retry simulation, or provide
+  missing payload.
+
+## Gotchas
+
+- A token can pass metadata checks and still be risky.
+- `plan_required` means the tool exists but cannot run under current upstream
+  credentials.
+- Do not provide signing instructions when a critical risk is unresolved.

package/agent-skills/packs/hive-solana-analysis/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: hive-solana-analysis
+description: Use this skill for Solana-specific analysis covering wallets, SPL token accounts, DAS assets, parsed transactions, priority fees, launch data, mints, or Solana NFT assets. Prefer Solana-native identifiers and providers over EVM assumptions.
+license: MIT
+metadata:
+  package: "@hiveintelligence/agent-skills"
+  category: "solana"
+  requires_network: "true"
+version: 1.0.0
+---
+
+# hive-solana-analysis — Solana Analysis
+
+Use this skill for Solana wallets, mints, SPL accounts, DAS assets, parsed
+transactions, priority fees, or Solana token safety questions.
+
+## Task toolset
+
+Use `solana_analysis`.
+
+Required identifiers: Solana wallet, mint, asset id, or transaction signature.
+
+## Procedure
+
+Read `references/workflow.md` when the request needs Solana-native identifier
+handling, DAS/SPL routing, priority-fee context, or a structured Solana report.
+
+1. Confirm the identifier type: wallet, mint, asset id, program id, or
+   transaction signature.
+2. Use Solana-native tools instead of EVM assumptions.
+3. For wallets, combine balances, token accounts, assets, and parsed history.
+4. For execution context, include slot/priority fee/freshness.
+
+## Example
+
+If the user gives a mint, use token/security or asset search paths. If the user
+gives a wallet, use owner/balance paths.
+
+## Runtime status handling
+
+Classify Helius or Solana provider issues as `missing_key`, `rate_limited`,
+`degraded`, or `failing`. Ask for a retry only when the status is transient.

package/agent-skills/packs/hive-solana-analysis/evals/evals.json

@@ -0,0 +1,27 @@
+{
+  "skill_name": "hive-solana-analysis",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Analyze this Solana wallet's SPL token accounts and recent parsed activity.",
+      "expected_output": "Uses solana_analysis, treats the identifier as Solana-native, inspects schemas, bounds token/history calls, and reports slot/freshness/runtime status.",
+      "files": [],
+      "assertions": [
+        "Chooses solana_analysis.",
+        "Avoids EVM assumptions.",
+        "Reports Solana-specific freshness such as slot or fetched time."
+      ]
+    },
+    {
+      "id": 2,
+      "prompt": "Check this Solana mint and whether there are any asset or launch-data signals.",
+      "expected_output": "Classifies the identifier as a mint, uses Solana token/DAS/launch paths, and reports provider caveats.",
+      "files": [],
+      "assertions": [
+        "Classifies mint versus wallet.",
+        "Uses Solana-native tool discovery.",
+        "Reports provider/runtime caveats."
+      ]
+    }
+  ]
+}

package/agent-skills/packs/hive-solana-analysis/references/workflow.md

@@ -0,0 +1,42 @@
+# Solana Analysis Workflow
+
+Use this reference for Solana wallets, SPL accounts, DAS assets, parsed
+transactions, priority fees, launch data, mints, and Solana NFTs.
+
+## Required identifiers
+
+- Solana wallet, mint, token account, asset id, program id, or transaction
+  signature.
+- Optional: slot/time window, owner, collection, or token filter.
+
+Do not apply EVM address, chain id, or approval assumptions to Solana requests.
+
+## Tool selection order
+
+1. Classify the identifier: wallet, mint, token account, asset, program, or
+   transaction.
+2. Use `search_tools` for Solana wallet, SPL token, DAS, parsed transaction,
+   priority fee, or launch-data tools.
+3. Inspect schemas before invocation.
+4. Use wallet paths for owner/balance/history questions.
+5. Use mint/asset paths for token/NFT questions.
+
+## Bounded calls
+
+- Limit parsed history, asset lists, and token accounts.
+- Include slot or fetched time where available.
+- Avoid multi-provider mixing without source labels.
+
+## Report template
+
+- Summary: Solana-specific read.
+- Calls made: endpoints, identifiers, filters.
+- Evidence: balances/assets/transactions/fees, source/freshness/runtime status.
+- Caveats: missing key, rate limit, DAS coverage, stale slot, truncated history.
+- Next action: transaction drilldown, asset verification, or risk check.
+
+## Gotchas
+
+- Wallets, mints, token accounts, and asset ids are different identifiers.
+- Priority fee estimates are time-sensitive.
+- Parsed transaction coverage can vary by provider and transaction type.

package/agent-skills/packs/hive-token-diligence/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: hive-token-diligence
+description: Use this skill when the user asks whether a token is real, liquid, risky, enriched, investable, tradeable, or worth researching further. Investigate exact chain and token identifiers across metadata, market context, holders, DEX liquidity, enrichment, and risk signals.
+license: MIT
+metadata:
+  package: "@hiveintelligence/agent-skills"
+  category: "token"
+  requires_network: "true"
+version: 1.0.0
+---
+
+# hive-token-diligence — Token Diligence
+
+Use this skill when the user asks whether a token is real, liquid, risky, or
+worth researching further.
+
+## Task toolset
+
+Use `token_diligence`.
+
+Required identifiers: chain and token contract or exact token id.
+
+## Procedure
+
+Read `references/workflow.md` when the request needs multi-source diligence,
+risk/liquidity prioritization, fallback handling, or a structured token report.
+
+1. Resolve the token with exact chain and contract.
+2. Pull metadata, price, pair/liquidity, holder, and risk tools as needed.
+3. Separate facts from interpretation: metadata, market, liquidity, holders,
+   security, enrichment.
+4. Preserve raw provider details when a risk flag depends on source-specific
+   fields.
+
+## Example
+
+For Ethereum USDC, use the chain plus contract address fixture rather than just
+the symbol `USDC`.
+
+## Runtime status handling
+
+Use Hive's runtime statuses directly. If Moralis enrichment is
+`plan_required`, keep the rest of the diligence report and mark enrichment as
+unavailable rather than claiming token diligence failed.

package/agent-skills/packs/hive-token-diligence/evals/evals.json

@@ -0,0 +1,27 @@
+{
+  "skill_name": "hive-token-diligence",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Run diligence on this Ethereum token contract before I trade it: 0x0000000000000000000000000000000000000000",
+      "expected_output": "Uses token_diligence, preserves exact chain/contract, plans metadata/liquidity/holder/risk checks, and reports caveats without trading advice.",
+      "files": [],
+      "assertions": [
+        "Chooses token_diligence.",
+        "Requires exact chain and contract.",
+        "Includes liquidity and risk evidence sections."
+      ]
+    },
+    {
+      "id": 2,
+      "prompt": "Is this token real or a scam? I only have the ticker.",
+      "expected_output": "Does not assume a contract from ticker alone, asks for chain/contract or performs discovery, and explains ambiguity.",
+      "files": [],
+      "assertions": [
+        "Does not treat ticker as unique.",
+        "Asks for chain and contract or resolves explicitly.",
+        "Avoids unsupported safety conclusion."
+      ]
+    }
+  ]
+}

package/agent-skills/packs/hive-token-diligence/references/workflow.md

@@ -0,0 +1,45 @@
+# Token Diligence Workflow
+
+Use this reference when a token needs metadata, liquidity, holder, enrichment,
+and risk evidence.
+
+## Required identifiers
+
+- Chain/network.
+- Exact token contract or provider-specific token id.
+- Optional: quote token, pool address, wallet holder, or time window.
+
+If the user gives only a ticker or name, resolve the exact contract before
+execution. Do not assume a ticker maps to one asset.
+
+## Tool selection order
+
+1. Resolve chain and contract from the prompt or ask for them.
+2. Use `search_tools` for token metadata, market, holder, DEX liquidity, and
+   risk capabilities.
+3. Inspect schemas before calling each endpoint.
+4. Start with metadata and market/liquidity checks.
+5. Add holder distribution and enrichment only when the user needs depth.
+6. Add security/risk checks when the user asks whether to trade, approve, or
+   trust the token.
+
+## Bounded calls
+
+- Limit holder lists and pool searches.
+- Separate token-level data from pool-level data.
+- Preserve provider-specific risk fields when they drive the conclusion.
+
+## Report template
+
+- Summary: token identity and overall diligence posture.
+- Calls made: endpoints and identifiers.
+- Evidence: metadata, liquidity, holders, risk/enrichment, source/freshness.
+- Caveats: missing provider keys, plan gates, stale liquidity, unresolved
+  contract ambiguity.
+- Next action: security drilldown, liquidity venue check, or holder analysis.
+
+## Gotchas
+
+- A verified name/logo is not proof of safety.
+- High FDV or high volume without pool depth can still be risky.
+- Missing enrichment is not the same as a clean risk result.

package/agent-skills/packs/hive-tool-discovery/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: hive-tool-discovery
+description: Use this skill when the exact Hive MCP tool, task toolset, provider, endpoint name, schema, or argument shape is unknown. Discover first with Hive resources and search_tools, then inspect schema before any invoke_api_endpoint call.
+license: MIT
+metadata:
+  package: "@hiveintelligence/agent-skills"
+  category: "discovery"
+  requires_network: "true"
+version: 1.0.0
+---
+
+# hive-tool-discovery — Find The Right Hive Tool
+
+Use this skill before calling Hive when the user's request is ambiguous or the
+exact endpoint name is unknown.
+
+## Procedure
+
+Read `references/discovery-surfaces.md` when the user asks what discovery
+surfaces exist, how agents know available endpoints, or when to use resources
+instead of tool calls.
+
+1. Read `hive://toolsets` for task-level routing.
+2. Call `search_tools` with the user's intent and optional provider/category.
+3. Pick the most specific tool or task toolset.
+4. Call `get_api_endpoint_schema` before execution.
+5. Call `invoke_api_endpoint` with only schema-valid arguments.
+
+## Example
+
+```json
+{
+  "query": "wallet investigation ethereum balances transfers",
+  "limit": 5
+}
+```
+
+## Runtime status handling
+
+Hive uses `ok`, `missing_key`, `plan_required`, `rate_limited`, `degraded`, and
+`failing`. Missing keys, plan gates, quota exhaustion, and rate limits are
+runtime states. Do not say a tool does not exist unless discovery fails to find
+it.
+
+## Guardrails
+
+- Do not hardcode stale endpoint names.
+- Use `hive://skills` when the question matches a recurring workflow.
+- Use `hive://status` when the user asks whether Hive or a provider is healthy.

package/agent-skills/packs/hive-tool-discovery/evals/evals.json

@@ -0,0 +1,38 @@
+{
+  "skill_name": "hive-tool-discovery",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "I know Hive has a lot of tools. Which one should I use to get token holders for an Ethereum contract?",
+      "expected_output": "Uses discovery before execution, searches token holder intent, selects the most specific endpoint, and inspects the endpoint schema.",
+      "files": [],
+      "assertions": [
+        "Calls or recommends search_tools with token holders, ethereum, contract.",
+        "Uses get_api_endpoint_schema before invocation.",
+        "Does not hardcode an endpoint without discovery."
+      ]
+    },
+    {
+      "id": 2,
+      "prompt": "Show me all the ways an agent can discover Hive MCP endpoints and provider availability.",
+      "expected_output": "Explains resources, meta tools, category listing tools, schema lookup, and runtime status surfaces.",
+      "files": [],
+      "assertions": [
+        "Mentions hive://toolsets, hive://tools, hive://providers, and hive://status.",
+        "Mentions search_tools, get_api_endpoint_schema, and invoke_api_endpoint.",
+        "Separates discovery from execution."
+      ]
+    },
+    {
+      "id": 3,
+      "prompt": "A Hive provider is missing an API key. Should the agent say the tool does not exist?",
+      "expected_output": "Classifies missing keys as runtime availability, not catalog absence, and tells the user the provider/tool state and next action.",
+      "files": [],
+      "assertions": [
+        "Explains missing_key as a runtime state.",
+        "Does not describe the endpoint as unavailable from the catalog.",
+        "Gives an actionable diagnostic step."
+      ]
+    }
+  ]
+}

package/agent-skills/packs/hive-tool-discovery/references/discovery-surfaces.md

@@ -0,0 +1,62 @@
+# Hive Discovery Surfaces
+
+Use this reference when the exact Hive endpoint is unknown. Discovery is a
+first-class workflow, not a fallback after a failed tool call.
+
+## Surfaces
+
+| Surface | Use when | Output |
+| --- | --- | --- |
+| `hive://toolsets` | The user described a task or workflow | Canonical task toolsets, required inputs, recommended tools |
+| `hive://tools` | The user asks what Hive can call | Full catalog summary without flooding root `tools/list` |
+| `hive://providers` | The user asks about provider coverage or provenance | Provider names, categories, auth/runtime notes |
+| `hive://status` | The user asks if Hive or a provider is healthy | Classified provider/runtime state |
+| `hive://skills` | The request matches a recurring workflow | Agent skills and when to apply them |
+| `search_tools` | Intent is known but exact endpoint is not | Ranked endpoint/toolset candidates |
+| Category listing tools | The user is inside a known category | Scoped tool lists for market, wallet, DeFi, NFT, security, and other domains |
+| `get_api_endpoint_schema` | Before any exact invocation | Parameters, required fields, validation shape |
+| `invoke_api_endpoint` | After schema validation | Bounded provider call with normalized output and provenance |
+
+## Decision rules
+
+- For broad crypto questions, start with `hive://toolsets`.
+- For "what tools do you have?" questions, read `hive://tools`.
+- For "which provider/source?" questions, read `hive://providers`.
+- For health, quota, key, or degradation questions, read `hive://status`.
+- For exact execution, never skip schema lookup unless the schema was already
+  loaded in the current turn.
+
+## Search query shape
+
+Good `search_tools` queries combine workflow, domain, chain, and identifier
+type:
+
+```json
+{
+  "query": "wallet investigation ethereum token balances transfers",
+  "limit": 5
+}
+```
+
+```json
+{
+  "query": "token security ethereum contract honeypot approvals",
+  "limit": 5
+}
+```
+
+```json
+{
+  "query": "prediction markets event outcomes traders polymarket",
+  "limit": 5
+}
+```
+
+## Common failure states
+
+- `missing_key`: the endpoint exists, but the configured key is absent.
+- `plan_required`: the endpoint exists, but the account plan does not allow it.
+- `rate_limited`: retry later or reduce the call volume.
+- `degraded`: provider returned partial, fallback, cached, or stale data.
+- `failing`: provider or Hive path failed. Return the classified failure and
+  the next diagnostic step.

package/agent-skills/packs/hive-wallet-investigation/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: hive-wallet-investigation
+description: Use this skill for wallet, portfolio, holder, whale, transfer, PnL, NFT exposure, DeFi position, or notable on-chain activity investigations. Require wallet address and chain before executing Hive wallet tools.
+license: MIT
+metadata:
+  package: "@hiveintelligence/agent-skills"
+  category: "wallet"
+  requires_network: "true"
+version: 1.0.0
+---
+
+# hive-wallet-investigation — Wallet Investigation
+
+Use this skill when the user asks to investigate a wallet, portfolio, holdings,
+transfers, PnL, NFT exposure, or DeFi positions.
+
+## Task toolset
+
+Use `wallet_investigation`.
+
+Required identifiers: wallet address and chain.
+
+## Procedure
+
+Read `references/workflow.md` when the request needs multi-chain handling,
+activity triage, risk caveats, or a structured wallet investigation report.
+
+1. Validate the address format for the requested chain.
+2. Start with balances and native balance.
+3. Add transfers, NFT holdings, DeFi positions, or PnL only when relevant.
+4. Summarize exposure, concentration, notable activity, and missing data.
+
+## Example
+
+If the user provides an EVM wallet but no chain, ask whether they want Ethereum,
+Base, Arbitrum, Polygon, or a multi-chain investigation.
+
+## Runtime status handling
+
+Classify provider failures as `missing_key`, `plan_required`, `rate_limited`,
+`degraded`, or `failing`. A single blocked enrichment tool should not suppress
+balances or transfers that did succeed.

package/agent-skills/packs/hive-wallet-investigation/evals/evals.json

@@ -0,0 +1,27 @@
+{
+  "skill_name": "hive-wallet-investigation",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Investigate this Ethereum wallet's balances and recent transfers: 0x0000000000000000000000000000000000000000",
+      "expected_output": "Uses wallet_investigation, validates chain/address, starts with balances, adds bounded recent transfers, and reports source/freshness/runtime status.",
+      "files": [],
+      "assertions": [
+        "Chooses wallet_investigation.",
+        "Starts with balances/native balance.",
+        "Bounds transfer history."
+      ]
+    },
+    {
+      "id": 2,
+      "prompt": "This EVM wallet might be active on several chains. Can you inspect it?",
+      "expected_output": "Asks whether the user wants a specific chain or multi-chain scope, avoids silently mixing chains, and labels each provider/source.",
+      "files": [],
+      "assertions": [
+        "Asks for chain scope or states multi-chain plan.",
+        "Does not silently mix chain data.",
+        "Reports provider/runtime caveats."
+      ]
+    }
+  ]
+}

package/agent-skills/packs/hive-wallet-investigation/references/workflow.md

@@ -0,0 +1,45 @@
+# Wallet Investigation Workflow
+
+Use this reference for wallet balances, transfers, PnL, NFTs, DeFi positions,
+and notable activity.
+
+## Required identifiers
+
+- Wallet address.
+- Chain/network, unless the user explicitly asks for multi-chain.
+- Optional: time window, asset filter, counterparty, protocol, or NFT
+  collection.
+
+Ask for chain when an EVM address appears without context. For Solana wallets,
+use the Solana skill when the request is Solana-specific.
+
+## Tool selection order
+
+1. Validate the identifier shape for the requested chain.
+2. Use `search_tools` for wallet balance, native balance, transfer, NFT, DeFi,
+   and PnL tools.
+3. Inspect schemas before endpoint invocation.
+4. Start with balances/native balance.
+5. Add transfers for activity questions.
+6. Add NFTs, DeFi positions, or PnL only when relevant.
+
+## Bounded calls
+
+- Use explicit `limit`, `page`, `per_page`, or time filters for transfers.
+- Do not fetch full history for a quick portfolio read.
+- Avoid mixing chains unless the user requested multi-chain analysis.
+
+## Report template
+
+- Summary: wallet posture and notable finding.
+- Calls made: endpoints, chain, wallet, filters.
+- Evidence: balances, transfers, exposure, provider/freshness/runtime status.
+- Caveats: missing chains, truncated history, unavailable enrichment, degraded
+  providers.
+- Next action: chain expansion, transfer drilldown, risk check, or PnL detail.
+
+## Gotchas
+
+- Wallet labels and owner identity are not guaranteed.
+- Token balances can include spam or illiquid assets.
+- Absence of DeFi/NFT data may reflect provider coverage, not true absence.

package/agent-skills/references/agents-routing.md

@@ -0,0 +1,49 @@
+# Hive AGENTS.md Routing Snippet
+
+Use this compact routing block in `AGENTS.md`, `CLAUDE.md`, `GEMINI.md`, or a
+client-specific always-loaded instruction file. It solves the common failure
+mode where the skill exists but the agent answers from memory before loading it.
+
+```markdown
+## Hive MCP Routing
+
+For live crypto intelligence, prefer Hive retrieval over model memory.
+
+- User asks about live crypto data, prices, wallets, tokens, DeFi, NFTs,
+  Solana, security, DEX pools, network state, or prediction markets:
+  use `hive-query`.
+- Exact Hive endpoint, provider, schema, or argument shape is unknown:
+  use `hive-tool-discovery`.
+- Clear domain request:
+  - prices, liquidity, exchanges, OHLC, order books: `hive-market-research`
+  - token metadata, holders, liquidity, enrichment, risk:
+    `hive-token-diligence`
+  - wallet balances, transfers, PnL, NFTs, DeFi positions:
+    `hive-wallet-investigation`
+  - token, approval, contract, dApp, phishing, simulation risk:
+    `hive-security-risk`
+  - DEX pools, pairs, trades, liquidity, OHLCV: `hive-dex-pool-analysis`
+  - protocol TVL, fees, yields, stablecoins, bridges:
+    `hive-defi-research`
+  - NFT ownership, metadata, floors, sales, rarity: `hive-nft-research`
+  - Solana wallets, SPL accounts, DAS assets, priority fees:
+    `hive-solana-analysis`
+  - blocks, gas, receipts, logs, RPC diagnostics:
+    `hive-network-infrastructure`
+  - prediction markets, events, outcomes, traders:
+    `hive-prediction-markets`
+- Setup, API key, CLI, or app integration:
+  use `hive-mcp`, `hive-build-onboarding`, `hive-cli`, or `hive-build`.
+
+Default execution loop:
+1. Read `hive://toolsets` or call `search_tools`.
+2. Select one task toolset or exact endpoint.
+3. Call `get_api_endpoint_schema`.
+4. Execute through `invoke_api_endpoint` with bounded args.
+5. Report provider, source/freshness, fallback/cache/degraded state, and
+   runtime status (`ok`, `missing_key`, `plan_required`, `rate_limited`,
+   `degraded`, or `failing`).
+```
+
+Keep this snippet short. The skill files carry the detailed workflow and should
+be loaded only after the routing layer selects the right Hive skill.