skill-adeerkhan-vitruvius-fmea-brainstorm · by Install
$ agentstack add skill-adeerkhan-vitruvius-fmea-brainstorm ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-adeerkhan-vitruvius-fmea-brainstorm) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
FMEA Brainstorm
Systematically identify and rank failure modes for an engineering system or component. This skill is for brainstorming and qualitative risk screening, not quantitative failure analysis.
Workflow
flowchart LR
Input["System Description"] --> Identify["Identify Failure Modes"]
Identify --> Rate["Rate S/O/D"]
Rate --> RPN["Calculate RPN"]
RPN --> Rank["Rank by Risk"]
Rank --> Output["Failure Mode Table"]Invocation
/fmea-brainstorm Include: operating environment, loads, materials, usage profile, safety criticality, regulatory context.
Methodology
- Define system — scope, operating conditions, safety criticality, regulatory context. Ask if incomplete.
- Identify failure modes — per component: how could it fail? Consider documented failures, code-specified modes, industry databases, analogous systems.
- Rate S/O/D 1-10 — Severity, Occurrence, Detection. Calculate RPN = S × O × D.
- Rank by RPN — Critical (RPN≥200 or S≥9), Moderate (100-200), Low (.md`: System Definition, Failure Modes table (Component/Mode/Effect/S/O/D/RPN/Mitigation), Critical Items (RPN≥200 or S≥9) with mitigation + verification, Moderate Items, Assumptions.
Scope and Boundaries
- This skill identifies and ranks failure modes — it does NOT produce quantitative probability data.
- Output is qualitative brainstorming, not a formal FMEA for regulatory submission.
- Ratings are engineering judgments based on available evidence, not statistical data.
- For safety-critical systems, follow up with detailed analysis (FEA, testing, reliability analysis).
- Evidence quality: see
references/evidence-quality-tiers.md. - Research-only, not for final engineering sign-off.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: adeerkhan
- Source: adeerkhan/vitruvius
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.