monitoring-ops

Instruments production systems for uptime, error, and performance monitoring.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/asfbay-bit/opchain --skill monitoring-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitoring-ops
Source: https://github.com/asfbay-bit/opchain/tree/main/skills/monitoring-ops
Command: npx skills add https://github.com/asfbay-bit/opchain --skill monitoring-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Post-deploy observability is essential for detecting, diagnosing, and responding to production issues. Monitoring-ops provides a structured, cross-skill framework to instrument deployments, track uptime and reliability, and orchestrate runbooks across the pipeline to minimize mean time to recovery.

Core Features & Use Cases

  • Post-deploy observability spanning uptime monitoring, error tracking, structured logging, alerting pipelines, and incident response runbooks.
  • Checkpoint-based session persistence to maintain state across engagements and enable seamless handoffs between skills.
  • Cross-skill coordination with standardized dashboards, SLO budgeting, and runbooks to reduce MTTR and improve reliability.

Quick Start

Trigger the monitoring-ops workflow on a deployed project with /monitor, then configure a basic health check and alerting rules to get started.

Frequently Asked Questions about monitoring-ops

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

FAQPage Schema
How do I set up post-deploy observability and health checks for my production application?

Post-deploy observability instruments production systems to monitor uptime, errors, and performance. You can configure basic health checks, structured logging, and alerting rules to track deployment reliability and detect issues early.

Can I use this monitoring workflow with frameworks like Next.js, FastAPI, or Cloudflare Workers?

Yes, the monitoring workflow applies across stacks like Cloudflare Workers, Next.js, Vercel, and FastAPI. It standardizes uptime monitoring, error tracking, and incident response runbooks regardless of your specific deployment platform.

What is SLO budgeting and how does it help with incident response?

SLO budgeting tracks reliability targets to determine when error thresholds are breached. It integrates with standardized incident templates and runbooks to automate reliability workflows, reducing mean time to recovery during production incidents.

How do I configure alerting pipelines and dashboards to reduce mean time to recovery?

Configure alerting pipelines and standardized dashboards to orchestrate incident response runbooks. This structured framework maintains state across engagements, enabling seamless handoffs and minimizing mean time to recovery for production issues.

Do I need a deployed project to start instrumenting uptime monitoring and error tracking?

Yes, you need a deployed project to instrument production systems. Trigger the workflow with a monitor command on your deployment, then configure health checks and alerting rules to begin tracking uptime and errors effectively.