tdsk-cli

Orchestrates Docker, Kubernetes, and DevSpace operations for the Threaded Stack monorepo.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/threadedstack/threadedstack --skill tdsk-cli-threadedstack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdsk-cli
Source: https://github.com/threadedstack/threadedstack/tree/main/.claude/skills/tdsk-cli
Command: npx skills add https://github.com/threadedstack/threadedstack --skill tdsk-cli-threadedstack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing a multi-service monorepo requires juggling Docker builds, Kubernetes secrets, DevSpace environments, and database migrations across many contexts. This Skill provides the knowledge base for the @tdsk/cli developer CLI, which unifies all of these DevOps operations under one hierarchical command interface. ## Core Features & Use Cases - Docker & Kubernetes Orchestration: Build, push, and run container images across six contexts (app, proxy, backend, admin, caddy, sandbox), manage K8s secrets with 7 presets, and inspect pods. - DevSpace & Database Workflows: Start, clean, and debug development environments, plus run migrations, seeds, and Drizzle Studio through nested task commands. - Fleet Toggle: Turn the autonomous AI agent fleet on or off with a single command that delegates to the database repo's toggleFleet script. - Use Case: A developer needs to build a sandbox image variant and deploy secrets to production. They run pnpm tdsk docker build --context sandbox --type claude followed by pnpm tdsk kube secret docker --env prod --namespace production. ## Quick Start Ask the assistant to build the proxy Docker image with a specific tag using the tdsk CLI.

Frequently Asked Questions about tdsk-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a Docker image for a specific service in the monorepo?▼

Run pnpm tdsk docker build with the --context flag targeting one of six contexts: app, proxy, backend, admin, caddy, or sandbox. Aliases like px, be, ad, cd, and sb resolve via the ECtxMap, and you can add --tag to version the image.

How do I create Kubernetes secrets with the tdsk CLI?▼

Use pnpm tdsk kube secret followed by a preset name: tdsk, docker, database, payments, email, or egress. The egress preset generates a self-signed CA certificate via OpenSSL, and you can target environments with --env and --namespace options.

What are sandbox image variants and how do I build them?▼

Sandbox variants are alternate image types for the sandbox context. When you pass --context sandbox with --type (e.g., claude or codex), getCtx() replaces the -base suffix in the image name with -<type>, producing images like image-claude.

Does tdsk fleet off persist after a new deployment?▼

No. The fleet off state is live database and workflow state, so running a full tdsk release re-reconciles the fleet back on. You must re-run tdsk fleet off after any deploy while the fleet should stay down.

Why does context resolution fail when running docker commands?▼

getCtx() validates that the context exists in cli.config.ts and that its directory exists on disk. Failures occur when using an unrecognized context name or alias, or when the repository path configured for that context is missing.