{
  "generatedFrom": "apps/web/src/data/mcp-facts.ts",
  "sourceOfTruth": "https://github.com/hive-intel/hive-skills",
  "runtimeResource": "hive://skills",
  "distribution": {
    "publicGitHubRepo": "https://github.com/hive-intel/hive-skills",
    "installAllCommand": "npx skills add hive-intel/hive-skills",
    "installSingleCommand": "npx skills add hive-intel/hive-skills --skill hive-token-diligence --yes",
    "listCommand": "npx skills add hive-intel/hive-skills --list",
    "claudePluginManifestPath": ".claude-plugin/plugin.json",
    "verified": "2026-07-11"
  },
  "count": 16,
  "skills": [
    {
      "name": "hive-mcp",
      "label": "Install Hive MCP",
      "description": "Connect Hive's hosted remote MCP endpoint to Claude, ChatGPT/OpenAI, Grok, Cursor, Windsurf, VS Code, Gemini CLI, and Codex.",
      "sourceDescription": "Use this skill when the user wants to install, configure, connect, verify, or debug Hive MCP in an AI client — Claude, ChatGPT/OpenAI, Grok, Cursor, Windsurf, VS Code, Gemini CLI, or Codex — including OAuth browser sign-in, headless API-key fallback, missing tools, 401/auth errors, and hosted-vs-stdio questions. For direct CLI or backend key creation use hive-build-onboarding; for calling Hive from app code use hive-build.",
      "category": "setup",
      "publicPath": "/skills/hive-mcp.md",
      "sourcePath": "agent-skills/packs/hive-mcp/SKILL.md",
      "toolsetIds": [
        "search_discovery"
      ],
      "useWhen": [
        "install hive",
        "connect mcp",
        "configure client"
      ]
    },
    {
      "name": "hive-build-onboarding",
      "label": "Get a Hive API Key",
      "description": "Guide agents through browser auth, dashboard key creation, and headless environment setup.",
      "sourceDescription": "Use this skill when the user needs a Hive API key or account — \"I don't have a key\", \"how do I sign up\", \"I lost my API key\", \"set up Hive for me\" — or needs browser sign-in versus headless/CI dashboard setup, key prefixes, or plan limits. Guide key creation without exposing secrets in chat, logs, screenshots, or committed files. After the key exists, route to hive-mcp or hive-cli to wire it up.",
      "category": "setup",
      "publicPath": "/skills/hive-build-onboarding.md",
      "sourcePath": "agent-skills/packs/hive-build-onboarding/SKILL.md",
      "toolsetIds": [
        "search_discovery"
      ],
      "useWhen": [
        "no api key",
        "sign up",
        "lost key"
      ]
    },
    {
      "name": "hive-build",
      "label": "Build With Hive",
      "description": "Use Hive from application code through REST, MCP clients, or the published TypeScript adapter.",
      "sourceDescription": "Use this skill when the user is integrating Hive into application code, backend services, agents, cron jobs, source-controlled adapters, or production systems — wiring Hive into a Next.js API route, a Python or Go cron job, a Rust or Java service, or a LangChain/CrewAI agent — rather than asking a one-off chat query.",
      "category": "build",
      "publicPath": "/skills/hive-build.md",
      "sourcePath": "agent-skills/packs/hive-build/SKILL.md",
      "toolsetIds": [
        "search_discovery"
      ],
      "useWhen": [
        "integrate api",
        "backend",
        "sdk",
        "production app"
      ],
      "procedure": [
        "Keep `HIVE_API_KEY` server-side. Browser apps should call a backend route you control.",
        "For public registry installs and non-TypeScript stacks, call the REST discovery and execution endpoints directly.",
        "For TypeScript backends, run `npm install hive-mcp-client` and use the adapter for schema lookup, endpoint invocation, retries, and metadata reads.",
        "Discover tools at runtime with `search_tools`, `hive://toolsets`, `/api/v1/tools` (discovery needs no key), or `getHiveEndpointSchema`; do not hardcode stale schemas.",
        "Preserve provider, freshness, warning, and runtime-status metadata in the application's own response shape."
      ],
      "notes": [
        "`npm install hive-mcp-client` installs the published adapter (0.1.5); the 0.3.0 release candidate is staged in the public mirror awaiting publication.",
        "REST remains the documented production fallback for registry-based installs, non-TypeScript services, and constrained runtimes."
      ]
    },
    {
      "name": "hive-cli",
      "label": "Use Hive CLI",
      "description": "Run Hive from shell scripts, cron jobs, and terminal research workflows.",
      "sourceDescription": "Use this skill when the user wants Hive from a terminal — \"run a CLI command for…\", \"show me from the terminal\", \"pipe this into jq\", \"give me a shell script\", \"set up a daily briefing\", cron jobs, or local diagnostics like hive doctor. Covers install, auth, domain subcommands, JSON/jq output, and scripting patterns. For agent-side tool calls use the MCP path instead; for app code use hive-build.",
      "category": "setup",
      "publicPath": "/skills/hive-cli.md",
      "sourcePath": "agent-skills/packs/hive-cli/SKILL.md",
      "toolsetIds": [
        "search_discovery"
      ],
      "useWhen": [
        "terminal",
        "cli",
        "jq",
        "cron"
      ]
    },
    {
      "name": "hive-query",
      "label": "Route A Crypto Query",
      "description": "Start from the user's intent, choose the canonical task toolset, inspect schemas, and call exact Hive tools.",
      "sourceDescription": "Default entry point for any live crypto question when Hive MCP is connected — prices, wallets, tokens, DeFi, NFTs, Solana, security, markets, DEX, networks, RWA perps. Use it whenever the answer depends on live or on-chain data instead of answering from memory, even if the user never mentions Hive. Routes intent to a canonical Hive task toolset, then schema lookup and bounded endpoint invocation. If a domain-specific hive-* skill clearly matches, prefer it; if routing cannot surface the exact tool or schema, hand off to hive-tool-discovery.",
      "category": "discovery",
      "publicPath": "/skills/hive-query.md",
      "sourcePath": "agent-skills/packs/hive-query/SKILL.md",
      "toolsetIds": [
        "market_research",
        "token_diligence",
        "wallet_investigation",
        "security_risk",
        "onchain_dex_pool_analysis",
        "defi_protocol_analysis",
        "nft_research",
        "network_infrastructure",
        "solana_analysis",
        "rwa_perp_analysis",
        "stateful_monitoring",
        "search_discovery"
      ],
      "useWhen": [
        "crypto question",
        "pick a tool",
        "tool routing",
        "unknown crypto data",
        "which hive endpoint"
      ]
    },
    {
      "name": "hive-stateful-monitoring",
      "label": "Stateful Monitoring",
      "description": "Create, list, update, and archive durable crypto intelligence monitors that agents can schedule, remember, and report from.",
      "sourceDescription": "Use this skill whenever the user wants Hive to remember, watch, monitor, schedule, alert, or report on crypto state across sessions — \"watch this wallet\", \"alert me if the price moves\", \"send me a daily digest\", \"what changed since last time\", \"remember that I care about X\". Converts durable intent into Hive monitors, alerts, reports, and memory facts that Hive workers execute later. For one-off live questions use hive-query or a domain skill instead.",
      "category": "stateful-monitoring",
      "publicPath": "/skills/hive-stateful-monitoring.md",
      "sourcePath": "agent-skills/packs/hive-stateful-monitoring/SKILL.md",
      "toolsetIds": [
        "stateful_monitoring"
      ],
      "useWhen": [
        "remember this",
        "monitor wallet",
        "watch token",
        "schedule crypto report",
        "alert me",
        "persistent crypto memory"
      ],
      "procedure": [
        "Convert the user's durable intent into a monitor `kind`, `target`, `rules`, and `cadence` before writing state.",
        "Call `hive_list_monitors` through the read-only `invoke_api_endpoint` before creating duplicates or changing an existing monitor.",
        "Inspect the exact write schema, show the proposed state change, and obtain explicit user approval before calling `invoke_stateful_endpoint` for `hive_create_monitor`, `hive_update_monitor`, or `hive_archive_monitor`.",
        "Use `hive_get_monitor_runs`, `hive_list_observations`, `hive_list_alerts`, `hive_get_latest_snapshot`, or `hive_generate_monitor_report` through `invoke_api_endpoint` when the user asks what changed or what Hive remembers.",
        "Use `invoke_stateful_endpoint` for an explicitly approved `hive_update_alert_status`, `hive_remember_fact`, `hive_forget_memory_fact`, or `hive_archive_subject` call. Use `invoke_api_endpoint` for the corresponding reads.",
        "Use B2B subject tools only for adapter state-boundary operations, with subject context injected by a trusted backend rather than model arguments.",
        "Explain that monitor execution is handled by Hive workers, not by the current chat session."
      ],
      "notes": [
        "Worker-supported monitor kinds are `wallet`, `token`, `protocol`, `market`, `watchlist_digest`, `token_discovery_risk`, and `risk_watch`.",
        "For B2B adapter mode, state is isolated by server-injected subject context. Never ask the model or end user to provide `__hive_user_id` or `__hive_subject_id`.",
        "If stateful tools return `missing_key` or an auth-required error, say the monitor was not saved and explain which backend or auth prerequisite is missing."
      ]
    },
    {
      "name": "hive-tool-discovery",
      "label": "Tool Discovery",
      "description": "Use task discovery, schema lookup, read-only invocation, approved stateful writes, and result validation correctly.",
      "sourceDescription": "Use this skill when the exact Hive MCP tool, task toolset, provider, endpoint name, schema, operation type, or argument shape is unknown and hive-query routing was not enough — including \"what can Hive do\", \"which provider covers X\", \"is Hive healthy\", or any failed tool-name guess. Discover first with compact Hive resources and search_tools, then inspect the schema before routing reads to invoke_api_endpoint or explicitly approved Hive writes to invoke_stateful_endpoint.",
      "category": "discovery",
      "publicPath": "/skills/hive-tool-discovery.md",
      "sourcePath": "agent-skills/packs/hive-tool-discovery/SKILL.md",
      "toolsetIds": [
        "search_discovery"
      ],
      "useWhen": [
        "unknown tool",
        "schema",
        "discovery",
        "search tools",
        "invoke endpoint",
        "category tool"
      ]
    },
    {
      "name": "hive-market-research",
      "label": "Market Research",
      "description": "Research prices, liquidity, exchanges, OHLC, order books, and derivatives context.",
      "sourceDescription": "Use this skill for any live crypto market question — prices, 24h moves, liquidity, exchange/venue data, OHLC candles, order books, tickers, funding rates, derivatives, trading context — even casual asks like \"what's BTC at\" or \"is ETH pumping\". Use it whenever the answer needs current market numbers instead of memory. For on-chain pool depth and DEX trades use hive-dex-pool-analysis; for protocol TVL/fees/yields use hive-defi-research.",
      "category": "market",
      "publicPath": "/skills/hive-market-research.md",
      "sourcePath": "agent-skills/packs/hive-market-research/SKILL.md",
      "toolsetIds": [
        "market_research"
      ],
      "useWhen": [
        "price",
        "market",
        "spot",
        "exchange",
        "order book",
        "ohlc",
        "volume",
        "funding",
        "open interest",
        "liquidations",
        "derivatives",
        "options"
      ]
    },
    {
      "name": "hive-token-diligence",
      "label": "Token Diligence",
      "description": "Investigate token metadata, market context, liquidity, holders, enrichment, and risk.",
      "sourceDescription": "Use this skill whenever the user asks whether a specific token is real, legit, liquid, well-held, enriched, investable, or worth researching — \"is this token a scam\", \"run diligence on 0x…\", \"who holds this\", \"does it have real liquidity\" — even if they never say \"diligence\". Investigates metadata, market context, holders, DEX liquidity, enrichment, and risk signals for an exact chain and contract. For pre-transaction risk checks (approvals, signing, swap simulation) use hive-security-risk; for pool-level depth and trade flow use hive-dex-pool-analysis; for Solana mints use hive-solana-analysis.",
      "category": "token",
      "publicPath": "/skills/hive-token-diligence.md",
      "sourcePath": "agent-skills/packs/hive-token-diligence/SKILL.md",
      "toolsetIds": [
        "token_diligence"
      ],
      "useWhen": [
        "token",
        "contract",
        "holders",
        "top traders",
        "metadata",
        "socials",
        "liquidity",
        "token risk before buying",
        "token diligence"
      ]
    },
    {
      "name": "hive-wallet-investigation",
      "label": "Wallet Investigation",
      "description": "Inspect wallet balances, transfers, NFTs, PnL, DeFi positions, and notable activity.",
      "sourceDescription": "Use this skill whenever the user wants to look inside a wallet or address — portfolio, holdings, balances, transfers, PnL, NFT exposure, DeFi positions, whale moves, \"what does this address hold\", \"trace this wallet's activity\" — even if they just paste an address. Requires wallet address and chain before executing Hive wallet tools. For Solana wallets use hive-solana-analysis; for \"is this address malicious\" risk checks use hive-security-risk.",
      "category": "wallet",
      "publicPath": "/skills/hive-wallet-investigation.md",
      "sourcePath": "agent-skills/packs/hive-wallet-investigation/SKILL.md",
      "toolsetIds": [
        "wallet_investigation"
      ],
      "useWhen": [
        "wallet",
        "portfolio",
        "balances",
        "holdings",
        "pnl",
        "profitability",
        "transfers",
        "swaps",
        "defi positions",
        "chain activity"
      ]
    },
    {
      "name": "hive-security-risk",
      "label": "Security Risk",
      "description": "Check token, approval, address, phishing, contract, and simulation risk signals.",
      "sourceDescription": "Use this skill before the user signs, approves, swaps, connects a wallet to a dApp, or touches an unknown contract, URL, or transaction payload — any \"should I sign/approve/ape/connect\" moment, even when the user only implies the transaction. Runs token, address, approval, phishing, and simulation risk checks and reports severity, evidence, and remediation instead of guessing. For research-style \"is this token worth a look\" questions use hive-token-diligence.",
      "category": "security",
      "publicPath": "/skills/hive-security-risk.md",
      "sourcePath": "agent-skills/packs/hive-security-risk/SKILL.md",
      "toolsetIds": [
        "security_risk"
      ],
      "useWhen": [
        "security",
        "risk",
        "safe",
        "scam",
        "rugpull",
        "honeypot",
        "malicious",
        "phishing",
        "dapp",
        "approval",
        "calldata",
        "simulate"
      ]
    },
    {
      "name": "hive-dex-pool-analysis",
      "label": "DEX And Pool Analysis",
      "description": "Analyze on-chain pools, pairs, liquidity, trades, OHLCV, and DEX flow.",
      "sourceDescription": "Use this skill when the user asks about a DEX pool or trading pair — liquidity depth, recent swaps/trades, OHLCV candles, trending pools, fee tiers, or token-level DEX flow on a chain — including \"how deep is the X/Y pool\", \"what's trading on Uniswap\", or a pasted pair address. For CEX prices, order books, and funding use hive-market-research; for whole-token diligence use hive-token-diligence.",
      "category": "dex",
      "publicPath": "/skills/hive-dex-pool-analysis.md",
      "sourcePath": "agent-skills/packs/hive-dex-pool-analysis/SKILL.md",
      "toolsetIds": [
        "onchain_dex_pool_analysis"
      ],
      "useWhen": [
        "dex",
        "pool",
        "pair",
        "liquidity",
        "trades",
        "ohlcv",
        "trending pools",
        "uniswap"
      ]
    },
    {
      "name": "hive-defi-research",
      "label": "DeFi Research",
      "description": "Analyze protocols, TVL, fees, revenue, stablecoins, bridges, and yield pools.",
      "sourceDescription": "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.",
      "category": "defi",
      "publicPath": "/skills/hive-defi-research.md",
      "sourcePath": "agent-skills/packs/hive-defi-research/SKILL.md",
      "toolsetIds": [
        "defi_protocol_analysis"
      ],
      "useWhen": [
        "defi",
        "protocol",
        "tvl",
        "fees",
        "revenue",
        "stablecoin",
        "bridge",
        "yield",
        "apy"
      ]
    },
    {
      "name": "hive-nft-research",
      "label": "NFT Research",
      "description": "Research NFT collections, ownership, metadata, floor price, sales, rarity, and spam checks.",
      "sourceDescription": "Use this skill when the user asks about NFT collections or assets on EVM chains — ownership, metadata, traits, floor prices, sales, rarity, spam/authenticity checks — like \"what's the floor on this collection\", \"who owns this NFT\", \"is this collection spam\". Use it whenever the user needs current NFT evidence rather than a general explanation of NFTs. For Solana-native assets (mints, DAS, compressed NFTs) use hive-solana-analysis.",
      "category": "nft",
      "publicPath": "/skills/hive-nft-research.md",
      "sourcePath": "agent-skills/packs/hive-nft-research/SKILL.md",
      "toolsetIds": [
        "nft_research"
      ],
      "useWhen": [
        "nft",
        "collection",
        "floor",
        "sales",
        "owner",
        "metadata",
        "rarity",
        "spam"
      ]
    },
    {
      "name": "hive-solana-analysis",
      "label": "Solana Analysis",
      "description": "Analyze Solana wallets, SPL token accounts, DAS assets, parsed transactions, and priority fees.",
      "sourceDescription": "Use this skill for anything Solana-native — wallets, mints, SPL token accounts, DAS assets, parsed transactions, priority fees, pump.fun launches, Solana NFTs, Solana token risk. Prefer it over EVM-shaped skills whenever the identifier is a base58 address, mint, or transaction signature, even if the user never says \"Solana\". Uses Solana-native identifiers and providers instead of EVM assumptions.",
      "category": "solana",
      "publicPath": "/skills/hive-solana-analysis.md",
      "sourcePath": "agent-skills/packs/hive-solana-analysis/SKILL.md",
      "toolsetIds": [
        "solana_analysis"
      ],
      "useWhen": [
        "solana",
        "spl",
        "das",
        "priority fee",
        "pumpfun",
        "token accounts",
        "parsed transaction"
      ]
    },
    {
      "name": "hive-network-infrastructure",
      "label": "Network Infrastructure",
      "description": "Read chain state, gas, blocks, receipts, logs, transaction status, and RPC diagnostics.",
      "sourceDescription": "Use this skill when the user asks about chain state or transaction plumbing — gas prices, blocks, transaction receipts and status (\"did my tx go through\"), event logs, supported networks, fee data, or RPC diagnostics. Use it whenever the answer needs current chain-level evidence. For wallet holdings use hive-wallet-investigation; for Solana slots/fees use hive-solana-analysis.",
      "category": "network",
      "publicPath": "/skills/hive-network-infrastructure.md",
      "sourcePath": "agent-skills/packs/hive-network-infrastructure/SKILL.md",
      "toolsetIds": [
        "network_infrastructure"
      ],
      "useWhen": [
        "gas",
        "block",
        "receipt",
        "logs",
        "rpc",
        "transaction status",
        "chain state",
        "tenderly networks"
      ]
    }
  ]
}