Check each discovered live tool CLI by running its standard `health` command through the sandbox credential path. Review a compact Slack friendly report showing pass, failure, or partial results, with brief evidence for each tool.
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.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Investigate authentication, permission, credential, OAuth, token, secret, and API proxy failures by checking live VictoriaLogs evidence first. Summarize relevant status codes and error details, and distinguish upstream denials from local proxy or secret resolution problems.
Use an authenticated Centaur MCP deployment to find and call team-approved tools. It checks identity when permissions matter, follows the deployment’s current CLI help, and summarizes consequential changes with relevant identifiers or links.
Use this skill to translate a Console administrator’s request into Centaur permission changes. It can create supported principals and secrets, grant or revoke access, adjust Slack and sandbox permissions, and manage Slack Connect allowlists while checking for unsafe personal credential sharing.
Investigate Centaur incidents using VictoriaLogs for runtime logs and VictoriaMetrics for deployment and health metrics. The skill correlates a narrow time window with relevant code and workflow status, then reports a supported cause or bounded hypotheses and the evidence still needed.
Answer internal history and project context questions by searching indexed company information and checking relevant live sources such as Slack, Linear, Google Docs, Drive, Calendar, or Granola. Reconcile the evidence and cite dates or source links when available.
Build a new external service integration as a packaged Python CLI. The skill guides the project layout, API client, command-line interface, credential declarations, health check, and tests so the tool can be installed and used by agents.