capture-lessons

Convert verified debugging experience into reusable skill guidance or archived lessons.

Updated May 21, 2026
One-click install
npx skills add https://github.com/Sighthesia/just-demand --skill capture-lessons-sighthesia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: capture-lessons
Source: https://github.com/Sighthesia/just-demand/tree/main/.opencode/skills/capture-lessons
Command: npx skills add https://github.com/Sighthesia/just-demand --skill capture-lessons-sighthesia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Hard-won debugging insights and workflow lessons often disappear after a task ends, forcing future agents to rediscover the same traps. This Skill turns verified experience into retrieval-friendly guidance that shapes future Just Demand behavior. ## Core Features & Use Cases - Destination Selection: Decide whether a lesson becomes a new skill, extends an existing skill, or stays archived with the task. - Structured Capture Format: Write lessons with trigger conditions, failure modes, and preferred actions so future agents can retrieve and apply them quickly. - Boundary Enforcement: Prevent raw logs, secrets, unverified guesses, and one-off details from polluting reusable skills. - Use Case: After a long debugging session reveals a recurring state-machine trap, use this Skill to encode the trigger, symptom, and fix as a new skill under .opencode/skills/ so the next agent avoids the same mistake. ## Quick Start After verification passes on a non-trivial debugging task, ask the agent to capture the lesson learned as a reusable skill or archive it with the task.

Frequently Asked Questions about capture-lessons

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

FAQPage Schema
How do I turn a debugging session into a reusable skill?▼

After verification passes, decide whether the lesson is portable enough for a new skill, refines an existing skill, or belongs only in the task archive. Write it with trigger conditions, the visible failure mode, and the preferred action so future agents can retrieve it during routing.

When should a lesson become a new skill versus an archived note?▼

Create a new skill when the lesson is portable across modules, projects, or repos. Extend an existing skill when it refines current workflow guidance. Archive only when the lesson is task-specific, one-off, or not yet proven reusable.

What should a captured lesson include to be useful later?▼

A captured lesson should name the trigger conditions, state the user-visible failure mode or success cue, and give the preferred action in Just Demand terms. Keep the description short enough to scan during future routing decisions.

What content should not be captured as a skill?▼

Do not capture raw logs, secrets, unverified guesses, or one-off business details as reusable skills. Task-specific context belongs in the task archive, which remains the historical record for that work.

When is it correct to capture nothing after a task?▼

Capture nothing when the experience is not yet reusable, such as a single unverified occurrence or a lesson tied only to one task's business context. The valid outcomes are a new or updated skill, an archive-only lesson, or no change.