coo-alerts

Monitor system health by checking ingest failures, agent issues, and database connectivity.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/OrionArchitekton/cosmocrat-core --skill coo-alerts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coo-alerts
Source: https://github.com/OrionArchitekton/cosmocrat-core/tree/main/skills/ops/coo-alerts
Command: npx skills add https://github.com/OrionArchitekton/cosmocrat-core --skill coo-alerts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill proactively monitors the health of critical system components, identifying and alerting on potential issues before they impact users.

Core Features & Use Cases

  • Automated Health Checks: Regularly checks ingest pipelines, agent status, database connectivity, and disk space.
  • Proactive Alerting: Notifies relevant parties about failures in ingest, agent operations, or connectivity to ClickHouse and Langfuse.
  • Use Case: Ensure the continuous operation of the system by automatically detecting and reporting on ingest failures or agent malfunctions.

Quick Start

Run the coo-alerts skill to check the system's health status.

Frequently Asked Questions about coo-alerts

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

FAQPage Schema
How do I monitor system health for ingest failures and agent issues?

To monitor system health, you can use automated health checks to regularly verify ingest pipelines, agent status, database connectivity, and disk space, alerting you to failures before they impact users.

Does automated health checking work with ClickHouse and Langfuse?

Yes, proactive alerting directly monitors connectivity to ClickHouse and Langfuse, notifying relevant parties about database connectivity issues or agent operation failures during scheduled execution.

What is the best way to set up proactive alerting for operational dashboards?

The best way to establish proactive alerting for operational dashboards is applying scheduled execution with read-only access to system metrics, automatically detecting and reporting ingest failures or malfunctions.

How do I automate incident response workflows for database connectivity issues?

You automate incident response workflows by running scheduled, read-only checks against system metrics and logs to identify database connectivity problems, ensuring continuous operation by automatically reporting anomalies.

What system components are checked during an automated health check?

Automated health checks regularly inspect ingest pipelines, agent status, database connectivity, and disk space to proactively identify and alert on potential issues across critical system components.

Why do I need read-only access for scheduled system health monitoring?

You need read-only access for scheduled system health monitoring because the process safely checks system metrics and logs to detect ingest failures and agent issues without modifying operational data.