orkestra-docker

Manage Docker containers and diagnose multi-stack environments using label-based detection.

1|1|Updated Dec 20, 2025
One-click install
npx skills add https://github.com/orkestra-cc/orkestra --skill orkestra-docker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orkestra-docker
Source: https://github.com/orkestra-cc/orkestra/tree/main/.claude/skills/orkestra-docker
Command: npx skills add https://github.com/orkestra-cc/orkestra --skill orkestra-docker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the complexity of managing multiple concurrent Docker stacks by providing reliable, label-based detection of services, containers, and their associated compose configurations.

Core Features & Use Cases

  • Authoritative Detection: Identifies the correct compose files and stack identity for any running container using Docker labels rather than unreliable environment variables.
  • Targeted Operations: Enables safe, per-service lifecycle management including logs, restarts, and force-rebuilds without disrupting the entire stack.
  • Use Case: When a Go backend binary lags behind code changes due to file system watcher issues, use this skill to perform a targeted container-internal build and restart to restore development velocity.

Quick Start

Run the detection command to identify the correct stack and service names before executing any docker compose operations.

Frequently Asked Questions about orkestra-docker

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

FAQPage Schema
How do I identify the correct Docker compose file for a running container in a multi-stack environment?

You can identify the correct Docker compose file by inspecting Docker labels on the running container. This skill uses label-based detection to reliably map running containers to their specific stack identity and compose configuration.

How do I restart a single service in a Docker compose stack without disrupting the entire environment?

You can restart a single service by executing targeted lifecycle management commands based on stack-namespaced container labels. This skill enables safe, per-service operations like restarts without bringing down the entire stack.

Why does my Go backend container lag behind code changes during local development?

Your Go backend container may lag due to file system watcher issues failing to detect changes. This skill resolves the lag by performing a targeted container-internal binary rebuild and restart to restore development velocity.

What is the best way to manage multiple concurrent Docker stacks without container naming conflicts?

The best way to manage multiple concurrent Docker stacks is through isolated project namespaces and accurate stack-namespaced container labels. This ensures commands target the correct service and compose configuration reliably.

Are Docker environment variables reliable for detecting container stack identity?

Docker environment variables are not reliable for detecting container stack identity. This skill bypasses them entirely, using authoritative Docker labels to correctly identify running services and their associated compose files.

How do I tail logs for a specific service within an isolated Docker project namespace?

You can tail logs for a specific service by first running the detection command to identify the correct stack and service names. This skill then facilitates targeted log tailing within the isolated project namespace.