learner

Convert debugging outcomes into reusable codebase-specific skills with quality validation.

3|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/marcmunoz-uno/jailbreak --skill learner-marcmunoz-uno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learner
Source: https://github.com/marcmunoz-uno/jailbreak/tree/main/skills/learner
Command: npx skills add https://github.com/marcmunoz-uno/jailbreak --skill learner-marcmunoz-uno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps turn a complicated, codebase-specific win (a tricky bug fix, a hidden gotcha, or an undocumented behavior) into a reusable skill that can be applied to future problems instead of being forgotten.

Core Features & Use Cases

  • Skill extraction framework: Converts a real debugging episode into a structured skill with clear problem statement, exact fix, triggers, and scope.
  • Quality gate for reusability: Rejects overly generic, easily Googleable, or vague learnings to keep skills precise and actionable.
  • Expertise vs workflow separation: Classifies outcomes as either updateable expertise or stable workflow, improving safety of future improvements.
  • Project-level capture template: Provides a consistent storage approach and a skill body template so extracted skills remain discoverable and maintainable.

Quick Start

Ask the AI to extract a learner skill by providing the specific error message, the exact fix (with file paths/line numbers), and the recognition triggers from your latest debugging session.

Frequently Asked Questions about learner

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

FAQPage Schema
How do I extract reusable skills from debugging outcomes?

You extract reusable skills from debugging outcomes by providing the specific error message, exact fix with file paths, and recognition triggers to generate a structured, codebase-relevant skill for future problem solving.

What is the best way to capture project learning for undocumented behaviors?

Capturing project learning for undocumented behaviors requires classifying the outcome into either updateable expertise or stable workflow, applying a quality gate to ensure the knowledge is precise and actionable rather than vague.

How does a quality gate improve knowledge capture for tricky bug fixes?

A quality gate improves knowledge capture by rejecting overly generic, easily Googleable, or vague learnings, ensuring that only precise, codebase-specific gotchas and fixes are saved as reusable skills.

When should I classify a debugging fix as expertise instead of a workflow?

You should classify a debugging fix as expertise instead of a workflow when the outcome involves updateable knowledge, whereas stable, repeatable processes should be classified as workflow to improve the safety of future improvements.

What information do I need to start extracting a skill from a codebase-specific gotcha?

To start extracting a skill from a codebase-specific gotcha, you need the specific error message encountered, the exact fix including file paths and line numbers, and the recognition triggers that identify the problem.

Can I use this skill extraction framework for generic, easily Googleable programming errors?

No, this skill extraction framework applies a quality gate that rejects generic, easily Googleable errors, focusing solely on non-obvious gotchas, undocumented behaviors, and fixes that required real investigation.