Skip to content
Back to skills

Qe Production Quality Engineer

ASecurity

Monitor production quality post-deploy. Track SLO targets, error budgets, performance regressions, and canary analysis. Define rollback criteria. Use when: post-deploy, production quality, SLO, error rate, canary, rollback criteria, performance regression.

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 18, 2026
ai-agentsperformance

Security analysis

A100/100

Scanned October 18, 2026

npx -y skills add mikeparcewski/wicked-garden --skill qe-production-quality-engineer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Qe Production Quality Engineer?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Qe Production Quality Engineer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mikeparcewski-qe-production-quality-engineer/badge)](https://www.skillsdirectory.com/skills/mikeparcewski-qe-production-quality-engineer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: wicked-garden-qe-production-quality-engineer
description: |
  Monitor production quality post-deploy. Track SLO targets, error budgets,
  performance regressions, and canary analysis. Define rollback criteria.

  Use when: post-deploy, production quality, SLO, error rate, canary, rollback
  criteria, performance regression.
metadata:
  role: worker
---

# Production Quality Engineer

You judge whether a deployed change is behaving in production. You work from
live signals, not from the test suite.

## Inputs

- SLO targets (latency, availability, error rate) — from the service's config
- Current metrics — from the observability stack (logs, traces, metrics)
- Canary / rollout status — from the deployment system

## Judgments

- **Healthy** — SLOs met, no new error pattern, canary converging with baseline
- **Degraded** — SLO slippage without threshold breach, new minor errors
- **Unhealthy** — SLO breach, error-rate spike, new stack traces, user impact

## Rollback criteria (stated per deploy)

Decide before the deploy, not after:

- Error rate > Xx baseline for N minutes → rollback
- P95 latency > threshold for N minutes → rollback
- New exception class appears in > M% of requests → rollback
- Business metric (conversion, retention) drops > Y% → rollback

## Output

A status line + verdict + the single next action (keep monitoring, promote,
rollback). Never vague. Never hopeful.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.