How do I install the Squads Learn skill?

Run npx skillmds@latest add tomevault-io/squads-learn in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Squads Learn safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Squads Learn?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Squads Learn free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Squads Learn?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Squads Learn by tomevault-io — Agent Skill

Name: Squads Learn
Author: tomevault-io

Squads Learn

Capture learnings after completing work. Use when finishing a task, fixing a bug, discovering a pattern, or learning something worth remembering for future sessions. Helps build institutional memory. Use when this capability is needed.

tomevault-io e466b3e 2 files · 3.4 KB Updated Sep 17, 2026

File contents

Capture Learnings

After completing work, capture what you learned so future sessions can benefit.

When to Use

After fixing a bug - What was the root cause? How did you find it?
After completing a feature - What approach worked? What didn't?
After research - What did you discover? What's the key insight?
When you notice a pattern - Something that works consistently

How to Capture

Quick Learning (one-liner)

squads learn "The auth token needs to be refreshed after 1 hour, not when the API returns 401"

With Context

squads learn "Always check memory before researching to avoid duplicate work" \
  --squad engineering \
  --category pattern \
  --tags "memory,research,efficiency"

Workflow Integration

End of Task

Before marking a task complete, ask yourself:

What worked that I should remember?
What didn't work that I should avoid?
Is there a pattern here worth capturing?

If yes to any → squads learn "<insight>"

Before Similar Tasks

Check existing learnings:

squads learnings search "auth"
squads learnings show engineering --tag auth

Examples

# After fixing a bug
squads learn "PostgreSQL connection pool exhaustion was caused by unclosed transactions in error paths" --category failure --tags db,postgres,connection

# After successful implementation
squads learn "Using TypeScript strict mode caught 3 type errors before runtime" --category success --tags typescript,types

# Noticing a pattern
squads learn "When context exceeds 70%, always run squads memory sync before continuing" --category pattern --tags context,memory

# General tip
squads learn "The gh CLI is faster than the GitHub API for simple operations" --category tip --tags github,cli

View Learnings

squads learnings show <squad>           # Squad's learnings
squads learnings search "<query>"       # Search all learnings
squads learnings show engineering -n 5  # Last 5 for engineering

Key Principle

Learnings compound. Each captured insight makes future sessions smarter. A 30-second squads learn call can save hours of re-discovery.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: squads-learndescription: Capture learnings after completing work. Use when finishing a task, fixing a bug, discovering a pattern, or learning something worth remembering for future sessions. Helps build institutional memory. Use when this capability is needed.---# Capture LearningsAfter completing work, capture what you learned so future sessions can benefit.## When to Use- **After fixing a bug** - What was the root cause? How did you find it?- **After completing a feature** - What approach worked? What didn't?- **After research** - What did you discover? What's the key insight?- **When you notice a pattern** - Something that works consistently## How to Capture### Quick Learning (one-liner)```bashsquads learn "The auth token needs to be refreshed after 1 hour, not when the API returns 401"```### With Context```bashsquads learn "Always check memory before researching to avoid duplicate work" \ --squad engineering \ --category pattern \ --tags "memory,research,efficiency"```### Categories- `success` - Something that worked well- `failure` - Something that didn't work (learn from mistakes)- `pattern` - A reusable approach- `tip` - General advice## Workflow Integration### End of TaskBefore marking a task complete, ask yourself:1. What worked that I should remember?2. What didn't work that I should avoid?3. Is there a pattern here worth capturing?If yes to any → `squads learn "<insight>"`### Before Similar TasksCheck existing learnings:```bashsquads learnings search "auth"squads learnings show engineering --tag auth```## Examples```bash# After fixing a bugsquads learn "PostgreSQL connection pool exhaustion was caused by unclosed transactions in error paths" --category failure --tags db,postgres,connection# After successful implementationsquads learn "Using TypeScript strict mode caught 3 type errors before runtime" --category success --tags typescript,types# Noticing a patternsquads learn "When context exceeds 70%, always run squads memory sync before continuing" --category pattern --tags context,memory# General tipsquads learn "The gh CLI is faster than the GitHub API for simple operations" --category tip --tags github,cli```## View Learnings```bashsquads learnings show <squad> # Squad's learningssquads learnings search "<query>" # Search all learningssquads learnings show engineering -n 5 # Last 5 for engineering```## Key Principle**Learnings compound.** Each captured insight makes future sessions smarter. A 30-second `squads learn` call can save hours of re-discovery.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/agents-squads) — claim your Tome and manage your conversions.

Frequently asked questions