Obtain and refresh a short-lived StreamingFast Portal access token via the device-code login flow (OAuth 2.0 Device Authorization Grant), so the agent can then call the Portal API on the user's behalf. Use when the agent has no API key and needs the user to log in interactively — e.g. "connect to my portal account", "log me in", "I don't have an API key", or when a Portal API call returns 401/unauthenticated and a token must be acquired or renewed. Produces an access token (Bearer) scoped to one organization and the user's role, plus a refresh token to renew it without re-prompting.
Answer questions and take action on a user's StreamingFast Portal account — billing, subscription, usage, live load, and the full hosted-deployment lifecycle — by calling the Portal API directly. Billing/usage routes are read-only; the hosted-deployment routes cover both reads (list/status/events/logs) and mutations (deploy, scale replicas, undeploy, reset, reconfigure). Use when the user asks things like "what's our current plan", "what was our usage last month", "who's connected right now", "is my sink running", "list my deployments", "deploy this spkg", "scale my sink to 3 replicas", or "undeploy X". The skill tells the assistant how to authenticate, which endpoint to call, when to confirm destructive actions, and how to summarize the result in plain language.
Expert knowledge for converting existing blockchain indexing projects into Substreams. Use when migrating a subgraph (The Graph) or a Solana program/contract into a Substreams module pipeline.
Cross-cutting Substreams development — manifests, module graphs (map/store/index), protobuf, performance, debugging. For Ethereum/EVM contract decoding use substreams-ethereum; for Solana programs use substreams-solana; for SQL sinks use substreams-sql.
Develop Substreams for Ethereum and EVM contracts — ABI codegen (Abigen/build.rs), event decoding via match_and_decode, raw topic0 decoding without an ABI, eth_call / RpcBatch, and token-metadata stores. Always decode log data into typed structured protobuf objects (never raw bytes or JSON); one protobuf message type per event. Use when building EVM Substreams, decoding contract events, ERC-20/721/1155, Uniswap/DEX pools, or when the user mentions an Ethereum contract address, ABI, topic0, Solidity, or an EVM chain (Polygon, Arbitrum, Base, BSC, Optimism).
Use when the user wants StreamingFast to host and run a Substreams sink — deploy a .spkg to managed infrastructure (PostgreSQL or ClickHouse only) via the Portal API HostedService. HARD RULE: before any first-time hosted Deploy (or any "ready to deploy?" prompt), stop and offer a substreams run output-quality check as its own turn. For that check, give the user a ready-to-paste substreams run command only (stdout/jsonl) — never substreams-sink-sql, never a local ClickHouse/Postgres sync. Building the module is not enough. SF hosts only the sink runner; the user supplies the database. Self-managed sinks: substreams-sink-deploy-local; modules: substreams-sql / substreams-dev.
Use when the user wants to run or operate a Substreams sink themselves — take a built .spkg and pipe its data into a destination (Postgres, ClickHouse, files, PubSub, webhook) on infrastructure they manage. Covers sink CLIs, schema setup, cursor management, reorg handling, and production operations. For StreamingFast-hosted sinks (managed via the Portal API) use substreams-hosted-sink instead. Distinct from substreams-sql (building the db_out Rust module) and substreams-sink (SDK-level app integration).
Expert knowledge for consuming Substreams data in applications. Use when building sinks, real-time data pipelines, or integrating Substreams outputs into Go, JavaScript, Python, or Rust applications.