PulseMon Skill

Monitor your cron jobs and background tasks through PulseMon.

Setup

The user needs a PulseMon API key. They can generate one at https://pulsemon.dev/dashboard/settings under "API Keys".

Store it as the environment variable PULSEMON_API_KEY.

Base URL

All API requests go to: INLINECODE1

Authentication

Every request must include the header:

CODEBLOCK0

Available Actions

List all monitors

INLINECODE2

Returns an array of monitors with their name, slug, status (up/down/waiting/paused), last ping time, and expected interval.

Get a specific monitor

INLINECODE3

Returns full monitor details including recent pings and incidents.

Create a monitor

INLINECODE4

CODEBLOCK1

Body:

CODEBLOCK2

• - name: Human-readable name (required, 1-100 characters)
• slug: URL-safe identifier, lowercase letters, numbers, and hyphens only (required, 3-60 characters)
• expectedInterval: Seconds between expected pings (required, minimum 10, maximum 2592000)
• gracePeriod: Extra seconds before alerting (optional, 0-86400, defaults to a sensible value based on the interval)
• tags: Array of string tags for organisation (optional)
• maxDuration: Max allowed run time in milliseconds (optional, null to disable). Alerts if a ping reports a duration exceeding this threshold.

Update a monitor

INLINECODE5

CODEBLOCK3

Body: any of these fields (at least one required):

• - name: string (1-100 characters)
• expectedInterval: number (10-2592000)
• gracePeriod: number (0-86400)
• isPaused: boolean
• tags: array of strings
• maxDuration: number or null (milliseconds)

Delete a monitor

INLINECODE6

Pause a monitor

INLINECODE7

Resume a monitor

INLINECODE8

List pings for a monitor

INLINECODE9

List incidents for a monitor

INLINECODE10

Ping a monitor

Pings are sent directly to the ping endpoint (no API key needed):

INLINECODE11

Optional query params:

• - status: "success" (default), "fail", or "start"
• duration: Job duration in milliseconds

INLINECODE12 with JSON body:

CODEBLOCK4

• - status=start: Signals a job has begun. Enables overlap detection. Does not reset the deadline.
• status=success: Signals the job completed. Resets the deadline.
• status=fail: Records a failure. Does not reset the deadline.
• body: Job output (up to 10 KB). Included in alert notifications.
• duration: Job run time in ms. Checked against maxDuration threshold if set.

Response Format

All responses are JSON with this shape:

CODEBLOCK5

On error:

CODEBLOCK6

Common Intervals

When the user says a time like "every hour" or "daily", convert to seconds:

• - Every minute: 60
• Every 5 minutes: 300
• Every 15 minutes: 900
• Every 30 minutes: 1800
• Every hour: 3600
• Every 6 hours: 21600
• Every 12 hours: 43200
• Daily: 86400
• Weekly: 604800

Guidelines

• - When listing monitors, show name, status, and last ping time in a readable format.
• When a monitor is "down", mention how long it's been down.
• When creating a monitor, suggest a sensible grace period if the user doesn't specify one (e.g. 10% of the interval, minimum 30 seconds).
• After creating a monitor, show the user the ping URL: INLINECODE13
• Always confirm before deleting a monitor.
• When the user says "check my monitors" or similar, use the list endpoint and summarise the results.
• Format durations in human-readable form (e.g. "2 hours ago" instead of a raw timestamp).