Skip to content
Skills Library
Programming · Automation

learn-pattern

/learn-pattern

Save a new error pattern to memory for future recognition. When you discover a new error pattern and its fix, use this to remember it. Saved to patterns.yaml, matched during investigate_alert and debug_prod.

Repository
skills ↗
Licence
Apache-2.0
Last repository change
27.10.2026

Assessment and security

90/ 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.
Content25 / 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 27.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Save a new error pattern to memory for future recognition. When you discover a new error pattern and its fix, use this to remember it. Saved to patterns.yaml, matched during investigate_alert and debug_prod.

Original author description

Save a new error pattern to memory for future recognition. When you discover a new error pattern and its fix, use this to remember it. Saved to patterns.yaml, matched during investigate_alert and debug_prod.

How it works

  1. Inputs
  2. Workflow
  3. Key MCP Tools
  4. Note
Original SKILL.md headings · 59 lines, 275 words
SKILL.md preview
---
name: learn-pattern
description: Save a new error pattern to memory for future recognition. When you discover a new error pattern and its fix, use this to remember it. Saved to patterns.yaml, matched during investigate_alert and debug_prod.
---

# Learn Pattern

Saves error patterns to memory for future debugging sessions.

## Inputs

| Input      | Type   | Default   | Purpose                                            |
| ---------- | ------ | --------- | -------------------------------------------------- |
| `pattern`  | string | required  | Short name (e.g., "OOMKilled", "ImagePullBackOff") |
| `meaning`  | string | required  | What the error means                               |
| `fix`      | string | required  | How to fix it                                      |
| `commands` | string | -         | Comma-separated diagnosis commands                 |
| `category` | string | "general" | pod_errors, log_patterns, network, general         |

## Workflow

### 1. Validate Inputs

- pattern, meaning, fix required
- Return error if any missing

### 2. Parse Commands

- Split by comma, strip whitespace

### 3. Optional: Validate Tool Names

- If commands provided: check tool names exist in MCP registry
- Warn if CLI commands (kubectl, oc) — suggest MCP tools

### 4. Save Pattern

- Read `memory/learned/patterns.yaml`
- Ensure category exists
- Build entry: pattern, meaning, fix, commands (if any)
- If pattern exists in category: update; else append
- Write back with last_updated

### 5. Log (if success)

- `memory_session_log("Learned pattern: {pattern}", "Category: {category}, Action: added|updated")`

### 6. Output

- Success: "Pattern added/updated", details, "Will be matched during investigate_alert and debug_prod"
- Failure: validation error or save error

## Key MCP Tools

- `memory_read` — read patterns (or file read)
- `memory_write` / file write — save to `memory/learned/patterns.yaml`
- `memory_session_log` — session logging
- Alternative: `learn_tool_fix` for tool-specific fixes (different from general patterns)

## Note

For tool-specific fixes (e.g., bonfire_deploy + "manifest unknown"), use `learn_tool_fix` instead. This skill is for general error patterns used across skills.

Versions

RepositoryScoreLicence
This page · dmzoneill/skills90Apache-2.0
rkawaishi/workato-dev-kit100MIT
rkawaishi/workato-dev-kit100MIT
rkawaishi/workato-dev-kit100MIT
rkawaishi/workato-dev-kit84MIT

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

  • 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".
  • 100pattern-recognition
    Identify and apply existing codebase patterns for consistency. TRIGGER when: writing new code that should match conventions, or reviewing code for pattern drift. SKIP: language-specific patterns (use python-patterns or react-patterns); security review (use…
  • 100write-design-pattern
    Write a design pattern catalog entry. Use when the user asks to document a design pattern, add a pattern to the catalog, or after a refactoring session identifies a reusable pattern.
  • 92pattern-recognition-specialist
    Analyzes code for design patterns, anti-patterns, naming conventions, and duplication. Use when checking codebase consistency or verifying new code follows established patterns.
  • 100learn
    Applies this rulebook's research method to a new admin portal (Stripe, Linear, Vercel or any portal the user has legitimate access to) and proposes rule changes with evidence for a pull request to the anydash repo. Runs the ui-pattern-mining skill read-only through REA or…
  • 100systematic-debugging
    Use when something is broken — an error message, stack trace, failing test, crash, wrong output, "it doesn't work", build failure, or unexpected behavior. Finds the root cause with evidence before changing code, then saves the fix to memory.

Feedback and reports

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