Skip to content
Skills Library
AI & agents · Writing

squads-learn

/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.

Repository
squads-cli ↗
Licence
MIT
Last repository change
20.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 20.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Original author description

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.

How it works

  1. When to Use
  2. How to Capture
  3. Workflow Integration
  4. Examples
  5. View Learnings
  6. Key Principle
Original SKILL.md headings · 83 lines, 358 words
SKILL.md preview
---
name: squads-learn
description: 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.
---

# 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)

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

### With Context

```bash
squads 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 Task

Before 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 Tasks

Check existing learnings:
```bash
squads learnings search "auth"
squads learnings show engineering --tag auth
```

## Examples

```bash
# 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

```bash
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.

Versions

The database has no other skills named squads-learn.

Database snapshot: 13.11.2026 · package version 53902c3316f3 (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

  • 100journal-record
    Use when you've learned something worth remembering — a decision, design rationale, user behavior pattern, process learning, research finding, or style convention. Records it to the persistent team knowledge graph for future sessions.
  • 95squads-cli
    Squads CLI — operate your squads through the loop; intent in, reviewed work out. TRIGGER when running squads, dispatching agents, triaging the inbox, reading/writing memory, recording feedback, or checking status/usage.
  • 100capture-learnings
    Capture and apply accumulated knowledge via structured memory. Use when the user gives feedback, shares preferences, corrects a mistake, or when you discover something worth remembering for future conversations.
  • 100mma-journal-record
    Use when you've learned something worth remembering — a decision, design rationale, user behavior pattern, process learning, research finding, or style convention. Records it to the persistent team knowledge graph for future sessions.
  • 100pattern-learn
    Use when the user wants to extract a reusable pattern from recent work and store it for future use. "Save this as a pattern", "remember this approach", "learn from this commit".
  • 100learn
    Start autonomous knowledge building daemon — browse learnings, store findings, synthesize. Use when user wants to learn, build knowledge graph, or grow expertise.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.