learn

Extract a learned skill from the current conversation and classify it as Expertise or Workflow.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/atmigtnca/sidep-ops --skill learn-atmigtnca
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learn
Source: https://github.com/atmigtnca/sidep-ops/tree/main/skills/learn
Command: npx skills add https://github.com/atmigtnca/sidep-ops --skill learn-atmigtnca

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extracts a learned skill from the current conversation and codifies it as a reusable expertise/workflow artifact for future tasks.

Core Features & Use Cases

  • Distinguishes between Expertise (domain knowledge and heuristics) and Workflow (stable extraction procedures).
  • Guides iterative improvement while preserving the core workflow and context for reuse across projects.
  • Supports knowledge capture in a structured format that can be version-controlled and referenced later.

Quick Start

Identify a non-trivial insight from this conversation, classify it as Expertise or Workflow, and save it as a reusable skill artifact.

Frequently Asked Questions about learn

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture knowledge learned during a conversation into reusable documentation?

To capture knowledge learned during a conversation, the skill extracts non-trivial insights and codifies them as reusable artifacts. It identifies core principles and actionable guidance, preserving context for future projects.

What is the difference between expertise and workflow knowledge management?

Expertise captures domain knowledge and heuristics, while workflow defines stable extraction procedures. Distinguishing between them ensures insights are stored in the appropriate location with clear triggers for future reference.

How do I extract non-googleable context-specific insights from my code analysis?

You extract non-googleable context-specific insights by analyzing conversation patterns and file references. The extracted skill includes concrete references to discovered patterns and is stored as a version-controlled artifact.

Can I version-control and reference extracted expertise workflows later?

Yes, you can version-control and reference extracted expertise workflows later. The skill captures knowledge in a structured format that supports iterative improvement and can be referenced across multiple projects.

When should I not use automated skill extraction for conversation documentation?

You should avoid automated skill extraction when the conversation insight is trivial, easily searchable, or lacks concrete file references. The process specifically targets non-googleable, context-specific domain knowledge.

Does this knowledge management workflow support iterative improvement of extracted skills?

Yes, this knowledge management workflow supports iterative improvement. It guides the refinement of extracted skills while preserving the core workflow and context, ensuring stable procedures remain reusable across projects.