canary

Generate curl-based uptime watcher scripts with strict input validation for HTTP/HTTPS URLs.

4|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Dragoon0x/dragoon-skills --skill canary-dragoon0x
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/Dragoon0x/dragoon-skills/tree/main/skills/canary
Command: npx skills add https://github.com/Dragoon0x/dragoon-skills --skill canary-dragoon0x

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manually monitoring deployed URLs for uptime is tedious and prone to human error, especially when you need consistent, repeatable checks after deployments or before high-stakes events.

Core Features & Use Cases

  • Strict Input Validation: Automatically verifies that provided URLs use HTTP/HTTPS, expected status codes fall between 100-599, and check intervals are between 5-86400 seconds to prevent invalid configurations.
  • Dual Operation Modes: Generates a curl-based watcher script that supports both one-shot checks (exits with 0/1 status for easy CI integration) and continuous --watch mode for ongoing monitoring.
  • Common Use Case: Use this skill immediately after deploying a new release to catch downtime early, or set up a heartbeat check before a major product launch to confirm service stability.

Quick Start

Use the canary skill to generate a ready-to-run uptime watcher script for your deployed production URL at https://your-app.com.

Frequently Asked Questions about canary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a curl script for HTTP uptime monitoring of deployed URLs?

A curl uptime monitoring script validates deployed HTTP URLs by checking expected status codes and intervals. It supports one-shot checks for CI integration and continuous mode for ongoing monitoring, eliminating manual overhead.

Can I use a watcher script for CI/CD deployment checks and continuous monitoring?

Generated watcher scripts support dual modes: one-shot checks exit with 0/1 status for CI/CD integration, while continuous watch mode handles ongoing monitoring. Both modes use strict input validation for protocols, status codes, and intervals.

What URL protocols and status codes are supported for uptime checks?

Uptime checks support HTTP and HTTPS protocols with expected HTTP status codes validated between 100-599. Check intervals are configurable from 5 to 86400 seconds, ensuring strict input validation prevents invalid monitoring configurations.

How do I set up pre-event heartbeat checks for web endpoints?

Set up pre-event heartbeat checks by generating a curl-based watcher script targeting your deployed web endpoints. Configure expected HTTP status codes and intervals to confirm service stability before high-stakes events or major product launches.

What are the limitations of using curl scripts for URL monitoring?

Curl-based URL monitoring is limited to HTTP/HTTPS protocol checks and HTTP status code validation (100-599). It focuses strictly on endpoint availability and does not simulate complex user interactions or render browser content.