Mirrord Quickstart Skill
SkillCloud & infraGuide users from zero to their first working mirrord session. Use when a user is new to mirrord, wants to install it, or needs help running their first session connecting to a Kubernetes cluster.
Use Mirrord Quickstart Skill in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Mirrord Quickstart Skill and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Mirrord Quickstart Skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.
No other account needed.
Add Ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
What this skill tells your AI
The instructions your AI receives, as published by metalbear-co/skills in skills/mirrord-quickstart/SKILL.md and read by Ahel’s review.
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
# 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)
Do not run remote install scripts that pipe a network download into a shell interpreter. Use only methods your organization approves.
Official guide: Follow mirrord installation documentation for supported options (package managers, pinned release binaries with checksum verification, etc.).
Summary for the agent:
- macOS / Linux: Point the user to the official docs for Homebrew, apt, or pinned binary install steps — do not invent or paste one-liners that fetch and execute remote scripts.
- Windows: Point the user to the official docs for supported installers.
Security: Prefer package managers or manually verified binaries from official release artifacts. Never execute installation by piping downloaded content into a shell.
Verify installation:
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
# 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
# Quick test: print remote env vars
mirrord exec --target pod/<pod-name> -- env | grep -i database
What's Next
Once the first session works, point users to:
mirrord ui— launches a local dashboard showing every active session on the machine, with a live event stream (HTTP requests, file operations, DNS, outgoing connections). See Local UI.mirrord up— for debugging several microservices together from onemirrord-up.yaml(compose-style). Point to the mirrord-up skill.- Browser extension — routes requests made from Chrome to the local process, for testing an HTTP-filtered session from a browser instead of
curl. See Debugging from Browser. - mirrord for Teams features (DB branching, queue splitting, preview environments, concurrent steal on one target) need the Operator. On a cluster with no license, an AI agent can offer the user a seven-day Enterprise trial and start it once they agree: point to the mirrord-operator skill, "Agent-started trial".
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: Follow the official quick-start for their OS (no remote pipe-to-shell installs)
- Run:
mirrord lsto see targets - Connect:
mirrord exec --target pod/X -- <their-app> - Verify: Show them it's working
Signals
- GitHub stars
- 28
- Forks
- 6
- Last commit
- Oct 2026
Advanced
- Item type
- skill
- Key
mirrord-quickstart- Source
- github.com/metalbear-co/skills
github.com/metalbear-co/skills
Related picks
Skill · microsoft
The pick for Kubernetesinfra-containers-kubernetes
Skill · agents-inc
The pick for Kubernetesvercel-react-best-practices
Skill · vercel-labs
More in Cloud & infraweb-design-guidelines
Skill · vercel-labs
More in Cloud & infraturborepo
Skill · vercel
More in Cloud & inframicrosoft-foundry
Skill · microsoft
More in Cloud & infra