Skip to content
Back to skills

Audit Explanatory Compression

ASecurity

Test whether an elegant/simple explanation earns its compression by forbidding alternatives, subsuming independent facts, or making risky predictions, rather than merely relabeling observations with a compact vocabulary.

  • 499 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 24, 2026
researchnodetesting

Security analysis

A100/100

Scanned September 24, 2026

npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill audit-explanatory-compression --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Audit Explanatory Compression?

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

Security grade badge for Audit Explanatory Compression
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-audit-explanatory-compression/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-audit-explanatory-compression)

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: audit-explanatory-compression
description: "Test whether an elegant/simple explanation earns its compression by forbidding alternatives, subsuming independent facts, or making risky predictions, rather than merely relabeling observations with a compact vocabulary."
---

# audit-explanatory-compression
## Purpose
Test whether an elegant explanation earns compression by excluding alternatives, subsuming independent facts, or making risky predictions.
## Input contract
```yaml
mode_contracts:
  earned-simplicity: &compression_audit_input
    required: [explanation, covered_facts, alternatives]
    optional: [predictions, evidence]
    constraints: [facts_and_alternatives_must_be_independently_enumerated]
  decorative-simplicity: *compression_audit_input
  risky-prediction: *compression_audit_input
```
## Execution protocol
Do not perform called SOP operations inline; each loaded SOP owns its contract and thresholds.

1. You MUST load skill `classify-simplicity-evidence` to classify the explanation's compression evidence.
2. You MUST load skill `test-risky-prediction` to derive and test risky predictions.
3. You MUST load skill `construct-critique` to attack the explanation. You MUST load skill `score-object` to score its remaining support.
Deviation: omit prediction testing only when no nontrivial prediction can be derived, and mark the explanation non-discriminating.
## Output contract
```yaml
mode_contracts:
  earned-simplicity: &compression_audit_output
    produces: [forbidden_set, risky_predictions, accommodation_audit, deletion_test_result, elegance_verdict, earning_prediction]
    delta_fields: [findings, evidence_updates, uncertainties, decisions]
  decorative-simplicity: *compression_audit_output
  risky-prediction: *compression_audit_output
```
## Thresholds and quality gates
- Earned simplicity requires at least one independent fact compressed and one risky alternative-forbidding prediction, each evidence-linked.
- Decorative simplicity is a failure when it merely renames observations.
## Failure and counterexamples
Do not reward brevity alone. Mark weak when independent facts, exclusions, or predictions are absent.
## Provenance map
- resolved: elegance-trap-probe
## Preserved source criteria ledger
| source | source line | kind | source criterion |
|---|---:|---|---|
| v4 architecture | node desc | textual | Distinguish earned simplicity from decorative relabeling. |
## Context checkpoint / Delta notes
Append covered facts, alternatives, risky predictions, critique, and score rationale.

## Mode branches
- `earned-simplicity`: seek independent compression and exclusions.
- `decorative-simplicity`: test for relabeling.
- `risky-prediction`: prioritize prospective 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…