Skip to content
Skills Library
AI & agents · Analysis

identify-skill-gaps

/identify-skill-gaps

Use when analyzing Claude Code conversation logs to find patterns in repeated user instructions that could become skills. Ask for date range first.

Licence
MIT
Last repository change
27.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
1
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/extract-user-messages.ts

What it does and when to use it

Use when analyzing Claude Code conversation logs to find patterns in repeated user instructions that could become skills. Ask for date range first.

Original author description

Use when analyzing Claude Code conversation logs to find patterns in repeated user instructions that could become skills. Ask for date range first.

How it works

  1. Step 1: Ask for Date Range
  2. Step 2: Extract User Messages
  3. Step 3: Analyze for Patterns
  4. Step 4: Output Prioritized List
Original SKILL.md headings · 65 lines, 285 words
SKILL.md preview
---
name: identify-skill-gaps
description: Use when analyzing Claude Code conversation logs to find patterns in repeated user instructions that could become skills. Ask for date range first.
---

# Identify Skill Gaps

Analyze Claude Code conversation logs to identify areas where the user repeatedly gives similar instructions that could be turned into skills.

## Step 1: Ask for Date Range

**FIRST**: Ask the user what date range they want to analyze.

Example: "What date range would you like me to analyze? (e.g., December 1-15, 2024)"

## Step 2: Extract User Messages

Claude Code stores conversation logs in `~/.claude/projects/` as JSONL files.

**NEVER assume logs aren't accessible.** They ARE stored locally.

Run the extraction script with the date range:

```bash
scripts/extract-user-messages.ts --after YYYY-MM-DD
```

This filters out tool calls, assistant responses, and metadata—keeping only what the user said.

## Step 3: Analyze for Patterns

Analyze the output and apply the waste analysis framework from [references/wastes.md](references/wastes.md).

1. **Apply each lens** to identify waste patterns
2. **Look for repetition across conversations** - the same waste appearing multiple times signals high-value skill opportunities
3. **Quantify the waste** - count how many messages/characters users spend on each pattern
4. **Prioritize by frequency and cost** - repeated, lengthy wastes are the best skill candidates

**What counts as a pattern**: The user giving similar instructions in 3+ separate conversations.

Focus on identifying waste where users repeatedly spend conversation time on things that could be eliminated by a skill.

## Step 4: Output Prioritized List

Create a markdown list with:

```markdown
## Potential Skills

### 1. [Skill Name] - HIGH PRIORITY

**Frequency**: Found in [X] conversations
**Rationale**: [Why this would be useful]
**Example instructions**:

- "[Quote from conversation]"
- "[Another quote]"

### 2. [Skill Name] - MEDIUM PRIORITY

...
```

**Priority levels**:

- HIGH: 5+ occurrences, affects workflow significantly
- MEDIUM: 3-4 occurrences, clear pattern
- LOW: 2 occurrences, worth noting
Files in this package (3)
  • SKILL.md 2 KB
  • references/wastes.md 7 KB
  • scripts/extract-user-messages.ts 3 KB

Versions

The database has no other skills named identify-skill-gaps.

Database snapshot: 13.11.2026 · package version fe71301ac405 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100create-skill-claude
    Use this skill when the user asks to "create a skill", "add a skill", "make a new skill", "build a skill", or wants to automate a repeated workflow into a reusable prompt. Guides creating a properly structured Claude Code skill.
  • 100sweep
    Use when mining prompt history to rank skill usage, count how often each skill runs, find never-invoked skills, or improve repeated instructions.
  • 100conversation-analyzer
    Analyzes your Claude Code conversation history to identify patterns, common mistakes, and opportunities for workflow improvement. Use when user wants to understand usage patterns, optimize workflow, identify automation opportunities, or check if they're following best practices.
  • 100self-improvement-sweep
    Use when mining prompt history to rank skill usage, count how often each skill runs, find never-invoked skills, or improve repeated instructions.
  • 95agent-instructions
    Write and maintain repository guidance across AGENTS.md, CLAUDE.md, and .agents/skills. Use when creating or editing skills, deciding where instructions belong, or diagnosing instruction sprawl and skill selection. Do not use merely because another skill is being executed.
  • 100skills-discovery
    Analyze team workflows to identify missing skills, agent behavior gaps, or repeated corrections that indicate need for new skills. Use when analyzing what skills would help, identifying why agents keep making the same mistakes, conducting skill gap analysis, or when user asks…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.