monitor

Monitor post-deploy health signals and escalate to diagnose on trip.

2|Updated Oct 2, 2025
One-click install
npx skills add https://github.com/misty-step/volume --skill monitor-misty-step
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitor
Source: https://github.com/misty-step/volume/tree/main/.agents/skills/monitor
Command: npx skills add https://github.com/misty-step/volume --skill monitor-misty-step

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

After a deployment, this skill watches key health and observability signals and escalates to diagnose if a regression is detected, ensuring quick visibility and safe handoffs.

Core Features & Use Cases

  • Monitors post-deploy health signals and logs to a central event stream.
  • Escalates to /diagnose on trip and closes clean when signals stay green through the grace window.
  • Provides structured hand-off data and supports configurable grace windows and signals.

Quick Start

Start monitoring a deployment by invoking the monitor after a deployment to observe signals and trigger escalation if needed.

Frequently Asked Questions about monitor

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

FAQPage Schema
How do I monitor post-deploy health signals and escalate automatically?

To monitor post-deploy health signals, this skill observes health checks, logs, and canary signals after a deployment, escalating to diagnose if a regression is detected while closing clean when signals stay green through the configured grace window.

What is a post-deploy grace window and how does it work?

A post-deploy grace window is a configurable duration after deployment where health signals are observed. If signals stay green through this window, monitoring closes cleanly; if a regression is detected, it escalates to diagnose.

How do I set up automatic escalation when post-deploy canary signals trip?

Automatic escalation on canary signal trips is configured via .spellbook/monitor.yaml, which defines the inputs, signals, and escalation behavior to trigger a diagnose action when a regression is detected.

Does post-deploy monitoring require a deploy receipt reference to start?

Yes, post-deploy monitoring requires a deploy receipt reference as an input, along with an optional grace duration, to begin observing health checks and canary signals after a deployment.

Why does my post-deploy monitoring close before all signals are checked?

Post-deploy monitoring closes cleanly when signals stay green through the configured grace window, enforcing a one-terminal-event contract per invocation to ensure structured hand-offs and safe escalations.