Learn add
Add a lesson to a skill LEARN.md file, routing feedback to skill, template, or context learning. Use when capturing workflow lessons.From its SKILL.md
npx -y skills add parhumm/jaan-to --skill learn-addAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
What its file declares
Copied from the file, not written here
The file declares its own license as PROPRIETARY. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
5.4 KB, as published. Nobody here has run it
learn-add
Route feedback to the appropriate LEARN.md file.
Context Files
$JAAN_LEARN_DIR/*.learn.md- Skill lessons$JAAN_CONTEXT_DIR/*.md- Context files and lessons${CLAUDE_PLUGIN_ROOT}/docs/extending/language-protocol.md- Language resolution protocol
Input
Arguments: $ARGUMENTS
Expected format: "target" "lesson"
- Target: skill name,
$JAAN_TEMPLATES_DIR/name, or$JAAN_CONTEXT_DIR/name - Lesson: the feedback to add
Examples:
/jaan-to:learn-add "pm-prd-write" "Always ask about rollback strategy"/jaan-to:learn-add "$JAAN_CONTEXT_DIR/tech" "All new tables need soft delete"
If no input provided, ask for target and lesson.
Pre-Execution Protocol
Language Settings
Read and apply language protocol: ${CLAUDE_PLUGIN_ROOT}/docs/extending/language-protocol.md
Override field for this skill: language_learn-add
PHASE 1: Analysis (Read-Only)
Step 1: Parse Input
Extract target and lesson from arguments.
If format is unclear:
- "Which skill/context should this lesson apply to?"
- "What is the lesson to add?"
Step 2: Determine Target File
Route based on target:
| Target Pattern | LEARN.md Location |
|---|---|
Skill name (e.g., pm-prd-write) | $JAAN_LEARN_DIR/jaan-to-{skill}.learn.md |
System skill (e.g., skill-create) | $JAAN_LEARN_DIR/jaan-to-{skill}.learn.md |
$JAAN_TEMPLATES_DIR/{name} | $JAAN_TEMPLATES_DIR/LEARN.md |
$JAAN_CONTEXT_DIR/{name} | $JAAN_CONTEXT_DIR/LEARN.md |
$JAAN_CONTEXT_DIR/tech | $JAAN_CONTEXT_DIR/tech.md (constraints section) |
$JAAN_CONTEXT_DIR/team | $JAAN_CONTEXT_DIR/team.md (norms section) |
Step 3: Auto-Categorize Lesson
Detect category from lesson keywords:
| Category | Trigger Keywords |
|---|---|
| Better Questions | ask, question, clarify, confirm, "should ask" |
| Edge Cases | edge, special, case, handle, check, "need to handle" |
| Workflow | workflow, process, step, order, "before/after" |
| Common Mistakes | avoid, mistake, wrong, don't, never, "should not" |
If unclear, ask: "Which category? [questions/edge-cases/workflow/mistakes]"
Step 4: Read Current LEARN.md
Read the target LEARN.md file if it exists at $JAAN_LEARN_DIR/jaan-to-{name}.learn.md.
If not found, check legacy path $JAAN_LEARN_DIR/jaan-to:{name}.learn.md — if legacy found, rename it to the dash-prefixed path first.
If neither exists, prepare to create with template.
HARD STOP - Human Review Check
Show preview:
Ready to Add Lesson
**File:** {file path}
**Category:** {category}
**Lesson:** {lesson text}
Preview:
## {Category}
- {existing lessons...}
- {new lesson} <-- NEW
Confirm? [y/n/edit]
Do NOT proceed without explicit approval.
PHASE 2: Write
Step 5: Update LEARN.md
If file exists:
- Read current content
- Find the category section (e.g.,
## Better Questions) - Append new lesson as bullet point
- Update "Last updated" date
- Write file
If file doesn't exist:
- Check if plugin has seed data:
${CLAUDE_PLUGIN_ROOT}/skills/{skill-name}/LEARN.md - If seed exists and has meaningful content (contains
-bullet points), use it as starting point - If no seed exists, create from the template below
- Add the new lesson to the appropriate category
- Write file to:
$JAAN_LEARN_DIR/jaan-to-{skill-name}.learn.md
LEARN.md Template
# Lessons: {skill-name}
> Last updated: {date}
## Better Questions
- {lesson if category matches}
## Edge Cases
- {lesson if category matches}
## Workflow
- {lesson if category matches}
## Common Mistakes
- {lesson if category matches}
Step 6: Confirm Write
Lesson Added
**File:** {path}
**Category:** {category}
**Lesson:** {lesson}
Step 7: Offer to Commit
Ask user:
Commit this lesson? [y/n]
If confirmed:
- Stage:
git add {file_path} - Commit:
git commit -m "learn({skill}): {short lesson summary}" - Show: "Lesson committed:
{commit hash}"
If declined:
- Skip commit, lesson is saved locally
- Show: "Lesson saved (not committed)"
Error Handling
No Target
"No target specified. Which skill or context should this lesson apply to?"
Target Not Found
"Skill '{target}' not found. Available skills: {list}"
Empty Lesson
"No lesson provided. What feedback should be remembered?"
LEARN.md Create Fail
"Could not create LEARN.md. Check file permissions."
Trust Rules
- NEVER modify without user confirmation
- ALWAYS show preview before writing
- PRESERVE existing lessons
- ASK when category is unclear
Skill Alignment
- Two-phase workflow with HARD STOP for human approval
- Single source of truth (no duplication)
- Plugin-internal automation
- Maintains human control over changes
Definition of Done
- Target skill/context identified and validated
- Lesson categorized (questions/edge-cases/workflow/mistakes)
- Preview shown and user approved
- LEARN.md file updated with new lesson
- Commit offered to user