compound-learnings
Transform session learnings into permanent capabilities (skills, rules, agents). Use when asked to "improve setup", "learn from sessions", "compound learnings", or "what patterns should become skills".
npx skills add parcadei/Continuous-Claude-v3 --skill compound-learnings --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Compound Learnings Transform ephemeral session learnings into permanent, compounding capabilities. ## When to Use - "What should I learn from recent sessions?" - "Improve my setup based on recent work" - "Turn learnings into skills/rules" - "What patterns should become permanent?" - "Compound my learnings" ## Process ### Step 1: Gather Learnings ```bash # List learnings (most recent first) ls -t $CLAUDE_PROJECT_DIR/.claude/cache/learnings/*.md | head -20 # Count total ls $CLAUDE_PROJECT_DIR/.claude/cache/learnings/*.md | wc -l ``` Read the most recent 5-10 files (or specify a date range). ### Step 2: Extract Patterns (Structured) For each learnings file, extract entries from these specific sections: | Section Header | What to Extract | |----------------|-----------------| | `## Patterns` or `Reusable techniques` | Direct candidates for rules | | `**Takeaway:**` or `**Actionable takeaway:**` | Decision heuristics | | `## What Worked` | Success patterns | | `## What Failed` | Anti-patterns (invert to rules) | | `## Key Decisions` | Design principles | Build a frequency table as you go: ```markdown | Pattern | Sessions | Category | |---------|----------|----------| | "Check artifact
- When to Use
- Process
- Step 1: Gather Learnings
- Step 2: Extract Patterns (Structured)
- Step 2b: Consolidate Similar Patterns
- Step 3: Detect Meta-Patterns
- Step 4: Categorize (Decision Tree)
- Step 5: Apply Signal Thresholds
- Step 6: Propose Artifacts
- Step 7: Create Approved Artifacts
- Step 8: Summary Report
- Quality Checks
- Files Reference
List learnings (most recent first) ls -t $CLAUDE_PROJECT_DIR/.claude/cache/learnings/*.md | head -20 Count total ls $CLAUDE_PROJECT_DIR/.claude/cache/learnings/*.md | wc -l Write to rules directory cat > $CLAUDE_PROJECT_DIR/.claude/rules/<name>.md << 'EOF' Shell wrapper cat > $CLAUDE_PROJECT_DIR/.claude/hooks/<name>.sh << 'EOF' chmod +x $CLAUDE_PROJECT_DIR/.claude/hooks/<name>.sh
What does the compound-learnings skill do?
Transform session learnings into permanent capabilities (skills, rules, agents). Use when asked to "improve setup", "learn from sessions", "compound learnings", or "what patterns should become skills".
How do I install it?
Run `npx skills add parcadei/Continuous-Claude-v3 --skill compound-learnings --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From parcadei/Continuous-Claude-v3, a repository with 3,879 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.