agentleFS
wrg32786wrg32786/aigent-os/skills/solution-hunt/SKILL.md

solution-hunt

Skill25 starsChanged 7 days agoMITView on GitHub

Find creative workarounds using local memory and skills. Use when a blocker requires an alternate solution.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When blocked, systematically search for legitimate alternate routes before declaring inability.

    line 8
  2. Very specific:

    Read $AIGENT_VAULT/memory/SKILL_LEDGER.md.

    line 26
  3. Very specific:

    If the solution involved a new pattern: log to memory/SKILL_CHAINS.md

    line 68
  4. Very specific:

    If it exposed a gap: log to memory/SKILL_GAPS.md

    line 69
  5. Very specific:

    If it fixed a recurring issue: log to memory/FAILURE_MODES.md via /learn-from-failure

    line 70

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/solution-hunt — Creative workaround engine

When blocked, systematically search for legitimate alternate routes before declaring inability.

Trigger

/solution-hunt <blocker description> or /solution-hunt (asks for blocker)

Flow

1. Define the blocker

From argument or ask: "What's blocking you?" Get a concrete description of what can't be done and why.

2. Search local memory

Grep the vault for related concepts, prior solutions, similar blockers:

Grep pattern: {blocker keywords} in $AIGENT_VAULT/

3. Search local skills

Read $AIGENT_VAULT/memory/SKILL_LEDGER.md. Prefix-match against taxonomy paths. Check memory/SKILL_CHAINS.md for prior chains that solved similar problems.

4. Search GitHub

mcp__github__search_repositories: "{blocker} workaround" OR "{blocker} alternative"
mcp__github__search_code: "{specific error or API}" language:typescript OR language:python

5. Search docs and web

mcp__tavily__tavily_search: "{blocker} workaround" OR "{blocker} alternative solution"
mcp__tavily__tavily_extract: {relevant doc URLs found}

6. Identify 3 routes

RouteDescription
Direct fixSolve the root cause — fix the bug, update the dep, change the config
WorkaroundLegitimate alternate path — different API, different tool, decompose the task
Replace componentSwap the blocking tool/dependency entirely

7. Rank by tradeoffs

FactorWeight
Speed to implementHigh
Risk of side effectsHigh
MaintainabilityMedium
Cost (tokens, API calls, money)Medium

8. Present top 3

For each route, show:

  • Description (1-2 sentences)
  • Tradeoffs (speed/risk/maintenance)
  • Confidence (high/medium/low)
  • Implementation steps (3-5 bullets)

9. Execute chosen path

On user selection, implement the chosen route. If it requires a new skill, route through /skill-hunt.

10. Capture learning

  • If the solution involved a new pattern: log to memory/SKILL_CHAINS.md
  • If it exposed a gap: log to memory/SKILL_GAPS.md
  • If it fixed a recurring issue: log to memory/FAILURE_MODES.md via /learn-from-failure

Hard Boundary

Creative workaround means legitimate alternate route. NEVER:

  • Bypass access controls or authentication
  • Violate terms of service of any platform
  • Exploit security vulnerabilities
  • Hide behavior from the principal
  • Bypass paywalls or rate limits through exploits
  • Use credentials from screenshots or logs

Per [[Capability Expansion Doctrine]] — the authority matrix governs what the AIgent may do. Expansion does not override authority levels.

Related

  • [[concepts/Capability Expansion Doctrine]] — the doctrine this skill serves
  • [[memory/SKILL_LEDGER]] — local capability index
  • [[memory/SKILL_CHAINS]] — proven multi-skill sequences
  • [[memory/FAILURE_MODES.md]] — where failure learnings land
  • /skill-hunt — external search when local solutions don't exist
  • /learn-from-failure — structured failure capture

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.