Manage Skill
Purpose
Execute the Workflow and Report sections to manage Claude Code skills.
Variables
- •IS_DOTFILES:
trueif current repo is dotfiles, otherwisefalse - •SCOPE:
- •if IS_DOTFILES, then ask user (user-level/project-local)
- •if not IS_DOTFILES, then
project-local
- •SKILLS_DIR:
- •if user-level then
files/claude/skills - •if project-local then
.claude/skills
- •if user-level then
- •SETTINGS_FILE:
- •if user-level then
files/claude/settings.json - •if project-local then
.claude/settings.local.json
- •if user-level then
Workflow
- •Determine the operation (create, edit, or delete) from user's request
- •Execute the operation:
- •If create, then:
- •If requirements unclear, then ask using AskUserQuestion: skill name, purpose, tool restrictions
- •If IS_DOTFILES, then ask scope (user-level/project-local)
- •Create
SKILLS_DIR/[skill-name]/SKILL.md - •Follow the format in format.md, see basic-structure.md for template
- •If edit, then:
- •Locate
SKILLS_DIR/[skill-name] - •Read and modify
SKILL.mdor supporting files as requested
- •Locate
- •If delete, then:
- •Confirm with user before deletion
- •Remove
SKILLS_DIR/[skill-name]
- •If create, then:
- •Update
SETTINGS_FILEpermissions as needed
Report
Inform the user:
- •The operation performed and skill location
- •For user-level: remind to run Nix to deploy
- •For project-local: immediately available in the current project