adding-uptime-monitors
Skill0 starsChanged 9 days agoMITView on GitHub
Adds a new uptime monitor to an Uptimely project without duplicating an existing one, and optionally runs a first check. Use when the user asks to 'start monitoring https://api.example.com/health', 'add a monitor', 'monitor my website', 'watch this API endpoint', 'set up uptime monitoring', 'alert me if this URL goes down', or 'ping this site'. Creates the monitor only after confirmation.
In this repository66 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- 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
- checking-uptime-statusSkill
- 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, 2 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Create a monitor without duplicating an existing one, then check it once if the user wants.
- 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 34
Call uptimely:uptimely_monitor_list and uptimely:uptimely_monitor_target_list.
- Very specific: line 41
Never call uptimely:uptimely_monitor_create or uptimely:uptimely_run_monitor_probe without the user's yes for that exact call, and never …
- Very specific: line 43
If uptimely:uptimely_monitor_create is not reachable, the user did not grant monitors:write.
- Distinctive: line 44
Only monitor URLs the user owns or is responsible for.
≈ “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/adding-uptime-monitors/SKILL.md by scripts/sync-skills.mjs. Edit the plugin copy, then run the script. -->Add an Uptimely monitor
Create a monitor without duplicating an existing one, then check it once if the user wants.
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. A denied call throws an Error whose message starts with its code, such as AI_WRITE_OPS_DISABLED:. If the operations are listed as individual tools instead, call them directly. The rules below apply on both surfaces.
Tools you will use
uptimely:uptimely_project_list: the projects this connection can reach, to get theprojectId.uptimely:uptimely_monitor_list: existing monitors, to avoid a duplicate.uptimely:uptimely_monitor_target_list: the targets existing monitors check.uptimely:uptimely_monitor_create: create the monitor record. It writes to the project but does not itself contact the URL.uptimely:uptimely_monitor_get: read the new monitor back.uptimely:uptimely_run_monitor_probe: run an on-demand check of the new monitor. It makes a real request to the URL.
Workflow
- Get the
projectIdfromuptimely:uptimely_project_list(ask which one if there are several) and the URL or host to monitor. Suggest a clear name, such as "API: health". - Call
uptimely:uptimely_monitor_listanduptimely:uptimely_monitor_target_list. If the same URL is already monitored, tell the user and stop unless they want a second monitor. - Show the monitor you will create: project, name, type, and URL, plus any settings the user asked for. Ask for a yes.
- On a yes, call
uptimely:uptimely_monitor_createon its own. Then calluptimely:uptimely_monitor_geton the new id and report its configuration. - Offer a first check. Only on a separate yes, call
uptimely:uptimely_run_monitor_probeand reportok, the response status, and the response time.
Rules
- Never call
uptimely:uptimely_monitor_createoruptimely:uptimely_run_monitor_probewithout the user's yes for that exact call, and never put both in oneuptimely:execute_typescriptprogram. - On
AI_WRITE_OPS_DISABLED, nothing was created. Say a project owner or admin must turn on Allow AI write operations under Settings > API Keys, and pass on thesettingsUrlif the result includes one. - If
uptimely:uptimely_monitor_createis not reachable, the user did not grantmonitors:write. - Only monitor URLs the user owns or is responsible for. Ask if that is unclear.
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.

