Skip to content
Skills Library
AI & agents · Automation

learner

/learner

Extract learned skills from conversations. Use for "learn this", "extract skill", and "capture knowledge".

Licence
Apache-2.0
Last repository change
27.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
1
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 to check before installing
  • SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

Extract learned skills from conversations. Use for "learn this", "extract skill", and "capture knowledge".

Triggers from the description

learn thisextract skillcapture knowledge
Original author description

Extract learned skills from conversations. Use for "learn this", "extract skill", and "capture knowledge".

How it works

  1. Skill: learner
  2. When to Use
  3. Skillify: 5-Step Extraction Workflow
  4. Learning Capture Process
  5. What to Learn
  6. Skill Template
  7. Output Format
  8. Quality Gate: 3 Questions
  9. Skillify Output Format
  10. Constraints
Original SKILL.md headings · 225 lines, 708 words
SKILL.md preview
---
name: learner
description: Extract learned skills from conversations. Use for "learn this", "extract skill", and "capture knowledge".
trigger: /oma:learner
---

## Skill: learner

Extract reusable skills and patterns from work sessions.

## When to Use

- After successful problem-solving
- When discovering useful patterns
- Before ending sessions with learnings
- To capture tribal knowledge
- When doing something novel well

## Skillify: 5-Step Extraction Workflow

When a repeatable task pattern emerges during a session, follow these steps to capture it as a reusable OMA skill.

### Step 1: Identify Repeatable Task
- Is this something done more than once?
- Does the context (codebase, config, environment) repeat?
- Would another agent benefit from this knowledge?

### Step 2: Extract Inputs, Steps, and Criteria
- List every input the task requires (file paths, IDs, flags, etc.)
- Document the ordered steps to complete it
- Note success criteria and failure modes

### Step 3: Decide Placement
Choose the right scope based on reusability:

| Scope | Path | When to Use |
|-------|------|-------------|
| **Built-in** | `plugins/oma/skills/` | Universal, high-value, plugin-wide |
| **User** | `~/.augment/plugins/marketplaces/oh-my-auggie/plugins/oma/skills-learned/` | Personal, machine-specific |
| **Project** | `.oma/skills/` | Team-shared, codebase-specific |

### Step 4: Draft SKILL.md with YAML Frontmatter
```markdown
---
name: {skill-name}
description: {one-line description}
trigger: /oma:{skill-name}
allowed-tools: [Read, Glob, Bash, Edit, Write]
model: sonnet4.6
---

## Skill: {skill-name}

{body content}
```

### Step 5: Flag Fuzzy Items for Human Review
Mark anything uncertain with a note:
```
<!-- TODO: Verify {item} with human before publishing -->
```
Items to flag: hard-coded values, version-dependent steps, untested edge cases.

---

## Learning Capture Process

### 1. Identify Learnings
- What worked well?
- What did we discover?
- What would we do differently?
- What patterns emerged?

### 2. Extract Pattern
- Generalize from specific
- Create reusable form
- Document context
- Add examples

### 3. Create Skill Entry
- Name the skill
- Define trigger
- Write content
- Add constraints

### 4. Integrate
- Place in skill catalog
- Update AGENTS.md
- Test with examples
- Share if valuable

## What to Learn

### Techniques
- Useful algorithms
- Efficient approaches
- Clever solutions
- Tool combinations

### Patterns
- Common structures
- Repeated solutions
- Best practices
- Anti-patterns to avoid

### Context
- When to use X vs Y
- Trade-offs made
- Constraints that matter
- Environmental factors

### Mistakes
- What went wrong
- Why it went wrong
- How to avoid
- Recovery approach

## Skill Template

```markdown
---
name: {skill-name}
description: {one-line description}
trigger: /oma:{skill-name}
---

## Skill: {skill-name}

{descriptive content}

## When to Use
{context}

## Examples
```
{examples}
```

## Constraints
{limitations}
```

## Output Format

```
## Learner: Extracted Skill

### Source Session
**Topic:** {what was learned}
**Date:** {when}
**Outcome:** {result}

### What We Learned
{key insight 1}
{key insight 2}
{key insight 3}

### Pattern Extracted
**Name:** {skill-name}
**Trigger:** /oma:{name}
**When to use:** {context}

### Skill Content
```markdown
{generated skill content}
```

### Integration
- [ ] Skill created
- [ ] Tested with examples
- [ ] Added to catalog
- [ ] Documented in project

### Next Steps
{how to apply}
```

## Quality Gate: 3 Questions

Before finalizing any extracted skill, answer all three questions. A skill should pass at least 2 of 3 to be worth capturing.

### 1. Non-Googleable?
Would a web search not readily find this solution?

- If **yes**: high value to capture (hard-won knowledge)
- If **no**: the web already has it; consider linking instead of capturing

### 2. Codebase-Specific?
Does it depend on project context, local paths, custom tooling, or undocumented behavior?

- If **yes**: strong candidate for project/project scope
- If **no**: candidate for built-in or user scope

### 3. Hard-Won?
Did it require debugging, iteration, or repeated failure to discover?

- If **yes**: high value to capture so others don't repeat the effort
- If **no**: the knowledge is likely obvious or already well-documented

---

## Skillify Output Format

When skillify is complete, report:

```
## Skillify Complete

**Skill Name:** {name}
**Target Location:** {path}
**Trigger:** /oma:{name}

### Draft Workflow
{steps extracted}

### Open Questions
- {fuzzy item 1}
- {fuzzy item 2}
```

---

## Constraints

- Extract from real work
- Generalize appropriately
- Don't overfit to specifics
- Test extracted patterns
- Keep skills focused

Versions

RepositoryScoreLicence
This page · r3dlex/oh-my-auggie100Apache-2.0
tranhieutt/software_development_department98MIT

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

  • 95SkillDistiller
    USE WHEN distill, extract skill, capture patterns, teach from conversation, learn from session, skill from conversation. Analyzes conversations to extract user guidance patterns — corrections, questions, quality gates, analysis modes — and collaboratively distills them into…
  • 80cmk:learn
    Use when the user asks to "remember this", "save this learning", "capture the key findings", "what do we know about X", "save that gotcha", or needs to extract and record non-obvious learnings, gotchas, and valuable knowledge from conversations, research sessions, debugging,…
  • 90Learn
    Create, extract, or update a skill. Use when authoring a new skill from scratch, extracting knowledge from the current session, or updating an existing skill when the user's intentions contradicted skill guidance or content is confusing/outdated.
  • 100self-improving-agent
    Curate Claude Code's auto-memory into durable project knowledge. Analyze MEMORY.md for patterns, promote proven learnings to CLAUDE.md and .claude/rules/, extract recurring solutions into reusable skills. Use when: (1) reviewing what Claude has learned about your project, (2)…
  • 100learn-eval
    Extract a reusable pattern from this session and route it to where something reads it, or drop it. Use when saving what was learned in this session (今回の学びを残して).
  • 100learn
    Extract reusable knowledge from the current session into a persistent skill. Use when you discover something non-obvious, create a workaround, or develop a multi-step workflow that future sessions would benefit from.

Feedback and reports

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