continuous-learning

Extract reusable knowledge from coding sessions and codify it into new Claude Code skills.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? AI coding agents start every session from zero, so hard-won debugging insights and workarounds are lost when the session ends. This Skill captures non-obvious solutions discovered during work and saves them as new reusable skills that surface automatically in future sessions. ## Core Features & Use Cases - Automatic Skill Extraction: Evaluates completed tasks for extractable knowledge (debugging techniques, workarounds, project-specific patterns) and writes new SKILL.md files with retrieval-optimized descriptions. - Retrospective Mode: Run /retrospective at the end of a session to review the conversation, prioritize the highest-value discoveries, and extract 1-3 new skills. - Quality Gates & Deduplication: Verifies solutions actually worked, checks existing skills for near-matches, and confirms with a dry-run preview before writing anything. - Use Case: After spending an hour diagnosing a Prisma "too many connections" error in a serverless deployment, the Skill saves a prisma-connection-pool-exhaustion skill with exact trigger errors and the verified fix, so the next occurrence is resolved in minutes. ## Quick Start Ask the agent to run a retrospective and save what we learned from this debugging session as a reusable skill.

Frequently Asked Questions about continuous-learning

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

FAQPage Schema
How do I save a debugging solution as a reusable Claude Code skill?

Trigger the retrospective by saying "save this as a skill" or running /retrospective after solving a problem. The Skill drafts a new SKILL.md with trigger conditions and the verified fix, shows a dry-run preview, and writes it to .claude/skills/ or ~/.claude/skills/ after confirmation.

What makes a good skill description for semantic matching?

A good description includes exact error messages, observable symptoms, framework or tool names, and action phrases like "Use when". Vague descriptions like "helps with database problems" fail to surface; specific ones like "Fix for PrismaClientKnownRequestError in serverless" match reliably.

When should knowledge not be extracted into a skill?

Skip extraction for secrets or PII, one-off user-specific configurations, unverified fixes, content already covered in official documentation, and trivial knowledge like basic syntax. The Skill's quality gates reject anything that would not help someone hitting the same problem months later.

How do I set up automatic activation for every session?

Copy the continuous-learning-activator.sh script to ~/.claude/hooks/, make it executable, and register it as a UserPromptSubmit hook in ~/.claude/settings.json. The hook injects a reminder on every prompt to evaluate the session for extractable knowledge.

Does the continuous learning skill work at project level and user level?

Yes, it supports both installation paths. Project-level skills go in .claude/skills/ for codebase-specific patterns, while user-level skills go in ~/.claude/skills/ for knowledge that applies across all projects.