name: olore-checkly-latest description: Local Checkly documentation reference (latest). Checkly monitoring documentation. Use for synthetic monitoring, Playwright checks, API monitoring, Monitoring as Code (MaC), alerting, and CI/CD integration.
Checkly Documentation
Checkly monitoring documentation. Use for synthetic monitoring, Playwright checks, API monitoring, Monitoring as Code (MaC), alerting, and CI/CD integration.
Quick Reference
| Task | Entry Point |
|---|---|
| Getting started | contents/quickstarts/ |
| Core concepts | contents/concepts/ |
| CLI reference | contents/cli/ |
| Monitoring as Code constructs | contents/constructs/ |
| API checks | contents/detect/synthetic-monitoring/api-checks/ |
| Browser / Playwright checks | contents/detect/synthetic-monitoring/browser-checks/ |
| Uptime monitoring | contents/detect/uptime-monitoring/ |
| Alerting | contents/communicate/alerts/ |
| REST API reference | contents/api-reference/ |
| Trace integration (OTel) | contents/resolve/traces/ |
| CI/CD integration | contents/integrations/ci-cd/ |
When to use
Use this skill when the user asks about:
- Creating and configuring Checkly checks (API, browser, Playwright, multistep, heartbeat, uptime)
- Monitoring as Code (MaC) using the Checkly CLI and constructs
- Setting up alert channels, dashboards, or status pages
- Integrating Checkly with CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins, Vercel)
- Infrastructure as Code with Terraform or Pulumi Checkly providers
- Connecting OpenTelemetry traces for root cause analysis
- Checkly REST API usage
- Private locations and custom runtime configuration
How to find information
- First, read
TOC.mdfor complete file listing organized by directory - Identify relevant section based on user's question
- Read specific files for details
TOC.md contains all files organized by directory - always check it first.