Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
npx skills add https://github.com/malob/nix-config --skill malo-find-skills
This skill helps you discover and install skills from the open agent skills ecosystem (https://skills.sh). Based on the find-skills skill by Vercel, adapted for this Nix-managed environment.
Use this skill when the user:
All paths below (e.g. home/claude.nix, configs/claude/skills/) are relative to the nix-config directory.
Skills are split into two categories:
configs/claude/skills/ committed to the nix-config repo. These are skills we author and maintain.npx skills add. These are managed by an activation script in home/claude.nix and are gitignored (they appear as symlinks in the skills directory, not regular directories).The activation script defines a list called externalSkills. On every nh darwin switch --no-nom, it removes all Claude Code external skills and reinstalls only the declared ones. This keeps external skills declarative and reproducible.
Run the find command with a relevant query:
npx skills find [query]
For example:
npx skills find react performancenpx skills find pr reviewnpx skills find changelogYou can also browse skills at https://skills.sh/
When you find relevant skills, present them with:
To try a skill immediately:
npx skills add <owner/repo> --skill <name> -g -a claude-code -y
Always pass -a claude-code to avoid installing for other agents. The -g flag installs globally (user-level) and -y skips prompts.
If the user wants to keep the skill across rebuilds, add it to the externalSkills list in home/claude.nix:
externalSkills = [
"anthropics/skills --skill pdf"
"owner/repo --skill new-skill" # <- add here
];
Then nh darwin switch --no-nom will install it on every activation.
If no existing skill fits, or the user wants to build their own:
configs/claude/skills/<skill-name>/SKILL.md with YAML frontmatter (name and description) and instructionsreferences/, scripts/, or other supporting filesIf no relevant skills exist:
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Take malob/malo-find-skills from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.
The instructions reference npx.
Without those the skill loads but fails at the first command.