rca-systems-theoretic
From the author
Systems-theoretic approaches to root cause analysis for complex socio-technical systems where linear causal chains fail. Covers Nancy Leveson's STAMP (Systems-Theoretic Accident Model and Process), STPA (System-Theoretic Process Analysis) for hazard analysis, CAST (Causal Analysis based on STAMP) for post-incident investigation, Rasmussen's risk-management framework and dynamic safety model, Hollnagel's FRAM (Functional Resonance Analysis Method), and AcciMap. Use when investigating incidents in healthcare, aviation, nuclear, autonomous systems, distributed microservices, or any system where multiple actors and control loops interact — especially when classical RCA produces a "list of human errors" that leaves the underlying system design unchanged.
Install
npx skills add Tibsfox/gsd-skill-creator --skill rca-systems-theoretic -a claude-code
Installs to .claude/skills/rca-systems-theoretic/ · Each command fetches the skill straight from GitHub with the open skills CLI.
No download: this skill’s licence (Custom or unclear) does not let us redistribute its files. The install commands fetch them from GitHub instead.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 72
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- rca-distributed-systemsTibsfox/gsd-skill-creatorRoot cause analysis techniques for modern distributed systems, microservices, and cloud infrastructure. Covers trace-based causality (OpenTelemetry, Jaeger, Tempo), service dependency graph analysis, DynaCausal-style dynamic causality-aware RCA, anomaly localization with metrics/logs/traces correlation, the Microsoft AgentRx framework for AI agent failures, chaos-engineering-as-RCA, and the 2025 industry shift toward causal-graph-based AIOps. Use when investigating a production incident in a microservice mesh, a Kubernetes cluster, a distributed database, or any system where the fault could originate in any of dozens of services and the causal chain runs through network hops, retries, timeouts, queues, and asynchronous message flows.DevOps★ 71
- rca-classical-methodsTibsfox/gsd-skill-creatorClassical root cause analysis techniques for quality improvement and incident investigation. Covers 5 Whys (with Card's 2017 critique and boundary conditions), Ishikawa/fishbone diagrams, Fault Tree Analysis (FTA), Failure Modes and Effects Analysis (FMEA), Cause Mapping, and Doggett's method-selection framework. Use when investigating a failure, running a post-incident analysis, building a fishbone, calculating fault tree cut sets, running an FMEA pass, or deciding which classical technique fits the problem. Not suitable alone for complex socio-technical failures — escalate to rca-systems-theoretic or rca-causal-inference when the incident has multiple interacting causal chains.Finance★ 71
- rca-human-factorsTibsfox/gsd-skill-creatorHuman-factors root cause analysis for incidents involving operators, crews, clinicians, or any human actors. Covers James Reason's Swiss Cheese Model and active/latent failure taxonomy, HFACS (Human Factors Analysis and Classification System), Just Culture algorithm (Marx/GAIN), Crew Resource Management (CRM) findings, and high-reliability organization (HRO) principles. Use when investigating incidents in aviation, healthcare, nuclear operations, emergency response, or any context where "operator error" is a tempting but shallow explanation and the real question is what organizational and design factors made the error foreseeable.Design★ 71
- rca-causal-inferenceTibsfox/gsd-skill-creatorMathematical foundations of root cause analysis using Judea Pearl's Structural Causal Models (SCMs), do-calculus, counterfactual reasoning, Bayesian networks for fault diagnosis, graph-theoretic centrality for fault localization, information-theoretic methods (transfer entropy, mutual information), and Granger causality. Use when the incident involves quantifiable observational data, when you need to distinguish correlation from causation, when you want to compute "what would have happened if we had done X instead," or when building automated fault-detection systems that reason about cause rather than pattern-match on symptoms.Other★ 71
- postmortemnicepkg/ai-workflowUse when analyzing failures, outages, incidents, or negative outcomes, conducting blameless postmortems, documenting root causes with 5 Whys or fishbone diagrams, identifying corrective actions with owners and timelines, learning from near-misses, establishing prevention strategies, or when user mentions postmortem, incident review, failure analysis, RCA, lessons learned, or after-action review.Engineering★ 288
- blameless-postmortemTibsfox/gsd-skill-creatorGoogle SRE-style blameless postmortem authoring. Structure, timeline construction, contributing-factor extraction, action-item discipline, and the cultural practices that make postmortems produce learning rather than theater. Use when writing a postmortem after an incident, reviewing a draft postmortem, running a postmortem review meeting, building a postmortem template, or teaching a team how to write postmortems that actually improve the system. Complements rca-human-factors (for the "why people did what they did" analysis) and the rca-classical-methods / rca-systems-theoretic / rca-causal-inference / rca-distributed-systems skills (which supply the investigation techniques that populate the postmortem's analysis section).Finance★ 71
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in