tempoxyz

Interact with authenticated private Tempo Zone RPC endpoints, derive X-Authorization-Token zone auth tokens, identify zone IDs and chain IDs from ZoneFactory or repo metadata, and debug 401/403 auth failures. Use when calling rpc-zone-*-private endpoints, web3_clientVersion, eth_chainId, zone_getZoneInfo, or any private zone JSON-RPC method that needs a zone auth token.

Deploy a fresh ZoneFactory contract to Moderato Tempo L1 after ABI or implementation-breaking changes, verify the deployment, and update repo constants and docs.

Deploy Tempo Zones, start zone nodes, validate router swap-and-deposit flows, and debug zone sync, portal ingestion, withdrawal, sequencer key, and generated zone artifact issues in this repository. Use when working with just deploy-zone, zone-up, deploy-router, demo-swap-and-deposit, or generated/<name>/zone.json.

Answer Tempo blockchain questions using official documentation. Use when asked about Tempo protocol, TIP-20 tokens, fees, transactions, stablecoin DEX, or any Tempo-related questions.

Use this skill when building applications on Tempo, integrating Tempo into an app, writing or reviewing Tempo code, or answering Tempo developer questions about accounts, wallets, passkeys, stablecoin payments, fee sponsorship, MPP, hosted services, indexer queries, stablecoin issuance, the Stablecoin DEX, contract verification, SDKs, or Tempo protocol concepts. For agent wallet setup, service discovery, or paid HTTP requests, use the tempo-wallet skill.

Use this skill when the user wants to call an API, make an HTTP request, discover available services, set up Tempo Wallet, manage balances, or access external data with automatic payments.

Set up and run tidx to index Tempo blockchain data. Covers installation, configuration, deployment (Docker, bare metal), PostgreSQL + ClickHouse setup, sync architecture, monitoring, and operational best practices. Use when deploying or operating a tidx indexer.

Query indexed Tempo chain data via tidx HTTP API and CLI. Covers SQL queries for blocks, txs, logs, receipts, event CTE decoding, engine routing (PostgreSQL OLTP vs ClickHouse OLAP), live streaming. Use when querying Tempo chain data or working with tidx.

TypeScript SDK for the Payment HTTP Authentication Scheme. Handles 402 Payment Required flows with Tempo, Stripe, and other payment methods. Use when integrating payments or mppx into a client or server application.

TypeScript SDK for the Payment HTTP Authentication Scheme. Handles 402 Payment Required flows with Tempo, Stripe, and other payment methods. Use when integrating payments or mppx into a client or server application.

Build, launch, and drive the Tempo explorer app to verify changes end-to-end. Use when verifying explorer changes at runtime (SSR meta tags, API routes, pages).

Reviews and critiques IETF Internet-Drafts and RFC submissions for style compliance, technical clarity, prior art gaps, and publication readiness. Use when analyzing existing drafts or providing editorial feedback.

Use this skill when a user wants to set up, initialize, operate, or troubleshoot schelk: a Linux-only CLI for repeatable benchmarking on large stateful datasets using a virgin block device, a scratch block device, and dm-era metadata on a ramdisk. Use it for installation, prerequisite checks, init-new, init-from, mount, recover, promote, full-recover, status, and crash or reboot recovery.

Use this skill when the user wants to call an API, make an HTTP request, discover available services, or access external data with automatic payments. Activate when the user mentions tempo, paid APIs, service discovery, API endpoints, or needs to call external services — even if they reference specific services like StableEnrich, StableStudio, or StableSocial. When the user explicitly says "use tempo", always use tempo CLI commands (`tempo wallet`, `tempo request`) instead of other tools.

Builds applications on Tempo network using TypeScript SDK, Rust node, and Foundry. Use when working with Tempo transactions, TIP-20 tokens, stablecoins, or Tempo protocol integration.

Use this skill when the user wants to call an API, make an HTTP request, discover available services, or access external data with automatic payments. Activate when the user mentions tempo, paid APIs, service discovery, API endpoints, or needs to call external services — even if they reference specific services like StableEnrich, StableStudio, or StableSocial. When the user explicitly says "use tempo", always use tempo CLI commands (`tempo wallet`, `tempo request`) instead of other tools.

Export funds with a Tempo export key (access key) to a recipient address. Use when asked to export, withdraw, or sweep tokens from Tempo.