Individual skill

mirrord-up

Helps users run multiple concurrent mirrord sessions from a single mirrord-up.yaml (compose-style multi-service local debugging). Use when the user mentions mirrord up, mirrord-up.yaml, mirrord up init, debugging several related microservices together, or managing multiple mirrord sessions' lifecycle in one command.

mirrord/mcp/corpus/skills/mirrord-up/SKILL.md

Read pinned source

Source commit 89bfc07c6a44e768cd0d060c79326fe585ae5601

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: No
Observed behavior: Network or broad shell
Last checked: Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 5,410
Repository last updated: Nov 11, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

cloud Repository topic
kubernetes Repository topic
debug Repository topic
traffic Repository topic
api Repository topic
ide Repository topic
vscode Repository topic
cli Repository topic
development Repository topic
devtool Repository topic
testing Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

README.mddoc · 2,466 bytes
SKILL.mdcore · 19,364 bytes
SKILL.mdcore · 19,364 bytes
SKILL.mdcore · 19,364 bytes

Read excerpt


# mirrord up Skill

## Purpose

Help users create and run **multiple concurrent mirrord sessions** from one config file — think docker compose, but for mirrord — as documented in [Multiple concurrent sessions (mirrord up)](https://metalbear.com/mirrord/docs/using-mirrord/multiple-concurrent-sessions).

Useful when they need to debug **several related microservices** and manage those sessions' lifecycle together.

Each `services` entry is typically a **different** application with its own target, command, and configuration — `mirrord up` is for running several distinct applications together, not for targeting multiple pods of the *same* application. For that (label-based targeting), point users to the **mirrord-operator** or **mirrord-config** skill instead of trying to model it with `mirrord-up.yaml`.

## When to Use This Skill

Trigger on questions like:
- "How do I run multiple mirrord sessions at once?"