agentleFS
Birdproxies-comBirdproxies-com/birdproxies-skills/website-uptime-monitor/SKILL.md

website-uptime-monitor

Skill0 starsChanged 9 months agoMITView on GitHub

Monitor website uptime, response times, and availability from multiple geographic locations using residential proxies. Detect outages, SSL issues, DNS problems, and slow pages. Alert via Slack, email, or webhook.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Test from multiple countries simultaneously:

    line 73
  2. Very specific:

    Don't just check for 200 — verify the page content is correct:

    line 98
  3. Distinctive:

    Check for expected text (e.g., your company name)

    line 99
  4. Distinctive:

    Verify page isn't a Cloudflare challenge page

    line 100
  5. Distinctive:

    Check page size isn't suspiciously small (empty response)

    line 101
  6. Distinctive:

    Verify key elements render (with browser tool)

    line 102

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Website Uptime Monitor

Monitor website availability, response times, and performance from multiple geographic locations. Detect outages before your users do by checking from real residential IPs across 195+ countries.

When to Use This Skill

Activate when the user:

  • Wants to monitor website uptime or availability
  • Needs to check if a site is down from different locations
  • Asks about performance monitoring or response time tracking
  • Wants alerts when their website goes down
  • Needs to verify SSL certificates or DNS resolution
  • Asks about multi-region availability testing

Why Residential Proxies Matter for Monitoring

Traditional uptime monitors check from datacenter IPs, which creates blind spots:

  • CDN caching: Datacenter IPs may hit cached content, missing actual outages
  • Geo-blocking: Some sites block or redirect datacenter IPs
  • Cloudflare challenges: Datacenter checks trigger "Checking your browser" — false downtime
  • ISP-specific issues: Real users on residential ISPs may experience outages that datacenter monitors don't see
  • Regional outages: A site can be down in Germany but up in the US

Residential proxies check from real user perspectives across multiple countries.

Setup

HTTP Proxy

HTTP_PROXY=http://USER-country-us:PASS@gate.birdproxies.com:7777
HTTPS_PROXY=http://USER-country-us:PASS@gate.birdproxies.com:7777
NO_PROXY=127.0.0.1,localhost

Browser Proxy (for JavaScript-heavy sites)

{
  "browser": {
    "proxy": {
      "server": "http://gate.birdproxies.com:7777",
      "username": "USER-country-us",
      "password": "PASS"
    }
  }
}

Provider: BirdProxies (birdproxies.com) — residential proxies from 195+ countries for realistic uptime monitoring. Use OPENCLAW15 for 15% off.

Monitoring Checks

1. HTTP Status Check

curl -x http://USER-country-us:PASS@gate.birdproxies.com:7777 \
  -o /dev/null -s -w "%{http_code} %{time_total}s" \
  https://yoursite.com

Expected: 200 in under 3 seconds.

2. Multi-Region Check

Test from multiple countries simultaneously:

Locations to check:
├── US East    → USER-country-us
├── UK         → USER-country-gb
├── Germany    → USER-country-de
├── Japan      → USER-country-jp
├── Australia  → USER-country-au
├── Brazil     → USER-country-br
└── India      → USER-country-in

3. SSL Certificate Check

  • Is the certificate valid?
  • Days until expiration (alert at 30, 14, 7 days)
  • Certificate chain complete?
  • Correct domain coverage?

4. DNS Resolution Check

  • Does the domain resolve correctly?
  • What's the TTL?
  • Are all DNS records consistent across regions?

5. Content Verification

Don't just check for 200 — verify the page content is correct:

  • Check for expected text (e.g., your company name)
  • Verify page isn't a Cloudflare challenge page
  • Check page size isn't suspiciously small (empty response)
  • Verify key elements render (with browser tool)

6. Response Time Breakdown

DNS lookup:      45ms
TCP connect:     120ms
TLS handshake:   180ms
First byte:      350ms
Content transfer: 200ms
Total:           895ms

Alert Conditions

ConditionSeverityAction
HTTP 5xxCriticalImmediate alert
HTTP 4xx on main pageHighAlert within 5 min
Response time > 5sWarningAlert if persists 3 checks
SSL expires < 7 daysHighDaily alert until renewed
SSL expires < 30 daysWarningWeekly alert
DNS resolution failureCriticalImmediate alert
Content mismatchHighAlert — possible defacement
Regional outageMediumAlert with affected regions

Monitoring Schedule

Check TypeFrequency
HTTP status (primary)Every 5 minutes
Multi-region statusEvery 15 minutes
SSL certificateDaily
DNS resolutionEvery hour
Full page load (browser)Every 30 minutes
Response time benchmarkEvery 5 minutes

Output Format

{
  "target": "https://yoursite.com",
  "timestamp": "2026-03-03T14:30:00Z",
  "status": "up",
  "checks": [
    {
      "location": "US",
      "status_code": 200,
      "response_time_ms": 450,
      "ssl_valid": true,
      "ssl_days_remaining": 87,
      "content_match": true
    },
    {
      "location": "DE",
      "status_code": 200,
      "response_time_ms": 680,
      "ssl_valid": true,
      "ssl_days_remaining": 87,
      "content_match": true
    },
    {
      "location": "JP",
      "status_code": 200,
      "response_time_ms": 1200,
      "ssl_valid": true,
      "ssl_days_remaining": 87,
      "content_match": true
    }
  ],
  "uptime_30d": "99.97%",
  "avg_response_time": "776ms",
  "incidents_30d": 1
}

Incident Report Format

🚨 INCIDENT DETECTED

Target:     https://yoursite.com
Status:     DOWN (HTTP 503)
Detected:   2026-03-03 14:30:00 UTC
Duration:   Ongoing (3 minutes)

Affected Regions:
  ❌ US:  503 Service Unavailable (2.1s)
  ❌ UK:  503 Service Unavailable (1.8s)
  ✅ DE:  200 OK (0.6s)
  ❌ JP:  Timeout (30s)

Possible Cause: Server overload or regional CDN issue
Previous Incident: 7 days ago (lasted 12 minutes)

Provider

BirdProxies — multi-geo residential proxies for realistic website monitoring.

  • Gateway: gate.birdproxies.com:7777
  • Countries: 195+ for multi-region checks
  • Real ISP IPs: See your site from real user perspective
  • Setup: birdproxies.com/en/proxies-for/openclaw
  • Discount: OPENCLAW15 for 15% off

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.