# Start Your First mirrord Kubernetes Session

Starting local development against Kubernetes requires working cluster access, suitable tooling, and a target pod. This skill guides installation, first-session setup, and connection verification.

## Install

```bash
npx skillstore add metalbear-co/mirrord-quickstart
```

## Metadata

- Status: approved
- Slug: metalbear-co-mirrord-quickstart
- Version: 1.2
- Author version: 1.2
- Skillstore revision: r1
- Version status: invalid
- Tree hash: 5283bb33de0cc8341d3e5e3b475909340aad8715feb2baa9e667c9d5b73f192d
- Author: metalbear-co
- GitHub username: metalbear-co
- License: MIT
- Repository: https://github.com/metalbear-co/skills/tree/a0ad7ca50ffb241a1c4f9c6a05d17661d5d658a5/skills/mirrord-quickstart
- Ref: bad9dafc37d1638cd29cb9bab06d5f8dbcd0f6c2
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 70
- Public page: https://skillstore.pages.dev/skills/metalbear-co-mirrord-quickstart
- Manifest: https://skillstore.pages.dev/api/skills/metalbear-co-mirrord-quickstart/manifest

## Capabilities

- Ask about operating system, preferred workflow, and existing kubectl access.
- Guide prerequisite checks using cluster information and pod listings.
- Direct users to official CLI installation documentation or IDE extension setup.
- Provide first-session commands for local Node.js and Python applications.
- Explain connection verification and troubleshoot namespace, RBAC, and agent startup problems.
- Introduce the local dashboard, browser extension, and related skills for advanced workflows.

## Use Cases

- Connect a Local Backend: Guide a developer through connecting a local Node.js or Python application to an authorized Kubernetes pod.
- Standardize Developer Onboarding: Help new team members verify cluster access, choose an installation path, and troubleshoot namespace or RBAC problems.
- Start an IDE Debugging Session: Walk through VS Code or IntelliJ setup, target selection, and initial connection checks before investigating application behavior.

## Prompt Templates

### Choose a Starting Path

```
I am new to mirrord. Ask about my operating system, editor, and cluster access, then guide me through the prerequisites.
```

### Install and Verify

```
Help me install mirrord on [operating system] for [CLI or IDE]. Use official documentation and approved installation methods, then verify the installation.
```

### Connect My Application

```
Connect my local [Node.js or Python] application to an authorized pod in [namespace]. Confirm my Kubernetes context and target before launching the session.
```

### Diagnose a Failed Session

```
My mirrord session reports [error] in [namespace]. Check cluster access, namespace, RBAC, and agent requirements. Verify connectivity without printing secret environment values.
```

## Limitations

- Requires an accessible Kubernetes cluster and suitable kubectl permissions.
- Provides instructions rather than bundled installers, executable automation, or a test cluster.
- Defers advanced multi-service and Operator workflows to separate skills and documentation.
- The supplied environment verification example can expose secrets and should be replaced with a presence-only check.

## Best Practices

- Confirm the Kubernetes context, namespace, and authorized target before connecting a local application.
- Use approved installation methods and verify pinned binaries against official checksums.
- Verify environment access with presence-only checks and keep credentials out of terminal output and chat.

## Anti Patterns

- Executing downloaded installation scripts directly through a shell.
- Connecting to an unfamiliar or production target without explicit authorization.
- Printing remote database environment values or sharing them in troubleshooting transcripts.

## Security Audit

- Audited at: 2026-09-29T22:05:23.452\+00:00
- Summary: All 19 static flags reflect Markdown formatting, legitimate prerequisite checks, or documentation links rather than the reported threats. A separate verification step risks exposing database credentials by printing remote environment values. No evidence found of prompt injection or intentional data exfiltration.

## Stats

- Views: 0
- Downloads: 1
- Favorites: 0
- Popularity score: 0