Skip to content
Automation
Skill

/identify-load-bearing-factors

Identify factors/assumptions/uncertainties whose change most strongly controls the conclusion.

From plugin
de-anthropocentric-research-engine
507200 skills

Claude Code

$ npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill identify-load-bearing-factors --agent claude-code

SKILL.md

identify-load-bearing-factors.SKILL.md
name: identify-load-bearing-factors
description: "Identify factors/assumptions/uncertainties whose change most strongly controls the conclusion."

identify-load-bearing-factors

Purpose

Identify factors or assumptions whose change most strongly controls the conclusion.

Input contract

required: [conclusion, factor_or_assumption_set, perturbation_evidence]
optional: [necessity_sufficiency_results, uncertainty_contributions, critical_path]
constraints: [load-bearing status is tied to observed or reasoned conclusion change; preserve factor identity]

Procedure

1. Assemble ablation, necessity/sufficiency, fragility, and uncertainty evidence. 2. Compare conclusion changes attributable to each factor. 3. Classify factors as necessary, sufficient, jointly necessary, or decorative where supported. 4. Rank load-bearing factors and state the evidence gap for each uncertain ranking.

Output contract

produces: [load_bearing_register, necessity_sufficiency_map, fragility_ranking, evidence_gaps]
delta_fields: [findings, evidence_updates, decisions, uncertainties]

Quality gates

  • Every factor receives a role classification and evidence-backed importance assessment.
  • Fragility severity and alternative credibility are reported separately.
  • EVPI or uncertainty-contribution results retain the caller's units and are not treated as causal proof.

Parameterization

The caller must provide conclusion schema, factor/assumption list, perturbation results, classification ontology, importance metric, and uncertainty representation.

Failure and counterexamples

Reject a load-bearing claim based only on correlation, an untested factor, or a perturbation that changes multiple undeclared inputs.

Provenance map

  • resolved: stress-test/load-bearing-identification
  • resolved: deep-insight/fragility-flagging
  • resolved: deep-insight/critical-path-identification

Preserved source criteria ledger

No numeric source gate was present in the resolved source nodes; the role and evidence requirements above preserve their qualitative constraints.

Read more
@yogsoth-ai
Ships withde-anthropocentric-research-engine

A research skill graph for AI-native science. 271 markdown files. No runtime, no dependencies, no build step.

Stars on GitHub

Momentum

stars in total
507
Star history of yogsoth-ai/de-anthropocentric-research-engine on GitHub, a chart by star-history.com

More skills from other plugins.

agent-builder

agent-builder

Load immediately after an Agent intent, before the first agent_builder_* call. Governs how you create, configure, test, and…

n8n12d209k
@n8n-io@n8n-ioInstall Skill
browser-use

browser-use

Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers…

@browser-use@browser-useInstall Skill
agent-browser

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling…

@vercel-labs-2@vercel-labs-2Install Skill
add-anydoc

add-anydoc

Add local office-document-to-Markdown conversion to NanoClaw agent containers with the pinned Firecrawl AnyDoc CLI. Use when…

@nanocoai@nanocoaiInstall Skill

Questions about identify-load-bearing-factors.

Which coding agents can use identify-load-bearing-factors?
identify-load-bearing-factors installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.