Individual skill

mirrord-operator

Help users install and configure the mirrord Operator for team/enterprise environments. Use when users ask about operator setup, Helm installation, cloud API key or license configuration, air-gapped/offline licensing, enabling features (queue splitting, DB branching, preview environments, multi-cluster), internal registries, OpenShift/GKE Autopilot, RBAC, or multi-user mirrord deployments. Also use when an AI agent hits a Team or Enterprise feature on a cluster with no license and needs to offer the user a trial (agent-started trial; the trial is Enterprise tier).

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

Read pinned source

Source commit f787de4101c06892250c133e9bd30788c176ab36

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 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 12, 2026
License
MIT

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

Files and excerpt

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

Browse files
Read excerpt

# Mirrord Operator Skill

## Purpose

Help users install and operate the mirrord Operator — the persistent Kubernetes control plane that enables all mirrord **Team / Enterprise** features:
- **Install / upgrade** the operator via Helm
- **Authenticate** it with a cloud API key (default) or a license (key / offline PEM / license server)
- **Enable features** (queue splitting, DB branching, preview environments, multi-cluster)
- **Configure** registries, TLS, RBAC, and platform specifics (OpenShift, GKE Autopilot)
- **Troubleshoot** operator issues

## Why the Operator?

In open-source mirrord each session is standalone (the CLI creates a privileged agent pod directly). The Operator centralizes this:
Back to top