subgraphs
Use this skill when the user asks about Goldsky Subgraphs — deploying, managing, or querying subgraphs. Triggers on: 'deploy a subgraph', 'migrate from The Graph', 'what is a subgraph', 'GraphQL endpoint', 'low-code or no-code subgraph', 'subgraph tags', 'subgraph webhooks', 'cross-chain subgraph', 'subgraph stalled', 'subgraph API key', 'init subgraph', 'scaffold subgraph', 'subgraph logs', 'pause subgraph', 'start subgraph', 'graft subgraph'. Also use this skill when the user wants to build a GraphQL API over onchain data, power a dApp frontend with indexed blockchain data, or reuse an existing TheGraph subgraph on Goldsky. For questions about streaming raw chain data directly to a database without GraphQL, use the turbo-builder or mirror skills instead.
- Installs
- 48
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/goldsky-io/goldsky-agent --skill subgraphs- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads subgraphs automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Goldsky Subgraphs
Subgraphs are hosted GraphQL APIs that index onchain events and expose them via a queryable endpoint. They are best for frontend applications and dApps that need flexible GraphQL queries over structured onchain data.
Could a Turbo pipeline solve this instead? If your goal is to stream raw onchain data into a database (PostgreSQL, ClickHouse, Kafka, S3) — not query via GraphQL — a Turbo pipeline is faster, cheaper, and requires no custom indexing code. Say "help me build a Turbo pipeline" and the turbo-builder skill will guide you.
When to Use Subgraphs
| Use case | Best tool |
|---|---|
| Frontend / dApp needs a GraphQL API | Subgraphs |
| Custom business logic in indexing handlers | Subgraphs |
| Migrate existing TheGraph subgraph | Subgraphs |
| Stream raw blockchain data to a database | Turbo pipelines |
| Real-time analytics in ClickHouse or Kafka | Turbo pipelines |
| Sync subgraph data into your own database | Mirror + subgraph source |
Initialize a Subgraph
Scaffold a new subgraph project locally:
goldsky subgraph init my-subgraph/1.0.0 --target-path ./my-subgraph
Key init flags
| Flag | Description |
|---|---|
--target-path <path> | Directory to write subgraph files to |
--from-config <path> | Path to instant subgraph JSON configuration file |
--abi <source> | ABI source for contract(s) |
--contract <address> | Contract address(es) to watch |
--contract-events <names> | Event names to index |
--contract-calls <names> | Call names to index |
--contract-name <name> | Name of the contract(s) |
--network <network> | Network for contract(s) — see docs for supported networks |
--start-block <block> | Block to start indexing from |
--description <text> | Subgraph description |
--call-handlers | Enable call handlers |
--build | Build the subgraph after writing files |
--deploy | Deploy the subgraph after build |
--force | Overwrite existing files at the target path |
Deploy a Subgraph
Goldsky supports multiple deployment paths:
From source (most common)
Requires a compiled subgraph in a local directory.
# Install CLI and log in
curl https://goldsky.com | sh
goldsky login
# Deploy from local build output
goldsky subgraph deploy my-subgraph/1.0.0 --path ./build
From ABI (instant subgraph)
Generate and deploy a subgraph directly from a contract ABI — no AssemblyScript needed:
goldsky subgraph deploy my-subgraph/1.0.0 --from-abi ./MyContract.json
From IPFS hash
Deploy a subgraph already published to IPFS:
goldsky subgraph deploy my-subgraph/1.0.0 --from-ipfs-hash QmXyz...
Use --ipfs-gateway <url> to specify a custom gateway (defaults to https://ipfs.network.thegraph.com).
No-code (dashboard wizard)
Use the Goldsky dashboard to deploy pre-built subgraphs for common standards (ERC-20, ERC-721, etc.) without writing code. Navigate to app.goldsky.com → Subgraphs → Create.
Migrate from The Graph
One-step migration — no code changes needed:
goldsky subgraph deploy my-subgraph/1.0.0 \
--from-url <your-thegraph-deployment-url>
See docs.goldsky.com/subgraphs/deploying-subgraphs.
Deploy flags reference
| Flag | Description |
|---|---|
--path <dir> | Path to compiled subgraph directory |
--from-url <url> | GraphQL endpoint of a publicly deployed subgraph (The Graph migration) |
--from-ipfs-hash <hash> | IPFS hash of a publicly deployed subgraph |
--from-abi <path> | Generate a subgraph from an ABI file |
--ipfs-gateway <url> | Custom IPFS gateway (default: https://ipfs.network.thegraph.com) |
--tag <tags> | Tag the subgraph after deployment (comma-separated for multiple) |
--start-block <number> | Override start block |
--graft-from <name/version> | Graft from the latest block of an existing subgraph |
--remove-graft | Remove grafts from the subgraph prior to deployment |
--enable-call-handlers | Enable call handlers (only with --from-abi) |
--description <text> | Description/notes for the subgraph |
Note:
--path,--from-url,--from-ipfs-hash, and--from-abiare mutually exclusive — use only one.
GraphQL Endpoints
Every deployed subgraph gets a public GraphQL endpoint:
https://api.goldsky.com/api/public/<project-id>/subgraphs/<name>/<version>/gn
To get your endpoint URL:
goldsky subgraph list
Public vs. private endpoints
By default endpoints are public. To control endpoint visibility:
# Disable public endpoint
goldsky subgraph update my-subgraph/1.0.0 --public-endpoint disabled
# Enable private endpoint (requires API key)
goldsky subgraph update my-subgraph/1.0.0 --private-endpoint enabled
To require an API key for private endpoints:
- Go to app.goldsky.com → Settings → API Keys and create a key.
- Add the
Authorizationheader to requests:Authorization: Bearer <your-api-key>
Subgraph Tags
Tags pin a human-readable alias (like prod) to a specific subgraph version, so your frontend URL never changes when you redeploy.
# Create or update a tag
goldsky subgraph tag create my-subgraph/1.0.0 --tag prod
# Tagged endpoint:
# https://api.goldsky.com/api/public/<project-id>/subgraphs/my-subgraph/prod/gn
# Delete a tag
goldsky subgraph tag delete my-subgraph/1.0.0 --tag prod
You can also tag at deploy time:
goldsky subgraph deploy my-subgraph/2.0.0 --path ./build --tag prod
See docs.goldsky.com/subgraphs/tags.
Webhooks
Subgraph webhooks send a payload to an HTTP endpoint on every entity change (INSERT, UPDATE, DELETE). Useful for notifications and push-based flows.
# Create a webhook
goldsky subgraph webhook create my-subgraph/1.0.0 \
--name my-webhook \
--url https://example.com/hook \
--entity Transfer \
--secret my-secret
# List all webhooks
goldsky subgraph webhook list
# List available entities for a subgraph
goldsky subgraph webhook list-entities my-subgraph/1.0.0
# Delete a webhook
goldsky subgraph webhook delete my-webhook
| Flag | Description |
|---|---|
--name <name> | Webhook name (must be unique) — required |
--url <url> | URL to send events to — required |
--entity <entity> | Subgraph entity to send events for — required |
--secret <secret> | Secret included with each webhook request |
Tip: If you need guaranteed delivery to a database, use Mirror to sync subgraph data instead of webhooks — it's more reliable.
See docs.goldsky.com/subgraphs/webhooks.
Managing Subgraphs
List subgraphs
# List all subgraphs
goldsky subgraph list
# List a specific subgraph
goldsky subgraph list my-subgraph/1.0.0
# Show only tags or deployments
goldsky subgraph list --filter tags
goldsky subgraph list --filter deployments
# Summary view
goldsky subgraph list --summary
Update a subgraph
goldsky subgraph update my-subgraph/1.0.0 \
--public-endpoint enabled \
--private-endpoint disabled \
--description "Production deployment"
| Flag | Values | Description |
|---|---|---|
--public-endpoint | enabled / disabled | Toggle public endpoint visibility |
--private-endpoint | enabled / disabled | Toggle private endpoint (requires API key) |
--description | text | Description/notes for the subgraph |
Pause and resume
# Pause a subgraph (stops indexing)
goldsky subgraph pause my-subgraph/1.0.0
# Resume a paused subgraph
goldsky subgraph start my-subgraph/1.0.0
Delete a subgraph
goldsky subgraph delete my-subgraph/1.0.0
# Skip confirmation prompt
goldsky subgraph delete my-subgraph/1.0.0 --force
Logs and Debugging
Tail a subgraph's logs to diagnose issues:
# View recent logs
goldsky subgraph log my-subgraph/1.0.0
# Logs from the last hour, errors only
goldsky subgraph log my-subgraph/1.0.0 --since 1h --filter error
# JSON format for parsing
goldsky subgraph log my-subgraph/1.0.0 --format json
| Flag | Default | Description |
|---|---|---|
--since <duration> | 1m | Show logs newer than duration (e.g. 5s, 2m, 3h) |
--format <format> | text | Output format: pretty, json, or text |
--filter <level> | info | Minimum log level: error, warn, info, debug |
--levels <levels> | — | Explicit comma-separated log levels to include |
--interval <seconds> | 5 | Seconds between log checks |
Stalled subgraphs
If a subgraph stops progressing, Goldsky auto-pauses it and sends an email notification. To diagnose:
- Check logs:
goldsky subgraph log my-subgraph/1.0.0 --since 1h --filter error - Look for handler errors, RPC timeouts, or out-of-memory issues
- Fix the issue and redeploy, or contact support@goldsky.com
Cross-Chain Subgraphs
To index the same contract across multiple chains, deploy separate subgraphs per chain, then use a Mirror pipeline to merge them into one database table.
See docs.goldsky.com/subgraphs/introduction.
CLI Command Reference
| Action | Command |
|---|---|
| Initialize subgraph | goldsky subgraph init <name/version> |
| Deploy from source | goldsky subgraph deploy <name/version> --path . |
| Deploy from The Graph | goldsky subgraph deploy <name/version> --from-url <url> |
| Deploy from ABI | goldsky subgraph deploy <name/version> --from-abi <path> |
| Deploy from IPFS | goldsky subgraph deploy <name/version> --from-ipfs-hash <hash> |
| List subgraphs | goldsky subgraph list |
| Delete subgraph | goldsky subgraph delete <name/version> |
| Pause subgraph | goldsky subgraph pause <name/version> |
| Start subgraph | goldsky subgraph start <name/version> |
| Update subgraph | goldsky subgraph update <name/version> --public-endpoint enabled |
| Tail logs | goldsky subgraph log <name/version> |
| Create tag | goldsky subgraph tag create <name/version> --tag <tag> |
| Delete tag | goldsky subgraph tag delete <name/version> --tag <tag> |
| Create webhook | goldsky subgraph webhook create <name/version> --name <n> --url <u> --entity <e> |
| List webhooks | goldsky subgraph webhook list |
| Delete webhook | goldsky subgraph webhook delete <webhook-name> |
| List webhook entities | goldsky subgraph webhook list-entities <name/version> |
Related
/turbo-builder— Build a streaming pipeline to a database instead of a GraphQL API- Goldsky docs: docs.goldsky.com/subgraphs/introduction
FAQ
What does the subgraphs skill do?
Use this skill when the user asks about Goldsky Subgraphs — deploying, managing, or querying subgraphs. Triggers on: 'deploy a subgraph', 'migrate from The Graph', 'what is a subgraph', 'GraphQL endpoint', 'low-code or no-code subgraph', 'subgraph tags', 'subgraph webhooks', 'cross-chain subgraph', 'subgraph stalled', 'subgraph API key', 'init subgraph', 'scaffold subgraph', 'subgraph logs', 'pause subgraph', 'start subgraph', 'graft subgraph'. Also use this skill when the user wants to build a GraphQL API over onchain data, power a dApp frontend with indexed blockchain data, or reuse an existing TheGraph subgraph on Goldsky. For questions about streaming raw chain data directly to a database without GraphQL, use the turbo-builder or mirror skills instead.
How do I install subgraphs?
Run npx skills add https://github.com/goldsky-io/goldsky-agent --skill subgraphs in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/subgraphs/ (personal) or .claude/skills/subgraphs/ (project).
Which AI agents can use subgraphs?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is subgraphs safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains subgraphs?
It is published by goldsky-io in goldsky-io/goldsky-agent. It has 48 recorded installs.
More from goldsky-io/goldsky-agent
turbo-pipelines
goldsky-io/goldsky-agent
Turbo pipeline YAML reference and architecture guide. Covers: YAML field syntax (startat, from, version, primarykey), source/transform/sink configuration, validation errors, resource sizing (xs–xxl), architecture decisions (dataset vs kafka, streaming vs job, fan-out vs fan-in, sink selection, pipeline splitting). Triggers on: 'what does field X do', 'what fields does a postgres sink need', 'what resource size', 'should I use kafka or dataset', 'how to structure my pipeline'. For writing transforms, use /turbo-transforms. For end-to-end building, use /turbo-builder.
turbo-transforms
goldsky-io/goldsky-agent
Write SQL, TypeScript, and dynamic table transforms for Turbo pipelines. Covers: decoding EVM logs with gslogdecode, filtering/casting blockchain data, UNION ALL for combining events, TypeScript/WASM transforms (invoke function), dynamic lookup tables (dynamictablecheck), transform chaining, and Solana decoding. Triggers on: 'decode Transfer events', 'write a SQL transform', 'filter by contract', 'TypeScript transform', 'dynamic table', 'UNION ALL'. For pipeline YAML structure, use /turbo-pipelines. For end-to-end building, use /turbo-builder.
turbo-doctor
goldsky-io/goldsky-agent
Diagnose and fix broken Goldsky Turbo pipelines interactively. Triggers on: pipeline in error state, stuck starting, connection refused, not getting data, duplicate rows, missing fields, slow backfill, or any named pipeline misbehaving. Runs logs/status commands, identifies root cause, and offers fixes. For CLI syntax or error pattern lookup without an active problem, use /turbo-operations instead.
turbo-builder
goldsky-io/goldsky-agent
Build and deploy new Goldsky Turbo pipelines: requirements, dataset selection, YAML, validation, and deployment. Use for 'build a pipeline', 'index X on Y chain', or moving chain/contract data into Postgres, MySQL, ClickHouse, Kafka, Pub/Sub, S3, SQS, or webhooks. Also use for data goals such as Polymarket fills/positions/PnL, prediction markets, stablecoin or circulating supply, proof of reserves, sanctions/AML transfer monitoring, deposit detection, CCTP burns/mints, cross-chain settlement, payment reconciliation, wallet history streamed into the user's own database, token holder registries, tokenized equities/RWA, and wash-trading detection. A REST lookup of one wallet's balances or transfers is /feeds, not a pipeline, and so is a read of Polymarket activity, positions or balances. Debug existing pipelines with /turbo-doctor; look up syntax with /turbo-pipelines.
datasets
goldsky-io/goldsky-agent
Use this skill when the user needs to look up or verify Goldsky blockchain dataset names, chain prefixes, dataset types, or versions. Triggers on questions like 'what\'s the dataset name for X?', 'what prefix does Goldsky use for chain Y?', 'what version should I use for Z?', or 'what datasets are available for Solana/Stellar/Arbitrum/etc?'. Also use for chain-specific dataset questions (e.g., polygon vs matic prefix, stellarnet balance datasets, solana token transfer dataset names), and to answer 'is there a dataset for X?' where X is a domain rather than a chain — decoded logs, token transfers and balances, mint/burn events for circulating supply, DEX or prediction-market activity (Polymarket), or the raw blocks, transactions and traces behind wallet history and reconciliation. Do NOT trigger for questions about CLI commands, pipeline setup, or general Goldsky architecture unless the core question is about finding the right dataset name or chain prefix. Wallet Feeds API queries are /
auth-setup
goldsky-io/goldsky-agent
Set up Goldsky CLI authentication and project configuration. Use this skill when the user needs to: install the goldsky CLI (what's the official install command?), run goldsky login (including when the browser opens but 'authentication failed'), run goldsky project list and see 'not logged in' or 'unauthorized', switch between Goldsky projects, check which project they're currently authenticated to, or fix 'unauthorized' errors when running goldsky turbo commands. Also use for 'walk me through setting up goldsky CLI from scratch for the first time', and when they just installed Goldsky and say 'Set it up and help me get started'. If any other Goldsky skill hits an auth error, redirect here first.
Popular backend & apis skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
entra-app-registration
microsoft/azure-skills
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.
google-agents-cli-adk-code
google/agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).
embedded-captions
heygen-com/hyperframes
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
entra-agent-id
microsoft/azure-skills
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).
neon
neondatabase/agent-skills
Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.