solution-capture

Captures non-trivial problem resolutions as reusable skill directories with indexed storage.

2|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/HACK-WU/skills --skill solution-capture-hack-wu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: solution-capture
Source: https://github.com/HACK-WU/skills/tree/main/skills/solution-capture
Command: npx skills add https://github.com/HACK-WU/skills --skill solution-capture-hack-wu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After solving a tricky debugging, configuration, or deployment problem, the hard-won solution is usually lost. This Skill evaluates whether a solved problem is worth recording and, if so, persists it as a standard reusable skill so the same issue can be resolved instantly next time. ## Core Features & Use Cases - Worthiness Evaluation: Applies explicit criteria (multi-step resolution, reproducibility, non-obvious tricks) to decide whether a problem deserves recording, avoiding noise from trivial fixes. - Standard Skill Output: Writes each solution as a SKILL.md directory under a categorized .solutions/ tree (debugging, configuration, deployment, integration, architecture, performance, general), at project level or user level. - Index Maintenance & Deduplication: Checks INDEX.md before writing to avoid duplicates, then appends a structured entry with description, trigger keywords, and directory path after every capture. - Use Case: After spending an hour diagnosing a JWT token expiry bug, tell the AI to record it; the Skill creates .solutions/debugging/jwt-token-expiry/SKILL.md with the problem, step-by-step fix, and pitfalls, plus an index entry for future lookup. ## Quick Start After the AI resolves a tricky issue, say "record this solution" to have it evaluated and saved into the .solutions directory with an updated index.

Frequently Asked Questions about solution-capture

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

FAQPage Schema
How do I save a debugging solution for reuse later?

After the AI resolves a non-trivial problem, say "record this solution" or "save this solution". The Skill evaluates whether the fix involved multiple steps or non-obvious tricks, then writes it as a SKILL.md directory under .solutions/ with an updated index.

What kinds of problems are worth recording as solutions?

Record problems requiring three or more steps, documentation lookups, trial and error, or non-obvious workarounds. Skip one-line fixes, routine CRUD operations, and one-off issues that will not recur.

Where are captured solutions stored?

Solutions are stored in a project-level .solutions/ directory for project-specific issues, or a user-level ~/.solutions/ directory for cross-project knowledge. Each solution lives under a category folder like debugging, configuration, or deployment.

Does solution capture avoid duplicate entries?

Yes. Before writing, the Skill reads INDEX.md and checks for overlapping trigger keywords or similar titles. If a match exists, it updates the existing solution instead of creating a duplicate.

When should I not use solution capture?

Do not use it for simple facts (use memory instead), code-level knowledge (use a knowledge base), or trivial one-command fixes. It is designed only for complete, reusable problem-to-solution workflows.