Risk Based Testing
Produce a risk matrix or heatmap that quantifies what could break by business impact × probability.
Use Edge to load the skill risk-based-testing from petrkindlmann/qa-skills for my task. If Edge is not set up, read getedge.cc/SKILL.md and ask me first.
2 static scans, 0 counted findings.
Edge checks it again each time your agent loads it.
From the petrkindlmann public repository. Edge did not write or edit this skill.
What it does
- Produce a risk matrix or heatmap that quantifies what could break by business impact × probability, runs failure mode analysis on the top items, and maps test coverage to risk zones.
- Includes stakeholder interview frameworks and continuous reassessment.
- Run this BEFORE test-strategy or test-planning.
- Use when: "risk assessment," "risk matrix," "risk heatmap," "what could break," "critical paths," "failure modes," "where to focus testing." Not for: multi-quarter QA direction : use test-strategy.
- Not for: a single sprint/release test plan : use test-planning.
- Not for: hands-on session-based bug hunting : use exploratory-testing.
How it works
- 1Copy
Try for free gives you one prompt.
- 2Paste
Paste it into Claude Code, Codex or Cursor.
- 3Ask
Ask for the outcome. Your agent loads Risk Based Testing.
Related skills
Build a single sprint or release test plan. Covers feature decomposition into testable scenarios, requirements-to-test coverage mapping, effort estimation by test type, prioritization matrices (risk × effort), resource a
Produce a multi-quarter QA strategy document. Covers scope, risk-based prioritization, test levels (unit/integration/E2E), pyramid analysis, entry/exit criteria, quality KPIs, tool selection rationale, CI scaling levers,
Orchestrate the QA team through a full testing cycle — qa-lead strategy and test plan, qa-tester case writing, execution, sign-off.
Design test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when the user needs help with testing approaches, coverage, or te
Prioritize assumptions using an Impact × Risk matrix and suggest experiments for each. Use when triaging a list of assumptions, deciding what to test first, or applying the assumption prioritization canvas.
Identify, assess, and mitigate operational risks. Trigger with "what are the risks", "risk assessment", "risk register", "what could go wrong", or when the user is evaluating risks associated with a project, vendor, proc
No evidence record yet
No measured run with and without this skill yet, so this page makes no performance claim. 2 static scans, 0 counted findings. Security state at 2026-11-18: reviewed. Static scans check the code, not how well the skill works.
State definitionsSkill details
Security scansReviewed
2 static scans, 0 counted findings. Security state at 2026-11-18: reviewed. Edge checks it again each time your agent loads it.
Edge static checks (Edge-run): edge-static/1.0.2. Scope: Static patterns for remote execution, credentials with network sends, obfuscation, prompt overrides, hidden Unicode, binaries and persistence. Raw findings: not supplied.
Edge committed-secret checks (Edge-run): edge-secrets/1.0.0. Scope: Credentials committed in the skill's files (values never shown). Raw findings: not supplied.
Socket (skills.sh mirror): Version unavailable. Scope: Not supplied by the mirrored record. Raw findings: not supplied.
Snyk (skills.sh mirror): Version unavailable. Scope: Not supplied by the mirrored record. Raw findings: not supplied.
- Edge static checks
- Pass · 0 counted findings · 2026-11-18
- Edge committed-secret checks
- Pass · 0 counted findings · 2026-11-18
Creator, source & licencepetrkindlmann
From the petrkindlmann public repository. Edge did not write or edit this skill.
- Repository
- petrkindlmann/qa-skills
- Skill file
- View source at revision
- Revision
- b3bb61bd268b147476252c6ed5a0440c87b97441
- Package hash
- sha256:7b28d8fb289af1cc2fec842e1c457e06c3a305952142013b7c7e99aa02f5ba92
- Licence
- MIT
- Description
- Produce a risk matrix or heatmap that quantifies what could break by business impact × probability, runs failure mode analysis on the top items, and maps test coverage to risk zones. Includes stakeholder interview frameworks and continuous reassessment. Run this BEFORE test-strategy or test-planning. Use when: "risk assessment," "risk matrix," "risk heatmap," "what could break," "critical paths," "failure modes," "where to focus testing." Not for: multi-quarter QA direction : use test-strategy. Not for: a single sprint/release test plan : use test-planning. Not for: hands-on session-based bug hunting : use exploratory-testing. Related: test-strategy, test-planning, release-readiness, qa-metrics.
Quoted from the skill’s own description
Read skill files2 files
2 files, 24.9 KB at revision b3bb61bd268b.
Questions about Risk Based Testing
What does Risk Based Testing do?
Produce a risk matrix or heatmap that quantifies what could break by business impact × probability. Published by petrkindlmann (petrkindlmann/qa-skills).
Is Risk Based Testing safe to use?
Edge security state: Reviewed (2 Edge-run static scans, scanned Nov 18, 2026). The Evidence tab shows the scan.
How do I use Risk Based Testing in Claude Code, Codex or Cursor?
Click Try for free, pick your agent and follow its one step. Edge is free, with no Edge account.