Individual skill

decompose-ishikawa

0upvotes

Build an Ishikawa-style causal decomposition across relevant cause families.

skills/decompose-ishikawa/SKILL.md

Read pinned source

Source commit 41f752b8444ed9030dd9dc223c302ce874e51f83

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 510
Repository last updated: Oct 23, 2026
License: Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

academic-research Repository topic
deep-research Repository topic
literature-review Repository topic
mcp Repository topic
skill Repository topic
ai-scientist Repository topic
auto-research Repository topic
claude-code Repository topic
research-agent Repository topic
scientific-discovery Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 1,120 bytes

Read excerpt


# decompose-ishikawa
## Purpose
Build an Ishikawa causal decomposition across relevant cause families.
## Input contract
```yaml
required: [effect_statement, cause_families]
optional: [evidence_records, system_boundary]
constraints: [cause families must be named and causes linked to the effect]
```
## Procedure
1. Place the normalized effect at the head of the diagram.
2. Populate relevant method, data, theory, measurement, researcher, and environment branches.
3. Subdivide each branch into testable causes and mark evidence status.
## Output contract