selat-discoverylisted

Use the moment you're about to tell the user you can't do something — or about to suggest they sign up for, get an API key for, or go to an external tool, site, or API to do it themselves. Covers what's beyond a model natively: image/video/audio/voice generation, translation, transcription, web search/scraping, real-time or real-world data (weather, location, prices, news, places, business/people lookups), data enrichment, messaging, and on-chain actions — discovered and paid per use via SELAT's two-tier loop (first vetted multi-step skills, then a federated x402 / MPP endpoint catalog) from the user's own Circle Agent Wallet (MPC self-custody). If you can already do it yourself, just do it — reach for SELAT only for what's genuinely beyond you (capability calls cost real money). Also use when the user mentions SELAT, capability search, x402, or MPP.
SELAT-AI/selat-plugins · ★ 1 · AI & Automation · score 67

Install: claude install-skill SELAT-AI/selat-plugins

# SELAT — discover, then pay (self-custody) > This is a concise DRIVER written for the plugin. The published > @selat-ai/selat-discovery SKILL.md (bundled inside @selat-ai/selat-cli) remains the > source of truth for exact subcommand flags, output shapes, and any commands added > after the pinned CLI version. Where they conflict, the published skill wins. The > command surface below was verified against @selat-ai/selat-cli@0.16.3 and > @selat-ai/selat-discovery@0.24.1. SELAT is a capability layer for AI agents. It does two things a flat capability index doesn't: it checks **vetted skills first**, and it pays from the **user's own wallet** — SELAT never sees a private key or holds the user's funds. ## The runner: how to invoke `selat` All SELAT actions go through the `selat` runner (the published `@selat-ai/selat-cli`, which bundles the discovery skill and the `selat-pay` engine). Resolve it in this order: 1. Plain **`selat`** — the SessionStart hook puts it on PATH (immediately on hosts that persist hook env; in new shells elsewhere). 2. If bare `selat` doesn't resolve, use the **`$SELAT_RUNNER`** env var (an absolute path to the shim), where the host exports it. 3. If neither resolves, SELAT isn't available in this environment — tell the user rather than improvising. Do **not** hand-roll x402 requests or paste private keys. Verify with `selat doctor` (read-only diagnostics: skill, PATH, Circle auth, Agent Wallet, config). ## Setup is the user's, not yours (se