checking-uptime-status
Skill0 starsChanged 9 days agoMITView on GitHub
Reports the current health and recent history of an Uptimely project: monitor status, open incidents and alerts, uptime over a period, who is on call, maintenance windows, status pages, and telemetry services. Use when the user asks 'is anything down', 'is my site up', 'what incidents are open', 'how did the checkout monitor do this week', 'who is on call', 'is maintenance scheduled', 'show uptime', or wants a status check or monitoring overview. Read-only.
In this repository66 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adding-uptime-monitorsSkill
- analyzing-page-performanceSkill
- booking-meetingsSkill
- building-onboarding-workflowsSkill
- building-study-guidesSkill
- capturing-tasksSkill
- capturing-web-pagesSkill
- chasing-unpaid-invoicesSkill
- checking-domain-connectionsSkill
- checking-email-deliverabilitySkill
- checking-notification-deliverySkill
- cleaning-up-bookkeepingSkill
- connecting-customer-domainsSkill
- discussing-buildsSkill
- drafting-invoicesSkill
- drafting-social-postsSkill
- editing-demosSkill
- editing-page-draftsSkill
- extracting-document-textSkill
- finding-meeting-timesSkill
- handling-flaky-changesSkill
- investigating-tasksSkill
- making-demo-videosSkill
- managing-bookingsSkill
- managing-content-calendarSkill
- managing-demosSkill
- managing-voice-librarySkill
- planning-revisionSkill
- preflighting-domainsSkill
- publishing-pagesSkill
- reading-financial-reportsSkill
- reading-text-aloudSkill
- reading-web-pagesSkill
- reporting-snapvisor-usageSkill
- researching-course-materialSkill
- researching-summary-librarySkill
- responding-to-incidentsSkill
- reviewing-email-performanceSkill
- reviewing-notification-workflowsSkill
- reviewing-social-performanceSkill
- reviewing-visual-buildsSkill
- reviewing-workloadSkill
- searching-getitdone-api-docsSkill
- sending-email-campaignsSkill
- sending-notificationsSkill
- setup-bioflowSkill
- setup-calySkill
- setup-demofySkill
- setup-dodomainSkill
- setup-getitdoneSkill
- setup-notiflySkill
- setup-postifySkill
- setup-sendlySkill
- setup-shortySkill
- setup-snapvisorSkill
- setup-superbooksSkill
- setup-unotesSkill
- setup-upapiSkill
- setup-uptimelySkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 0 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Every tool in this skill comes from the uptimely MCP server, the Uptimely connector, and is written here as uptimely:<tool>.
- Very specific: line 15
Tools listed by name: call them directly, for example uptimely:uptimely_monitor_list.
- Very specific: line 41
Call uptimely:uptimely_project_overview.
- Very specific: line 42
If anything is not healthy, call uptimely:uptimely_monitor_list and name the monitors that are down or degraded, then …
- Very specific: line 43
Call uptimely:uptimely_on_call_current and say who is on call now and who is next.
- Very specific: line 44
Call uptimely:uptimely_maintenance_list and mention any window that is in progress or coming up soon, since it can explain a down monitor.
- Very specific: line 50
Never call a write operation from this skill: uptimely:uptimely_monitor_create, uptimely:uptimely_run_monitor_probe, …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
<!-- Generated from plugins/uptimely/skills/checking-uptime-status/SKILL.md by scripts/sync-skills.mjs. Edit the plugin copy, then run the script. -->Uptimely status check
Answer "is anything wrong, and who is handling it" for one Uptimely project from live data.
Connecting and calling the tools
Every tool in this skill comes from the uptimely MCP server, the Uptimely connector, and is written here as uptimely:<tool>.
- Tools listed by name: call them directly, for example
uptimely:uptimely_monitor_list. - Only
uptimely:search_toolsanduptimely:execute_typescriptlisted (Code Mode, the default): calluptimely:search_toolsfirst, then call each tool insideuptimely:execute_typescriptasexternal_<tool>(for exampleexternal_uptimely_monitor_list); the program mustreturnits result. Scopes, confirmations and gates are identical on both surfaces. - "Tool not found": switch to the Code Mode route instead of retrying the direct call. If
uptimely:search_toolsdoes not return the tool either, its OAuth scope was not granted; the user reconnects Uptimely and approves that scope. - No
uptimelytools at all: Uptimely is not connected yet. Follow thesetup-uptimelyskill.
The Uptimely server's default surface lists two tools, uptimely:search_tools and uptimely:execute_typescript. Call uptimely:search_tools for the declarations, then call each operation below as external_<name>(...) inside a uptimely:execute_typescript program. Batch independent reads with Promise.all, for example the overview, monitor list, and open incidents in one program. A denied call throws an Error whose message starts with its code, such as PROJECT_ACCESS_DENIED:. If the operations are listed as individual tools instead, call them directly.
Tools you will use
uptimely:uptimely_project_list: the projects this connection can reach, with their ids. Takes no input.uptimely:uptimely_project_overview: monitor, incident, alert, and status page counts plus the project's overall health.uptimely:uptimely_monitor_list: every monitor with its current status.uptimely:uptimely_monitor_get: one monitor's configuration.uptimely:uptimely_monitor_status_history: a monitor's recorded status transitions with durations over a window.uptimely:uptimely_monitor_target_list: the targets a monitor checks.uptimely:uptimely_incident_list: incidents, optionally only active ones (activeOnly).uptimely:uptimely_incident_get: one incident with state, severity, root cause, notes, and state timeline.uptimely:uptimely_alert_list: alerts and their states.uptimely:uptimely_on_call_current: who is on call now and who is next, per schedule.uptimely:uptimely_maintenance_list: scheduled and past maintenance windows.uptimely:uptimely_status_page_list: the project's status pages.uptimely:uptimely_telemetry_service_list: the project's telemetry services.
Workflow
- Get the
projectId. Every operation exceptuptimely:uptimely_project_listneeds it. Calluptimely:uptimely_project_list; if it returns one project, use it, and if several, ask the user which one. Reuse the id for every later call. - Call
uptimely:uptimely_project_overview. Lead with the overall health in one line. - If anything is not healthy, call
uptimely:uptimely_monitor_listand name the monitors that are down or degraded, thenuptimely:uptimely_incident_listwithactiveOnly: trueanduptimely:uptimely_alert_list, and name the open incidents and active alerts with their state and severity. - Call
uptimely:uptimely_on_call_currentand say who is on call now and who is next. - Call
uptimely:uptimely_maintenance_listand mention any window that is in progress or coming up soon, since it can explain a down monitor. - For a history question ("how did X do this week"), find the monitor in
uptimely:uptimely_monitor_list, then calluptimely:uptimely_monitor_status_historyfor the window. Report total downtime, the number of outages, and the longest one. - Offer next steps that match what you found: the
responding-to-incidentsskill for an unhandled outage, or thewriting-postmortemsskill for a resolved one.
Rules
- Never call a write operation from this skill:
uptimely:uptimely_monitor_create,uptimely:uptimely_run_monitor_probe,uptimely:uptimely_incident_declare,uptimely:uptimely_incident_state_change,uptimely:uptimely_incident_postmortem_save,uptimely:uptimely_alert_create, oruptimely:uptimely_alert_state_change. PROJECT_ACCESS_DENIEDmeans the id is wrong or the account is not a member. Useuptimely:uptimely_project_listto pick a valid id; never guess one.- Report times in the user's timezone and say which one you used.
- Report only what the tools return. Do not estimate uptime percentages the data does not contain.
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
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.

