agentleFS
heytcassheytcass/claudeos/.claude/skills/add-module/SKILL.md

add-module

Skill1 starsChanged 17 days agoMITView on GitHub

Scaffold a new NixOS module, wire it into imports, and validate

9 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If category unclear, ask.

    line 24
  2. Distinctive:

    Use the module-creator subagent, or create directly following the template:

    line 28
  3. Very specific:

    Add to the category's default.nix:

    line 56

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “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

Add NixOS Module

Scaffold a new module following project conventions, wire it in, and validate.

Usage

/add-module <category>/<name> — e.g. /add-module apps/tailscale or /add-module common/firewall

Steps

1. Determine Location

Categories map to directories:

  • common/ — system foundations (boot, networking, users)
  • desktop/ — GNOME, audio, fonts, theme
  • apps/ — applications and services
  • home/ — home-manager modules (shell, git, etc.)

If category unclear, ask.

2. Scaffold Module

Use the module-creator subagent, or create directly following the template:

# modules/<category>/<name>.nix
{ config, lib, pkgs, ... }:
{
  # Configuration here
}

For modules with options, use mkEnableOption + mkIf:

{ config, lib, pkgs, ... }:
let
  cfg = config.services.<name>;
in {
  options.services.<name> = {
    enable = lib.mkEnableOption "<name> service";
  };

  config = lib.mkIf cfg.enable {
    # ...
  };
}

3. Wire Into Imports

Add to the category's default.nix:

imports = [
  ./<name>.nix  # Add this line
];

For home-manager modules, add to home/default.nix.

4. Validate

claudeos-validate stages untracked files, runs nix flake check, and dry-run-builds every host the flake defines:

claudeos-validate

5. Report

Show the new module path and confirm it builds for all hosts.

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.