Skip to content
Back to skills

Score Fmea Risk

ASecurity

Score severity, occurrence, detectability, and derive action priority for a failure mode.

  • 499 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 24, 2026
research

Security analysis

A100/100

Scanned September 24, 2026

npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill score-fmea-risk --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Score Fmea Risk?

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

Security grade badge for Score Fmea Risk
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-score-fmea-risk/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-score-fmea-risk)

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: score-fmea-risk
description: "Score severity, occurrence, detectability, and derive action priority for a failure mode."
---

# score-fmea-risk
## Purpose
Score severity, occurrence, detectability, and derive action priority for a failure mode.
## Input contract
```yaml
required: [failure_mode, severity_scale, occurrence_scale, detectability_scale]
optional: [evidence, priority_rule]
constraints: [scale anchors and direction must be declared before scoring]
```
## Procedure
1. Score severity, occurrence, and detectability against anchored scales.
2. Derive action priority using the declared rule.
3. Record evidence, uncertainty, and rationale for each score.
## Output contract
```yaml
produces: [severity_score, occurrence_score, detectability_score, action_priority, rationale]
delta_fields: [findings, evidence_updates, uncertainties, decisions]
```
## Quality gates
- Fixed scale semantics and scoring formula are retained; no relative substitution for risk methodology.
- A-class evidence coverage: declared universe = all failure modes in the register; numerator = modes with complete three-score evidence; batch increment = one scored mode batch; stopping reason = all material modes scored or residual unscored modes explicitly accepted; source references = incident data, tests, expert rationale; direction/threshold reason = prioritize higher severity/occurrence and lower detectability according to the declared rule.
## Failure and counterexamples
Do not compare scores from incompatible scales. Mark unknown rather than inventing a score.
## Provenance map
- resolved: severity-scoring
- resolved: occurrence-scoring
- resolved: detection-scoring
- resolved: action-priority-matrix

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…