
Cc Skill Continuous Learning
Capture reusable debugging and project patterns from finished Claude Code sessions into ~/.claude/skills/learned/ via a Stop hook evaluator.
Install
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill cc-skill-continuous-learningWhat is this skill?
- Stop hook runs once per session end—lighter than UserPromptSubmit on every message
- Detects error_resolution, user_corrections, workarounds, debugging_techniques, and project_specific patterns
- Ignores simple_typos, one_time_fixes, and external_api_issues to reduce noise
- Configurable min_session_length default 10 with medium extraction_threshold and auto_approve false
- Writes extracted skills to ~/.claude/skills/learned/ with evaluate-session.sh orchestration
Adoption & trust: 493 installs on skills.sh; 40.1k GitHub stars; 2/3 security scanners passed (skills.sh audits).
Recommended Skills
Find Skillsvercel-labs/skills
Skill Creatoranthropics/skills
Lark Skill Makerlarksuite/cli
Skills Clixixu-me/skills
Write A Skillmattpocock/skills
Using Superpowersobra/superpowers
Journey fit
Primary fit
First appears in Build/agent-tooling because it extends how your coding agent learns, yet it runs after any session regardless of product phase. Stop-hook automation and learned-skill extraction are agent-runtime tooling, not application feature work.
Common Questions / FAQ
Is Cc Skill Continuous Learning safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Cc Skill Continuous Learning
{ "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" ], "ignore_patterns": [ "simple_typos", "one_time_fixes", "external_api_issues" ] } #!/bin/bash # Continuous Learning - Session Evaluator # Runs on Stop hook to extract reusable patterns from Claude Code sessions # # Why Stop hook instead of UserPromptSubmit: # - Stop runs once at session end (lightweight) # - UserPromptSubmit runs every message (heavy, adds latency) # # Hook config (in ~/.claude/settings.json): # { # "hooks": { # "Stop": [{ # "matcher": "*", # "hooks": [{ # "type": "command", # "command": "~/.claude/skills/continuous-learning/evaluate-session.sh" # }] # }] # } # } # # Patterns to detect: error_resolution, debugging_techniques, workarounds, project_specific # Patterns to ignore: simple_typos, one_time_fixes, external_api_issues # Extracted skills saved to: ~/.claude/skills/learned/ set -e SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" CONFIG_FILE="$SCRIPT_DIR/config.json" LEARNED_SKILLS_PATH="${HOME}/.claude/skills/learned" MIN_SESSION_LENGTH=10 # Load config if exists if [ -f "$CONFIG_FILE" ]; then MIN_SESSION_LENGTH=$(jq -r '.min_session_length // 10' "$CONFIG_FILE") LEARNED_SKILLS_PATH=$(jq -r '.learned_skills_path // "~/.claude/skills/learned/"' "$CONFIG_FILE" | sed "s|~|$HOME|") fi # Ensure learned skills directory exists mkdir -p "$LEARNED_SKILLS_PATH" # Get transcript path from environment (set by Claude Code) transcript_path="${CLAUDE_TRANSCRIPT_PATH:-}" if [ -z "$transcript_path" ] || [ ! -f "$transcript_path" ]; then exit 0 fi # Count messages in session message_count=$(grep -c '"type":"user"' "$transcript_path" 2>/dev/null || echo "0") # Skip short sessions if [ "$message_count" -lt "$MIN_SESSION_LENGTH" ]; then echo "[ContinuousLearning] Session too short ($message_count messages), skipping" >&2 exit 0 fi # Signal to Claude that session should be evaluated for extractable patterns echo "[ContinuousLearning] Session has $message_count messages - evaluate for extractable patterns" >&2 echo "[ContinuousLearning] Save learned skills to: $LEARNED_SKILLS_PATH" >&2 --- name: cc-skill-continuous-learning description: "Development skill from everything-claude-code" risk: none source: community date_added: "2026-02-27" --- # cc-skill-continuous-learning Development skill skill. ## When to Use This skill is applicable to execute the workflow or actions described in the overview. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.