Reusable how-to guides that extend Claude's capabilities — available in every session, every project
Location: ~/.claude/skills/
ai-servicers.com
A skill is a SKILL.md file that Claude reads when a relevant task comes up.
Think of them as onboarding guides. Instead of Claude having to figure out how things work from scratch each session, a skill hands it the procedures, naming standards, gotchas, and tool integrations for a specific domain.
Zero boot cost. Skill metadata (name + description) is always loaded. The full SKILL.md body is only read when the skill is triggered — keeping context lean.
Result: 0 tokens at boot • full depth on demand • context stays focused
$HOME/secrets/ not project dirs. Covers Bitwarden, credential rotation, security audits.docs/context/ (7 files). Auto-triggered via Stop/SubagentStop hooks with smart git diff. Ensures agents maintain architecture, decisions, security, operations, testing, gotchas, and specs across sessions.~/.claude/skills/my-skill-name/SKILL.md — frontmatter with name + description triggers invocationreferences/ for docs, scripts/ for automation, assets/ for templatesname: — machine name, matches directory namedescription: — plain English trigger guide. Claude reads this to decide when to invoke. Include keywords.
Use the skill-creator skill for the full guided workflow.
24 skills in ~/.claude/skills/ —
available in every session, every project.
Zero tokens at boot. Metadata is indexed at startup. Full skill content loads only when triggered. Context stays focused — depth appears exactly when needed.
Skills cover infrastructure enforcement, AI workflow orchestration, specialist development knowledge, and meta-tools for extending the system itself.
ai-servicers.com