agentleFS
LukeJMaddenLukeJMadden/Veltrix-skills/skills/operations/deployment-monitor/SKILL.md

deployment-monitor

Skill1 starsChanged 8 months agoMITView on GitHub

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

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If READY → log and exit

    line 12
  2. Distinctive:

    If BUILDING → wait, check next cycle

    line 13
  3. Distinctive:

    If ERROR → enter self-heal flow

    line 14
  4. Distinctive:

    Never force-deploy over a working version

    line 51
  5. Distinctive:

    Never skip CI checks

    line 52
  6. Distinctive:

    Never deploy on Fridays unless critical

    line 53
  7. Distinctive:

    Check cron schedule before any restart (no restarts within 5 minutes of a scheduled job)

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Monitor deployments and self-heal when possible.

Check Flow

Every 30 minutes:

  1. Query deployment API for latest status
  2. If READY → log and exit
  3. If BUILDING → wait, check next cycle
  4. 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)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.