keep-aiops

Manage alerts and orchestrate incident workflows via the Keep AIOps API.

1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/BjzyLabs/vCenterCert --skill keep-aiops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: keep-aiops
Source: https://github.com/BjzyLabs/vCenterCert/tree/main/.ruler/skills/keep-aiops
Command: npx skills add https://github.com/BjzyLabs/vCenterCert --skill keep-aiops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Modern infrastructure generates alerts from multiple monitoring tools, but teams struggle with alert fragmentation, manual triage, and inconsistent incident response. This skill provides a centralized interface to manage alerts and orchestrate automated responses via Keep AIOps.

Core Features & Use Cases

  • Centralized alert management and routing across multiple monitoring sources via Keep AIOps.
  • Automated remediation workflows triggered by specific alert conditions to reduce mean time to repair.
  • Investigation context enrichment and audit trails to improve incident resolution consistency.
  • Intelligent alert routing to on-call schedules and escalation policies.

Quick Start

Configure your environment with KEEP_API_URL and KEEP_API_KEY, then start querying alerts and triggering workflows. For example, fetch firing alerts with the Keep API and start a remediation workflow using the appropriate endpoint. Example: curl -H "X-API-KEY: $KEEP_API_KEY" "$KEEP_API_URL/alerts?status=firing" | jq

Frequently Asked Questions about keep-aiops

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

FAQPage Schema
How do I aggregate cross-source alerts for automated incident response?

Aggregating cross-source alerts for automated incident response requires a centralized interface to consolidate alerts from multiple monitoring tools. This skill uses Keep AIOps to apply cross-source alert aggregation, enrich investigation context, and orchestrate automated workflows.

How do I configure API credentials to query firing alerts in Keep AIOps?

Configuring API credentials to query firing alerts requires setting the environment variables KEEP_API_URL and KEEP_API_KEY with valid Keep API access. This setup enables you to fetch firing alerts and trigger automated remediation workflows via the API endpoints.

Can I trigger automated remediation workflows based on specific alert conditions?

You can trigger automated remediation workflows based on specific alert conditions using this skill. It integrates with Keep AIOps to apply automated workflows for incident response, reducing mean time to repair across multiple monitoring sources.

Does this approach support intelligent alert routing to on-call schedules?

This approach supports intelligent alert routing to on-call schedules and escalation policies. The skill provides centralized alert management and routing across multiple monitoring sources via the Keep AIOps platform to improve incident resolution consistency.

What is the best way to enrich investigation context during incident triage?

The best way to enrich investigation context during incident triage is to centralize alert management and apply audit trails. This skill uses Keep AIOps to provide investigation context enrichment, ensuring consistent incident resolution across fragmented monitoring sources.

Do I need Keep API access to orchestrate incident response workflows?

You need Keep API access, a valid API key, and the environment variables KEEP_API_URL and KEEP_API_KEY to orchestrate incident response. These prerequisites are required for the skill to function and communicate with the Keep AIOps platform.