25 tagged deployment platform, measured the same way as everything else here.
Browse within: ci-cd 15docker 15error-tracking 15full-stack 7
Skill Claude CodeCodex
Start (or restart) a local multi-node Temps cluster using Docker-in-Docker — one control plane + 3 worker nodes, each a privileged DinD container running its own dockerd + temps agent, wired with the real multi-host overlay (VXLAN, computecidr allocation) via tools/dev-cluster/ in whichever checkout/worktree you run…
Skill Claude CodeCodex
Add Temps error tracking to applications using the Sentry-compatible SDK. Temps exposes a Sentry-compatible DSN that works with the official Sentry SDK for each language/framework — no code changes beyond initialization are required. Use when the user wants to: (1) Add error tracking to any app (React, Next.js, Vue…
Skill Claude CodeCodex
Build external plugins for the Temps deployment platform. Use when the user wants to create, modify, or debug a Temps plugin binary — a standalone Rust process that communicates with Temps over a Unix domain socket. Also use when the user mentions "temps plugin", "external plugin", "plugin binary", "plugin for temps"…
Skill Claude CodeCodex
Publish a stoop site over HTTP with an API key, from a server-side app, agent, or CI job that has no folder and no terminal. Use when code you are writing needs to publish or revise a web page at runtime — a bot posting a report, a job publishing a dashboard. If you have the files on disk and a terminal, use stoop…
Skill Claude CodeCodex
The stoop platform SDK reference: platform.db, identity, ai, files, channel, and the served house-style theme. Load before writing any platform. call in a stoop site, whichever way the site is published.
Skill Claude CodeCodex
Deploy a static site to stoop from a folder using the stoop CLI. Use when you have the site's files on disk and a terminal: creating, changing, deploying, or debugging a stoop site, or shipping a quick prototype or demo. If you are a server-side app or agent publishing at runtime with no folder and no terminal, use…
Skill Claude CodeCodex
This skill should be used when the user asks to "build an app on OBTO", "create an OBTO app", "scaffold an app", "add a page/route/script to my OBTO app", or any task that creates or modifies OBTO application artifacts. Covers the stateless contract, the reliability-first build loop, and the done-means-done smoke gate.
Skill Claude CodeCodex
This skill should be used when the user asks to "deploy to OBTO", "upload a large file/module to OBTO", "ship this artifact", "push this script to the platform", or when any single artifact source is too large for one tool call. Covers deployment order, choosing the write path (patch vs. upsert vs. chunked vs.…
Skill Claude CodeCodex
This skill should be used when the user reports an OBTO error, asks "why did this OBTO call fail", mentions errors like collectionnotinallowlist, must pass appName/domain, hostmismatch, scopeownershipmismatch, stale tools, or wants to debug an OBTO app via logs. Covers the structured error envelope and the standard…