Skills installed
Skills live in ~/.claude/skills/. Each is a single SKILL.md file with frontmatter (name, description, allowed-tools) and the body is plain-English instructions Claude follows.
Currently installed
Section titled “Currently installed”| Skill | Path | Purpose | Trigger phrases |
|---|---|---|---|
daily-driver | ~/.claude/skills/daily-driver/SKILL.md | Build today’s daily note | ”good morning”, “build today’s note”, “daily driver” |
process-inbox | ~/.claude/skills/process-inbox/SKILL.md | Triage 00-Inbox/ | ”process my inbox”, “inbox zero”, “triage” |
prep-for | ~/.claude/skills/prep-for/SKILL.md | Person briefing | ”prep for [Name]”, “brief me on [Name]“ |
process-meeting | ~/.claude/skills/process-meeting/SKILL.md | Structure meeting notes | ”process this meeting”, “I just got off a call” |
content-engine | ~/.claude/skills/content-engine/SKILL.md | Blog post + illustrations | ”write a blog post about”, “make a thread” |
weekly-review | ~/.claude/skills/weekly-review/SKILL.md | Sunday synthesis | ”weekly review”, “review my week” |
nano-banana | ~/.claude/skills/nano-banana/SKILL.md | Image generation via Gemini CLI | ”generate an image of”, “create a thumbnail” |
Not yet installed (planned)
Section titled “Not yet installed (planned)”These workflows are documented on this site but the skill files don’t exist yet:
| Skill | Workflow page | Status |
|---|---|---|
synthesize | Research Synthesizer | Design ready, not built |
review-cards | Spaced Repetition | Design ready, not built |
make-cards | Spaced Repetition | Design ready, not built |
rebuild-mocs | MOC Maintainer | Design ready, not built |
When you’re ready to build any of these, ask Claude — the design notes on the workflow pages are detailed enough to scaffold from.
How to inspect a skill
Section titled “How to inspect a skill”notepad C:\Users\justi\.claude\skills\daily-driver\SKILL.mdThe file has YAML frontmatter (don’t change name — it’s the skill ID), then markdown instructions. Editing is safe; Claude re-reads on next invocation. No rebuild step.
How to add a new skill
Section titled “How to add a new skill”mkdir C:\Users\justi\.claude\skills\my-new-skillnotepad C:\Users\justi\.claude\skills\my-new-skill\SKILL.mdInside the file:
---name: my-new-skilldescription: One-sentence description that triggers Claude's recognition. Make this specific — the more your trigger phrases match, the better skill routing works.allowed-tools: mcp__mcp-obsidian__obsidian_get_file_contents, mcp__mcp-obsidian__obsidian_append_content---
# My New Skill
Plain-English instructions for Claude here. Be specific about steps, files to read, files to write, edge cases, and tone.Restart Claude Code (or wait for skill discovery to refresh) and the skill is live.
How to delete a skill
Section titled “How to delete a skill”rmdir /S C:\Users\justi\.claude\skills\my-old-skillDone. No registry to clean.
Removing a skill from skill routing without deleting it
Section titled “Removing a skill from skill routing without deleting it”Add disabled: true to the frontmatter. Claude will skip routing to it but the file remains for reference.
Where skills came from on your machine
Section titled “Where skills came from on your machine”I wrote all 7 of these during our Claude Code session in early May 2026. They reference your specific vault layout (00-Inbox/, 10-Daily/, etc.). If you change folder names, update the skills.