Mirrord Quickstart Skill
Purpose
Help new users get mirrord running quickly:
- •Check system requirements
- •Install mirrord (CLI, VS Code, or IntelliJ)
- •Connect to their first Kubernetes target
- •Verify the connection works
Critical First Steps
Step 1: Detect user's environment Ask or detect:
- •Operating system (macOS, Linux, Windows)
- •Preferred workflow (CLI, VS Code, IntelliJ)
- •Do they have kubectl configured?
Step 2: Verify requirements
bash
# Check kubectl access kubectl cluster-info kubectl get pods -A | head -5
If kubectl fails, help them configure it first.
Installation Paths
CLI (recommended for getting started)
macOS/Linux:
bash
brew install metalbear-co/mirrord/mirrord
Or without brew:
bash
curl -fsSL https://raw.githubusercontent.com/metalbear-co/mirrord/main/scripts/install.sh | bash
Windows:
bash
choco install mirrord
Verify installation:
bash
mirrord --version
VS Code Extension
- •Open VS Code Extensions (Cmd/Ctrl+Shift+X)
- •Search "mirrord"
- •Install "mirrord" by MetalBear
- •Look for mirrord icon in status bar
IntelliJ Plugin
- •Open Settings → Plugins → Marketplace
- •Search "mirrord"
- •Install and restart IDE
- •Find mirrord in navigation toolbar
First Session
CLI approach
bash
# List available targets mirrord ls # Run a local process with mirrord mirrord exec --target pod/<pod-name> -- <your-command> # Example: Node.js app mirrord exec --target pod/api-server-7c8d9 -- node app.js # Example: Python app mirrord exec --target pod/backend-abc123 -- python main.py
IDE approach
- •Enable mirrord (click status bar icon / toolbar button)
- •Select target pod when prompted
- •Run/debug your application normally
- •mirrord intercepts and connects automatically
Verification
After running, verify the connection:
- •Check logs - You should see mirrord initialization messages
- •Test environment - Remote env vars should be available locally
- •Test network - Make a request to your remote service; it should reach your local process
bash
# Quick test: print remote env vars mirrord exec --target pod/<pod-name> -- env | grep -i database
Common First-Timer Issues
| Issue | Solution |
|---|---|
| "kubectl not found" | Install kubectl and configure cluster access |
| "No pods found" | Check namespace: kubectl get pods -n <namespace> |
| "Permission denied" | Check RBAC permissions for your kubectl context |
| "Agent failed to start" | Ensure cluster runs Linux kernel 4.20+ |
Response Guidelines
- •Ask about their setup - OS, IDE preference, existing kubectl access
- •Go step by step - Don't overwhelm with all options at once
- •Verify each step - Confirm installation worked before moving on
- •Celebrate success - When they connect, explain what just happened
Example Interaction
User: "I want to try mirrord"
Response:
- •Ask: macOS/Linux/Windows? CLI or IDE?
- •Check:
kubectl cluster-infoworking? - •Install: One command based on their OS
- •Run:
mirrord lsto see targets - •Connect:
mirrord exec --target pod/X -- <their-app> - •Verify: Show them it's working