Agent skill

Risk Management Specialist

by alirezarezvani in alirezarezvani/claude-skills

Medical device risk management specialist implementing ISO 14971 throughout product lifecycle.

MITAuto-check passedLegal & Compliance

Install Risk Management Specialist

skills CLI
$ npx skills add alirezarezvani/claude-skills --skill risk-management-specialist -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install alirezarezvani/claude-skills risk-management-specialist --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ra-qm-team/skills/risk-management-specialist .claude/skills/risk-management-specialist && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
risk-management-specialist
GitHub stars
28k
Used in
1 other repo
Token cost
~4.1k tokens
SKILL.md length
1,432 words
Files
6 (incl. scripts, references)
Skills in repo
342
Repo updated
First seen
Licence
MIT

At a glance

Medical device risk management specialist implementing ISO 14971 throughout product lifecycle.

  • Works in 8 steps: Define scope of risk management activities → Establish risk acceptability criteria → Assign responsibilities → …
  • User mentions risk management
  • SKILL.md covers Table of Contents, Risk Management Planning…, Risk Analysis Workflow and Risk Evaluation Workflow, plus 3 more sections
  • Runs Python scripts from its folder; calls python

What it does

Risk Management Specialist is an agent skill from alirezarezvani/claude-skills. 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.

Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `references/iso14971-implementation-guide.md`, `references/risk-analysis-methods.md` and `references/risk-assessment-templates.md`).

It sits in Legal & Compliance, covering Legal risk assessment. The repository describes itself as: 380 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 380+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8… The licence is MIT.

When your agent uses it

  • User mentions risk management
  • Fault tree analysis
  • Hazard identification
  • Benefit-risk analysis

Example prompts

  • “/risk-management-specialist”

Requirements

  • Python 3

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Define scope of risk management activities
  2. Establish risk acceptability criteria
  3. Assign responsibilities
  4. Define verification activities
  5. Plan production and post-production activities
  6. Obtain plan approval
  7. Establish risk management file
  8. Validation: Plan approved; acceptability criteria defined; responsibilities assigned; file established

What it can do on your machine

Read from SKILL.md and the folder at commit 19392f7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Risk Management Specialist loads about 4.1k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 110 tokens; SKILL.md has 1,432 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~110
When it runs · the whole SKILL.md, loaded when a task matches
~4.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~12k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from alirezarezvani/claude-skills at commit 19392f7, republished under its MIT licence (© alirezarezvani). 1,432 words, ~4,137 tokens.

Download SKILL.mdSave it as .claude/skills/risk-management-specialist/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
risk-management-specialist
description
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.

Risk Management Specialist

ISO 14971:2019 risk management implementation throughout the medical device lifecycle.


Table of Contents


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 verification
    • Acceptance criteria
  5. Plan production and post-production activities:
    • Information sources
    • Review triggers
    • Update procedures
  6. Obtain plan approval
  7. Establish risk management file
  8. Validation: Plan approved; acceptability criteria defined; responsibilities assigned; file established
Risk Management Plan Content
SectionContentEvidence
ScopeDevice and lifecycle coverageScope statement
CriteriaRisk acceptability matrixRisk matrix document
ResponsibilitiesRoles and authoritiesRACI chart
VerificationMethods and acceptanceVerification plan
Production/Post-ProductionMonitoring activitiesSurveillance plan
Risk Acceptability Matrix (5x5)
Probability \ SeverityNegligibleMinorSeriousCriticalCatastrophic
Frequent (P5)MediumHighHighUnacceptableUnacceptable
Probable (P4)MediumMediumHighHighUnacceptable
Occasional (P3)LowMediumMediumHighHigh
Remote (P2)LowLowMediumMediumHigh
Improbable (P1)LowLowLowMediumMedium
Risk Level Actions
LevelAcceptableAction Required
LowYesDocument and accept; still reduce as far as possible (EU MDR)
MediumAfter reduction AFAPReduce as far as possible; document why further reduction is impossible
HighAfter reduction AFAPReduction required; demonstrate all further options exhausted
UnacceptableNoDesign change mandatory

