learn

Extract and document non-obvious learnings and multi-step workflows from user sessions.

1|1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/xashgg/claude-code-my-workflow-codex --skill learn-xashgg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learn
Source: https://github.com/xashgg/claude-code-my-workflow-codex/tree/main/.codex/skills/learn
Command: npx skills add https://github.com/xashgg/claude-code-my-workflow-codex --skill learn-xashgg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users extract and document non-obvious knowledge, workarounds, and multi-step workflows from their sessions, making it easily accessible and reusable in future sessions.

Core Features & Use Cases

  • Skill Extraction: Document and create reusable skills from non-obvious learnings.
  • Avoid Duplication: Check for existing skills to avoid duplication and enhance efficiency.
  • Multi-Step Workflow: Capture and document complex workflows for future reference.
  • Use Case: When you encounter a non-standard issue during your work and develop a creative solution, use this Skill to document the process and create a reusable skill for future sessions.

Quick Start

To create a new skill, run the command: /learn [skill-name]

Frequently Asked Questions about learn

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

FAQPage Schema
How do I document non-obvious learnings and workflows from my sessions?

To document non-obvious learnings, you can extract and capture creative solutions from your sessions. This process evaluates your findings, checks for existing skills to avoid duplication, and creates detailed, reusable knowledge for future workflows.

What is the best way to capture multi-step workflows for future reference?

Capturing multi-step workflows involves documenting complex processes and non-standard workarounds encountered during work. This approach extracts session knowledge and creates detailed skill descriptions to enhance future workflow efficiency and accessibility.

How do I avoid duplicating effort when creating new skills from session knowledge?

To avoid duplicating effort when creating skills, you must check for existing skills before documenting new learnings. This ensures your captured session knowledge remains unique, preventing redundant workflow documentation and enhancing overall efficiency.

Can I create a reusable skill from an ad-hoc workaround I developed?

Yes, you can create a reusable skill from an ad-hoc workaround. The process extracts your non-obvious learnings, evaluates them against existing skills, and documents the multi-step workflow into a detailed skill for future sessions.

When do I need to use workflow documentation for knowledge capture?

You need workflow documentation for knowledge capture when you encounter a non-standard issue and develop a creative solution. Documenting this session learning transforms temporary workarounds into reusable skills, making complex processes accessible for future reference.

Are there limitations to extracting knowledge from sessions?

A limitation of extracting knowledge from sessions is that it requires you to manually evaluate learnings and check for existing skills. This means it works best for non-obvious, multi-step workflows rather than simple, automated tasks.