/ Каталог / Песочница / 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 использует ту же схему mcpServers, что и Claude Desktop. Конфиг проекта приоритетнее глобального.

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

Щёлкните значок MCP Servers на боковой панели Cline, затем "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 использует массив объектов серверов, а не 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"
        ]
      }
    }
  }
}

Добавьте в 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 — эффект 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.✓ Скопировано
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

Ещё

Ресурсы

📖 Читать официальный README на GitHub

🐙 Открытые задачи

🔍 Все 400+ MCP-серверов и Skills