- Home
- Skills
- DevOps & Cloud
- KEEPitALIVE
Works with the AI Agents you already use
KEEPitALIVE
Configure and manage production uptime monitoring, heartbeats, and incident automation via KEEPitALIVE.
Free
KEEPitALIVE
Example session with this skill installed
Check the health of my 'production-api' monitor and show me any incidents from the last 24 hours.
- Read your context and instructions
- Compiled the keepitalive
Example output — simulated monitoring data.
I retrieved the health status and incident history for the production-api monitor over a simulated 24-hour period.
Service health
- Monitor: production-api (HTTP)
- Observed state: UP
- Last observation: 2026-10-14T14:05:00Z
- Data source: KEEPitALIVE monitoring data (simulated)
Incident timeline
| Time (UTC) | Event | Evidence |
|---|---|---|
| 2026-10-14 02:15 | DOWN | Connection timeout (5,000 ms threshold exceeded) |
| 2026-10-14 02:22 | UP | HTTP 200 OK, latency 145 ms |
Reliability summary
- Coverage window: 2026-10-13 14:05 UTC to 2026-10-14 14:05 UTC
- Confirmed incidents: 1
- Recorded downtime: 7 minutes
- Calculated uptime: 99.51%
Recommended next steps
- Investigate logs: Review application and infrastructure logs around 02:15 UTC to identify possible causes.
- Review thresholds: Confirm that the configured timeout reflects your API's expected response times.
Verify notifications: Check that downtime and recovery notifications are configured and routed to the appropriate team.
4. Continue monitoring: Watch for recurring timeout failures or increased latency.
Conclusion: The simulated monitor recovered after a seven-minute interruption. Additional application-level evidence is needed to determine the root cause.
Connects securely to your tools. The creator never sees your data.
About this skill
Production systems fail, and generic LLMs often hallucinate status codes or suggest the wrong monitoring type for private infrastructure. This skill provides a structured framework for configuring and managing KEEPitALIVE monitoring through AI agents. It ensures your agent selects the correct monitoring strategy—whether that is active polling for public APIs or heartbeats for internal cron jobs—while adhering to security best practices and official API contracts.
What it does
- Configure monitors by selecting between HTTP, API, Browser, Ping, TCP, DNS, and Game Server types based on service requirements.
- Instrument heartbeats for private-network jobs, backups, and cron tasks to detect failures or missed runs without exposing internal ports.
- Automate incident response by retrieving check history, observing status transitions, and drafting evidence-based post-mortems.
- Manage triggers to configure webhooks and notifications based on state changes or specific event payloads.
- Audit reliability by generating reports from actual observation windows, latency data, and recorded downtime.
How it works
- Discovery: The skill retrieves the latest agent guide and OpenAPI specification to ensure endpoint names and payloads are current.
- Classification: It analyzes the target service to determine if it requires active polling or a passive heartbeat/event receiver.
- Configuration: The agent plans the monitor setup, including intervals and alert destinations, requesting explicit approval before resource mutation.
- Operation: It executes verified MCP tools or REST calls using scoped API keys, adhering to least-privilege principles.
Frameworks & tools
This skill interfaces with the KEEPitALIVE REST API and the @keepitalive/mcp server. It is designed for use within environments like Claude Code or Cursor that support MCP or outbound HTTP requests.
Why this beats prompting it yourself
Generic prompts often fail to distinguish between active polling and heartbeats, leading to "false green" status for private jobs. This skill enforces precise monitoring semantics, prevents the fabrication of uptime metrics, and ensures that sensitive heartbeat tokens are never committed to version control.
Use cases
- Monitor a public REST API including specific JSON response body assertions.
- Track success/failure of nightly database backups running in a private VPC.
- Notify the team via webhook when a GitHub Actions deployment fails.
- Generate a weekly reliability report based on verified monitoring data.
Known limitations
Requires an active KEEPitALIVE account and a scoped API key. Does not independently host checks; it manages the KEEPitALIVE service. Destructive operations and billing changes require manual confirmation.
Requires KEEPitALIVE account and API key. Skill does not host monitors; it manages the service via API/MCP. Destructive actions require explicit user approval.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
2 uses
Times used to date
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 1 month ago
- Free with an Agensi account
Requires
Permissions
Allowed Hosts