learn
/learn
Extract reusable knowledge from the current session into a persistent skill. Use when you discover something non-obvious, create a workaround, or develop a multi-step workflow that future sessions would benefit from.
- Author
- pedrohcgs ↗
- Repository
- claude-code-my-workflow ↗
- Licence
- MIT
- Last repository change
- 27.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Extract reusable knowledge from the current session into a persistent skill. Use when you discover something non-obvious, create a workaround, or develop a multi-step workflow that future sessions would benefit from.
Arguments
/learn [skill-name (kebab-case)]
Original author description
Extract reusable knowledge from the current session into a persistent skill. Use when you discover something non-obvious, create a workaround, or develop a multi-step workflow that future sessions would benefit from.
How it works
- When to Use This Skill
- Workflow Phases
- Output
- Example: Creating a Skill
SKILL.md preview
--- name: learn description: | Extract reusable knowledge from the current session into a persistent skill. Use when you discover something non-obvious, create a workaround, or develop a multi-step workflow that future sessions would benefit from. argument-hint: "[skill-name (kebab-case)]" allowed-tools: ["Read", "Write", "Bash", "Glob", "Grep"] disable-model-invocation: true metadata: author: Claude Code Academic Workflow version: 1.0.0 --- # /learn — Skill Extraction Workflow Extract non-obvious discoveries into reusable skills that persist across sessions. ## When to Use This Skill Invoke `/learn` when you encounter: - **Non-obvious debugging** — Investigation that took significant effort, not in docs - **Misleading errors** — Error message was wrong, found the real cause - **Workarounds** — Found a limitation with a creative solution - **Tool integration** — Undocumented API usage or configuration - **Trial-and-error** — Multiple attempts before success - **Repeatable workflows** — Multi-step task you'd do again - **User-facing automation** — Reports, checks, or processes users will request ## Workflow Phases ### PHASE 1: Evaluate (Self-Assessment) Before creating a skill, answer these questions: 1. "What did I just learn that wasn't obvious before starting?" 2. "Would future-me benefit from this being documented?" 3. "Was the solution non-obvious from documentation alone?" 4. "Is this a multi-step workflow I'd repeat?" **Continue only if YES to at least one question.** ### PHASE 2: Check Existing Skills Search for related skills to avoid duplication: ```bash # Check project skills ls .claude/skills/ 2>/dev/null # Search for keywords grep -r -i "KEYWORD" .claude/skills/ 2>/dev/null ``` **Outcomes:** - Nothing related → Create new skill (continue to Phase 3) - Same trigger & fix → Update existing skill (bump version) - Partial overlap → Update with new variant ### PHASE 3: Create Skill Create the skill file at `.claude/skills/[skill-name]/SKILL.md`: ```yaml --- name: descriptive-kebab-case-name description: | [What the skill does, then the situations it applies to — the key use first. Include an exact error string only when that string is the trigger.] - What the skill does - Trigger conditions (symptoms; an exact error message when that is the trigger) - When to use it (contexts, scenarios) metadata: author: [you] version: "1.0" argument-hint: "[expected arguments]" # Optional --- # Skill Name ## Problem [Clear problem description — what situation triggers this skill] ## Context / Trigger Conditions [When to use — exact error messages, symptoms, scenarios] [Be specific enough that you'd recognize it again] ## Solution [Step-by-step solution] [Include commands, code snippets, or workflows] ## Verification [How to verify it worked] [Expected output or state] ## Example [Concrete example of the skill in action] ## References [Documentation links, related files, or prior discussions] ``` ### PHASE 4: Quality Gates Before finalizing, verify: - [ ] Description has specific trigger conditions (not vague) - [ ] Solution was verified to work (tested) - [ ] Content is specific enough to be actionable - [ ] Content is general enough to be reusable - [ ] No sensitive information (credentials, personal data) - [ ] Skill name is descriptive and uses kebab-case ## Output After creating the skill, report: ``` ✓ Skill created: .claude/skills/[name]/SKILL.md Trigger: [when to use] Problem: [what it solves] ``` ## Example: Creating a Skill User discovers that a specific R package silently drops observations: ```markdown --- name: fixest-missing-covariate-handling description: | Handle silent observation dropping in fixest when covariates have missing values. Use when: estimates seem wrong, sample size unexpectedly small, or comparing results between packages. metadata: author: [you] version: "1.0" --- # fixest Missing Covariate Handling ## Problem The fixest package silently drops observations when covariates have NA values, which can produce unexpected results when comparing to other packages. ## Context / Trigger Conditions - Sample size in fixest is smaller than expected - Results differ from Stata or other R packages - Model has covariates with potential missing values ## Solution 1. Check for NA patterns before regression: ```r summary(complete.cases(data[, covariates])) ``` 2. Explicitly handle NA values or use `na.action` parameter 3. Document the expected sample size in comments ## Verification Compare `nobs(model)` with `nrow(data)` — difference indicates dropped obs. ## References - fixest documentation on missing values - [LEARN:r-code] entry in MEMORY.md ```
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · pedrohcgs/claude-code-my-workflow | 100 | MIT |
| lucamartins/ouroboros | 100 | MIT |
| boykush/scraps | 100 | MIT |
| nicsuzor/academicops | 100 | MIT |
| cookys/autopilot | 100 | MIT |
| joelhooks/PAROL6 | 100 | MIT |
| tw93/Waza | 100 | MIT |
| fainir/agent-harness | 100 | MIT |
| amit429/understanding-map | 100 | MIT |
Database snapshot: 13.11.2026 · package version bac3c9d6513f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100skill-extractor
Extracts reusable skills from work sessions. Use when: (1) a non-obvious problem was solved worth preserving, (2) a pattern was discovered that would help future sessions, (3) a workaround or debugging technique needs documentation. Manual invocation only via /skill-extractor… - 100learn-eval
Extract a reusable pattern from this session and route it to where something reads it, or drop it. Use when saving what was learned in this session (今回の学びを残して). - 100hard-won-skill-extractor
Use when a tricky bug, non-obvious workaround, hidden gotcha, or undocumented behavior took real debugging effort to discover and should be captured as a reusable learned skill. - 80cmk:learn
Use when the user asks to "remember this", "save this learning", "capture the key findings", "what do we know about X", "save that gotcha", or needs to extract and record non-obvious learnings, gotchas, and valuable knowledge from conversations, research sessions, debugging,… - 100skill-capture
Turn a recurring in-session workflow into a reusable Claude Code skill. Load this the moment you notice you have run the SAME multi-step sequence (same ordered steps or commands, small variation allowed) about three times in the current session, or when open candidates are… - 100session-learning
This skill should be used when the user asks about "session learning", "learn from session", "improve future sessions", "session reflection", "session metrics", "session analysis", "/session-reflect", "req learning", "learning updates", "rollback learning", or wants to…