EU MDR — AFAP, not ALARP: For CE-marked devices, risks must be reduced as far as possible (AFAP) without economic considerations (MDR Annex I, GSPR 1–4; EN ISO 14971:2019/A11:2021 Z-annexes deviation). ALARP ("as low as reasonably practicable"), which permits cost-benefit weighing in acceptability decisions, is not an acceptable criterion under the EU MDR — a notified body will flag it. ISO 14971:2019 itself removed ALARP from the normative text. ALARP may persist in some non-EU jurisdictions (e.g., the UK HSE tradition); if used outside the EU, flag the deviation from EU requirements explicitly.


Risk Analysis Workflow

Identify hazards and estimate risks systematically.

Workflow: Conduct Risk Analysis
  1. Define intended use and reasonably foreseeable misuse:
    • Medical indication
    • Patient population
    • User population
    • Use environment
  2. Select analysis method(s):
    • FMEA for component/function analysis
    • FTA for system-level analysis
    • HAZOP for process deviations
    • Use Error Analysis for user interaction
  3. Identify hazards by category:
    • Energy hazards (electrical, mechanical, thermal)
    • Biological hazards (bioburden, biocompatibility)
    • Chemical hazards (residues, leachables)
    • Operational hazards (software, use errors)
  4. Determine hazardous situations:
    • Sequence of events
    • Foreseeable misuse scenarios
    • Single fault conditions
  5. Estimate probability of harm (P1-P5)
  6. Estimate severity of harm (S1-S5)
  7. Document in hazard analysis worksheet
  8. Validation: All hazard categories addressed; all hazards documented; probability and severity assigned
Hazard Categories Checklist
CategoryExamplesAnalyzed
ElectricalShock, burns, interference☐
MechanicalCrushing, cutting, entrapment☐
ThermalBurns, tissue damage☐
RadiationIonizing, non-ionizing☐
BiologicalInfection, biocompatibility☐
ChemicalToxicity, irritation☐
SoftwareIncorrect output, timing☐
Use ErrorMisuse, perception, cognition☐
EnvironmentEMC, mechanical stress☐
Analysis Method Selection
SituationRecommended Method
Component failuresFMEA
System-level failureFTA
Process deviationsHAZOP
User interactionUse Error Analysis
Software behaviorSoftware FMEA
Early design phasePHA
Probability Criteria
LevelNameDescriptionFrequency
P5FrequentExpected to occur>10⁻³
P4ProbableLikely to occur10⁻³ to 10⁻⁴
P3OccasionalMay occur10⁻⁴ to 10⁻⁵
P2RemoteUnlikely10⁻⁵ to 10⁻⁶
P1ImprobableVery unlikely<10⁻⁶
Severity Criteria
LevelNameDescriptionHarm
S5CatastrophicDeathDeath
S4CriticalPermanent impairmentIrreversible injury
S3SeriousInjury requiring interventionReversible injury
S2MinorTemporary discomfortNo treatment needed
S1NegligibleInconvenienceNo injury

See: references/risk-analysis-methods.md


Risk Evaluation Workflow

Evaluate risks against acceptability criteria.

Workflow: Evaluate Identified Risks
  1. Calculate initial risk level from probability × severity
  2. Compare to risk acceptability criteria
  3. For each risk, determine:
    • Acceptable: Document and accept (EU MDR: still reduce as far as possible)
    • Reduction required (AFAP): Proceed to risk control
    • Unacceptable: Mandatory risk control
  4. Document evaluation rationale
  5. Identify risks requiring benefit-risk analysis
  6. Complete benefit-risk analysis if applicable
  7. Compile risk evaluation summary
  8. Validation: All risks evaluated; acceptability determined; rationale documented
Risk Evaluation Decision Tree
Risk Estimated
      │
      ▼
Apply Acceptability Criteria
      │
      ├── Low Risk ──────────► Accept and document
      │
      ├── Medium Risk ───────► Reduce as far as possible (AFAP)
      │   │                    Document why further reduction impossible
      │   ▼
      │   Further reduction possible?
      │   │
      │   Yes──► Implement control
      │   No───► Document AFAP rationale (no economic considerations)
      │
      ├── High Risk ─────────► Risk reduction required
      │   │                    Must demonstrate reduction AFAP
      │   ▼
      │   Implement control
      │   Verify residual risk
      │
      └── Unacceptable ──────► Design change mandatory
                               Cannot proceed without control
AFAP Demonstration Requirements (EU MDR)
CriterionEvidence Required
All control options consideredAnalysis of every feasible control per the hierarchy (design, protective measures, information)
Further reduction impossibleEvidence each remaining option is technically infeasible or does not further reduce risk
State of the artComparison to similar devices and current standards
Stakeholder inputClinical/user perspectives

