/ 目录 / 演练场 / infinite-gratitude
● 社区 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

安装

选择你的客户端

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "infinite-gratitude-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/sstklen/infinite-gratitude",
        "~/.claude/skills/infinite-gratitude"
      ],
      "_inferred": true
    }
  }
}

打开 Claude Desktop → Settings → Developer → Edit Config。保存后重启应用。

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "infinite-gratitude-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/sstklen/infinite-gratitude",
        "~/.claude/skills/infinite-gratitude"
      ],
      "_inferred": true
    }
  }
}

Cursor 使用与 Claude Desktop 相同的 mcpServers 格式。项目级配置优先于全局。

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "infinite-gratitude-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/sstklen/infinite-gratitude",
        "~/.claude/skills/infinite-gratitude"
      ],
      "_inferred": true
    }
  }
}

点击 Cline 侧栏中的 MCP Servers 图标,然后选 "Edit Configuration"。

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "infinite-gratitude-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/sstklen/infinite-gratitude",
        "~/.claude/skills/infinite-gratitude"
      ],
      "_inferred": true
    }
  }
}

格式与 Claude Desktop 相同。重启 Windsurf 生效。

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "infinite-gratitude-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/sstklen/infinite-gratitude",
        "~/.claude/skills/infinite-gratitude"
      ]
    }
  ]
}

Continue 使用服务器对象数组,而非映射。

~/.config/zed/settings.json
{
  "context_servers": {
    "infinite-gratitude-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/sstklen/infinite-gratitude",
          "~/.claude/skills/infinite-gratitude"
        ]
      }
    }
  }
}

加入 context_servers。Zed 保存后热重载。

claude mcp add infinite-gratitude-skill -- git clone https://github.com/sstklen/infinite-gratitude ~/.claude/skills/infinite-gratitude

一行命令搞定。用 claude mcp list 验证,claude mcp remove 卸载。

使用场景

实战用法: 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.

前置条件
  • Skill installed — git clone https://github.com/sstklen/infinite-gratitude ~/.claude/skills/infinite-gratitude
步骤
  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 搭配,撬动十倍杠杆

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
每次调用 Token 数
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