API Health Checker

Tests API endpoints by sending requests, validating responses, measuring performance, handling authentication, and generating detailed health reports.

This skill is coherent for API testing, but exercise caution when providing secrets or testing internal endpoints. Do not paste long-lived production API keys into prompts unless you trust the environment; prefer short-lived or scoped tokens. Decide in advance whether response bodies and headers (which may contain sensitive data) should be included in reports. Limit tests to the endpoints you control and avoid instructing the skill to scan internal/localhost addresses unless you intend that. If you need continuous monitoring, verify how results will be stored or transmitted — this instruction-only skill does not declare any persistent storage or transmit destinations, so ask the publisher how reports are delivered and retained before sending sensitive data.

Type: OpenClaw Skill Name: ub2-api-health-checker Version: 1.0.0 The skill bundle, consisting of `_meta.json` and `SKILL.md`, describes an API health checker. The `SKILL.md` documentation outlines standard functionality for testing API endpoints, including support for various HTTP methods, response validation, performance measurement, and handling authentication headers (API keys, Bearer tokens). While handling authentication tokens involves sensitive data, this is a necessary and expected capability for an API health checker and the instructions do not suggest any malicious intent such as exfiltration, unauthorized access, or prompt injection against the agent to perform actions beyond the stated purpose.