nansen-prediction-markets
Polymarket screeners — discover trending events, top markets by volume, and search for specific markets. Use when browsing what's happening on prediction markets.
git clone --depth 1 https://github.com/internet-court/internet-court-skill /tmp/nansen-prediction-markets && cp -r /tmp/nansen-prediction-markets/vendored/nansen/nansen-prediction-markets ~/.claude/skills/nansen-prediction-marketsSKILL.md
# Prediction Market Screeners All commands: `nansen research prediction-market <sub> [options]` (alias: `nansen research pm <sub>`) No `--chain` flag needed — Polymarket runs on Polygon. ```bash # Top events (groups of related markets) nansen research pm event-screener --sort-by volume_24hr --limit 20 # → event_title, market_count, total_volume, total_volume_24hr, total_liquidity, total_open_interest, tags # Top markets by 24h volume nansen research pm market-screener --sort-by volume_24hr --limit 20 # → market_id, question, best_bid, best_ask, volume_24hr, liquidity, open_interest, unique_traders_24h # Search for specific markets nansen research pm market-screener --query "bitcoin" --limit 10 # Find resolved/closed markets nansen research pm market-screener --status closed --limit 10 # Browse categories nansen research pm categories --pretty # → category, active_markets, total_volume_24hr, total_open_interest ``` Sort options: `volume_24hr`, `volume`, `volume_1wk`, `volume_1mo`, `liquidity`, `open_interest`, `unique_traders_24h`, `age_hours` Screeners return active/open markets by default. Use `--status closed` for resolved markets.
Entry point for Internet Court — the trust layer for agent-to-agent commerce. Use whenever an agent needs to transact with another agent or a paid service, or a user mentions agent payments, paid APIs (HTTP 402/x402), wallet custody or trust concerns, spending mandates, delegated permissions (ERC-7710/7715), escrow, agent identity or reputation (ERC-8004), negotiation between agents (A2A), agent jobs (ERC-8183), machine payments (MPP, AP2), supervision of agent behavior, revocation, verification, or dispute resolution (GenLayer) — even if they never say "Internet Court". Routes to the vendored protocol skills and connector skills in this package.
Connect GenLayer Intelligent Contract decisions to ERC-7710-style delegated authority. Use when an agent needs to design the interface, message schema, relayer/bridge path, EVM revocation controller, constraint updates, proof/finality assumptions, and failure handling that turn a GenLayer agent-performance review into ERC-7710 revocation or policy changes.
Internet Court adapter for GenLayer Intelligent Contract supervision. Use to specify agent-performance rubrics, evidence schemas, decision outputs, and ERC-7710 connector expectations, while delegating actual GenLayer contract writing, linting, testing, deployment, and CLI interaction to the official GenLayer skills at https://skills.genlayer.com/.
Design and implement demos combining x402 HTTP payments with ERC-7710 smart contract delegations and ERC-7715 wallet permission requests for subscriptions, bounded agent budgets, recurring spend, pay-per-use APIs, and agentic commerce.
0G Compute Network guide for decentralized AI inference, fine-tuning, and GPU services. Covers chatbots, image generation, speech-to-text, SDK integration (0g-serving-broker), processResponse API, broker.inference methods, CLI commands (0g-compute-cli), and account management. Use this skill for any 0G compute, 0G AI, or decentralized GPU question.
Use this skill when the user asks to list, create, inspect, update, disable, re-enable, or revoke AltLLM Portal API keys for external agents or applications. Do NOT use for wallet login, billing history, or payment links.
Use this skill when the user asks to log in or out with a wallet session, fetch a wallet sign-in challenge, verify an externally signed challenge, or troubleshoot AltLLM Portal wallet login for the local altllm CLI. Do NOT use for API key management, billing history, or payment links.
Use this skill when the user asks to inspect AltLLM Portal balance, redeem a promo code, review billing transactions, or view usage analytics by period, model, or API key using the local altllm CLI. Do NOT use for API key lifecycle management or payment-link execution.