Skip to content
Back to skills

Validate Causal Link

ASecurity

Audit a causal relation for clarity, existence, sufficiency, and logical completeness using CLR-style checks.

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

Security analysis

A100/100

Scanned September 24, 2026

npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill validate-causal-link --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Validate Causal Link?

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

Security grade badge for Validate Causal Link
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-validate-causal-link/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-validate-causal-link)

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: validate-causal-link
description: "Audit a causal relation for clarity, existence, sufficiency, and logical completeness using CLR-style checks."
---

# validate-causal-link

## Purpose

Audit a causal relation for clarity, existence, sufficiency, and logical completeness using CLR-style checks.

## Input contract

```yaml
required: [causal_relation, source_evidence, boundary_conditions]
optional: [causal_graph, alternative_explanations, clr_checklist]
constraints: [the relation has explicit cause and effect; distinguish clarity, existence, sufficiency, and logical completeness]
```

## Procedure

1. Parse the causal relation and define its scope and terms.
2. Check whether the stated cause exists and is connected to the effect.
3. Test sufficiency, omitted conditions, and alternative explanations.
4. Record each CLR result and return a validated, weakened, or unresolved link.

## Output contract

```yaml
produces: [causal_link_assessment, clr_results, missing_conditions, evidence_requests]
delta_fields: [findings, evidence_updates, hypothesis_updates, uncertainties]
```

## Quality gates

- All eight CLR categories are retained when the caller supplies the full checklist.
- Clarity, existence, sufficiency, and logical completeness are reported separately.
- A causal label is not accepted when evidence supports only association.

## Parameterization

The caller must provide the cause/effect schema, evidence and boundary conditions, CLR checklist, alternative-explanation fields, and verdict vocabulary.

## Failure and counterexamples

Reject links with undefined variables, missing scope, circular support, or causal language unsupported by the evidence.

## Provenance map

- resolved: deep-insight/clr-validation

## Preserved source criteria ledger

| source | physical line | kind | source criterion |
|---|---:|---|---|
| deep-insight/clr-validation | 13 | structural | Retain eight CLR validation categories for causal claims: clarity, existence, sufficiency, and logical completeness are explicit checks. |

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…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.