think-tank — Claude Code skill: what it does, how to install
Simulates a multi-persona expert debate inside Claude Code. It uncovers blind spots and weighs architectural trade-offs before you start planning implementation.
npx claude-code-templates@latest --skill productivity/think-tankWhat think-tank does
This skill stages a structured debate between distinct personas inside a single conversation. Instead of spinning up isolated agents, Claude Code runs all viewpoints in one shared context. Participants challenge each other directly, concede valid points, and build on arguments in real time.
The setup brings together 4 to 6 roles. A neutral moderator leads the exchange and cuts through circular talk. Two or three domain specialists take opposing technical stances, while an outside thinker provides unexpected cross-disciplinary parallels. You participate as an active stakeholder. Personas pause to ask about your deadlines or team size whenever context is missing.
Discussions begin with problem framing before any debate starts. The moderator clarifies constraints and checks what you already attempted. If the core question lacks definition, the session stops to formulate a precise problem statement first.
What it helps with
- compare conflicting architectural patterns before implementation
- identify trade-offs between competing software stacks
- uncover hidden operational risks under strict project constraints
- evaluate technology decisions from diverse domain perspectives
Example prompts for the agent
- Run a think tank on monolith vs microservices for our upcoming project
- Debate trade-offs between PostgreSQL and DynamoDB for an analytics service
- Help me decide whether to adopt GraphQL or stick with REST before we start planning
How to install think-tank
1claude-code-templates
npx claude-code-templates@latest --skill productivity/think-tank2Skills CLI (Vercel)
npx skills add davila7/claude-code-templates --skill think-tank -a claude-code3Manually: put the files in place
~/.claude/skills/think-tank/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/think-tank/
Manually: put the files in place
.agents/skills/think-tank/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/think-tank/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install davila7/claude-code-templates think-tank2Manually: put the files in place
.github/skills/think-tank/SKILL.mdPlatform CLI
gemini skills install https://github.com/davila7/claude-code-templates --path cli-tool/components/skills/productivity/think-tankManually: put the files in place
.devin/skills/think-tank/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about think-tank
How do I install think-tank in Claude Code?
Run npx claude-code-templates@latest --skill productivity/think-tank in your terminal.
What does think-tank do?
It runs a moderated debate with simulated domain figures directly in your terminal. The session analyzes trade-offs and risks before you draft an architecture or engineering plan.
Who takes part in the simulated debate?
The session assembles 4 to 6 participants, including an impartial moderator, opposing domain specialists, and an outside thinker. An experienced practitioner may also join to ground the discussion in production realities.