agentleFS
olafkfreundolafkfreund/nix-skills/skills/microvm-nix/SKILL.md

microvm-nix

Skill9 starsChanged 55 days agoMITView on GitHub

Configure and troubleshoot declarative microVMs with microvm.nix when working in a NixOS flake.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the repository instructions, flake inputs, target host, VM nixosConfigurations, imports, and existing microVM modules before editing.

    line 8
  2. Distinctive:

    Use declaring VMs and the introduction for the module shape.

    line 12
  3. Very specific:

    Never search /nix/store (for example find /nix/store/*foo-* -name libfoo.so) and never copy a literal store path.

    line 28
  4. Very specific:

    Do not quote attribute names that are valid identifiers ([A-Za-z_][A-Za-z0-9_'-]*, dashes included).

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

microvm.nix

Read the repository instructions, flake inputs, target host, VM nixosConfigurations, imports, and existing microVM modules before editing. Preserve the project's module and feature-flag conventions.

Use declaring VMs and the introduction for the module shape. Use declarative deployment, host integration, and host systemd for host-managed VMs. Consult options, the networking references, and shares only for the relevant workload.

Distinguish a VM's NixOS configuration from the host's microvm.vms management. Treat host paths, shared stores, networking, interfaces, and device passthrough as trust boundaries. Existing deployed VMs may require the documented microvm update flow instead of an automatic host rebuild update.

Validate the flake and dry-build the affected host or VM before starting or updating runtime services.

Nix style

  • Never search /nix/store (for example find /nix/store/*foo-* -name libfoo.so) and never copy a literal store path. Find the providing package with nix-locate, and refer to it through Nix: ${pkgs.foo}/lib or lib.makeLibraryPath [ pkgs.foo ].
  • Do not quote attribute names that are valid identifiers ([A-Za-z_][A-Za-z0-9_'-]*, dashes included). Write pkgs.foo-bar and packages.x86_64-linux, not pkgs."foo-bar". Quote only other names (".config/foo", "2.0"), the keywords assert else if in inherit let or rec then with, and interpolations ("${name}"). Upstream examples in references sometimes quote needlessly; do not copy that style.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.