agents/skills/managing-skills/SKILL.md
Use when adding, installing, removing, or managing agent skills in this dotfiles repo. Triggers on "add skill", "install skill", "remove skill", "delete skill", "new skill", "manage skills", or any skill management task.
npx skillsauth add juanibiapina/dotfiles managing-skillsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Two kinds: own (local, editable) and external (from GitHub repos, read-only in nix store).
Files involved:
agents/skills/ - own skills directoryflake.nix - flake inputs for external sourcesnix/modules/homemanager/agents.nix - source wiringAll skills end up at ~/.agents/skills/<name>/.
Create dir under agents/skills/ with SKILL.md. Own skills get live symlinks back to repo (editable without rebuild).
agents/skills/my-skill/SKILL.md
Stage new files, run make.
Add flake input in flake.nix, wire source in agents.nix. Three patterns:
Repo has skills/ dir with multiple skill subdirs.
# flake.nix
caveman-skill = { url = "github:JuliusBrussee/caveman"; flake = false; };
# agents.nix sources
caveman = { src = inputs.caveman-skill; subdir = "skills"; };
Repo has nested skill dirs. Pick specific ones by relative path under subdir. Installed name is last path component.
# agents.nix sources
agent-library = {
src = inputs.agent-skills-library;
subdir = "skills";
pick = [
"design/radix-ui-design-system"
"business/seo-audit"
];
};
Entire repo is one skill. Attribute name becomes skill name.
# flake.nix
last30days-skill = { url = "github:mvanhorn/last30days-skill"; flake = false; };
# agents.nix sources
last30days = { src = inputs.last30days-skill; };
Own: delete dir from agents/skills/.
External: remove flake input from flake.nix and source entry from agents.nix.
git add flake.nix nix/modules/homemanager/agents.nix # stage new/changed files
gob run make
Own skill names must not collide with external skill names (build will fail).
development
Use before starting work on any coding task: implementing a feature, fixing a bug, refactoring, or changing code. Drives the complete implementation.
development
Use when writing code plans, architecture, or generally discussing code
testing
Use when writing, reviewing, or improving tests, deciding what to mock, or designing interfaces for testability.
development
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.