ceae-skill

Analyze hardware parameter failures into Mermaid causal trees with 5-Why recursion.

33|7|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/patsnap/skills --skill ceae-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ceae-skill
Source: https://github.com/patsnap/skills/tree/main/open-platform/ceae-skill
Command: npx skills add https://github.com/patsnap/skills --skill ceae-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires matplotlib, networkx, and includes scripts (resource) components.

What problem does it solve?

This Skill helps engineers turn ambiguous hardware performance failures into a structured root-cause investigation instead of guessing.

Core Features & Use Cases

  • Converts vague goals such as temperature rise, deformation, noise, or parameter overruns into measurable engineering targets.
  • Builds a first-principles causal tree across mechanical, materials, electrical, and manufacturing viewpoints.
  • Supports TRIZ-style collaboration, key-defect selection, and Mermaid-based cause-and-effect visualization for review and archiving.

Quick Start

Ask for a TRIZ root-cause analysis of your hardware parameter problem and provide the target value, measured value, test conditions, and the specific symptom.

Frequently Asked Questions about ceae-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform root cause analysis for hardware parameter failures like temperature rise or deformation?

Root cause analysis for hardware parameter failures converts ambiguous symptoms like temperature rise or deformation into measurable targets using first-principles decomposition and 5-Why recursion. It builds a causal tree across mechanical, materials, and electrical viewpoints to identify the core defect.

Can I visualize a TRIZ causal tree using Mermaid for engineering troubleshooting?

You can visualize a TRIZ causal tree using Mermaid to generate cause-and-effect diagrams for engineering troubleshooting. The process creates a visual causal tree from the analysis and exports it as a PNG file for team review and archiving.

What is the best way to structure ambiguous hardware optimization goals for manufacturing troubleshooting?

The best way to structure ambiguous hardware optimization goals is applying TRIZ collaboration and first-principles decomposition to translate them into specific engineering targets. This isolates the key defect driving the manufacturing or material failure.

Does this root cause analysis approach work for electrical and mechanical troubleshooting?

This root cause analysis approach works comprehensively for electrical, mechanical, materials, and manufacturing troubleshooting. It evaluates parameter overruns across these domains by mapping interactions within a unified first-principles causal tree.

How do I start a TRIZ root-cause analysis for a hardware parameter problem?

To start a TRIZ root-cause analysis, provide the target value, measured value, test conditions, and the specific hardware symptom. The analysis then applies 5-Why recursion and TRIZ collaboration to isolate the underlying cause.

Why use first-principles decomposition instead of guessing for hardware failure analysis?

First-principles decomposition prevents guessing during hardware failure analysis by systematically breaking down ambiguous symptoms into measurable engineering targets. It structurally maps the failure chain across domains to pinpoint the exact root cause.