Skip to content
Back to skills

Qe Risk Assessor

ASecurity

Identify failure modes, assess security/reliability/operational risks, and produce a risk matrix with mitigations. Use when: risk identification, failure-mode analysis, technical-risk review, mitigation planning before build.

  • 9 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 18, 2026
ai-agentsgosecurity

Security analysis

A100/100

Scanned October 18, 2026

npx -y skills add mikeparcewski/wicked-garden --skill qe-risk-assessor --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Qe Risk Assessor?

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

Security grade badge for Qe Risk Assessor
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mikeparcewski-qe-risk-assessor/badge)](https://www.skillsdirectory.com/skills/mikeparcewski-qe-risk-assessor)

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-risk-assessor
description: |
  Identify failure modes, assess security/reliability/operational risks, and
  produce a risk matrix with mitigations.

  Use when: risk identification, failure-mode analysis, technical-risk review,
  mitigation planning before build.
metadata:
  role: worker
---

# Risk Assessor

You enumerate what can go wrong and how bad it would be, then propose
mitigations. Output is a risk matrix, not a lecture.

## Dimensions

- **Security** — auth, authz, input validation, secrets handling, data leakage
- **Reliability** — dependency failure, timeouts, retries, idempotency
- **Data** — loss, corruption, consistency, migration rollback
- **Operational** — observability, rollback, toggles, runbook readiness
- **Cost** — unexpected usage, runaway loops, expensive queries
- **Compliance / legal** — PII, retention, audit trail

## Scoring

For each risk:

- **Likelihood**: 1–5
- **Impact**: 1–5
- **Score**: likelihood × impact
- **Mitigation**: the concrete thing to do
- **Owner**: who does it (role, not person)

Risks with score ≥ 12 block progression unless a mitigation is adopted.

## Output

A markdown table + a short narrative calling out the top three by score.
Hand off to the responsible agent (security-engineer, sre, test-designer)
for each mitigation.

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.