Automated summary
Structured failure investigation methodology for mechanical components, covering fractography, metallography, failure-mode identification, and root cause analysis.
Strengths
- Walks through a four-phase process from evidence preservation to metallography, with concrete checklists at each step
- Provides lookup tables mapping fracture features (striations, dimples, cleavage facets) to failure mechanisms
- Combines SEM/EDS fractography, metallographic examination, and root cause frameworks (5-Why, Fishbone)
- Includes corrective action development and failure analysis report generation
Limitations
- Purely methodological: it does not perform actual SEM/EDS or metallographic analysis, only recommends it
- Does not cover quantitative fracture mechanics calculations or probabilistic fault tree analysis
- Assumes the user already has the failed samples and access to laboratory equipment
Use when a mechanical component has fractured or degraded and you need to structure the investigation, interpret fracture observations, or draft a failure analysis report.
Security analysis
SafeThe SKILL.md is purely reference documentation: methodology phases, fractography/metallography interpretation tables, root-cause frameworks, and input/output JSON schemas. There are no shell commands, downloads, obfuscated payloads, secret handling, or destructive instructions; the declared Bash/Write permissions are unused by the content and carry no inherent execution risk as written.
- •Declares Bash and Write in allowed-tools, but the body contains no executable commands, scripts, or file-system operations
- •References external laboratory equipment (SEM/EDS, metallography) that the agent cannot actually operate; no network or credential handling involved
Examples
My steel drive shaft failed after about 2 million cycles. There are beach marks radiating from the keyway fillet and almost no plastic deformation. Walk me through a failure analysis: root cause via 5-Why and corrective actions.I have a fractured aluminum bracket with a flat, chevron-marked surface. Help me plan the fractography and metallography work: what to section, which etchant, and what features to look for in SEM.Draft a failure analysis report for a stainless steel flange that cracked with branching cracks in a chloride environment. Structure it per the failure-analysis methodology: evidence, examination, fractography, metallography, conclusions, corrective actions.name: failure-analysis description: Systematic failure analysis methodology for mechanical component failures allowed-tools:
- Read
- Write
- Glob
- Grep
- Bash
metadata:
specialization: mechanical-engineering
domain: science
category: materials-testing
priority: medium
phase: 8
tools-libraries:
- SEM/EDS analysis tools
- Metallographic equipment
- NDT methods graph: domains: [domain:mechanical-engineering] skillAreas: [skill-area:physics-simulation, skill-area:mathematical-reasoning, skill-area:motion-planning] roles: [role:systems-integration-engineer, role:research-engineer]
Failure Analysis Skill
Purpose
The Failure Analysis skill provides systematic methodology for investigating mechanical component failures, enabling root cause identification through fractography, metallography, stress analysis, and structured problem-solving approaches.
Capabilities
- Fractography interpretation (SEM, optical)
- Metallographic examination guidance
- Root cause analysis frameworks (5-Why, Fishbone)
- Failure mode identification (fatigue, corrosion, overload)
- Stress analysis correlation to failure location
- Chemical analysis interpretation
- Corrective action development
- Failure analysis report generation
Usage Guidelines
Investigation Process
Phase 1: Evidence Preservation
-
Documentation
- Photograph failed components as-received
- Document orientation and assembly position
- Record operating conditions at failure
- Preserve all fragments
-
Chain of Custody
- Log all handling
- Secure storage
- Controlled access
- Document any cleaning or cutting
Phase 2: Visual Examination
-
Macroscopic Features | Feature | Indication | |---------|------------| | Beach marks | Fatigue | | Chevron marks | Brittle fracture | | Shear lips | Ductile overload | | Corrosion products | Environmental attack | | Wear patterns | Tribological failure |
-
Fracture Origin
- Identify initiation site
- Look for stress concentrations
- Check for material defects
- Document surface conditions
Phase 3: Fractography
-
Optical Microscopy
- Low magnification overview
- Document fracture features
- Identify regions of interest
-
Scanning Electron Microscopy (SEM) | Fracture Feature | Failure Mode | |------------------|--------------| | Striations | Fatigue crack growth | | Dimples | Ductile overload | | Cleavage facets | Brittle fracture | | Intergranular | Creep, SCC, hydrogen | | Quasi-cleavage | Mixed mode |
-
EDS Analysis
- Identify corrosion products
- Detect contamination
- Verify material composition
Phase 4: Metallography
-
Sample Preparation
- Section perpendicular to fracture
- Mount in appropriate media
- Grind and polish
- Select appropriate etchant
-
Examination
- Grain structure
- Heat treatment condition
- Inclusions and defects
- Microcracking
- Decarburization
Failure Mode Identification
Fatigue Failure
Characteristics:
- Beach marks (macroscopic)
- Striations (microscopic)
- Origin at stress concentration
- Minimal plastic deformation
- Flat fracture surface
Contributing Factors:
- Cyclic loading
- Stress concentration
- Residual stress
- Material defects
- Environmental effects
Overload Failure
Ductile:
- Significant plastic deformation
- Cup-and-cone fracture (tensile)
- Shear lips
- Dimpled fracture surface
Brittle:
- Little plastic deformation
- Flat fracture surface
- Chevron marks pointing to origin
- Cleavage or intergranular fracture
Corrosion Failures
| Type | Characteristics | Environment | |------|-----------------|-------------| | Uniform | General metal loss | Acids, bases | | Pitting | Localized attack | Chlorides | | SCC | Branching cracks | Specific ion + stress | | Corrosion fatigue | Accelerated fatigue | Cyclic + corrosive | | Hydrogen embrittlement | Intergranular fracture | Hydrogen source |
Wear Failures
| Type | Mechanism | Evidence | |------|-----------|----------| | Adhesive | Material transfer | Galling, scoring | | Abrasive | Hard particle cutting | Grooves, scratches | | Erosive | Fluid/particle impact | Surface damage pattern | | Fretting | Small amplitude motion | Oxide debris, pitting |
Root Cause Analysis
5-Why Method
Problem: Shaft failure
Why 1: Fatigue fracture
Why 2: High stress concentration at keyway
Why 3: Sharp corner radius
Why 4: Drawing did not specify radius
Why 5: Design review did not catch omission
Root Cause: Inadequate design review process
Fishbone Diagram Categories
- Material: Composition, defects, properties
- Machine: Equipment condition, maintenance
- Method: Process, procedure, design
- Man: Training, error, supervision
- Environment: Temperature, humidity, contamination
- Measurement: Calibration, accuracy
Process Integration
- ME-016: Failure Analysis Investigation
Input Schema
{
"failed_component": {
"part_number": "string",
"material": "string",
"service_history": "string",
"failure_date": "date"
},
"operating_conditions": {
"loads": "string",
"environment": "string",
"temperature": "number (C)",
"cycles_or_hours": "number"
},
"available_evidence": {
"fracture_surfaces": "boolean",
"mating_parts": "boolean",
"lubricant_samples": "boolean",
"maintenance_records": "boolean"
},
"analysis_scope": "preliminary|comprehensive"
}
Output Schema
{
"failure_mode": "fatigue|overload|corrosion|wear|other",
"root_cause": "string",
"contributing_factors": "array",
"evidence_summary": {
"visual": "string",
"fractography": "string",
"metallography": "string",
"chemical": "string"
},
"corrective_actions": [
{
"action": "string",
"category": "design|material|process|maintenance",
"priority": "high|medium|low"
}
],
"preventive_recommendations": "array",
"report_reference": "string"
}
Best Practices
- Preserve evidence before any destructive examination
- Document all observations photographically
- Follow systematic investigation process
- Consider multiple failure mechanisms
- Correlate fracture features with stress analysis
- Validate root cause with evidence
Integration Points
- Connects with FEA Structural for stress analysis
- Feeds into Material Selection for improved materials
- Supports Design Review for lessons learned
- Integrates with Quality for corrective actions
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/mechanical-failure-analysis-mrwakbbx/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/mechanical-failure-analysis-mrwakbbx' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/mechanical-failure-analysis-mrwakbbx/download' --output '.skill-downloads/mechanical-failure-analysis-mrwakbbx/SKILL.md.part' && mv '.skill-downloads/mechanical-failure-analysis-mrwakbbx/SKILL.md.part' '.skill-downloads/mechanical-failure-analysis-mrwakbbx/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/mechanical-failure-analysis-mrwakbbx/SKILL.md' && test -s '.skill-downloads/mechanical-failure-analysis-mrwakbbx/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/failure-analysis' && cp -R '.skill-downloads/mechanical-failure-analysis-mrwakbbx' '.claude/skills/failure-analysis'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/mechanical-failure-analysis-mrwakbbx'openskills read 'mechanical-failure-analysis-mrwakbbx'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/mechanical-failure-analysis-mrwakbbx/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
ClickHouse Performance Comparison
Testing
Evaluate ClickHouse performance test results, check PR performance changes, compare with history, and assess whether a result is actionable.
Analyze CI Performance Reports
Testing
Analyze CI performance comparison reports for a ClickHouse PR. Cross-references master history to distinguish real regressions from flaky tests.
Santa Method
Testing
Multi-agent adversarial verification with two independent reviewers. Output is checked twice and iteratively fixed until both pass before shipping.