/ Annuaire / Playground / infinite-gratitude
← Tous les serveurs ↗ GitHub
● Communauté sstklen ⚡ Instantané

infinite-gratitude

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

▶ Voir la démo 📦 Installer 💡 Cas d'usage

Pourquoi l'utiliser

Fonctionnalités clés

Démo en direct

Aperçu en pratique

infinite-gratitude-skill.replay ▶ prêt
0/0

Installer

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

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

~/.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 utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

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

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "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
    }
  }
}

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

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

Continue utilise un tableau d'objets serveur plutôt qu'une 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"
        ]
      }
    }
  }
}

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

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

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : infinite-gratitude

Tackle a research question single-agent prompts fail on

👤 Researchers, analysts, strategists ⏱ ~60 min advanced

Quand l'utiliser : Questions that need breadth (many sources) and depth (skepticism, synthesis) — where one pass hallucinates.

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

Résultat : A research brief richer than a single-agent answer.

Pièges
  • Agents converge and critic rubber-stamps — Prompt the critic explicitly to find flaws; force disagreement
Combiner avec : filesystem

Draft a policy memo with explicit dissenting views

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

Quand l'utiliser : The decision needs to survive scrutiny from people who'll disagree.

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

Résultat : A memo your skeptics can see was genuinely considered.

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

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.✓ Copié
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✓ Copié

Outils

Ce que ce MCP expose

OutilEntréesQuand appelerCoût
dojo_run question, optional agent roster Big, ambiguous questions 0 (but high token use)
single_agent role name, task Just one role needed 0

Coût et limites

Coût d'exécution

Quota d'API
None
Tokens par appel
High — 10 agents each doing real work
Monétaire
Free (Claude API usage applies)
Astuce
Use for high-stakes questions only. Single-agent suffices for most research.

Sécurité

Permissions, secrets, portée

Stockage des identifiants : None
Sortie de données : None from skill itself

Dépannage

Erreurs courantes et correctifs

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 autres

AlternativeQuand l'utiliserCompromis
Single-agent with explicit stepsStraightforward questionsLess depth, cheaper
planning-with-files-skillYou want durable state across long sessions but not multi-roleNo role specialization

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills