moltbookdowndetector

Probe Moltbook endpoints and report reachability and latency.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/officialpm/moltbookdowndetector --skill moltbookdowndetector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moltbookdowndetector
Source: https://github.com/officialpm/moltbookdowndetector/tree/main/public
Command: npx skills add https://github.com/officialpm/moltbookdowndetector --skill moltbookdowndetector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a lightweight, agent-friendly way to monitor Moltbook uptime by probing endpoints and reporting reachability and latency, helping teams detect outages quickly.

Core Features & Use Cases

  • Real-time health checks for Moltbook endpoints (API and public site)
  • Latency reporting and overall status (ok/failed) with contextual details
  • Optional authenticated probe when MOLTBOOK_API_KEY is configured to detect auth-specific outages
  • Public status and metrics endpoints suitable for dashboards and automation

Quick Start

Use the Moltbookdowndetector to query endpoint health.

Step 1: Check the status JSON curl -s https://moltbookdowndetector.vercel.app/api/agent-check | jq . Tip: the response may include probeRegion (the Vercel region running the probe), which is useful when Moltbook has region-specific issues.

Step 2: Optional: Fetch agent context curl -s https://moltbookdowndetector.vercel.app/api/agent-context

Scoped checks:

API-only

curl -s "https://moltbookdowndetector.vercel.app/api/agent-check?category=api" | jq .

One endpoint

curl -s "https://moltbookdowndetector.vercel.app/api/agent-check?name=Posts%20Feed" | jq .

Step 3: Interpret results

  • ok: true → all probes are healthy
  • ok: false → at least one probe is failing
  • action → OK or BACKOFF
  • recommendedBackoffMinutes → suggested backoff window when unhealthy

When unhealthy, inspect:

  • totalProbes, totalFailures, totalDegraded
  • byCategory
  • failures[] — endpoints that failed (timeout/5xx/non-OK)
  • degraded[] — endpoints that were successful but slow

Each item includes:

  • name
  • category
  • status
  • ms
  • url
  • error

(Optional: You can query the full raw probe output with /api/check.)

Frequently Asked Questions about moltbookdowndetector

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

FAQPage Schema
How do I check Moltbook API uptime and latency?

To check Moltbook API uptime and latency, query the health-check endpoint to probe endpoints and report reachability. You receive a status JSON indicating overall health, latency in milliseconds, and specific failures or degraded responses.

How does an automated uptime monitor detect API outages?

An automated uptime monitor detects API outages by probing endpoints and reporting reachability and latency. It categorizes responses as ok, degraded, or failed based on timeouts, 5xx errors, and latency thresholds to identify broken or slow connections.

Do I need an API key to monitor Moltbook status?

You do not need an API key to monitor basic Moltbook status because public endpoints are probed by default. Configuring a Moltbook API key is optional and enables authenticated probes to detect auth-specific outages.

What is the difference between failed and degraded health check results?

Failed health check results indicate endpoints returned non-OK status codes, 5xx errors, or timeouts. Degraded results mean the endpoints were ultimately reachable and successful, but the response latency was unusually slow.

How do I get monitoring data for a specific Moltbook endpoint?

To get monitoring data for a specific Moltbook endpoint, query the health-check API and append the endpoint name as a parameter. This scopes the probe to return status, latency, and error details for that single endpoint.

What should I do when Moltbook health check status is unhealthy?

When Moltbook health check status is unhealthy, inspect the failures and degraded arrays for error details. The response includes a recommendedBackoffMinutes window and an action parameter suggesting OK or BACKOFF for automation pipelines.