Economic considerations (cost of further risk reduction) must not enter the EU acceptability decision (MDR Annex I GSPR 2; EN ISO 14971:2019/A11:2021). Cost may inform business decisions about whether to market the device — never whether a risk is acceptable.

Benefit-Risk Analysis Triggers
SituationBenefit-Risk Required
Residual risk remains highYes
No feasible risk reductionYes
Novel deviceYes
Unacceptable risk with clinical benefitYes
All risks lowNo

Risk Control Workflow

Implement and verify risk control measures.

Show full SKILL.md (580 more words)Show less
Workflow: Implement Risk Controls
  1. Identify risk control options:
    • Inherent safety by design (Priority 1)
    • Protective measures in device (Priority 2)
    • Information for safety (Priority 3)
  2. Select optimal control following hierarchy
  3. Analyze control for new hazards introduced
  4. Document control in design requirements
  5. Implement control in design
  6. Develop verification protocol
  7. Execute verification and document results
  8. Evaluate residual risk with control in place
  9. Validation: Control implemented; verification passed; residual risk acceptable; no unaddressed new hazards
Risk Control Hierarchy
PriorityControl TypeExamplesEffectiveness
1Inherent SafetyEliminate hazard, fail-safe designHighest
2Protective MeasuresGuards, alarms, automatic shutdownHigh
3InformationWarnings, training, IFULower
Risk Control Option Analysis Template
RISK CONTROL OPTION ANALYSIS

Hazard ID: H-[XXX]
Hazard: [Description]
Initial Risk: P[X] × S[X] = [Level]

OPTIONS CONSIDERED:
| Option | Control Type | New Hazards | Feasibility | Selected |
|--------|--------------|-------------|-------------|----------|
| 1 | [Type] | [Yes/No] | [H/M/L] | [Yes/No] |
| 2 | [Type] | [Yes/No] | [H/M/L] | [Yes/No] |

SELECTED CONTROL: Option [X]
Rationale: [Justification for selection]

IMPLEMENTATION:
- Requirement: [REQ-XXX]
- Design Document: [Reference]

VERIFICATION:
- Method: [Test/Analysis/Review]
- Protocol: [Reference]
- Acceptance Criteria: [Criteria]
Risk Control Verification Methods
MethodWhen to UseEvidence
TestQuantifiable performanceTest report
InspectionPhysical presenceInspection record
AnalysisDesign calculationAnalysis report
ReviewDocumentation checkReview record
Residual Risk Evaluation
After ControlAction
AcceptableDocument, proceed
Reduced AFAPDocument rationale (no economic considerations), proceed
Still unacceptableAdditional control or design change
New hazard introducedAnalyze and control new hazard

Post-Production Risk Management

Monitor and update risk management throughout product lifecycle.

Workflow: Post-Production Risk Monitoring
  1. Identify information sources:
    • Customer complaints
    • Service reports
    • Vigilance/adverse events
    • Literature monitoring
    • Clinical studies
  2. Establish collection procedures
  3. Define review triggers:
    • New hazard identified
    • Increased frequency of known hazard
    • Serious incident
    • Regulatory feedback
  4. Analyze incoming information for risk relevance
  5. Update risk management file as needed
  6. Communicate significant findings
  7. Conduct periodic risk management review
  8. Validation: Information sources monitored; file current; reviews completed per schedule
Information Sources
SourceInformation TypeReview Frequency
ComplaintsUse issues, failuresContinuous
ServiceField failures, repairsMonthly
VigilanceSerious incidentsImmediate
LiteratureSimilar device issuesQuarterly
RegulatoryAuthority feedbackAs received
ClinicalPMCF dataPer plan
Risk Management File Update Triggers
TriggerResponse TimeAction
Serious incidentImmediateFull risk review
New hazard identified30 daysRisk analysis update
Trend increase60 daysTrend analysis
Design changeBefore implementationImpact assessment
Standards updatePer transition periodGap analysis
Periodic Review Requirements
Review ElementFrequency
Risk management file completenessAnnual
Risk control effectivenessAnnual
Post-market information analysisQuarterly
Risk-benefit conclusionsAnnual or on new data

Risk Assessment Templates

→ See references/risk-assessment-templates.md for details

Decision Frameworks

