ask-graphql-mcp
- Repo stars 0
- Author repo skills-registry
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 (graphql_agent 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 topaidonly when free-tier limit is reached or user explicitly asks - API key (required for paid mode)
- Optional
X-ENDPOINT-AUTHORIZATIONwhen upstream endpoint is private
When endpoint URL is missing:
- Run pre-skill
graphql-endpoint-discovery - If high-confidence endpoint candidate exists, continue automatically
- If ambiguous, ask user to confirm among top candidates
- If no candidate, ask user for endpoint directly
Deterministic invocation rules
Use this exact routing logic:
- If task is Web3/on-chain related and user message includes explicit endpoint URL (
http://orhttps://) -> call this skill directly. - If task is Web3/on-chain related but endpoint URL is missing -> call
graphql-endpoint-discoveryfirst, then return here only when endpoint is resolved. - If task is clearly non-Web3 and non-on-chain -> do not call this skill.
- In one user turn, at most one execution path is allowed:
- direct
ask-graphql-mcp, or graphql-endpoint-discoverythenask-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
- Default to free gateway:
https://ask-api.hermes-subnet.ai/mcp/graphql-agent - Use paid gateway only when needed:
https://ask-api.hermes-subnet.ai/mcp - Always set
X-ENDPOINTto the user endpoint - Set
X-ENDPOINT-AUTHORIZATIONonly when upstream endpoint requires auth - In paid mode, include
X-API-KEY
Use templates from references/config-templates.md when you need to emit copy-ready JSON.
Agent execution workflow
- Confirm endpoint and user objective. If endpoint is missing, run
graphql-endpoint-discoveryfirst. - Prefer session tool path: if
graphql_agentis available in current session tool list, use it. - If session tool is unavailable, use HTTP JSON-RPC path to Ask MCP gateway with required headers (
X-ENDPOINT, optionalX-ENDPOINT-AUTHORIZATION, andX-API-KEYin paid mode). - Send the user task to MCP in natural language.
- Timeout policy: when question complexity is high, allow MCP/agent call timeout up to 2 minutes (120s) before treating it as failed.
- If needed, send one follow-up clarification prompt to MCP.
- Return MCP result with concise interpretation for the user.
HTTP JSON-RPC path (when session tool is unavailable)
Use MCP gateway endpoint:
- Free:
https://ask-api.hermes-subnet.ai/mcp/graphql-agent - Paid:
https://ask-api.hermes-subnet.ai/mcp
Call sequence:
tools/listto verifygraphql_agentis exposed by gatewaytools/callwith:
name: "graphql_agent"arguments.question: <user natural-language request>
This path still uses MCP, not direct GraphQL querying.
Fallback workflow
If the task fails:
- Validate gateway URL matches current mode (free/paid).
- Validate
X-ENDPOINTformat and reachability. - Validate
X-ENDPOINT-AUTHORIZATIONfor private endpoints. - Validate
X-API-KEYin paid mode. - Retry with minimal known-good config.
If MCP returns free-tier rate limit/quota errors:
- Guide user to create API key at
https://ask.hermes-subnet.ai/billing/api-keys/ - Switch user to paid gateway
https://ask-api.hermes-subnet.ai/mcpwithX-API-KEY - Explicitly ask user to provide API key now so execution can continue immediately
- Provide a copy-ready paid config snippet with
X-API-KEYplaceholder in the same response - Do not end with only "retry later" or "wait for reset"; API key request must come first
If paid API key quota is exceeded:
- Guide user to check usage/quota at
https://ask.hermes-subnet.ai/billing/
Response standard
For endpoint analysis requests, structure responses as:
- Assumptions
- MCP answer summary
- Optional query/details provided by MCP
- Next step (run/verify/debug)
For pure setup requests, provide one copy-ready JSON block plus a short verification checklist.
When mentioning quota/rate-limit failures, always include the correct billing link:
- API key creation:
https://ask.hermes-subnet.ai/billing/api-keys/ - Usage/quota check:
https://ask.hermes-subnet.ai/billing/
For free-tier limit errors, treat API key guidance as highest-priority next action:
- First line should clearly request API key from user
- Include API key creation link in the same message
- Include paid-mode gateway and required header keys
Rate-limit detection and mandatory wording
Treat these as free-tier limit signals:
rate limit exceededquota exceededtoo many requestsretryAfter429
When any signal appears, reply with this mandatory first sentence pattern:
Free quota reached. Please create an API key at https://ask.hermes-subnet.ai/billing/api-keys/ and send it here so I can continue now.
Then include:
- Paid gateway URL:
https://ask-api.hermes-subnet.ai/mcp - Required paid header:
X-API-KEY - If relevant, quota page:
https://ask.hermes-subnet.ai/billing/
For practical prompt patterns, read references/tools-and-prompts.md.
<!-- tomevault:4.0:skill_md:2026-05-22 -->Source: ComeOnOliver/skillshub — distributed by TomeVault.
- Fluxly category
- AI
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Author / version / license
- @tomevault-io · no license declared
- Fluxly token estimate
- Lean
- Fluxly setup estimate
- Guided setup
- External API key
- Required · Vendor-specific
- Detected OS requirements
- Unspecified
- Runtime requirements
- Unspecified
- Detected file/system behavior
-
- Read-only
- Write / modify
- Shell exec
- Detected network behavior
- External requests
- Install commands
- None (reference only)
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
The current SKILL.md does not define a fixed output example. Confirm endpoint and user objective. If endpoint is missing, run graphql-endpoint-discovery first. Prefer session tool path: if graphqlagent is available in current session tool list, use it. If session tool is unavailable, use HTTP JSON-RPC path to Ask MCP…
If the task fails: Validate gateway URL matches current mode (free/paid). Validate X-ENDPOINT format and reachability.
# 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 (`graphql_agent` 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
… Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.
sections -> Primary goal → Hard constraint: no direct-query bypass → Required inputs → Deterministic invocation rules → MCP connection policy → Agent execution workflow
terms -> Use this skill to solve Web3/on-chain questions via Ask GraphQL MCP and a target GraphQL endpoint. · Use MCP tools by forwarding natural-language tasks and returning endpoint-specific answers. · Do not use direct GraphQL calls as default behavior. · Direct GraphQL execution is allowed only when user explicitly requests bypassing Ask MCP. · When endpoint URL is missing: 1. · Use this exact routing logic: 1. · Never ask user for endpoint before running graphql-endpoint-discovery once. · 1. Default to free gateway: https://ask-api.hermes-subnet.ai/mcp/graphql-agent 2.
files/cmd -> graphqlagent · graphql-endpoint-discovery · free · paid · X-ENDPOINT-AUTHORIZATION · http:// · https:// · ask-graphql-mcp
body sha256 -> d55a429c1838
Decide Fit First
Design Intent
How To Use It
Boundaries And Review