/ Directory / Playground / infinite-gratitude
← All servers ↗ GitHub
● Community sstklen ⚡ Instant

infinite-gratitude

by 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.

▶ Watch demo 📦 Install 💡 Use Cases

Why use it

Key features

Live Demo

What it looks like in practice

infinite-gratitude-skill.replay ▶ ready
0/0

Install

Pick your client

~/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
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.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 uses the same mcpServers schema as Claude Desktop. Project config wins over global.

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
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "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
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

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

Continue uses an array of server objects rather than a map.

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

Add to context_servers. Zed hot-reloads on save.

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

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use infinite-gratitude

Tackle a research question single-agent prompts fail on

👤 Researchers, analysts, strategists ⏱ ~60 min advanced

When to use: Questions that need breadth (many sources) and depth (skepticism, synthesis) — where one pass hallucinates.

Prerequisites
  • Skill installed — git clone https://github.com/sstklen/infinite-gratitude ~/.claude/skills/infinite-gratitude
Flow
  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.✓ Copied
    → 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.✓ Copied
    → Substantive critique, not agreement
  3. Final synthesis
    Give me the synthesizer's final artifact with dissent noted.✓ Copied
    → Document with main thesis + minority views preserved

Outcome: A research brief richer than a single-agent answer.

Pitfalls
  • Agents converge and critic rubber-stamps — Prompt the critic explicitly to find flaws; force disagreement
Combine with: filesystem

Draft a policy memo with explicit dissenting views

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

When to use: The decision needs to survive scrutiny from people who'll disagree.

Flow
  1. Frame the memo
    Use infinite-gratitude. Memo topic: should our engineering org adopt four-day work weeks? Run the full dojo.✓ Copied
    → 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.✓ Copied
    → Main memo + appendix of unresolved concerns

Outcome: A memo your skeptics can see was genuinely considered.

Combinations

Pair with other MCPs for X10 leverage

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.✓ Copied
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✓ Copied

Tools

What this MCP exposes

ToolInputsWhen to callCost
dojo_run question, optional agent roster Big, ambiguous questions 0 (but high token use)
single_agent role name, task Just one role needed 0

Cost & Limits

What this costs to run

API quota
None
Tokens per call
High — 10 agents each doing real work
Monetary
Free (Claude API usage applies)
Tip
Use for high-stakes questions only. Single-agent suffices for most research.

Security

Permissions, secrets, blast radius

Credential storage: None
Data egress: None from skill itself

Troubleshooting

Common errors and fixes

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

Alternatives

infinite-gratitude vs others

AlternativeWhen to use it insteadTradeoff
Single-agent with explicit stepsStraightforward questionsLess depth, cheaper
planning-with-files-skillYou want durable state across long sessions but not multi-roleNo role specialization

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills