A collection of Claude Code skills.
Each subdirectory is a self-contained skill with a SKILL.md (frontmatter + docs) plus any supporting files. Drop a skill folder into ~/.claude/skills/<skill-name>/ and it becomes available as /skill-name the next time Claude Code starts.
| Skill | What it does |
|---|---|
| list-sessions | List previous Claude Code sessions with session ID, working directory, and an optional one-line LLM-generated summary of the work done. Useful for finding which session to claude --resume after a long absence. |
Skills live under ~/.claude/skills/<skill-name>/SKILL.md. To install one from this repo:
git clone https://github.com/utkarash2991/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -R /tmp/claude-skills/list-sessions ~/.claude/skills/list-sessionsOr symlink so updates stay in sync:
git clone https://github.com/utkarash2991/claude-skills.git ~/code/claude-skills
mkdir -p ~/.claude/skills
ln -s ~/code/claude-skills/list-sessions ~/.claude/skills/list-sessionsRestart Claude Code (or open a new session) and the skill appears as /list-sessions.
- Create a new top-level directory:
mkdir my-skill && cd my-skill - Add a
SKILL.mdwith YAML frontmatter at the top:--- name: my-skill description: One-line description triggering on phrases like "...", "...". version: 0.1.0 --- # My Skill What it does, how to invoke it, any flags.
- Add any supporting scripts in the same directory. Keep them self-contained — assume no external dependencies beyond what's standard on macOS / Linux (Python 3, bash, the
claudeCLI). - Add the skill to the table in this README.
- Make sure nothing in your skill writes user-specific or company-internal data into committed files. If your skill produces a cache, name it
cache.json(already covered by.gitignore) or add a new pattern.