manage-safety-analysis
Create, populate, and manage safety analysis spreadsheets (FMEA, FHA, HARA, custom) and fault trees (FTA) in Safety Analysis Manager
Install / Use
npx skills add matlab/simulink-agentic-toolkit --skill manage-safety-analysisInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Data & AnalyticsSupported Platforms
Tags
Our assessment of manage-safety-analysis
manage-safety-analysis scores 85/100 on our quality scale, 462nd of 608 Data & Analytics skills we index.
Its SKILL.md is 8.6 KB long, well organised into 20 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 1,148 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so manage-safety-analysis is actively maintained.
- Our last check on 2026-11-05 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
manage-safety-analysis compared with similar skills
All 4 of these similar skills score higher than manage-safety-analysis; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| manage-safety-analysis (this skill)by matlab | 85 | 1.1k | 2mo ago | SKILL.md |
| x402by browser-use | 100 | 121.0k | 4d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 56d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 56d ago | SKILL.md |
| prospectingby coreyhaines31 | 100 | 60.1k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install manage-safety-analysis?
- Run
npx skills add matlab/simulink-agentic-toolkit --skill manage-safety-analysis. The install tabs above show the steps for each supported agent. - Which AI agents does manage-safety-analysis work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is manage-safety-analysis safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is manage-safety-analysis still maintained?
- The repository was last updated about 2 months ago, so manage-safety-analysis is actively maintained.
Skill content
View source on GitHubname: manage-safety-analysis description: "Create, populate, and manage safety analysis spreadsheets (FMEA, FHA, HARA, custom) and fault trees (FTA) in Safety Analysis Manager. Use when the user asks to perform FMEA, hazard analysis, fault tree analysis, safety analysis, or work with Safety Analysis Manager documents. Requires Simulink Fault Analyzer." license: https://www.mathworks.com/content/dam/mathworks/license/pmrl/license.md metadata: version: "2.1" author: MathWorks
Safety Analysis Manager
Use evaluate_matlab_code with the safetyAnalysisMgr package to create, populate, query, and export safety analysis documents. Requires Simulink Fault Analyzer (R2023b+).
Version enforcement: APIs are annotated with the MATLAB release they were introduced. Do NOT use an API unless the user's MATLAB release is equal to or newer than the annotated version. If the user's release is unknown, assume R2023b and restrict to R2023b APIs only until confirmed. Check the reference files for per-API version annotations.
Safety Analysis Manager supports two document formats:
- Spreadsheets — tabular, row-based analysis (FMEA, FHA, HARA, HAZOP, custom)
- Trees — hierarchical, node-based analysis (Fault Tree Analysis, Attack Trees)
When to Use
Spreadsheet-based analysis
- Creating FMEA, FHA, HARA, HAZOP, or custom tabular documents
- Populating spreadsheets with failure modes, effects, and risk ratings
- Reviewing existing spreadsheets for consistency, completeness, and correctness
- Editing, searching, or flagging items in an existing spreadsheet
- Adding derived columns, callbacks, or custom logic to a spreadsheet
- Exporting spreadsheet results to Excel
- -> read
references/spreadsheet-api.mdandreferences/common-api.md
Tree-based analysis (R2026b+)
- Creating Fault Tree Analysis (FTA) documents
- Building fault trees with gates (AND/OR), basic events, and intermediate events
- Computing minimal cut sets and top-event probability
- Importance analysis and quantitative assessment
- -> read
references/tree-api.mdandreferences/common-api.md
Common operations (both formats)
- Opening, saving, closing
.mldatxdocuments - Adding callbacks (AnalyzeFcn, PreSaveFcn, custom)
- Flagging elements for review (error, warning, check)
- Detecting changes in linked artifacts
- Creating traceability links to model blocks or requirements
- Document attributes and metadata
- -> read
references/common-api.md
When NOT to Use
- Building or editing Simulink model structure -> use
building-simulink-models - Running simulations or tests -> use
simulating-simulink-modelsortesting-simulink-models - Fault injection and simulation-based fault analysis -> use
inject-faults - Requirements traceability only -> use
generate-requirement-drafts
Workflow
Creating a New Spreadsheet (FMEA/FHA/HARA)
- Understand the source. Either:
- From a model: Always use
model_overviewto inspect the model structure first. Usemodel_readfor deeper subsystem details. Identify subsystems, signal paths, feedback loops, sensors, and actuators. These become FMEA rows or hazard entries. - From requirements: Read the requirements (via Requirements Toolbox or user-provided text) and derive functional elements, failure modes, and hazards from the specified system behavior.
- From a model: Always use
- Choose a document structure. Design columns appropriate for the specific system and analysis type. Use a built-in template only if the user explicitly requests one.
- Create and populate. Build the spreadsheet programmatically using the API.
- Open the manager. Call
safetyAnalysisMgr.openManagerso the user can see results. - Save. Always save to
.mldatxwhen the user confirms the content.
Creating a Fault Tree (R2026b+)
- Identify the top event. The undesired system-level failure (e.g., "Loss of Aircraft Control").
- Decompose with gates. Use OR gates for single-point failures, AND gates for redundant systems.
- Add basic events. Leaf nodes representing individual component failures or human errors.
- Set probabilities. Assign failure probabilities to basic events from reliability data or engineering estimates.
- Analyze. Compute minimal cut sets and top-event probability.
- Save and review. Save to
.mldatxand open the manager for visual inspection.
Reviewing an Existing Document
- Open the document. Use
safetyAnalysisMgr.openDocumentto load the.mldatxfile. - Read and analyze content. For spreadsheets, iterate over rows; for trees, traverse nodes. Check for:
- Grammar and spelling issues in text
- Inconsistencies between data and the model or requirements
- Duplicate entries or near-duplicate failure modes
- Missing information (empty cells, events without probabilities)
- Calculations that don't match their inputs
- Flag issues. Use
addFlagto mark problematic elements for user review. - Report findings. Summarize issues found and suggest corrections.
FMEA Generation Conventions
- One row per failure mode, not per block — a single block can have multiple failure modes.
- Map model structure to functions: subsystems → functional groups; individual blocks → functions within those groups.
- Use requirement IDs in the Subsystem/Function column when working from requirements (no model).
- Detection methods must reference observable signals (model-based) or testable acceptance criteria (requirements-based).
- Flag entries for review once a model becomes available — model-based analysis may reveal additional failure modes not apparent from requirements alone.
Guardrails
Always
- Use
evaluate_matlab_codewithproject_pathset to the skill'sscripts/folder so MATLAB can find helper scripts (e.g.,fileType). Never useaddpath. - Verify
.mldatxfiles withfileType(filePath)before opening — the extension is shared with other tools. Only proceed if it returns"document"or"template"; if it throws, the file is not a Safety Analysis Manager document. - When a model is available, read it with
model_overviewormodel_readbefore writing failure modes — ground the analysis in actual structure. When working from requirements alone, derive failure modes from the requirements text instead. - Always call
safetyAnalysisMgr.openManageras the final step after creating, modifying, or reviewing a document — never skip this. The user cannot see results until the manager is open. - Remind the user to save (or save programmatically with confirmation) — new documents have no file until explicitly saved
Never
- Use
close(doc, Force=true)orsafetyAnalysisMgr.closeAllDocuments(Force=true)without asking — this discards unsaved work - Delete rows, columns, or nodes from an existing document without user confirmation
Ask First
- Before overwriting an existing
.mldatxfile - Before adding flags (
addFlag) that mark elements as errors or warnings - Before deleting rows, columns, or nodes from an existing document
Review Gates
After Creating/Populating a Spreadsheet
Review this safety analysis spreadsheet for:
- Rows with empty detection methods, severity, or occurrence ratings
- Failure modes that don't trace back to a model element or requirement
- Duplicate or near-duplicate entries (same failure mode, different wording)
- Column values that are inconsistent with each other (e.g., high severity + no detection + low RPN)
- Missing common failure modes for the system type (sensors without bias/drift, actuators without stuck)
After Creating a Fault Tree (R2026b+)
Review this fault tree for:
- Basic events without assigned failure models or with placeholder probabilities
- Cut sets containing a single basic event (indicates missing redundancy or analysis gap)
- Common-cause failures not modeled (shared power supply, shared sensor, common software)
- Gates with only one input (redundant gate — simplify)
- Circular or illogical decomposition (effect listed as its own cause)
After Reviewing an Existing Document
Verify the review findings for:
- False positives (flagged items that are actually correct in context)
- Missed issues in rows/nodes that were not inspected
- Consistency of flag severity (errors vs warnings vs checks)
Domain-Specific References
- Spreadsheet operations (rows, columns, cells, formulas, search) ->
references/spreadsheet-api.md - Tree operations (nodes, gates, cut sets, quantitative analysis) ->
references/tree-api.md - Common operations (save, callbacks, flags, links, change detection) ->
references/common-api.md
Copyright 2026 The MathWorks, Inc.
Related Skills
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
prospecting
60.1kWhen the user wants to find and qualify prospects for outbound, or asks who to target first, which signal to prioritize, or where to spot buyers with the problem: buying signals, enrichment, verification, account research.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
