learner

Extract debugging insights, fixes, and triggers from troubleshooting conversations.

28|5|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/MeroZemory/oh-my-droid --skill learner-merozemory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learner
Source: https://github.com/MeroZemory/oh-my-droid/tree/main/skills/learner
Command: npx skills add https://github.com/MeroZemory/oh-my-droid --skill learner-merozemory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Learner eliminates the loss of hard-earned, project-specific debugging knowledge by guiding you through capturing the exact insight, triggers, and fixes before they fade from memory.

Core Features & Use Cases

  • Structured extraction: Walks you through documenting the precise problem statement, solution, and actionable triggers from your deep-dive investigations.
  • Quality guardrails: Emphasizes non-Googleable, hard-won discoveries that justify the effort to preserve within the Factory Droid project.
  • Use Case: After debugging a race condition in the orchestration layer, use Learner to save the exact error signature, root-cause fix, and warning signs so future agents can recognize and prevent it quickly.

Quick Start

Use the learner skill to record the problem, solution, triggers, and scope for a recently solved non-obvious bug.

Frequently Asked Questions about learner

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

FAQPage Schema
How do I capture project-specific debugging knowledge from a resolved troubleshooting conversation?

Capture project-specific debugging knowledge by extracting the problem statement, precise fix, triggers, and scope from completed troubleshooting conversations. This preserves non-Googlable solutions to guide future agents in project-level learning and prevent recurring issues.

What kind of debugging insights should I document for future agents?

Document hard-won, non-Googlable debugging insights that justify preservation. Focus on precise problem statements, root-cause fixes, error signatures, and warning signs discovered during deep investigations within your specific project automation stack.

How do I record a non-obvious bug fix within the Factory Droid automation stack?

Record a non-obvious bug fix by walking through structured extraction of the problem, solution, and actionable triggers. This documents the exact error signature and scope so future agents can recognize and prevent the race condition quickly.

When should I use a structured skill capture process for troubleshooting results?

Use skill capture when you have resolved a complex, non-Googlable bug through deep investigation. It is designed for hard-won discoveries like race conditions in orchestration layers where preserving exact triggers prevents future agent errors.

Does capturing debugging lessons require any specific dependencies or environment setup?

Capturing debugging lessons requires no external dependencies. It operates entirely within the Factory Droid automation stack to guide you through documenting problem statements and fixes using only your completed troubleshooting context.