Failure Analysis Report for Openclaw

Structures engineering failure investigations into defensible, court-ready report drafts tailored for licensed professional engineer review.

archlab-space
v0.1.0
Jun 2, 2026
0
609
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install failure-analysis-report

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install failure-analysis-report using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Failure Analysis Report?

The Failure Analysis Report skill is a specialized tool designed for forensic engineers, expert witnesses, and engineering consultants. It systematically guides users through documenting structural, mechanical, electrical, product, or fire failures. By adhering strictly to historical code compliance and data integrity rules, it ensures all gathered evidence transforms into a reliable foundation for litigation, insurance claims, or safety investigations.

This workflow focuses on generating defensible Openclaw Skills documentation. It explicitly flags missing historical standards, data gaps, and chain-of-custody issues instead of approximating or fabricating values. The final output provides a rigorously organized template containing hypothesis screenings and structured expert opinion frameworks, serving as an optimal preliminary draft for a licensed Professional Engineer (PE) to review, revise, and sign off on.

Failure Analysis Report Use Cases

  • Drafting Forensic Litigation Reports: Creating a defensible, structured investigation skeleton for legal disputes involving property damage or bodily injury.
  • Processing Insurance Claims: Documenting industrial, residential, or commercial failures systematically to support root cause verification.
  • Investigating Fire Origin and Cause: Applying the scientific method outlined in NFPA 921 to screen fire propagation hypotheses.
  • Engineering Failure Hypotheses Screening: Evaluating mechanical or structural failures across multiple operational vectors to eliminate competing failure modes.

How Failure Analysis Report Works

  1. Scope and Identification: Gathers preliminary administrative metadata, including client retention types, case numbers, and failure classifications (Structural, Mechanical, Fire, Electrical, or Product).
  2. Scene Documentation: Collects data regarding site access limits, documentation methods (e.g., 3D laser scans, drone photography), and evidence preservation protocols.
  3. Evidence Inventorying: populates a structured tracking schema that registers item conditions, locations found, and current disposition status.
  4. Historical Standards Alignment: Evaluates and maps the exact regulatory standards and codes that were active at the original time of construction or manufacture rather than current iterations.
  5. Hypothesis Screening & Routing: Cross-references supporting and contradicting evidence against 2–5 core failure hypotheses using domain-specific rules.
  6. Root Cause Determination: Formalizes the primary root cause based on established evidence, noting the exclusions and engineering certainty degrees.
  7. Expert Opinion Generation: Drafts a standard, non-binding professional opinion template requiring PE authorization.
  8. Limitations and Compilation: Inserts critical procedural constraints and compiles the full asset into a unified, formatted draft ready for professional engineer stamps.

Failure Analysis Report Setup

To initiate the failure analysis report drafting process within your agent environment, call the skill directly through your compatible execution framework:

openclaw skills run failure-analysis-report

Ensure that you have gathered all primary site notes, historical construction metadata, and laboratory evidence logs prior to launching the workflow to minimize open data flags.

Failure Analysis Report Data Schema & Taxonomy

The skill manages information following a rigid matrix to protect data integrity and clear lineage. The resulting draft populates the following major structural schema:

Section Element Type Field Rules & Taxonomies
Administrative Data Meta Fields Case Number, Report Date, Client Type, Filtered Failures
Evidence Inventory Markdown Table Item #, Description, Location, Condition, Disposition Status
Standards Matrix Markdown Table Code Title, Historical Edition Year, Source Verification Type
Hypothesis Grid Markdown Table Core Hypothesis, Supporting Evidence, Contradicting Evidence, Status
Expert Opinion Blockquote Regulated Boilerplate Draft [PE TO REVIEW, REVISE, AND ADOPT]

All missing variables or unresolved parameters automatically default to standard taxonomy flags such as [DATA NOT AVAILABLE — PE TO PROVIDE] or [STANDARDS DATE UNKNOWN — PE TO CONFIRM] to maintain structural honesty.

Failure Analysis Report Advanced Features

  • Domain-Specific Failure Routing: Automatically adjusts its prompt framework to focus on unique criteria depending on selection (e.g., NFPA 921 scientific logic for fire vs. fatigue/overload vectors for mechanical tools).
  • Automated Chain-of-Custody Gap Flagging: Scans the preservation protocols and issues immediate warnings if evidence transfer points are unverified.
  • Defensible Work-Product Protections: Automatically appends specialized legal disclosure recommendations for engineering counsel review to isolate reports from premature discovery.
  • Open-Items Appendix Automation: Dynamically extracts every placeholder tag throughout the workflow into a prioritized summary checklist for the final engineer review.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*