oc-monitoring-ops
Post-deployment observability: uptime monitoring, error tracking, structured logging, alerting pipelines, and incident response runbooks. Sits after oc-deploy-ops in the pipeline — oc-deploy-ops ships it, oc-monitoring-ops watches it. Use for /oc-monitor, "set up monitoring", "error tracking", "uptime check", "alerting", "incident response", "observability", "what's happening in prod", "set up Sentry", "logging strategy", "on-call", "runbook", "SLO", "SLI", "is prod healthy", "why is it slow", "error rate", "status page". NOT opchain skill-usage metering (oc-telemetry-ops).
Target: Cloud, operations & security. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Monitoring Ops
- /oc-monitor — Command Reference
- Session Persistence (Checkpoint Protocol)
- Resume on Start
- What's Tracked
- How This Skill Fits the Pipeline
- Cross-Skill Connections
- Observability Maturity Model
On first invocation, read references/orchestrator.md and follow its welcome protocol. Post-deployment observability skill. Deploy-ops ships the code; oc-monitoring-ops watches it run. Covers five domains: uptime monitoring, error tracking, structured logging, alerting pipelines, and incident response. This skill does NOT build features or deploy code — it instruments what's already deployed and establishes the feedback loop that catches problems before users report them. -- Checkpoint: {project-dir}/.checkpoints/oc-monitoring-ops.checkpoint.json When any /oc-monitor command is invoked: 1. Check for checkpoint 2. If exists: show tier, tools, SLO status, active incidents, maturity grade, next action 3. Ask: "Continue, restart, or show full checkpoint?" 4. On continue: load context, resume from nextactions[0] Monitoring-ops uniquely stores runtime state alongside pipeline progress — the last health check result, active incident count, and SLO budget consumption. This means the checkpoint serves double duty: session persistence AND operational snapshot. -- oc-deploy-ops ships it, oc-monitoring-ops watches it. The handoff: 1. oc-deploy-ops completes production promotion 2. oc-deploy-ops
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- asfbay-bit/opchain-skills
- Source file
- plugins/opchain/skills/oc-monitoring-ops/SKILL.md
- Fixed revision
- 1c7c7bd69a7d875a5dffb419911c24752ca6c285
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: asfbay-bit/opchain-skills · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T17:01:26.962Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
Apache-2.0. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.