MCP HubMCP Hub
스킬 목록으로 돌아가기

forage-solutions

pjt222
업데이트됨 2 days ago
4 조회
17
2
17
GitHub에서 보기
테스팅aidesign

정보

이 기술은 개미 군집 최적화를 사용해 여러 해결 경로를 병렬로 탐색하며, 유망한 접근법을 강화하고 막다른 길은 적절히 포기합니다. 원인이 명확하지 않거나 초기 해결책이 최적이 아닌 복잡한 문제 디버깅에 이상적입니다. 개발자는 이를 통해 경쟁 가설을 체계적으로 테스트하고, 미흡한 해결책에 성급하게 수렴하는 것을 피할 수 있습니다.

빠른 설치

Claude Code

추천
기본
npx skills add pjt222/agent-almanac -a claude-code
플러그인 명령대체
/plugin add https://github.com/pjt222/agent-almanac
Git 클론대체
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/forage-solutions

Claude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요

문서

Forage Solutions

Explore solution space via ant colony opt — deploy indep hypotheses as scouts, reinforce promising via evidence, detect diminishing returns, know when abandon strategy + explore elsewhere.

Use When

  • Problem w/ multiple plausible approaches, no clear winner
  • First approach not working but alts unclear
  • Debug w/ no obvious root cause — multiple hypotheses need parallel
  • Search codebase for behavior source, location unknown
  • Previous attempts converged prematurely suboptimal
  • Complement build-coherence when space must be explored before decision

In

  • Required: Problem/goal (what foraging for?)
  • Required: Current knowledge state (what already known?)
  • Optional: Previous approaches + outcomes
  • Optional: Exploration constraints (time, tool availability)
  • Optional: Urgency (affects explore-exploit balance)

Do

Step 1: Map Landscape

Before deploying, characterize shape.

Solution Distribution Types:
┌────────────────────┬──────────────────────────────────────────────────┐
│ Type               │ Characteristics and Strategy                     │
├────────────────────┼──────────────────────────────────────────────────┤
│ Concentrated       │ One correct answer exists (bug fix, syntax       │
│ (one right fix)    │ error). Deploy many scouts quickly to locate     │
│                    │ it. Exploit immediately when found               │
├────────────────────┼──────────────────────────────────────────────────┤
│ Distributed        │ Multiple valid approaches (architecture choice,  │
│ (many valid paths) │ implementation strategy). Scouts assess quality  │
│                    │ of each. Use `build-coherence` to choose         │
├────────────────────┼──────────────────────────────────────────────────┤
│ Ephemeral          │ Solutions depend on timing or sequence (race     │
│ (time-sensitive)   │ conditions, order-dependent bugs). Fast scouting │
│                    │ with immediate exploitation. Cannot revisit       │
├────────────────────┼──────────────────────────────────────────────────┤
│ Nested             │ Solving the surface problem reveals a deeper one │
│ (layers of cause)  │ (config issue masking an architecture problem).  │
│                    │ Scout at each layer before committing to depth   │
└────────────────────┴──────────────────────────────────────────────────┘

Classify. Distribution type → how many scouts + how fast switch exploration → exploitation.

→ Clear characterization informs scouting. Feels accurate not forced.

If err: completely unknown → itself = classification. Treat as potentially distributed + deploy broad scouts. First round reveals character.

Step 2: Deploy Scout Hypotheses

Gen indep hypotheses as scouts. Each probes diff direction.

  1. Gen 3-5 indep hypotheses about problem/solution
  2. Each → 1 cheap test (single file read, 1 grep, 1 check)
  3. Rate initial promise on evidence (not gut)
  4. Deploy indep: no let A influence test of B
