Run a focused Centaur tool health smoke test across every live tool CLI. Use when asked to smoke test tools, check all tool auth/connectivity, validate brokered credential injection, or produce a Slack-ready health report for the current deployment.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this skill for broad tool-by-tool smoke checks. It is narrower than the full qa skill: it only verifies that each live tool CLI is installed and that its health command succeeds through the normal sandbox credential path.
Do not invent one-off probes for each tool. The canonical smoke surface is:
<tool> health
Run the bundled runner from a sandbox or environment where centaur-tools and tool shims are installed:
uv run .agents/skills/tool-health-smoke/scripts/run_tool_health_smoke.py
The runner discovers tools with centaur-tools json, then executes each <tool> health command with a bounded timeout.
Review the generated Slack-friendly report. The first line is the overall result:
Overall: PASS|FAIL|PARTIAL - <reason>
Return the report in the Slack thread as the assistant response. Do not call the Slack posting API unless the user explicitly asks you to post through the Slack tool.
returncode != 0, invalid JSON, missing ok, or ok: false as a failed tool health check.health command as a failure. Tools are expected to expose health.uv run .agents/skills/tool-health-smoke/scripts/run_tool_health_smoke.py --timeout 45
uv run .agents/skills/tool-health-smoke/scripts/run_tool_health_smoke.py --concurrency 4
uv run .agents/skills/tool-health-smoke/scripts/run_tool_health_smoke.py --only slack,websearch,vlogs
uv run .agents/skills/tool-health-smoke/scripts/run_tool_health_smoke.py --json
Use --json only when you need machine-readable results for follow-up analysis. Use the default text output for Slack.
PASS: every discovered tool health command returned valid JSON with ok: true.FAIL: one or more tools failed, timed out, returned malformed output, or omitted the required health result.PARTIAL: discovery succeeded but no tools were found, or the run was intentionally filtered.When a tool fails because a credential is missing, check whether the client incorrectly requires an environment variable instead of using secret() or proxy-injected auth.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
Investigate reported auth, credential, permission, API proxy, 401, 403, 503, OAuth, token, or secret-resolution failures by querying VictoriaLogs first. Use when a user says an integration auth failed, a tool got unauthorized/forbidden/service unavailable, an api-proxy request failed, or asks why credentials/secrets are not working.
日本語の概要は準備中です。原文の説明を表示しています。
Use an authenticated Centaur MCP deployment to discover and call team-approved tools. Use when a task requires Centaur, its tool catalog, or the user's Centaur identity and permissions.
日本語の概要は準備中です。原文の説明を表示しています。
Change Centaur Console permissions with `centaur-console admin`. Use when a Console admin asks to create a principal for a Slack channel, user, or workflow, to create or edit a static or Postgres DSN secret (for example "make a pg dsn secret like X but with role Y"), or to give or remove a Slack channel's or user's access to a tool, secret, role, Slack channel, repo cache, observability, sessions, or workflows, or to allow or remove a Slack Connect workspace. Examples include \"create a principal for #channel\", \"give #channel access to github\" and \"let this channel read #other-channel\". Includes hard guardrails against sharing personal (DM) credentials.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate Centaur runtime behavior with VictoriaLogs (`vlogs`) and VictoriaMetrics (`vmetrics`). Use when a user reports something broken or stalled, a workflow, alert, or channel post never populated, asks to check code for issues, or needs thread, execution, sandbox, tool-call, service-health, or deploy evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Use Centaur's indexed company context and scoped read-only SQL together with direct Slack, Linear, Google Docs, Drive, Calendar, or Granola searches when answering internal company-history, prior-decision, project-context, meeting-context, roadmap/status, or cross-source memory questions. Indexed context includes Slack channels, user-visible Slack DMs, Google Docs, Google Calendar, Linear, and user-visible Granola notes. Use for questions like what was discussed, decided, planned, mentioned, or documented internally, especially when the user did not name one exact source.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold and build new tool integrations in tools/. Use when asked to create a new tool, add an API integration, or build a new client for an external service.
日本語の概要は準備中です。原文の説明を表示しています。