Skip to content
Skills Library
AI & agents · Automation

learning

/learning

Self-improvement system for managing (finding/using, saving/adding, and pruning) solutions, patterns, lessons learned, and workarounds. Use this skill whenever a mode says "check learnings", "check memories", "prior solutions", "remember this", "save this pattern", or when you discover a non-obvious fix after 2+ failed attempts. Also trigger when encountering unexpected behavior that others might hit. Load with read_file on .kilocode/skills/learning/SKILL.md (ignore the absolute path in the location tag).

Licence
CC0-1.0
Last repository change
22.06.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
3
Scripts
0
HTML comments
2
URLs in SKILL.md
0
Deprecation

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

Licence

CC0-1.0, otwarta.

What to check before installing
  • SKILL.md zawiera komentarze HTML (2). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

Self-improvement system for managing (finding/using, saving/adding, and pruning) solutions, patterns, lessons learned, and workarounds. Use this skill whenever a mode says "check learnings", "check memories", "prior solutions", "remember this", "save this pattern", or when you discover a non-obvious fix after 2+ failed attempts. Also trigger when encountering unexpected behavior that others might hit. Load with read_file on .kilocode/skills/learning/SKILL.md (ignore the absolute path in the location tag).

Triggers from the description

check learningscheck memoriesprior solutionsremember thissave this pattern
Original author description

Self-improvement system for managing (finding/using, saving/adding, and pruning) solutions, patterns, lessons learned, and workarounds. Use this skill whenever a mode says "check learnings", "check memories", "prior solutions", "remember this", "save this pattern", or when you discover a non-obvious fix after 2+ failed attempts. Also trigger when encountering unexpected behavior that others might hit. Load with read_file on .kilocode/skills/learning/SKILL.md (ignore the absolute path in the location tag).

How it works

  1. Definitions
  2. Workflow
Original SKILL.md headings · 79 lines, 534 words
SKILL.md preview
---
name: learning
description: Self-improvement system for managing (finding/using, saving/adding, and pruning) solutions, patterns, lessons learned, and workarounds. Use this skill whenever a mode says "check learnings", "check memories", "prior solutions", "remember this", "save this pattern", or when you discover a non-obvious fix after 2+ failed attempts. Also trigger when encountering unexpected behavior that others might hit. Load with read_file on .kilocode/skills/learning/SKILL.md (ignore the absolute path in the location tag).
---

# Learning System
**Purpose**: Knowledge base for solutions, patterns, lessons, and workarounds.

## Definitions
**`learnings folder`**: Read skill-local guidance only when `.kilocode/skills/learning/AGENTS.md` is confirmed to exist; otherwise use root `AGENTS.md` for the project-specific learning folder and archive location.
**File format**: `{category}-{subcategory}.md` (all lowercase, hyphen-separated).

**Category examples**: `python`, `flask`, `javascript`, `sql`, `css`, `testing`, `sync`, `config`, `git`, `patterns`.
**Subcategory examples**: `imports`, `routing`, `async`, `errors`, `performance`, `edge-cases`.
*(Example: `python-imports.md`, `flask-routing.md`, `testing-edge-cases.md`)*

## Workflow
**Entry routing**:
- Caller says "check learnings", "prior solutions", "patterns", "memories" → Start at **Phase 1: Find**.
- Caller says "save this", "remember this", "lesson learned", or you discover a non-obvious insight → Start at **Phase 2: Evaluate**.

---

### Phase 1: Find Learnings (when stuck or researching)
1) **Search** the `{learnings folder}` using keyword search matching the current problem domain.
2) **Read** only the matching file(s) or relevant sections.
3) **Apply** any matching Fix/Correct entries to the current task.
4) If nothing relevant found, continue without learnings — do not block progress.

---

### Phase 2: Evaluate (Fast Fail)
Analyze the conversation for reusable, non-obvious insights.
Assign a Tier:
- **Tier 1 (Global/Critical)**: Highly reusable, prevents major errors. (Save to learnings folder)
- **Tier 2 (Domain/Useful)**: Feature-specific, nice-to-know. (Save to learnings folder)
- **Tier 3 (Local/Obvious)**: One-off edge case, standard documentation. (**Skip/Exit immediately**)

