Agent skill

risk-management-specialist

Medical device risk management specialist implementing ISO 14971 throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use when user mentions risk management, ISO 14971, risk analysis, FMEA, fault tree analysis, hazard identification, risk control, risk matrix, benefit-risk analysis, residual risk, risk acceptability, or post-market risk.

Alireza Rezvani23,369★ · +428/wk · 1 repos on radarProfile →
claude-codecodexcursorships scriptsMIT
Install
npx skills add alirezarezvani/claude-skills --skill risk-management-specialist --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 6
SKILL.md size: 16 KB
Bundled scripts: yes
Path: ra-qm-team/skills/risk-management-specialist/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 23,791 · +422 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Risk Management Specialist ISO 14971:2019 risk management implementation throughout the medical device lifecycle. --- ## Table of Contents - [Risk Management Planning Workflow](#risk-management-planning-workflow) - [Risk Analysis Workflow](#risk-analysis-workflow) - [Risk Evaluation Workflow](#risk-evaluation-workflow) - [Risk Control Workflow](#risk-control-workflow) - [Post-Production Risk Management](#post-production-risk-management) - [Risk Assessment Templates](#risk-assessment-templates) - [Decision Frameworks](#decision-frameworks) - [Tools and References](#tools-and-references) --- ## Risk Management Planning Workflow Establish risk management process per ISO 14971. ### Workflow: Create Risk Management Plan 1. Define scope of risk management activities: - Medical device identification - Lifecycle stages covered - Applicable standards and regulations 2. Establish risk acceptability criteria: - Define probability categories (P1-P5) - Define severity categories (S1-S5) - Create risk matrix with acceptance thresholds 3. Assign responsibilities: - Risk management lead - Subject matter experts - Approval authorities 4. Define verification activities: - Methods for control verif

What's inside
Steps it walks through
  1. Table of Contents
  2. Risk Management Planning Workflow
  3. Workflow: Create Risk Management Plan
  4. Risk Management Plan Content
  5. Risk Acceptability Matrix (5x5)
  6. Risk Level Actions
  7. Risk Analysis Workflow
  8. Workflow: Conduct Risk Analysis
  9. Hazard Categories Checklist
  10. Analysis Method Selection
  11. Probability Criteria
  12. Severity Criteria
  13. Risk Evaluation Workflow
  14. Workflow: Evaluate Identified Risks
Ships with 5 files
  • references/iso14971-implementation-guide.md
  • references/risk-analysis-methods.md
  • references/risk-assessment-templates.md
  • scripts/fmea_analyzer.py
  • scripts/risk_matrix_calculator.py
More from claude-skills
All skills →
About this skill
What does the risk-management-specialist skill do?

Medical device risk management specialist implementing ISO 14971 throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use when user mentions risk management, ISO 14971, risk analysis, FMEA, fault tree analysis, hazard identification, risk control, risk matrix, benefit-risk analysis, residual risk, risk acceptability, or post-market risk.

How do I install it?

Run `npx skills add alirezarezvani/claude-skills --skill risk-management-specialist --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going