Skip to content
Back to skills

Assess Evidence Saturation

ASecurity

Estimate marginal information gain of new evidence batches relative to the current corpus and classify continuing/near-saturation/saturated.

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

Security analysis

A100/100

Scanned October 3, 2026

npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill assess-evidence-saturation --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Assess Evidence Saturation?

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

Security grade badge for Assess Evidence Saturation
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-assess-evidence-saturation/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-assess-evidence-saturation)

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: assess-evidence-saturation
description: "Estimate marginal information gain of new evidence batches relative to the current corpus and classify continuing/near-saturation/saturated."
---

# assess-evidence-saturation

## Purpose

Compare the marginal information gain of a new evidence batch with the comparable prior batch and classify acquisition as continuing, near-saturation, or saturated.

## Input contract

```yaml
required: [current_corpus, prior_comparable_batch, novelty_schema]
optional: [topic_schema, quality_weights, stopping_policy]
constraints: [batches must share a declared universe and comparable novelty calculation]
```

## Procedure

1. Declare the eligible evidence universe, novelty dimensions, and current/prior batch boundaries.
2. Compute new topic, independent-source, condition, or mechanism coverage for each comparable batch.
3. Compare marginal information gain and record the evidence supporting the comparison.
4. Classify continuing, near-saturation, or saturated and state the stopping rationale.

## Output contract

```yaml
produces: [declared_universe, batch_comparison, marginal_gain, saturation_state, stopping_rationale]
delta_fields: [findings, evidence_updates, uncertainties, decisions, open_questions]
```

## Quality gates

- Numerator, denominator, batch increment, source references, direction, and rationale are reproducible.
- The comparison uses the same novelty schema for both batches.
- Saturation is not declared from corpus size alone.
- Saturation describes acquisition only: it states that further retrieval adds little, never that the question the evidence addresses is answered.

## Failure and counterexamples

Do not compare incomparable batches, count duplicate sources as new information, or treat a low-quality batch as evidence of saturation.

## Provenance map

- `resolved: knowledge-acquisition-saturation-detection`

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.