ctx-add-learning
Record a learning. Use when discovering gotchas, bugs, or unexpected behavior that future sessions should know about.
Best use case
ctx-add-learning is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Record a learning. Use when discovering gotchas, bugs, or unexpected behavior that future sessions should know about.
Teams using ctx-add-learning should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ctx-add-learning/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ctx-add-learning Compares
| Feature / Agent | ctx-add-learning | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Record a learning. Use when discovering gotchas, bugs, or unexpected behavior that future sessions should know about.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
Record a learning in LEARNINGS.md. ## Before Recording Three questions: if any answer is "no", don't record: 1. **"Could someone Google this in 5 minutes?"** → If yes, skip it 2. **"Is this specific to this codebase?"** → If no, skip it 3. **"Did it take real effort to discover?"** → If no, skip it Learnings should capture **principles and heuristics**, not code snippets. ## When to Use - After discovering a gotcha or unexpected behavior - When a debugging session reveals root cause - When finding a pattern that will help future work ## When NOT to Use - General programming knowledge (not specific to this project) - One-off workarounds that won't recur - Things already documented in the codebase ## Execution ```bash ctx add learning "Title" \ --context "What were you doing when you discovered this?" \ --lesson "What's the key insight?" \ --application "How should we handle this going forward?" ``` ## Quality Checklist - [ ] Context explains what happened (not just what you learned) - [ ] Lesson is a principle, not a code snippet - [ ] Application gives actionable guidance for next time - [ ] Not already in LEARNINGS.md (check first)
Related Skills
ctx-learning-add
Record a learning. Use when discovering gotchas, bugs, or unexpected behavior that future sessions should know about.
ctx-verify
Verify before claiming completion. Use before saying work is done, tests pass, or builds succeed.
ctx-skill-creator
Create, improve, test, and deploy skills. Full skill lifecycle from intent to working skill file.
ctx-sanitize-permissions
Audit tool permissions for dangerous or overly broad entries. Use to ensure safe agent configuration.
ctx-recall
Browse session history. Use when referencing past discussions or finding context from previous work.
ctx-prompt
Apply, list, and manage saved prompt templates from .context/prompts/. Use when the user asks to apply, list, or create a reusable template like code-review or refactor.
ctx-journal-normalize
Normalize journal source markdown for clean rendering. Use after journal site shows rendering issues: fence nesting, metadata formatting, broken lists.
ctx-import-plans
Import plan files into project specs directory. Use to convert external plans into project-tracked specs.
ctx-compact
Archive completed tasks and trim context. Use when context files are growing large.
ctx-check-links
Audit docs for dead links. Use before releases, after restructuring docs, or when running a documentation audit.
ctx-add-task
Add a task. Use when follow-up work is identified or when breaking down complex work into subtasks.
ctx-add-decision
Record architectural decision. Use when a trade-off is resolved or a non-obvious design choice is made that future sessions need to know.