Jig Operator
Bootstrap a Jig server, wire the CLI, and deploy apps across standalone Docker, Compose, and Swarm without learning Jig internals.
Overview
jig-operator is an agent skill most often used in Operate (also Ship) that deploys and runs applications on Jig across Docker, Compose, and Swarm modes without diving into Jig internals.
Install
npx skills add https://github.com/klirix/jig --skill SKILL.mdWhat is this skill?
- Bootstrap Jig server and connect the Jig CLI end-to-end
- Prepare deployment config before first push
- Deploy apps with mode-aware flows: standalone Docker, Docker Compose, Swarm single-service, and Swarm stack
- Operate without requiring deep Jig internal knowledge
- Handles compose vs swarm topology differences in one operator workflow
- Covers four deployment modes: standalone Docker, Docker Compose, Swarm single-service, and Swarm stack
Adoption & trust: 6 GitHub stars.
What problem does it solve?
You have containerized apps but no repeatable Jig path from server bootstrap through CLI connect to mode-correct deploys.
Who is it for?
Indie builders shipping side projects or small APIs who standardized on Jig and want agent-guided deploys across common Docker topologies.
Skip if: Teams not using Jig, pure local dev without containers, or environments where you need deep custom Jig plugin development instead of operator workflows.
When should I use this skill?
User wants to deploy or operate applications with Jig, including bootstrapping server, CLI connect, deployment config, and mode-specific Docker/Compose/Swarm behavior.
What do I get? / Deliverables
After the skill runs, you have a connected Jig setup, prepared deployment config, and an app deployed in the right Docker, Compose, or Swarm mode for your environment.
- Connected Jig CLI session
- Deployment configuration aligned to target mode
- Running deployment on standalone Docker, Compose, or Swarm
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Deployment and day-two ops are the canonical home for Jig-driven releases and stack management after the app exists. Infra covers server bootstrap, deployment config, and mode-specific Docker/Swarm behavior.
Where it fits
Wire a built API image into Jig deployment config before the first production push.
Complete launch prep by deploying the release candidate via the correct Compose or Swarm mode.
Bootstrap a new Jig server and reconnect the CLI after migrating hosts.
Redeploy a stack after env or replica changes without guessing Swarm vs single-service behavior.
How it compares
Use for Jig-specific deploy orchestration instead of generic copy-paste Docker Compose snippets that ignore Swarm stack semantics.
Common Questions / FAQ
Who is jig-operator for?
Solo and indie builders who deploy with Jig on Docker or Swarm and want an agent to handle bootstrap, CLI connection, config prep, and mode-specific deploy steps.
When should I use jig-operator?
Use it in Operate when bootstrapping or redeploying on Jig; in Ship when finishing launch prep for containerized apps; and when switching between Compose and Swarm without re-learning Jig internals.
Is jig-operator safe to install?
Review the Security Audits panel on this Prism page and restrict agent shell/network permissions to hosts you control before running deploy commands.
SKILL.md
READMESKILL.md - Jig Operator
Use this when the user wants to deploy or operate applications with Jig, including bootstrapping a Jig server, connecting the Jig CLI, preparing deployment config, deploying apps, and handling mode-specific behavior for standalone Docker, Docker Compose, Swarm single-service, and Swarm stack deployments without diving into Jig internals. # jig-operator { "name": "jig-operator", "description": "Use this when the user wants to deploy or operate applications with Jig, including bootstrapping a Jig server, connecting the Jig CLI, preparing deployment config, deploying apps, and handling mode-specific behavior for standalone Docker, Docker Compose, Swarm single-service, and Swarm stack deployments without diving into Jig internals." }