suggest-skills

---
name: suggest-skills
description: Suggest new skills based on what happened in this session. Use when the user says "suggest skills", "what skills should I make", "recommend skills", "what am I missing", "what skills would help me", or any variation. Also use at the end of long sessions where repeated patterns emerged. This skill uses YOUR OWN experience from the current conversation — no transcript mining, no swarm, just honest reflection grounded in what you just lived through.
---

# Suggest Skills — Reflect and Recommend

You just spent a session working with the user. You have the richest possible context — every tool call, every correction, every workflow, every pain point. Use that.

## What to Do

Reflect on this session and suggest skills that would have made it better. That's it.

Look at what actually happened:

- **Repeated sequences** — Did you do the same 3+ steps more than once? That's a skill.
- **Pain points** — Did something fail, need debugging, or require a workaround? A skill could prevent that.
- **Manual setup** — Did you spend time on boilerplate before getting to the real work? A skill could skip that.
- **Corrections** — Did the user have to redirect you? A skill could encode that guidance upfront.
- **Missing context** — Did you have to research something that a skill could have injected automatically?
- **Tool patterns** — Did you use a tool/API repeatedly with similar parameters? A skill could standardize that.

## Before Recommending

Check what skills already exist:

```bash
ls ~/.claude/skills/
```

Don't recommend what's already there unless the existing skill is clearly inadequate for what you observed.

## How to Present

For each recommendation (suggest 3-5, not more):

```
### skill-name — one-line description

**What I noticed**: What happened in this session that motivates this skill
**What it would do**: 1-2 sentences
**Trigger**: When should it activate
```

Keep it short. The user can say "build that" and you go.

## If the User Says "Build That"

Create `~/.claude/skills/<skill-name>/SKILL.md` with proper frontmatter. Keep skills concise — a skill that's 50 lines and actually gets used beats a 300-line skill that's too complex to trigger.