learning-capturer

Captures solved debugging sessions from Littlebird screen capture into a greppable personal knowledge base.

84|37|Updated May 23, 2026
One-click install
npx skills add https://github.com/legioncodeinc/vibe-coding-tools --skill learning-capturer-legioncodeinc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: learning-capturer
Source: https://github.com/legioncodeinc/vibe-coding-tools/tree/main/src/quarantine/skills/keep/learning-capturer
Command: npx skills add https://github.com/legioncodeinc/vibe-coding-tools --skill learning-capturer-legioncodeinc

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Developers repeatedly re-debug problems they already solved because the fix lived in a terminal scrollback or chat session that is long gone. This Skill watches Littlebird capture for moments where something broke and then stopped being broken, and files each solve into a personal, greppable knowledge base keyed on the literal error text you will search for next time. ## Core Features & Use Cases - Solve Detection Pipeline: Runs six retrieval sweeps over Littlebird capture to find the three-phase shape of a solve (error surfaces, grind, cessation plus resumption), then classifies each candidate as solved, abandoned, solved by someone else, or solved by an AI assistant without understanding. - Greppable Knowledge Base: Writes one markdown file per entry with a verbatim SEARCH line, pinned versions, root cause status, the fix, what did not work, and an occurrence log, plus a generated INDEX.md, an open-walls ledger, and a permanent rejection ledger. - Mandatory Secret Scrubbing: Scrubs credentials from error strings before any comparison or report, using structure-preserving placeholders, and raises rotation flags without ever printing a matched value. - Use Case: After a painful debugging session, ask the Skill to capture what you learned; it drafts an entry from the actual capture, you approve or reject it, and months later a grep for the error string returns the exact fix. ## Quick Start Ask the assistant to capture what you learned from today's debugging session and file it into your knowledge base.

Frequently Asked Questions about learning-capturer

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

FAQPage Schema
How do I build a personal knowledge base of debugging fixes?▼

Run the learning-capturer skill after a hard session or via its weekly routine. It reads Littlebird capture, detects where an error appeared and then stopped, and drafts a knowledge base entry keyed on the literal error string, which you approve before anything is written.

How does the skill detect that a problem was actually solved?▼

It looks for a three-phase shape in timestamp-sorted capture: an error surfaces, a grind phase of searching and trying, then the error stops appearing and the original work resumes. Both halves of the final phase are required; cessation alone is filed as abandoned.

Does learning-capturer work without the Littlebird MCP?▼

No. The skill requires the Littlebird MCP on a Power or Pro plan and stops if no Littlebird tools are present. It cannot reconstruct a solve from your description because the forgotten detail is the point of the capture.

How are API keys and passwords in error messages handled?▼

A mandatory scrubbing pass runs before any comparison, report, or write. Secrets are replaced with structure-preserving placeholders like [USER]:[PASSWORD], matched values are never printed, and any credential found on screen raises a rotation flag naming only the field, time, and app.

What happens when I hit the same error a second time?▼

The dedupe check scores the new symptom against existing entries and the rejection ledger. A recurrence updates the existing entry's occurrence log instead of creating a duplicate, and four or more occurrences escalate to the top of the report with a proposed structural fix.

When should I not use learning-capturer?▼

Do not use it for documenting a procedure that worked the first time, which belongs to the sop-forge skill, or for general note-taking. It only files problems that were observed breaking and then resolved in capture.