How do I install the Common Cause Analysis skill?

Run npx skillmds@latest add ashfordeou/common-cause-analysis in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Common Cause Analysis safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Common Cause Analysis?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Common Cause Analysis free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Common Cause Analysis?

ashfordeOU (@ashfordeou) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Common Cause Analysis by ashfordeou

Name: Common Cause Analysis
Author: ashfordeOU

Common Cause Analysis

Use when you must plan or review common cause analysis for a safety assessment per ARP4761A: score the zonal safety analysis items in a zone, check that the analysis set covers zonal, particular risk, and common mode analysis, and flag zones that need action. Produces the zone score and verdict, and the common cause analysis set completeness check. Trigger: common cause analysis, zonal safety analysis, particular risk analysis, common mode analysis, arp4761a, zsa.

ashfordeOU f7d8279 3 files · 5.0 KB Updated Sep 17, 2026

File contents

ARP4761A Common Cause Analysis (systems-engineering-safety/arp4761a/common-cause-analysis)

Use when the task is common cause analysis per ARP4761A: zonal safety scoring, analysis set completeness, and action flags.

Domain quick reference

Common cause analysis covers three studies: zonal safety analysis (ZSA), particular risk analysis (PRA), and common mode analysis (CMA).
ZSA examines physical interference and environment hazards inside a zone; each item passes or fails.
A zone with many failed items needs action before the safety assessment closes.
The analysis set must cover all three studies for the common cause analysis to be complete.

Workflow

Collect the zone hazard items with their pass-fail status.
Score the zone with zsa_zone_check.
Check the analysis set with cca_complete.
Flag reporting needs and revisit failed items.
Gate the safety assessment on zone verdicts and set completeness.

Pitfalls

Treating a zonal pass list as a completed common cause analysis.
Missing the common mode study when the set claims coverage.
Accepting a zone with multiple failed items without action.

Behavior contract (gate 3)

The zone scoring and set completeness logic is exercised by the gate 3 contract test: scripts/test_common_cause_analysis.py against scripts/common_cause_analysis_logic.py (stdlib unittest, offline). Run: python3 scripts/test_common_cause_analysis.py

Compliance

Standards referenced, not reproduced: ARP4761A text is proprietary (SAE); summary-only per standards-map.yaml and brief 06.
compliance: STANDARDS-REF, gated: false.

---name: common-cause-analysisdescription: Use when you must plan or review common cause analysis for a safety assessment per ARP4761A: score the zonal safety analysis items in a zone, check that the analysis set covers zonal, particular risk, and common mode analysis, and flag zones that need action. Produces the zone score and verdict, and the common cause analysis set completeness check. Trigger: common cause analysis, zonal safety analysis, particular risk analysis, common mode analysis, arp4761a, zsa.license: Apache-2.0---# ARP4761A Common Cause Analysis (systems-engineering-safety/arp4761a/common-cause-analysis)Use when the task is common cause analysis per ARP4761A: zonalsafety scoring, analysis set completeness, and action flags.## Domain quick reference- Common cause analysis covers three studies: zonal safety analysis (ZSA), particular risk analysis (PRA), and common mode analysis (CMA).- ZSA examines physical interference and environment hazards inside a zone; each item passes or fails.- A zone with many failed items needs action before the safety assessment closes.- The analysis set must cover all three studies for the common cause analysis to be complete.## Workflow1. Collect the zone hazard items with their pass-fail status.2. Score the zone with zsa_zone_check.3. Check the analysis set with cca_complete.4. Flag reporting needs and revisit failed items.5. Gate the safety assessment on zone verdicts and set completeness.## Pitfalls- Treating a zonal pass list as a completed common cause analysis.- Missing the common mode study when the set claims coverage.- Accepting a zone with multiple failed items without action.## Behavior contract (gate 3)The zone scoring and set completeness logic is exercised by thegate 3 contract test: scripts/test_common_cause_analysis.py againstscripts/common_cause_analysis_logic.py (stdlib unittest, offline).Run:python3 scripts/test_common_cause_analysis.py## Compliance- Standards referenced, not reproduced: ARP4761A text is proprietary (SAE); summary-only per standards-map.yaml and brief 06.- compliance: STANDARDS-REF, gated: false.

Frequently asked questions