setup

Étoiles15

Forks4

Mis à jour2 juillet 2026 à 21:55

Use when TachiBot tools seem missing, a provider isn't working, or the user asks to set up/configure TachiBot or its API keys — runs doctor and walks through fixing the gaps

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

byPawel

byPawel/tachibot-mcp

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	setup
description	Use when TachiBot tools seem missing, a provider isn't working, or the user asks to set up/configure TachiBot or its API keys — runs doctor and walks through fixing the gaps
user-invocable	true

/setup — Guided TachiBot Configuration

Call the doctor tool. Relay: which keys are detected, how many tools are visible vs hidden, and the active profile.
For each MISSING key the user wants, tell them exactly where to get it (OpenRouter: openrouter.ai/keys — unlocks the most tools; Perplexity: perplexity.ai; Google AI Studio; OpenAI platform; xAI console) and how to add it for their client: Claude Code → claude mcp add with --env flags (or edit the tachibot entry in ~/.claude.json); Claude Desktop → extension settings or claude_desktop_config.json env block.
If they want fewer tools/tokens, explain profiles: full (63, default), balanced (52), code_focus (41), minimal (13) — set via TACHIBOT_PROFILE env in the same config.
After they update config, remind them to restart the client (or /mcp reconnect in Claude Code), then re-run doctor to confirm the delta.
Suggest a first call that exercises their newest key (e.g. jury for Gemini+any, grok_search for Grok).

Plus depuis ce dépôt

même dépôt

audit

byPawel/tachibot-mcp

Use when the user wants a security review of code or a diff — OWASP/CWE findings with severity, taint/data-flow analysis, and concrete fixes via security_review

2026-07-0515

test

byPawel/tachibot-mcp

Use when the user wants tests generated for code or a diff — enumerates edge cases and failure modes first, then emits runnable test code via testgen

2026-07-0515

prompt

byPawel/tachibot-mcp

Use when a task would benefit from a structured thinking technique but you're not sure which — recommends the right prompt technique for the intent (debug, spec, refactor, decision, design) and applies it

2026-07-0315

judge

byPawel/tachibot-mcp

Use for decisions or judgments worth multiple independent perspectives — multi-model council with parallel analysis, search grounding, and synthesis (30-60s); for a quick single-call verdict use the jury tool directly

2026-07-0215

redteam

byPawel/tachibot-mcp

Use when the user shares or finishes a plan and wants it stress-tested before execution — adversarial multi-model pre-mortem with ranked risks, mitigations, and concrete plan edits

2026-07-0215

review

byPawel/tachibot-mcp

Use when code changes are ready for review — a diff exists, the user says "review my changes/PR", or a commit is about to happen. Multi-model diff review (Kimi, DeepSeek, GPT-5.5 panel + Gemini judge) with a MERGEABLE verdict

2026-07-0215

name	setup
description	Use when TachiBot tools seem missing, a provider isn't working, or the user asks to set up/configure TachiBot or its API keys — runs doctor and walks through fixing the gaps
user-invocable	true

/setup — Guided TachiBot Configuration

Call the doctor tool. Relay: which keys are detected, how many tools are visible vs hidden, and the active profile.
For each MISSING key the user wants, tell them exactly where to get it (OpenRouter: openrouter.ai/keys — unlocks the most tools; Perplexity: perplexity.ai; Google AI Studio; OpenAI platform; xAI console) and how to add it for their client: Claude Code → claude mcp add with --env flags (or edit the tachibot entry in ~/.claude.json); Claude Desktop → extension settings or claude_desktop_config.json env block.
If they want fewer tools/tokens, explain profiles: full (63, default), balanced (52), code_focus (41), minimal (13) — set via TACHIBOT_PROFILE env in the same config.
After they update config, remind them to restart the client (or /mcp reconnect in Claude Code), then re-run doctor to confirm the delta.
Suggest a first call that exercises their newest key (e.g. jury for Gemini+any, grok_search for Grok).