Skip to content
Back to skills

Identify Load Bearing Factors

ASecurity

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

  • 499 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 24, 2026
researchnode

Security analysis

A100/100

Scanned September 24, 2026

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

Installs into .claude/skills of the current project.

Are you the author of Identify Load Bearing Factors?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Identify Load Bearing Factors
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-identify-load-bearing-factors/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-identify-load-bearing-factors)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
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

```yaml
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

```yaml
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.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…