Run any Skill in Manus with one click

tool-health-smoke

Stars916

Forks170

UpdatedJune 25, 2026 at 19:48

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

paradigmxyz

paradigmxyz/centaur

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

3 files

SKILL.md

readonly

name	tool-health-smoke
description	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.

Tool Health Smoke

Overview

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

Workflow

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.

Report Rules

Treat returncode != 0, invalid JSON, missing ok, or ok: false as a failed tool health check.
Treat a missing health command as a failure. Tools are expected to expose health.
Report the runner output directly. Health commands are responsible for returning compact, safe JSON.
Keep evidence compact: include the tool name, status, and one short detail or error.
Use Slack mrkdwn bullets, not Markdown tables.
Include all failed rows. If all tools pass, include a compact pass list or pass count.

Useful Options

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.

Interpreting Results

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.

More from this repository

same repository

company-context

paradigmxyz/centaur

Use Centaur's indexed company context 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.

2026-07-14916

paradigmxyz/centaur

Smoke test the full running Centaur system from a new Slack thread. Use when asked to QA the stack, run a smoke test, verify a deployment, check stack health, check deploy readiness, or prove Slack tools, file upload/download, company context, logs, metrics, and tool loading work end to end.

2026-07-10916

harness-development

paradigmxyz/centaur

Add, modify, or debug Centaur harness-server backends in crates/harness-server. Use when adding support for a new harness CLI, changing Codex App Server V2 normalization, investigating Claude Code/Amp/Codex streaming or steering behavior, removing Python/TypeScript harness normalizers, or differentially testing real harness stdout/stderr against the shared App Server protocol.

2026-06-11916

run-centaur-dev

paradigmxyz/centaur

Bring up the full Centaur development stack locally with cargo-run Rust API, Kind agent sandboxes, onepassword/iron-proxy credentials, Tailscale Funnel Slack webhooks, Slack app manifest setup, and centaur-session-cli smoke tests or thread attachment.

2026-06-11916

auth-failure-log-triage

paradigmxyz/centaur

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.

2026-05-25916

creating-tools

paradigmxyz/centaur

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.

2026-05-18916

name	tool-health-smoke
description	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.

Tool Health Smoke

Overview

Do not invent one-off probes for each tool. The canonical smoke surface is:

<tool> health

Workflow

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.

Report Rules

Treat returncode != 0, invalid JSON, missing ok, or ok: false as a failed tool health check.
Treat a missing health command as a failure. Tools are expected to expose health.
Report the runner output directly. Health commands are responsible for returning compact, safe JSON.
Keep evidence compact: include the tool name, status, and one short detail or error.
Use Slack mrkdwn bullets, not Markdown tables.
Include all failed rows. If all tools pass, include a compact pass list or pass count.

Useful Options

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.

Interpreting Results

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.