Risk Control Selection
What is the risk level?
        │
        ├── Unacceptable ──► Can hazard be eliminated?
        │                    │
        │                Yes─┴─No
        │                 │     │
        │                 ▼     ▼
        │            Eliminate  Can protective
        │            hazard     measure reduce?
        │                           │
        │                       Yes─┴─No
        │                        │     │
        │                        ▼     ▼
        │                   Add       Add warning
        │                   protection + training
        │
        └── High/Medium ──► Apply hierarchy
                            starting at Level 1
New Hazard Analysis
QuestionIf YesIf No
Does control introduce new hazard?Analyze new hazardProceed
Is new risk higher than original?Reject control optionAcceptable trade-off
Can new hazard be controlled?Add controlReject control option
Risk Acceptability Decision
ConditionDecision
All risks LowAcceptable
Medium risks reduced AFAPAcceptable
High risks reduced AFAP, documentedAcceptable if benefits outweigh
Any Unacceptable residualNot acceptable - redesign

Tools and References

Scripts
ToolPurposeUsage
risk_matrix_calculator.pyCalculate risk levels and FMEA RPNpython risk_matrix_calculator.py --help

Risk Matrix Calculator Features:

  • ISO 14971 5x5 risk matrix calculation
  • FMEA RPN (Risk Priority Number) calculation
  • Interactive mode for guided assessment
  • Display risk criteria definitions
  • JSON output for integration
References
DocumentContent
iso14971-implementation-guide.mdComplete ISO 14971:2019 implementation with templates
risk-analysis-methods.mdFMEA, FTA, HAZOP, Use Error Analysis methods
Quick Reference: ISO 14971 Process
StageKey ActivitiesOutput
PlanningDefine scope, criteria, responsibilitiesRisk Management Plan
AnalysisIdentify hazards, estimate riskHazard Analysis
EvaluationCompare to criteria, AFAP assessment (EU)Risk Evaluation
ControlImplement hierarchy, verifyRisk Control Records
ResidualOverall assessment, benefit-riskRisk Management Report
ProductionMonitor, review, updateUpdated RM File

SkillIntegration Point
quality-manager-qms-iso13485QMS integration
capa-officerRisk-based CAPA
regulatory-affairs-headRegulatory submissions
quality-documentation-managerRisk file management

© alirezarezvani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (scripts, references) in ra-qm-team/skills/risk-management-specialist of alirezarezvani/claude-skills.

  • SKILL.md
  • references/iso14971-implementation-guide.md
  • references/risk-analysis-methods.md
  • references/risk-assessment-templates.md
  • scripts/fmea_analyzer.py
  • scripts/risk_matrix_calculator.py

Open the folder on GitHubat commit 19392f7

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in alirezarezvani/claude-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Risk Management Specialist next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Risk Management Specialist compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Risk Management Specialist this skillalirezarezvani/claude-skills28k1 repos~4.1kAutomated safety check: PassMIT
Product Launch Legal Reviewanthropics/claude-for-legal9.6k2 repos~5kAutomated safety check: PassApache-2.0
Legal Risk Visualizationzh-xx/legal-assistant-skills174—~2.4kAutomated safety check: PassApache-2.0
Contract Renewal Trackeranthropics/claude-for-legal9.6k2 repos~3.1kAutomated safety check: PassApache-2.0
Deep Risk Analysiszubair-trabzada/ai-legal-claude1.8k—~1.9kAutomated safety check: PassNone
Canghe Tianyanchafreestylefly/canghe-skills461—~2.4kAutomated safety check: PassNone

