agentleFS
Sign inStart free
PthahnixPthahnix/De-Anthropocentric-Research-Engine/skills/build-failure-chain/SKILL.md

build-failure-chain

Skill504 starsChanged 49 days agoApache-2.0View on GitHub

Build multi-level cause -> failure mode -> effect chains and identify cascades/shared roots.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Place causes, failure modes, and effects in typed levels.

    line 16
  2. Distinctive:

    Every effect has a traceable upstream path or is marked unexplained.

    line 25
  3. Distinctive:

    Do not collapse correlation into a causal chain without an evidence or mechanism note.

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

build-failure-chain

Purpose

Build cause -> failure mode -> effect chains and identify cascades and shared roots.

Input contract

required: [functions_or_process, failure_modes, observed_effects]
optional: [causal_evidence, dependency_graph]
constraints: [each edge needs a mechanism or evidence note]

Procedure

  1. Place causes, failure modes, and effects in typed levels.
  2. Connect edges and record mechanism/evidence.
  3. Mark cascades, shared roots, and unresolved links.

Output contract

produces: [failure_chain, cascade_map, shared_root_report]
delta_fields: [findings, evidence_updates, uncertainties, decisions]

Quality gates

  • Every effect has a traceable upstream path or is marked unexplained.
  • Cycles and unsupported edges are flagged.

Failure and counterexamples

Do not collapse correlation into a causal chain without an evidence or mechanism note.

Provenance map

  • resolved: failure-chain-construction
  • resolved: failure-clustering

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free