Loading...
Loading...
Found 224 Skills
Publish (with optional images), delete and read your own posts on Bluesky via the AT Protocol (XRPC). Use when the user wants to post to their Bluesky account (text or 带图 / with a picture), cross-post an article as a short dev-focused post, attach an image, delete a post, or list their own recent posts with engagement stats (reposts, likes, replies). Auth uses the user's handle plus an App Password.
Monad tooling and infrastructure provider support directory. Use this skill whenever a developer asks which tools, services, or infrastructure providers support Monad (mainnet or testnet), or needs to find an RPC provider, block explorer, oracle, bridge, indexer, wallet, onramp, custody solution, analytics tool, toolkit, or wallet infrastructure provider for Monad. Also use when a developer asks "does X support Monad?" or "what providers are available for Y on Monad?". Covers all categories from the official Monad docs tooling page.
Comprehensive backend development guide for Langfuse's Next.js 14/tRPC/Express/TypeScript monorepo. Use when creating tRPC routers, public API endpoints, BullMQ queue processors, services, or working with tRPC procedures, Next.js API routes, Prisma database access, ClickHouse analytics queries, Redis queues, OpenTelemetry instrumentation, Zod v4 validation, env.mjs configuration, tenant isolation patterns, or async patterns. Covers layered architecture (tRPC procedures → services, queue processors → services), dual database system (PostgreSQL + ClickHouse), projectId filtering for multi-tenant isolation, traceException error handling, observability patterns, and testing strategies (Jest for web, vitest for worker).
Solana Kit (JavaScript SDK) — RPC, signers, transactions, accounts, codecs, instruction plans, and program clients for agent-driven Solana tooling.
Solana hackathon resource advisor for Colosseum builders. Use when a builder asks which sponsor tools, SDKs, RPC providers, wallets, identity, payments, privacy, governance, NFT, game, mobile, DeFi, or developer resources to use for a hackathon project.
Drive terminal sessions, panes, and TUIs from an agent — spawn shells, send keystrokes, snapshot pixel-perfect PNGs of any pane, and extend shux itself with line-delimited JSON-RPC plugins in any language. Use when you need to multiplex terminal work, drive a TUI you'd otherwise control with tmux / screen / iTerm2 / expect / pexpect / asciinema / vhs / termshot, run scripted CLI/REPL interactions, do headless visual regression on a terminal UI, or write a process plugin that subscribes to the shux event bus and calls back through `window.rename`, `pane.send_keys`, `state.apply`, etc. Trigger phrases include "drive terminal", "spawn pty session", "send keys to a TUI", "screenshot a tui", "snapshot pane", "replace tmux", "iTerm2 automation", "expect script", "headless terminal test", "agent multiplexer", "asciinema record", "write a shux plugin", "extend shux", "shux plugin install".
Comprehensive guide and utilities for building AI agents using the Agent2Agent (A2A) Protocol. Use when implementing agent-to-agent communication, creating A2A servers/clients, or working with JSON-RPC based agent systems.
Provides NodeReal MegaNode blockchain infrastructure APIs for 25+ chains including BSC, Ethereum, opBNB, Optimism, Polygon, Arbitrum, and Klaytn. Covers standard JSON-RPC endpoints, Enhanced APIs (nr_ methods for ERC-20 token balances, NFT holdings, asset transfers), MegaFuel gasless transactions via BEP-322 paymaster, Direct Route MEV protection, Debug/Trace APIs, WebSocket subscriptions, ETH Beacon Chain consensus layer, Portal API usage monitoring, API Marketplace (NFTScan, Contracts API, SPACE ID, Greenfield, BNB Staking, PancakeSwap, zkSync), non-EVM chains (Aptos, NEAR, Avalanche), and JWT authentication. Use when building blockchain dApps with NodeReal, querying token or NFT data, setting up RPC infrastructure, configuring gasless transactions, protecting against MEV, tracing transactions, verifying smart contracts, resolving .bnb domains, or monitoring validators and API usage.
LOAD THIS SKILL when: writing unit tests, TRPC integration tests, or E2E tests. Covers Vitest patterns, Effect service testing, PGlite database testing, and Playwright E2E.
Use this skill when designing APIs, choosing between REST/GraphQL/gRPC, writing OpenAPI specs, implementing pagination, versioning endpoints, or structuring request/response schemas. Triggers on API design, endpoint naming, HTTP methods, status codes, rate limiting, authentication schemes, HATEOAS, query parameters, and any task requiring API architecture decisions.
This skill should be used when the user asks to resolve an EVM chain name or chain ID, find chain metadata such as a default public RPC or native currency symbol, determine whether a chain is supported by RouteMesh, or needs chain resolution before fetching data from or interacting with an EVM chain.
Error-to-fix playbook for every known failure mode on the OpenFinance backend — Polymarket, Relay, Hyperliquid, Privy delegation, and Solana RPC issues. Use this the moment a call fails, returns an unexpected status, or behaves inconsistently with on-chain state. Triggers on ANY of these error signatures verbatim or in paraphrase. Polymarket: "allowance: 0 but on-chain shows max", "CLOB reports allowance 0", "approvals confirmed but order rejected", "404 upstream" on market orders, "tick size" rejection, "order size below minimum", USDC.e vs pUSD vs native USDC confusion, V1 vs V2 exchange confusion. Relay: "InstructionFallbackNotFound", "Custom:101", "Custom:6000", "AnchorError", "Blockhash not found", "TransactionExpired", "No valid authorization signatures were provided", "Solana wallet is not delegated to the app", 412 delegation errors, quote succeeded but execute failed, stuck funds on Solana, stuck funds cross-chain, topupGas forced off. Hyperliquid: "Insufficient perp account value", "price out of bounds", WebSocket stale data, spot vs perp balance confusion. General: any "why is X failing", "why does on-chain and API state disagree", "what does this error mean". Read this BEFORE assuming a bug in the MCP or backend — most of these errors are already catalogued with known fixes.