continuous-learning
This skill should be used when the user asks to 'extract patterns from this session', 'save what we learned', 'create a skill from this workflow', 'learn from this conversation', 'capture reusable knowledge', or wants to turn session patterns into reusable skills.
Best use case
continuous-learning is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
This skill should be used when the user asks to 'extract patterns from this session', 'save what we learned', 'create a skill from this workflow', 'learn from this conversation', 'capture reusable knowledge', or wants to turn session patterns into reusable skills.
Teams using continuous-learning should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/continuous-learning/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How continuous-learning Compares
| Feature / Agent | continuous-learning | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
This skill should be used when the user asks to 'extract patterns from this session', 'save what we learned', 'create a skill from this workflow', 'learn from this conversation', 'capture reusable knowledge', or wants to turn session patterns into reusable skills.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Continuous Learning Skill
Extract reusable patterns from sessions and save them as learned skills for future use.
## How It Works
This skill analyzes the session transcript to identify extractable patterns:
1. **Session Evaluation**: Checks if session has enough messages (default: 10+)
2. **Pattern Detection**: Identifies error resolutions, workarounds, debugging techniques
3. **Skill Extraction**: Saves useful patterns to `~/.claude/skills/`
## When to Use
- At end of long sessions with multiple problem-solving cycles
- After resolving complex errors that might recur
- When you develop project-specific conventions
## Invocation
Use `/learn` command or invoke directly:
```
/continuous-learning
```
## Configuration
Edit `config.json` to customize:
```json
{
“min_session_length”: 10,
“extraction_threshold”: “medium”,
“auto_approve”: false,
"learned_skills_path": "~/.claude/skills/learned/",
“patterns_to_detect”: [
“error_resolution”,
“user_corrections”,
“workarounds”,
“debugging_techniques”,
“project_specific”
]
}
```
## Pattern Types
| Pattern | Description |
|---------|-------------|
| `error_resolution` | How specific errors were resolved |
| `user_corrections` | Patterns from user corrections |
| `workarounds` | Solutions to framework/library quirks |
| `debugging_techniques` | Effective debugging approaches |
| `project_specific` | Project-specific conventions |
## Learned Skills Format
Extracted skills are saved following the standard skill directory structure:
```
~/.claude/skills/learned/
├── fix-marimo-import-error/
│ └── SKILL.md
├── debug-pixi-environment/
│ └── SKILL.md
└── wrds-connection-pattern/
└── SKILL.md
```
Each learned skill follows standard SKILL.md format with:
- Frontmatter (name and description)
- Problem context
- Solution pattern
- Example usage
## Integration
The skill reads from `CLAUDE_TRANSCRIPT_PATH` (JSON conversation transcript)
which is automatically set by Claude Code during sessions.
## Related
- `/learn` command - Manual pattern extraction mid-session
- `/checkpoint` command - Save session state
- Session-end hook - Auto-evaluates sessions for patternsRelated Skills
writing
This skill should be used when the user asks to 'write a paper', 'start a writing project', 'draft an article', 'write about', 'brainstorm writing topics', 'gather sources for a paper', 'what should I write about', or needs the writing workflow entry point for any writing task.
writing-validate
Validate draft sections cover all PRECIS claims before review.
writing-setup
Internal skill for creating PRECIS.md, OUTLINE.md, and ACTIVE_WORKFLOW.md. Called after brainstorm sources are gathered.
writing-revise
This skill should be used when the user asks to 'revise writing', 'fix review issues', 'polish draft', 'apply review feedback', 'complete writing workflow', or after /writing-review produces REVIEW.md with issues to fix.
writing-review
Internal skill for hierarchical document review. Called by writing-validate after claim validation passes.
writing-precis-reviewer
Internal skill used by writing-setup at exit gate. Dispatches a reviewer subagent to verify PRECIS.md quality before outlining. NOT user-facing.
writing-outline
Internal skill for creating detailed section outlines. Called by /writing workflow after PRECIS and master OUTLINE are complete.
writing-outline-reviewer
Internal skill used by writing-outline at exit gate. Dispatches a reviewer subagent to verify OUTLINE.md quality before drafting. NOT user-facing.
writing-lit-review
Internal skill for literature review and source materialization. Called after brainstorm, before setup. NOT user-facing.
writing-legal
Internal skill for academic legal writing. Loaded by /writing when style=legal. Based on Volokh's "Academic Legal Writing".
writing-handoff
Create structured handoff document for writing workflow session pause/resume.
writing-general
Internal skill for Strunk & White writing rules. Loaded by /writing for quick edits or as base layer for domain skills.