learn

Capture and organize learnings from completed work into Markdown files.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mariasebarespersona/Tum-AI --skill learn-mariasebarespersona
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learn
Source: https://github.com/mariasebarespersona/Tum-AI/tree/main/.claude/skills/learn
Command: npx skills add https://github.com/mariasebarespersona/Tum-AI --skill learn-mariasebarespersona

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture and organize learnings from completed work to help the team remember patterns, avoid repeated mistakes, and improve future outcomes.

Core Features & Use Cases

  • Capture learnings from completed tasks and store them in docs/learnings/ as searchable Markdown files.
  • Classify learnings as patterns, gotchas, decisions, or external observations to promote reuse.
  • Promote durable learnings to rules, skills, or memory as needed.

Quick Start

After completing a task, capture a concise insight and save it to docs/learnings/.

Frequently Asked Questions about learn

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture learnings from completed tasks to avoid repeating mistakes?

Capture learnings from completed tasks by extracting concise insights and saving them as searchable Markdown files in docs/learnings/. This helps teams remember patterns, avoid repeated mistakes, and improve future outcomes.

What's the best way to document workarounds and reusable patterns for future reference?

Document workarounds and reusable patterns by applying a retrospective process after non-obvious discoveries. Store these insights as classified Markdown files in docs/learnings/ so they remain searchable and accessible for future work.

When should I capture a learning from a completed task?

Capture a learning after completing a task where something non-obvious was discovered, a workaround was needed and corrected, or a reusable pattern emerged. This ensures durable knowledge is preserved for future reference.

Can I promote captured insights into rules or memory?

Promote durable learnings to rules, skills, or memory as needed. Classifying captured insights as patterns, gotchas, decisions, or external observations helps determine when to promote them for broader reuse.

Does this approach require any specific dependencies or frameworks?

No specific dependencies or frameworks are required. The approach works by storing learnings as searchable Markdown files in docs/learnings/, making it compatible with any standard documentation workflow.

How do I organize retrospective insights by pattern or gotcha?

Organize retrospective insights by classifying captured learnings as patterns, gotchas, decisions, or external observations. This classification promotes reuse and helps teams quickly find relevant knowledge in the docs/learnings/ directory.