tool-health-smoke

To run a smoke test for tool CLI health, execute this Skill to discover every live tool via the centaur-tools registry and check its health command. It validates authentication, connectivity, and configuration, returning a compact pass and failure summary.

Checking connectivity and authentication for multiple tool CLIs is done by running this Skill against the centaur-tools registry. It executes bounded command timeouts on installed tool shims, detecting missing CLIs, invalid JSON responses, and explicit health failures.

Yes, validating credential injection requires the centaur-tools registry and installed tool shims. This Skill queries each live tool for a JSON health response with an ok field, confirming that brokered credentials authenticate successfully across your deployment.

Yes, you can apply filtering and exclusion controls to limit tool health checks to specific integrations. The Skill supports focused checks of selected tools, optional concurrency, and bounded command timeouts to validate integration monitoring without testing every tool.

A tool health smoke test reports failures when CLIs return nonzero exits, invalid JSON, missing status fields, or explicit health failures. It also catches bounded command timeouts and missing status fields, identifying misconfigured or unauthenticated tool CLIs.

Yes, this smoke testing approach produces compact pass and failure summaries formatted as Slack-ready reports. It aggregates authentication, connectivity, and configuration failures from every live tool check into a summary suitable for sharing in a team thread.