self-add-skill

To add a new AI skill in a Nix home-manager environment, you create a dedicated directory under modules/home/ai/skills/<skill-name>, add a properly formatted SKILL.md file, commit the change via git, and apply it using home-manager switch. This repository-centric workflow ensures existing configurations remain untouched.

The correct SKILL.md frontmatter format requires a YAML block containing the skill name and description fields. After the frontmatter, you write the skill content, which enables proper discovery metadata and consistent deployment when applying changes with home-manager switch.

Yes, git version control is an enforced part of the workflow for managing AI skills in a Nix dotfiles repository. You must stage and commit the new skill directory and SKILL.md file before applying the deployment, enabling peer review and clear versioning history.

Home-manager switch applies new AI skills safely across machines by deploying from a centralized repository structure. By targeting the specific host with a flake reference, it ensures consistent and repeatable deployment without risking overwriting existing user configurations.

The best way to structure a Nix dotfiles repository for AI skill management is to centralize all skills under modules/home/ai/skills/<skill-name>. This creates a repeatable deployment process, enforces clear discovery metadata, and maintains a versioned workflow for peer review.

A repository-centric workflow is needed for adding skills to home-manager because it consolidates directory placement, frontmatter formatting, and deployment into a repeatable process. This approach prevents configuration overwrites and enables versioning and peer review before applying changes.