Self-Improvement via History Analysis

VerifiedSafe

Examines Claude Code conversation history to detect recurring friction patterns. Cross-references findings with existing CLAUDE.md and skill definitions to suggest targeted improvements. Best used when you want to systematically review and refine your setup based on actual usage pain points.

Sby Skills Guide Bot
ProductivityIntermediate
6/2/2026
Claude Code
#conversation-analysis#friction-patterns#improvement-suggestions#claude-md#self-improvement

Recommended for

Automated summary

Analyzes Claude Code conversation history to identify friction patterns and suggest improvements to configuration.

Strengths

  • Leverages real conversations for context-aware suggestions
  • Generates actionable improvement proposals in a file
  • Automates detection of recurring issues
  • Recommends updates to CLAUDE.md and skills

Limitations

  • Requires access to conversation history
  • Can be slow with large volumes of data
  • Does not automatically apply changes
When to use it

Use this skill when you or your project faces repeated friction with the Claude agent and you want systematic improvements.

When not to use it

Do not use if you have no relevant conversation history or prefer manual configuration adjustments.

Security analysis

Safe
Quality score90/100

The skill only reads local conversation history and writes a local markdown file; it uses no network calls, destructive commands, or data exfiltration. The bash commands are limited to listing files, and subagents only analyze content locally.

No concerns found

How this analysis is made

Examples

Full session review
/self-improvement
Recent analysis
/self-improvement last 3 days
Targeted keyword
/self-improvement refactoring

name: self-improvement description: Analyze conversation history to find friction patterns and suggest CLAUDE.md/skill improvements. Use when user wants to review what went wrong across sessions and systematically improve. (user) allowed-tools: Read, Bash, Grep, Glob, Task

Self-Improvement - Learn from History

Analyze Claude Code conversation history to find friction patterns, check what's already fixed, and suggest improvements.

Instructions

Phase 1: Find Conversations

# Get project directory (encode current path with dashes)
ls ~/.claude/projects/

# List today's conversations (or adjust -mtime for longer range)
ls -lt ~/.claude/projects/<encoded-path>/*.jsonl | head -20

Phase 2: Parallel Analysis

Spawn Task agents (subagent_type: general-purpose) to analyze conversations in parallel. Each agent reads one .jsonl file and extracts:

  1. What was user trying to accomplish?
  2. Problems/friction that occurred (include user quotes showing frustration)
  3. What worked well?
  4. Repeated patterns or inefficiencies

For large files (>500KB), prioritize those - they contain the meatiest sessions.

Phase 3: Synthesize

After all agents complete, combine findings:

  • Top friction patterns ranked by frequency
  • What worked well (don't lose these)
  • User frustration quotes (raw evidence)

Generalize aggressively. Look for the meta-pattern behind specific issues.

Phase 4: Cross-Reference

Read current documentation:

  • Project CLAUDE.md
  • User ~/.claude/CLAUDE.md
  • Skills in .claude/skills/ and ~/.claude/skills/

For each friction pattern, classify:

  • Already fixed - note location
  • Still missing - needs addition

Phase 5: Output

Create a markdown file (e.g., CLAUDE_IMPROVEMENTS.md) with:

# Suggested CLAUDE.md Improvements

Based on analysis of N conversations from [date range].

## 1. [Issue Name]

**Problem:** [Description of friction]

**Suggested addition to [location]:**

\```markdown
[Proposed text]
\```

---

## Already Fixed

| Issue | Where |
|-------|-------|
| ... | ... |

---

## Potential Skills

| Skill | Purpose |
|-------|---------|
| ... | ... |

---

## Raw Friction Log

- "user quote 1"
- "user quote 2"

Do not apply changes - create the file for user review.

Usage Examples

/self-improvement
/self-improvement last 3 days
/self-improvement refactoring

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/self-improvement-via-history-analysis-mm5t8aka/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/self-improvement-via-history-analysis-mm5t8aka' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/self-improvement-via-history-analysis-mm5t8aka/download' --output '.skill-downloads/self-improvement-via-history-analysis-mm5t8aka/SKILL.md.part' && mv '.skill-downloads/self-improvement-via-history-analysis-mm5t8aka/SKILL.md.part' '.skill-downloads/self-improvement-via-history-analysis-mm5t8aka/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Read, Bash, Grep, Glob, Task

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/self-improvement-via-history-analysis-mm5t8aka/SKILL.md' && test -s '.skill-downloads/self-improvement-via-history-analysis-mm5t8aka/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/self-improvement' && cp -R '.skill-downloads/self-improvement-via-history-analysis-mm5t8aka' '.claude/skills/self-improvement'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/self-improvement-via-history-analysis-mm5t8aka'

openskills read 'self-improvement-via-history-analysis-mm5t8aka'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/self-improvement-via-history-analysis-mm5t8aka/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills