continuous-learning

Extract reusable patterns from Claude Code sessions into project-local learned skills.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/maycuatroi1/agent-skills --skill continuous-learning-maycuatroi1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: continuous-learning
Source: https://github.com/maycuatroi1/agent-skills/tree/main/skills/continuous-learning
Command: npx skills add https://github.com/maycuatroi1/agent-skills --skill continuous-learning-maycuatroi1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Valuable debugging techniques, workarounds, and repeated command patterns discovered during Claude Code sessions are lost when the session ends, forcing you to rediscover them in future sessions. ## Core Features & Use Cases - Session-End Pattern Extraction: A Stop hook analyzes the transcript with claude -p and saves reusable patterns as discoverable Agent Skills under the project's .claude/skills/ directory. - CLI Suggestions: Detects repeated shell command patterns and proposes new subcommands for the project's own CLI, written to .claude/cli-suggestions/_pending/ for review. - Curator Lifecycle Management: Tracks usage telemetry, moves idle skills through active/stale/archived states, deduplicates near-identical skills, and snapshots backups before every run. - Use Case: After a long debugging session where you fixed a tricky Django ORM issue, the hook automatically saves that resolution as a learned skill so the next session in the same repo can apply it immediately. ## Quick Start Set up the continuous-learning Stop hook so reusable patterns from my Claude Code sessions are saved as skills in this project.

Frequently Asked Questions about continuous-learning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically save reusable patterns from Claude Code sessions?

Register the evaluate-session.sh script as a Stop hook in ~/.claude/settings.json. At each session end it backgrounds extract_patterns.py, which calls claude -p to analyze the transcript and writes approved skills to .claude/skills/<name>/ in the current project.

How does the continuous-learning curator manage learned skills?

The curate.py CLI tracks usage telemetry in usage.json and moves idle skills from active to stale to archived based on configurable day thresholds. It supports status, run, pin, promote, restore, prune, pause, and resume commands, and snapshots backups before every run.

Why are my learned skills not discovered by Claude Code?

Claude Code only discovers skills at depth one: .claude/skills/<name>/SKILL.md. Skills left in .claude/skills/.learned/_pending/ are intentionally hidden until promoted with the curator's promote command.

Does the Stop hook slow down or block session end?

No. The hook backgrounds the extractor with setsid/nohup (or a detached process on Windows) and exits 0 immediately. The claude -p analysis adds 10-60 seconds of background work without delaying the session.

What are the limitations of session-end pattern extraction?

The Stop hook fires only at session end with no mid-session observation, and usage telemetry is inferred from transcript text rather than a real skill-loaded signal, so it can under- or over-count. Auto-archiving therefore requires explicit --yes confirmation.