Skip to content
TrustedSkillsbeta
Back to all skills

Docker Compose Orchestration

Checked
manutej·vlatest·cloud

Automates Docker Compose deployments and management across your cloud infrastructure using manutej's orchestration engine.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add manutej/crush-mcp-server --skill docker-compose-orchestration -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

manutej

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Only contacts known or declared hosts: 0.0.0.0, gitlab.local.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    0.0.0.0localgitlab.locallocal

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned manutej/crush-mcp-server at bb8eed14fe.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
bb8eed14fe
Manifest
.claude/skills/docker-compose-orchestration/SKILL.md
Scanned
8 files, 7,892 lines
Copies in repo
2 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill allows AI agents to manage and orchestrate applications defined in docker-compose.yml files. It can start, stop, restart, and inspect services within a Docker Compose environment, automating deployment and management tasks. The agent can also handle common configuration adjustments based on user instructions.

When to use it

  • Automated Development Environments: Quickly spin up development environments with all necessary dependencies defined in a docker-compose.yml.
  • Staging Deployments: Deploy application stacks to staging environments for testing and validation.
  • Local Application Testing: Simplify local testing of multi-container applications by managing their lifecycle.
  • Reproducible Environments: Ensure consistent deployments across different machines using Docker Compose configurations.

Key capabilities

  • Start services defined in docker-compose.yml
  • Stop services defined in docker-compose.yml
  • Restart services defined in docker-compose.yml
  • Inspect service status and logs
  • Handle configuration adjustments within the Compose environment

Example prompts

  • "Start the 'web' and 'database' services."
  • "Stop all running containers from my project."
  • "Show me the logs for the 'app' service."
  • “Restart the ‘redis’ container.”

Tips & gotchas

  • The agent requires access to a directory containing a valid docker-compose.yml file.
  • Ensure Docker is installed and running on the system where the agent operates.