metalbear-co/mirrord / skills/skills/mirrord-config
mirrord-config
FlaggedHelps users generate, edit, and validate mirrord.json configuration files for mirrord (MetalBear). Use when the user wants to connect their local process to a Kubernetes environment, configure features (env/fs/network), or needs feedback on an existing mirrord.json. Always ensures output JSON is valid and schema-conformant.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 1.3 KB |
| SKILL.md | skill md | 11.7 KB |
| references/configuration.md | markdown | 51.6 KB |
| references/fs-mode-internals.md | markdown | 1.2 KB |
| references/schema.json | config | 353.1 KB |
references/fs-mode-internals.md
View on GitHub# fs.mode internals
Detail supporting the `fs.mode` guidance in the skill body.
## What is always read locally
A built-in local-by-default list applies in **every** fs mode, including the default `read`
(`mirrord/layer-lib/src/file/unix/read_local_by_default.rs`):
- **The process's current working directory** — your entire project tree
- **The executable being run**
- Runtime and package-manager paths: `/node_modules`, `/package.json`, `.yarnrc*`, `.tool-versions`
- Source and build artifacts by extension: `.js`, `.py`, `.pyc`, `.rb`, `.jar`, `.class`, `.so`, `.dll`, `.pdb`
- System paths: `/usr`, `/lib`, `/bin`, `/etc`, `/home`, `/opt`, `/tmp`, `/proc`, `/sys`, `/dev`
- Hidden files under `$HOME`
So `ts-node`, `nodemon`, `python -m`, `go run`, `dotnet watch` etc. all load local source under
the default config — no `fs` setting is needed for that.
## What `localwithoverrides` reads remotely
`localwithoverrides` reads `/etc/resolv.conf`, `/etc/hosts` and `/etc/hostname` remotely
by default ([`read_remote_by_default.rs`](https://github.com/metalbear-co/mirrord/blob/989aa3bb76682f8d7869752ea33fb50af8dd14f7/mirrord/layer-lib/src/file/unix/read_remote_by_default.rs#L3-L16)) — plus whatever you add to `fs.read_only` /
`fs.read_write`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |