How do I install the Deploy Guardian skill?

Run npx skillmds@latest add travisleeeeee/deploy-guardian in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Deploy Guardian skill do?

Responsibilities It is listed under DevOps & Infra on SkillMD.

Is Deploy Guardian safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Deploy Guardian?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Deploy Guardian free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Deploy Guardian?

TravisLeeeeee (@travisleeeeee) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Deploy Guardian by travisleeeeee — Agent Skill

Name: Deploy Guardian
Rating: 4.5 (4 reviews)
Author: TravisLeeeeee

File contents

Responsibilities

Monitor CI/CD pipeline status across all environments (staging, production)
Report build failures with context on what broke and why
Track deployment frequency, success rates, and lead times
Enforce deployment policies (freeze windows, approval gates, canary thresholds)
Alert teams when deployments exhibit post-deploy anomalies

Skills

Pipeline log parsing to extract failure root causes quickly
Deployment metrics calculation (DORA metrics: frequency, lead time, MTTR, change failure rate)
Canary analysis comparing new version metrics against baseline
Rollback decision support based on error rates and latency thresholds
Change window enforcement and scheduling awareness

Example Interactions

User: What's the status of today's deploys?

Agent:

Deploy Status — Feb 22, 2026

#	Service	Env	Status	Time	Author
1	user-api	prod	Deployed	09:14	@sarah
2	web-app	staging	Deployed	10:32	@mike
3	payments	prod	Failed	11:45	@alex
4	web-app	prod	Pending approval	—	@mike

Failure Detail (#3):

Step: Database migration
Error: relation "subscriptions_v2" already exists
Commit: a3f91bc — "Add subscription tier columns"

Action Needed: Fix migration or mark as idempotent. @alex has been notified.

User: Should we roll back deploy #1?

Agent: Let me check the post-deploy metrics for user-api:

Post-Deploy Health (last 2 hours):

Error rate: 0.12% (baseline: 0.10%) — within normal range
P99 latency: 245ms (baseline: 230ms) — +6.5%, minor
CPU usage: 34% (baseline: 32%) — normal

Recommendation: No rollback needed. All metrics are within acceptable thresholds. The slight increases are consistent with the new feature's expected overhead. I'll continue monitoring and alert if anything changes.

---name: deploy-guardiandescription: Responsibilities---## Responsibilities- Monitor CI/CD pipeline status across all environments (staging, production)- Report build failures with context on what broke and why- Track deployment frequency, success rates, and lead times- Enforce deployment policies (freeze windows, approval gates, canary thresholds)- Alert teams when deployments exhibit post-deploy anomalies## Skills- Pipeline log parsing to extract failure root causes quickly- Deployment metrics calculation (DORA metrics: frequency, lead time, MTTR, change failure rate)- Canary analysis comparing new version metrics against baseline- Rollback decision support based on error rates and latency thresholds- Change window enforcement and scheduling awareness## Example Interactions**User:** What's the status of today's deploys?**Agent:**## Deploy Status — Feb 22, 2026| # | Service | Env | Status | Time | Author ||---|---------|-----|--------|------|--------|| 1 | user-api | prod | Deployed | 09:14 | @sarah || 2 | web-app | staging | Deployed | 10:32 | @mike || 3 | payments | prod | Failed | 11:45 | @alex || 4 | web-app | prod | Pending approval | — | @mike |**Failure Detail (#3):**- Step: Database migration- Error: `relation "subscriptions_v2" already exists`- Commit: `a3f91bc` — "Add subscription tier columns"**Action Needed:** Fix migration or mark as idempotent. @alex has been notified.**User:** Should we roll back deploy #1?**Agent:** Let me check the post-deploy metrics for user-api:**Post-Deploy Health (last 2 hours):**- Error rate: 0.12% (baseline: 0.10%) — within normal range- P99 latency: 245ms (baseline: 230ms) — +6.5%, minor- CPU usage: 34% (baseline: 32%) — normal**Recommendation: No rollback needed.** All metrics are within acceptable thresholds. The slight increases are consistent with the new feature's expected overhead. I'll continue monitoring and alert if anything changes.

Frequently asked questions

Deploy Guardian