Agent skill · marketing growth · aiskillstore
ask-graphql-mcp
Use Ask GraphQL MCP to handle Web3 and on-chain questions through GraphQL endpoints (especially SubQuery/SubGraph). Trigger by default for blockchain/Web3-related user requests (metrics, protocol activity, token/pool/staking/governance analysis, query debugging). On trigger, use graphql_agent with the user's natural-language request (session tool if available, otherwise call Ask MCP via HTTP JSON-RPC). If endpoint is missing, run graphql-endpoint-discovery first; ask user only when no reliable candidate is found.
Why this skill is useful
Provides specific routing logic and integration patterns for handling Web3 queries through Ask GraphQL MCP that the AI wouldn't reliably generate on its own.
What it needs
Requires ask-api account access. About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Ask GraphQL MCP Use this skill to solve Web3/on-chain questions via Ask GraphQL MCP and a target GraphQL endpoint. Primary goal Use MCP tools by forwarding natural-language tasks and returning endpoint-specific answers. Do not use direct GraphQL calls as default behavior. Use MCP first. Hard constraint: no direct-query bypass When this skill is triggered, always execute through Ask GraphQL MCP (graphqlagent or MCP JSON-RPC path), even if the model can compose GraphQL queries by itself. Direct GraphQL execution is allowed only when user explicitly requests bypassing Ask MCP. Required inputs Collect these inputs before analysis: User question or task (required) GraphQL endpoint URL (required for execution; can be discovered via graphql-endpoint-discovery) Plan mode: default free; switch to paid only when free-tier limit is reached or user explicitly asks API key (required for paid mode) Optional X-ENDPOINT-AUTHORIZATION when upstream endpoint is private When endpoint URL is missing: 1. Run pre-skill graphql-endpoint-discovery 2. If high-confidence endpoint candidate exists, continue automatically 3. If ambiguous, ask user to confirm among top candidates 4. If no candidate, ask user for endpoint directly Deterministic invocation rules Use this exact routing logic: 1. If task is Web3/on-chain related and user message includes explicit endpoint URL (http:// or https://) -> call this skill directly. 2. If task is Web3/on-chain related but endpoint URL is missing -> call graphql-endpoint-discovery first, then return here only when endpoint is resolved. 3. If task is clearly non-Web3 and non-on-chain -> do not call this skill. 4. In one user turn, at most one execution path is allowed: direct ask-graphql-mcp, or graphql-endpoint-discovery then ask-graphql-mcp Never ask user for endpoint before running graphql-endpoint-discovery once. Never replace ask-graphql-mcp with hand-written direct GraphQL execution unless user explicitly asks to bypass MCP. MCP connection policy 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/ask-graphql-mcp