Deployment monitor

Skill LukeJMadden/Veltrix-skills/skills/operations/deployment-monitor

Self-healing deployment monitoring skill. Use when checking deployment health, responding to failures, or setting up monitoring.From its SKILL.md

Install

npx -y skills add LukeJMadden/Veltrix-skills --skill deployment-monitor

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.5 KB, 343 tokens by cl100k_base, as published. Nobody here has run it

Monitor deployments and self-heal when possible.

Check Flow

Every 30 minutes:

Query deployment API for latest status
If READY → log and exit
If BUILDING → wait, check next cycle
If ERROR → enter self-heal flow

Self-Heal Flow

Failure detected
  ├── Attempt redeploy (retry 1/3)
  │   ├── Wait for completion (max 3 minutes)
  │   ├── If READY → alert: "Self-healed after 1 attempt"
  │   └── If ERROR → retry 2/3
  │       ├── If READY → alert: "Self-healed after 2 attempts"
  │       └── If ERROR → retry 3/3
  │           ├── If READY → alert: "Self-healed after 3 attempts"
  │           └── If ERROR → alert: "FAILED — manual review needed"
  └── Last working deployment stays live (platform default)

Alert Format

Success:

Deployment self-healed after N attempt(s).
Commit: [message]
URL: [deployment URL]

Failure:

DEPLOYMENT FAILED — self-heal exhausted (3 attempts).
Commit: [message]
URL: [deployment URL]
State: ERROR
Last working deployment is still live. Manual review needed.

Safety Rules

Never force-deploy over a working version
Never skip CI checks
Never deploy on Fridays unless critical
Check cron schedule before any restart (no restarts within 5 minutes of a scheduled job)

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.