Searches project and user solution indexes to reuse previously documented fixes.
npx skills add https://github.com/HACK-WU/skills --skill solution-lookup-hack-wu
Please help me install this Agent Skill. Skill: solution-lookup Source: https://github.com/HACK-WU/skills/tree/main/skills/solution-lookup Command: npx skills add https://github.com/HACK-WU/skills --skill solution-lookup-hack-wu
.solutions/ or user-level ~/.solutions/ libraries, so prior experience is reused instead of repeating the same troubleshooting work. ## Core Features & Use Cases - Dual-level search: Reads both .solutions/INDEX.md (project) and ~/.solutions/INDEX.md (user), with project-level results taking priority. - Keyword matching: Extracts 3-6 keywords from the current problem (tech stack, error symptoms, operation type) and scores matches against each record's trigger keywords. - Guided reuse: Loads the matched solution's SKILL.md and scripts, presents a summary for user confirmation, then executes the documented steps. - Use Case: You hit a JWT token expiry error. The Skill extracts keywords like jwt, token, 过期, finds a matching entry in the index, loads the documented fix, and walks you through applying it. ## Quick Start Ask the AI to check whether there is an existing solution for the current error before starting to troubleshoot it.High-intent search queries and answers about installing and using this skill.
Extract 3-6 keywords from the error covering the tech stack, symptoms, and operation, then match them against the trigger keywords in .solutions/INDEX.md and ~/.solutions/INDEX.md. Matching entries are loaded and their documented steps are executed.
Project-level solutions live in .solutions/ and are version-controlled with the project, while user-level solutions live in ~/.solutions/ and apply across projects. When both match, the project-level solution takes priority.
Matching compares extracted keywords against each record's trigger keywords using exact and containment matching. Hitting two or more keywords is a strong match, one keyword is a weak suggestion, and zero hits means no existing solution.
The lookup is non-blocking: the AI reports that no match was found, lists how many records were searched, and proceeds with normal troubleshooting. After resolving the issue, the solution-capture skill can be used to document the new fix.
No. The lookup phase only reads and reuses solutions; it never edits them. Updates to existing solutions are handled separately through the solution-capture update workflow.
slbugParses Ruby/Rails/Grape solution files with YAML frontmatter and indexes categories.
JBonfimConvert code, issues, or technical context into detailed prompts for LLMs.
hiyenwongIndex local SKILL.md documents into a SQLite vector search index.
yusufcmgResearch existing tools and patterns before coding to prioritize reuse.