85dfa2ef2e
The !`command` blocks in SKILL.md go through Claude Code's Bash permission checker, which rejects $() command substitution. Simplified the git log command, replaced dynamic verify script path with a Read tool instruction, and narrowed allowed-tools to specific command patterns. Also documented the constraints in CLAUDE.md for future skill development. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Custom Claude Skills
Reusable Claude Code skills shared across all projects.
Setup
# Clone and install
cd ~/dev/claude/custom-claude-skills
./scripts/install.sh
The install script creates symlinks from ~/.claude/skills/ to this repo, making all skills available in every project.
Available Skills
| Skill | Invocation | Description |
|---|---|---|
| reflect | /reflect M8 |
Milestone reflection — reviews conversation history, git log, and project docs to produce structured reflection artifacts across MEMORY.md, FUTURE.md, README.md, and CLAUDE.md |
Adding a New Skill
- Create
skills/<skill-name>/SKILL.mdwith YAML frontmatter and instructions - Run
./scripts/install.shto create the symlink - Update this README's skill table
How Skills Work
Skills are Claude Code's extensibility mechanism. Each skill is a markdown file with:
- YAML frontmatter — metadata, tool restrictions, execution mode
- Dynamic context injection —
!command`` blocks run at load time to pre-fetch data - Structured instructions — what Claude should do when the skill is invoked
Skills in ~/.claude/skills/ are available across all projects (personal scope).
Scripts
| Script | Purpose | When to run |
|---|---|---|
scripts/install.sh |
Symlinks all skills into ~/.claude/skills/ |
After cloning or adding new skills |