Similar skills

  • Product Launch Legal Review

    anthropics/claude-for-legal

    Official

    Runs a category-by-category legal review of a product launch from a PRD or tracker ticket, calibrated to your team's framework, and writes a review memo in house format.

    9.6k GitHub starsUsed in 2 repos~5k tokens
    Legal & ComplianceAuto-check passed
  • Legal Risk Visualization

    zh-xx/legal-assistant-skills

    法律风险结构化分析与可视化。基于法律分析文本,执行五步风险抽取模型, 生成四层可视化输出(雷达图数据、风险矩阵、影响路径图、决策树)。

    174 GitHub stars~2.4k tokensUpdated 5 mo ago
    Legal & ComplianceAuto-check passed
  • Contract Renewal Tracker

    anthropics/claude-for-legal

    Official

    Shows which contracts renew soon and when notice must be sent by, working from a maintained renewal register, and warns about missed cancellation windows.

    9.6k GitHub starsUsed in 2 repos~3.1k tokens
    Legal & ComplianceAuto-check passed
  • Deep Risk Analysis

    zubair-trabzada/ai-legal-claude

    Clause-by-clause contract risk analysis with severity scoring, financial exposure estimates, and prioritized remediation guidance

    1.8k GitHub stars~1.9k tokensUpdated 6 mo ago
    Legal & ComplianceAuto-check passed
  • Canghe Tianyancha

    freestylefly/canghe-skills

    Generates Tianyancha-style company and industry insight dashboards from researched enterprise data.

    461 GitHub stars~2.4k tokensUpdated 4 mo ago
    Legal & ComplianceAuto-check passed
  • EU AI Act System Inventory

    anthropics/claude-for-legal

    Official

    Maintains a register of AI systems under the EU AI Act, recording each system's role and risk tier separately, because both can differ from one system to the next.

    9.6k GitHub starsUsed in 3 repos~2.8k tokens
    Legal & ComplianceAuto-check passed

More from alirezarezvani/claude-skills

All 342 skills in this repo
  • Agile Product Owner

    alirezarezvani/claude-skills

    Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.

    28k GitHub starsUsed in 3 repos~3.2k tokens
    Auto-check passed
  • Product Strategist

    alirezarezvani/claude-skills

    OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.

    28k GitHub starsUsed in 2 repos~1.8k tokens
    Auto-check passed
  • App Store Optimization

    alirezarezvani/claude-skills

    App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store.

    28k GitHub starsUsed in 1 repo~4.2k tokens
    Auto-check passed
  • AWS Solution Architect

    alirezarezvani/claude-skills

    Design AWS architectures for startups using serverless patterns and IaC templates.

    28k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Campaign Analytics

    alirezarezvani/claude-skills

    Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.

    28k GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check passed
  • Code to PRD

    alirezarezvani/claude-skills

    Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.

    28k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed

Questions about Risk Management Specialist

What does Risk Management Specialist do?

Medical device risk management specialist implementing ISO 14971 throughout product lifecycle. Risk Management Specialist is an agent skill from alirezarezvani/claude-skills. Medical device risk management specialist implementing ISO 14971 throughout product lifecycle.

When should I use Risk Management Specialist?

Risk Management Specialist fits situations like: user mentions risk management; fault tree analysis; hazard identification; benefit-risk analysis.

How do I install Risk Management Specialist in Claude Code?

Run `npx skills add alirezarezvani/claude-skills --skill risk-management-specialist -a claude-code`. Or copy the skill folder (ra-qm-team/skills/risk-management-specialist in alirezarezvani/claude-skills) into .claude/skills/risk-management-specialist in your project. Claude Code loads it when a task matches its description.

How do I install Risk Management Specialist in Codex?

Run `npx skills add alirezarezvani/claude-skills --skill risk-management-specialist -a codex`. Or copy the skill folder (ra-qm-team/skills/risk-management-specialist in alirezarezvani/claude-skills) into .agents/skills/risk-management-specialist in your project. Codex loads it when a task matches its description.

Can I use Risk Management Specialist in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alirezarezvani/claude-skills --skill risk-management-specialist -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/risk-management-specialist, .gemini/skills/risk-management-specialist, .github/skills/risk-management-specialist and .opencode/skills/risk-management-specialist in your project.

What does Risk Management Specialist need to run?

Going by SKILL.md and its folder, Risk Management Specialist needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Risk Management Specialist access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Risk Management Specialist safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Risk Management Specialist use?

Risk Management Specialist is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Risk Management Specialist use?

About 4.1k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.7k tokens, read only when the agent opens those files.

What are the alternatives to Risk Management Specialist?

Skills that share tags, products or a category with Risk Management Specialist: Product Launch Legal Review (anthropics/claude-for-legal, 9.6k stars), Legal Risk Visualization (zh-xx/legal-assistant-skills, 174 stars), Contract Renewal Tracker (anthropics/claude-for-legal, 9.6k stars) and Deep Risk Analysis (zubair-trabzada/ai-legal-claude, 1.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Risk Management Specialist?

alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-skills, which has 27,938 GitHub stars. The repository holds 342 skills in this directory. The repository was last updated on August 30, 2026.

Source: alirezarezvani/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.