Skip to content
Back to skills

Enumerate Validator Assumptions

ASecurity

Enumerate assumptions embedded in a validator/test/sandbox, including data-generation, measurement, simulator, oracle, metric, initialization, and acceptance assumptions.

  • 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 enumerate-validator-assumptions --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Enumerate Validator Assumptions?

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

Security grade badge for Enumerate Validator Assumptions
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-enumerate-validator-assumptions/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-enumerate-validator-assumptions)

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: enumerate-validator-assumptions
description: "Enumerate assumptions embedded in a validator/test/sandbox, including data-generation, measurement, simulator, oracle, metric, initialization, and acceptance assumptions."
---

# enumerate-validator-assumptions
## Purpose
Enumerate assumptions embedded in a validator, benchmark, sandbox, or test.
## Input contract
```yaml
required: [validator_artifact, target_claim]
optional: [data_generation, measurement, simulator, oracle, metric, initialization, acceptance_rule]
constraints: [assumptions must be classified by source and role]
```
## Procedure
1. Inspect data generation, measurement, simulator, oracle, metric, initialization, and acceptance.
2. Record each assumption and its relation to the target.
3. Mark evidence, uncertainty, and potential circularity.

If validator assumptions and dependencies are explicit, consider `build-noncircularity-matrix` as the next tactic.

## Output contract
```yaml
produces: [validator_assumption_inventory, dependency_links, circularity_candidates]
delta_fields: [findings, evidence_updates, uncertainties, open_questions]
```
## Quality gates
- No assumption is omitted merely because it is conventional.
## Failure and counterexamples
An unstated assumption remains unknown, not independent.
## Provenance map
- resolved: circular-validation-audit

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…