Scout Deployment Template:
┌───────┬──────────────────────┬──────────────────────┬──────────┐
│ Scout │ Hypothesis           │ Test (one action)    │ Promise  │
├───────┼──────────────────────┼──────────────────────┼──────────┤
│ 1     │                      │                      │ High/Med/│
│ 2     │                      │                      │ Low      │
│ 3     │                      │                      │          │
│ 4     │                      │                      │          │
│ 5     │                      │                      │          │
└───────┴──────────────────────┴──────────────────────┴──────────┘

Key: scouts assess not exploit. Quick signal each, not deep investigation first promising.

→ 3-5 indep hypotheses + cheap tests. None deeply explored yet — breadth-first pass.

If err: <3 hypotheses → (a) very constrained (concentrated — good, scout aggressive) or (b) understanding too shallow (read more context). Hypotheses not indep (variations same) → too narrow, force ≥1 contradicting others.

Step 3: Trail Reinforcement — Follow Evidence

After scout results, reinforce promising, let weak decay.

  1. Review results: which found supporting evidence?
  2. Strong evidence → reinforce: invest more investigation
  3. No evidence → decay: don't investigate w/o new signals
  4. Contradicting → inhibition: actively avoid
  5. Monitor premature convergence: all effort to first reinforced → force 1 scout into unexplored
Trail Reinforcement Decision:
┌───────────────────────────┬──────────────────────────────────────┐
│ Scout Result              │ Action                               │
├───────────────────────────┼──────────────────────────────────────┤
│ Strong supporting evidence│ REINFORCE — deepen investigation     │
│ Weak supporting evidence  │ HOLD — one more cheap test before    │
│                           │ committing                           │
│ No evidence               │ DECAY — deprioritize, scout elsewhere│
│ Contradicting evidence    │ INHIBIT — mark as dead end           │
│ Ambiguous result          │ REFINE — hypothesis was too vague,   │
│                           │ sharpen and re-scout                 │
└───────────────────────────┴──────────────────────────────────────┘

→ Clear prioritization on evidence not preference. Strongest gets most but ≥1 alt alive.

If err: all empty → hypotheses wrong, not approach. Reframe: "What assumptions could be wrong?" Gen new from diff angle. All strong → distributed (multiple valid) → build-coherence for selection.

Step 4: Marginal Value Theorem — Know When Leave

Monitor yield. Info per effort drops below avg across all → switch.

Marginal Value Assessment:
┌────────────────────────┬──────────────────────────────────────────┐
│ Signal                 │ Action                                   │
├────────────────────────┼──────────────────────────────────────────┤
│ New information per    │ CONTINUE — this trail is productive      │
│ action is high         │                                          │
├────────────────────────┼──────────────────────────────────────────┤
│ New information per    │ PREPARE TO SWITCH — squeeze remaining    │
│ action is declining    │ value, begin scouting alternatives       │
├────────────────────────┼──────────────────────────────────────────┤
│ Last 2-3 actions       │ SWITCH — the trail is depleted. The cost │
│ yielded nothing new    │ of staying exceeds the cost of switching │
├────────────────────────┼──────────────────────────────────────────┤
│ Information contradicts│ SWITCH IMMEDIATELY — not just depleted   │
│ earlier findings       │ but misleading. Cut losses               │
└────────────────────────┴──────────────────────────────────────────┘

Important: factor switching cost. Moving to new hypothesis = loading new context = cost. Don't switch marginal gains → only when clearly depleted.

→ Deliberate continue or switch on yield assessment, not habit/frustration. Switches evidence-based not impulse.

If err: switching too frequent (oscillation) → switching cost undervalued. Commit to current N more actions before reassess. Never switching (stuck despite declining) → hard cap: after N unproductive, switch regardless sunk cost.

Step 5: Adapt Strategy

Based on results → select next phase.

  1. Most empty, one weak → misframed. Step back + reframe: what question?
  2. One strong, others empty → concentrated. Exploit strong w/ full attention
  3. Multiple competing → distributed. build-coherence to select
  4. Clear winner emerging → explore → exploit. Reduce scouting budget 10-20% (keep 1 scout active alts), commit primary effort to winning
  5. All exhausted → solution may not exist in current space. Expand: diff tools, diff assumptions, ask user

