skills.rest
Lightricks
LightricksOFFICIAL
Explore all skills by this author →
Website𝕏@lightricksGitHub

monitoring

Route monitoring requests to specialized sub-agents for SQL, alerts, and documentation.

Updated Aug 23, 2026
Search Tags:#monitoring#analytics#routing#metrics#alerts#usage#revenue
One-click install
npx skills add https://github.com/Lightricks/ltx-analytics-agents --skill monitoring-lightricks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: monitoring
Source: https://github.com/Lightricks/ltx-analytics-agents/tree/main/agents/monitoring
Command: npx skills add https://github.com/Lightricks/ltx-analytics-agents --skill monitoring-lightricks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill centralizes and delegates complex monitoring workflows by routing requests to specialized sub-agents, ensuring consistent routing, execution, and visibility across revenue, usage, enterprise, cost, and API performance metrics.

Core Features & Use Cases

  • Routes monitoring requests to Revenue Monitor, Usage Monitor, Enterprise Monitor, BE Cost Monitor, and API Runtime Monitor.
  • Enforces consistent data sources, thresholds, and alerting patterns via shared knowledge.
  • Enables end-to-end monitoring orchestration with clear ownership and reporting.

Quick Start

Provide a monitoring request and let the agent dispatch to the appropriate sub-agent for detailed analysis and alerts.

Frequently Asked Questions about monitoring

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

FAQPage Schema
How do I route monitoring requests for revenue and usage metrics to the right agent?▼

Monitoring requests are routed by identifying the monitoring type and dispatching it to the corresponding sub-agent, such as Revenue Monitor or Usage Monitor. This ensures specialized analysis and consistent alert configuration for your metrics.

What is the best way to set up alerts for API runtime and backend cost metrics?▼

To set up alerts for API runtime and backend cost metrics, the monitoring task is routed to the API Runtime Monitor or BE Cost Monitor sub-agent. These sub-agents use shared knowledge to determine required data sources, metrics, and alert thresholds.

How do I generate monitoring SQL queries for enterprise metrics?▼

Generating monitoring SQL for enterprise metrics involves routing the request to the Enterprise Monitor sub-agent. The sub-agent reads shared schema and metric standards to assemble, validate, and present the required SQL queries and documentation.

Does this monitoring approach enforce consistent data sources and thresholds across different metrics?▼

Yes, the monitoring approach enforces consistent data sources, thresholds, and alerting patterns by utilizing shared knowledge files. This includes shared schema, metric standards, and event registries across all specialized sub-agents.

Can I use one centralized workflow for monitoring revenue, usage, and API performance simultaneously?▼

You can use a centralized monitoring workflow to handle revenue, usage, and API performance metrics simultaneously. The system delegates tasks to specialized sub-agents, ensuring consistent execution, clear ownership, and end-to-end orchestration.

Related Skills

Explore More Data & Analytics Skills→
shekerkammashekerkamma

connect-data

Connect CSV, DuckDB, MotherDuck, PostgreSQL, BigQuery, and Snowflake data sources.

Community
Advanced
jikig-aijikig-ai
12

deployment-verification-agent

Generate pre- and post-deploy SQL checklists and verification queries for production data PRs.

Official
Advanced
OsirsOsirs

metrics-dashboard

Design product metric dashboards with KPIs, data sources, and alert thresholds.

Community
Intermediate
BuilderIOBuilderIO
3

delegate-to-agent

Delegate AI tasks to agent chat via sendToAgentChat and agentChat APIs.

Official
Advanced