Skip to content
Back to skills

Update Confidence From Evidence

ASecurity

Update confidence in a concept, relation, claim, or model component from new supporting/contradicting evidence with explicit rationale.

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

Security analysis

A100/100

Scanned September 24, 2026

npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill update-confidence-from-evidence --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Update Confidence From Evidence?

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

Security grade badge for Update Confidence From Evidence
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-update-confidence-from-evidence/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-update-confidence-from-evidence)

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: update-confidence-from-evidence
description: "Update confidence in a concept, relation, claim, or model component from new supporting/contradicting evidence with explicit rationale."
---

# update-confidence-from-evidence
## Purpose
Update confidence in a concept, relation, claim, or model component from new supporting or contradicting evidence.
## Input contract
```yaml
required: [target_record, prior_confidence, new_evidence, update_rule]
optional: [support_weights, contradiction_weights, confidence_floor]
constraints: [each update cites evidence direction, provenance, weight rule, and prior state]
```
## Procedure
1. Verify target identity and freeze the prior confidence and evidence ledger.
2. Classify each new item as supporting, contradicting, or non-informative under the declared rule.
3. Apply the update rule, record the weight and direction, and cap the result to the permitted confidence range.
4. Emit the updated confidence, evidence trace, and unresolved conflicts.
## Output contract
```yaml
produces: [updated_confidence, evidence_trace, conflict_register, update_rationale]
delta_fields: [findings, evidence_updates, hypothesis_updates, uncertainties, decisions]
```
## Quality gates
- Every confidence change is reproducible from the prior state, evidence classification, and update rule.
- Contradicting evidence cannot be omitted from the ledger merely because the net score rises.
## Failure and counterexamples
Do not treat repeated copies of one source as independent support. If evidence polarity is ambiguous, leave confidence unchanged and mark uncertainty.
## Provenance map
- resolved: confidence-update
- resolved: confidence-scoring

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…