/ ディレクトリ / プレイグラウンド / infinite-gratitude
← 全サーバー ↗ GitHub
● コミュニティ sstklen ⚡ 即起動

infinite-gratitude

作者 sstklen · sstklen/infinite-gratitude

10 specialized agents collaborate on one research question — a multi-agent research dojo where each agent plays a distinct role.

Part of the 'AI Dojo' series. Spawns 10 agents with different roles (explorer, critic, synthesizer, etc.) that collaborate on a research task. Each agent commits its piece and the skill coordinates the handoffs — designed for tough research questions where one-shot prompting falls flat.

▶ デモを見る 📦 インストール 💡 ユースケース

なぜ使うのか

主な機能

ライブデモ

実際の動作

infinite-gratitude-skill.replay ▶ 準備完了
0/0

インストール

作者のリポジトリ · Claude Skills の公式ドキュメント

ユースケース

実用的な使い方： infinite-gratitude

Tackle a research question single-agent prompts fail on

👤 Researchers, analysts, strategists ⏱ ~60 min advanced

使うタイミング： Questions that need breadth (many sources) and depth (skepticism, synthesis) — where one pass hallucinates.

フロー
  1. Pose the question
    Use infinite-gratitude. Research question: what are the real bottlenecks in scaling post-transformer architectures in 2026? Run the 10-agent dojo.✓ コピーしました
    → Roles spin up: explorer, critic, synthesizer, etc., each producing a distinct contribution
  2. Watch the handoffs
    Show me the critic's pushback on the explorer's output.✓ コピーしました
    → Substantive critique, not agreement
  3. Final synthesis
    Give me the synthesizer's final artifact with dissent noted.✓ コピーしました
    → Document with main thesis + minority views preserved

結果： A research brief richer than a single-agent answer.

注意点
  • Agents converge and critic rubber-stamps — Prompt the critic explicitly to find flaws; force disagreement
組み合わせ： filesystem

Draft a policy memo with explicit dissenting views

👤 Policy wonks, internal strategy teams ⏱ ~90 min advanced

使うタイミング： The decision needs to survive scrutiny from people who'll disagree.

フロー
  1. Frame the memo
    Use infinite-gratitude. Memo topic: should our engineering org adopt four-day work weeks? Run the full dojo.✓ コピーしました
    → Multi-perspective outputs on pros, cons, empirical evidence, implementation risks
  2. Extract the dissent
    Keep the critic's dissent intact as an appendix; don't blend it away.✓ コピーしました
    → Main memo + appendix of unresolved concerns

結果： A memo your skeptics can see was genuinely considered.

組み合わせ

他のMCPと組み合わせて10倍の力を

infinite-gratitude-skill + paper-fetch-skill

Explorer agent downloads papers; synthesizer cites them

Run the dojo on [topic] and use paper-fetch-skill for the explorer's sources.✓ コピーしました
infinite-gratitude-skill + filesystem

Save each agent's output as its own file for traceability

Persist each agent's contribution to research/session-<date>/<role>.md✓ コピーしました

ツール

このMCPが提供する機能

ツール入力呼び出すタイミングコスト
dojo_run question, optional agent roster Big, ambiguous questions 0 (but high token use)
single_agent role name, task Just one role needed 0

コストと制限

運用コスト

APIクォータ
None
呼び出しあたりのトークン
High — 10 agents each doing real work
金額
Free (Claude API usage applies)
ヒント
Use for high-stakes questions only. Single-agent suffices for most research.

セキュリティ

権限、シークレット、影響範囲

認証情報の保管： None
データ送信先： None from skill itself

トラブルシューティング

よくあるエラーと対処法

Dojo feels repetitive

Agents may be blending; enforce distinct perspectives in prompts

Runs out of context mid-session

Save intermediate outputs to disk and resume fresh; don't carry everything in one session

代替案

infinite-gratitude 他との比較

代替案代わりに使う場面トレードオフ
Single-agent with explicit stepsStraightforward questionsLess depth, cheaper
planning-with-files-skillYou want durable state across long sessions but not multi-roleNo role specialization

その他

リソース

📖 GitHub の公式 README を読む

🐙 オープンな issue を見る

🔍 400以上のMCPサーバーとSkillsを見る