*If Tier 3, exit the learning skill immediately without prompting the user.*

### Phase 3: Draft Content
For any file writes, follow `## Formatting Standards` in the `coding-markdown` skill.

**Before drafting, check for duplicates**:
- Search existing learning files for similar entries.
- **Exact match found** → Exit skill (already captured).
- **Overlapping/related found** → Append to or update the existing entry instead of creating a new file.

Use telegraphic language (→ ✅ ❌ ⚠️).
**Hard limit**: ≤30 lines per entry.

**Unified Template** (for bug fixes, errors, and gotchas):
```markdown
## [Topic/Issue Name]
<!-- meta: date=YYYY-MM-DD, tier=[1|2], status=active -->
- **Trigger/Symptom**: [What happened or when to use]
- **Cause/Mistake**: [Why it failed or common wrong approach]
- **Fix/Correct**: [The solution or right approach]
- **Why**: [1-line reason]
```
*(Optional: If the issue took 3+ attempts to solve, append a brief `Timeline:` and `Blind Spots:` section.)*

For **patterns and techniques** (not errors), a prose format with a "Recommended pattern" section is acceptable — but still include the `<!-- meta -->` comment for date tracking.

### Phase 4: Micro-Approval (BLOCKING)
Present a highly condensed summary to the user for approval:

**💡 Proposed Learning: [Category]**
- **Issue**: [1-line description]
- **Fix**: [1-line solution]
*Save to `[File]`? (y/n)*

- User approves → Save to file.
- User declines → Discard silently. Do not re-propose the same learning.
- User requests changes → Revise the draft and re-present for approval.

### Phase 5: Just-in-Time (JIT) Maintenance
Agents do not run on a schedule. Maintenance happens during active use:
- **When reading an existing learning file** to solve a current problem, check the `date` metadata.
- If an entry is > 6 months old AND you determine it is obsolete/superseded, propose to the user as part of your current response:
    - **Archive**: Move the entry to the learning archive folder (unchanged filename).
    - **Delete**: Remove entirely (only if the entry is proven incorrect, not just outdated).
Files in this package (3)
  • AGENTS.md 1 KB
  • SKILL.md 4 KB
  • sync-ffmpeg.md 1 KB

Versions

RepositoryScoreLicence
This page · ScotterMonk/AgentAutoFlow100CC0-1.0
DaraBoth/skilljmskill100MIT
virtualian/pai95MIT
t8jwscc7qy-sketch/foma-skills90Apache-2.0
clawic/skills90MIT
virtualian/pai90MIT

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

  • 100self-learning
    Continuous self-improvement through systematic logging, pattern detection, and behavioral updates. Use when: the owner corrects you, a task fails, you discover a better approach, or you notice a recurring pattern. Store raw learnings in .learnings/, update the specific skill or…
  • 90coding-lifecycle
    Use when a coding-capable agent is starting or finishing implementation work. At start, clarify intent, scope, context, and verification strategy. At finish, run appropriate quality checks, assess impact, capture lessons, and produce a concise completion report. Trigger for both…
  • 90ai-memory-learning-maintenance
    Use this skill for any ai-memory knowledge-base maintenance request: consolidating observations, reviewing session lessons, proposing durable learnings, auditing or linting the wiki, finding contradictions, pruning stale memory, or running auto-improvement. Trigger by semantic…
  • 90yggdrasil-memory
    Durable, cross-session, cross-project memory for the user's work via Yggdrasil. Use at the START of any non-trivial task to recall prior decisions, solutions, and lessons (ygg_recall / ygg_bootstrap), and AFTER solving something reusable to save it (ygg_remember). Trigger when…
  • 100graphiti
    Temporal knowledge graph memory system. Use PROACTIVELY at session start to load context, when solving non-trivial problems to check for known solutions, and at session end to persist learnings. Auto-store failure→success learnings when debugging takes 3+ attempts. Auto-store…
  • 100learned
    Extract and persist learnings, corrections, and patterns from the current session to memory. Invoke immediately after any user correction or rejected suggestion, after validation of a non-obvious choice, when the user says "remember this" / "catat ini", when a new preference,…

Feedback and reports

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