Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
Fix ClawHub security scan - Add credential metadata declarations (CHECKLY_API_KEY, CHECKLY_ACCOUNT_ID). Metadata-only change, no functional updates.
What This Skill Does
Checkly CLI provides a TypeScript/JavaScript workflow for defining, testing, and deploying synthetic monitoring checks as code. Supports API checks, browser checks with Playwright, heartbeat monitors, and TCP/DNS monitors. Checks can be version-controlled, reviewed in PRs, and deployed through CI/CD pipelines.
Defining monitoring as code lets teams review, version, and deploy checks alongside application code rather than managing them separately in a web dashboard.
When to use it
- Deploying API endpoint monitoring as part of a release pipeline
- Writing browser flow tests with Playwright before shipping new features
- Importing existing Checkly checks from the web UI into version-controlled code
- Running synthetic checks locally during development before cloud deployment
- Managing monitoring configuration across multiple environments with Git
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Set up an API availability check for https://api.example.com/status
- 1Creates an ApiCheck construct in __checks__/api-status.check.ts with a GET request and status code assertion
- 2Runs 'npx checkly test' to validate the check against the Checkly runtime locally
- 3Commits the check file to version control
- 4Runs 'npx checkly deploy' to schedule the check for continuous monitoring in Checkly cloud
API check running on a schedule in Checkly cloud, alerting if the endpoint returns an unexpected status or exceeds response time thresholds
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.