npx skills add smithery/metalbear-co --skill mirrord-quickstart
metalbear-co/skills
mirrord-quickstart
Guide 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.
Installation
npx skills add metalbear-co/skills --skill mirrord-quickstart
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…
866.4K installsBrowser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installsReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…
617.3K installsBuild, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …
576.5K installsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …
568.9K installsAlso in this package
Other skills from metalbear-co/skills · top by installs.
npx skills add metalbear-co/skills
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
main
Skill metadata
Parsed from SKILL.md frontmatter.
More metadata
- author
- MetalBear
- version
- 1.1
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md4,149 B -
docs
README.md1,114 B -
docs
SUMMARY.md221 B
History
- First seen on skills.sh
- First recorded snapshot · 90 installs
SKILL.md
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
# 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
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