→ Strategic decision next phase follows logically from results. Feels like conclusion not guess.

If err: no strategy feels right → foraging revealed genuine uncertainty, valid outcome. Communicate to user: "Explored N, found X. Most promising Y because Z. Pursue or additional context?"

Check

  • Landscape characterized before scouting
  • ≥3 indep hypotheses gen + tested
  • Tests cheap (1 action each) + indep
  • Reinforcement on evidence not preference
  • Marginal value assessed before deep investigation
  • Strategy adapted to results not fixed plan

Traps

  • Premature exploitation: Dive deep first showing any promise w/o scouting alts. Most common — first good idea often not best.
  • Perpetual scouting: Gen hypotheses endless never commit. Set budget: after N scouts, commit best regardless.
  • Non-indep hypotheses: "Maybe in file A" + "maybe in file B imported by A" = not indep, share assumptions. Force genuine diversity.
  • Ignore inhibition: Evidence contradicts → let go. Continue investing contradicted because effort spent = sunk cost fallacy.
  • Scout w/o record: Not recorded → later scouts repeat. Briefly note each scout finding before moving.

  • forage-resources — multi-agent foraging model this adapts to single-agent
  • build-coherence — foraging reveals multiple valid needing eval
  • coordinate-reasoning — manages info flow between scout hypotheses + exploitation
  • awareness — monitors premature convergence + tunnel vision during foraging

GitHub 저장소

pjt222/agent-almanac
경로: i18n/caveman-ultra/skills/forage-solutions
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

연관 스킬

evaluating-llms-harness

테스팅

이 Claude Skill은 MMLU, GSM8K를 포함한 60개 이상의 표준화된 학술 과제에서 LLM 성능을 벤치마크하기 위해 lm-evaluation-harness를 실행합니다. 개발자들이 모델 품질을 비교하고, 학습 진행 상황을 추적하거나 학술 결과를 보고할 수 있도록 설계되었습니다. 이 도구는 HuggingFace와 vLLM 모델을 포함한 다양한 백엔드를 지원합니다.

스킬 보기

cloudflare-cron-triggers

테스팅

이 스킬은 cron 표현식을 사용하여 Worker를 스케줄링하기 위한 Cloudflare Cron Triggers 구현에 관한 포괄적인 지식을 제공합니다. 주기적 작업, 유지보수 작업, 자동화된 워크플로우 설정 방법을 다루며, 잘못된 cron 표현식이나 시간대 문제 같은 일반적인 이슈들을 해결하는 방법을 포함합니다. 개발자들은 이를 통해 스케줄된 핸들러 구성, cron 트리거 테스트, Workflows 및 Green Compute와의 연동 작업을 수행할 수 있습니다.

스킬 보기

webapp-testing

테스팅

이 Claude Skill은 Python 스크립트를 통해 로컬 웹 애플리케이션을 테스트하기 위한 Playwright 기반 툴킷을 제공합니다. 프론트엔드 검증, UI 디버깅, 스크린샷 캡처, 로그 확인 기능을 지원하며 서버 라이프사이클을 관리합니다. 브라우저 자동화 작업에 사용하되 컨텍스트 오염을 방지하기 위해 소스 코드를 읽지 않고 스크립트를 직접 실행하세요.

스킬 보기

finishing-a-development-branch

테스팅

이 스킬은 테스트 통과를 확인한 후 체계적인 통합 옵션을 제시하여 개발자가 완성된 작업을 마무리하도록 돕습니다. 구현이 완료된 후 머지, PR 생성, 브랜치 정리와 같은 워크플로우를 안내합니다. 코드가 준비되고 테스트가 완료되었을 때 개발 프로세스를 체계적으로 마무리하기 위해 사용하세요.

스킬 보기