skilllisted

# Skill Authoring Guidelines Read this before creating or modifying any skill. These conventions ensure skills are consistent, minimal, and fast to invoke. ## Skill structure ``` skills/<skill-name>/ ├── SKILL.md # Entry point (required) ├── scripts/ # Helper scripts (optional) └── references/ # Reference docs cited from SKILL.md (optional) ``` - Entry point is always `SKILL.md` - Place in `~/.claude/skills/` for global skills, `.claude/skills/` for project-local - Shared resources go in `~/.claude/skills/shared/` - **Creating the directory is not enough to keep the skill.** A skills directory is normally ignore-everything-then-allowlist, so a new skill is untracked and invisible until you add its un-ignore line — see [Gitignore](#gitignore) for the exact check. Do it when you create the directory, not at the end; the `skill-tracked.py` hook flags a miss when the SKILL.md is written, but the hook is a net, not the plan. ## Addressing Claude project data (per-project memory, sessions, etc.) If your skill needs to read or write anything under `~/.claude/projects/<project-id>/` — most commonly a project's memory directory — see `~/.claude/skills/skill/references/claude-project-memory-paths.md`. It documents the path mangling rule, the cross-platform CWD recipe, and the common gotchas. Cite that file from your skill rather than re-deriving the algorithm. ## Frontmatter Every SKILL.md starts with YAML frontmatter: ```yaml --- name: <skill-n