Specify environment variables that materially affect interpretation or reproducibility: hardware, software, data, configuration, and versioning.
Scanned 9/24/2026
npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill specify-execution-environment --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Specify Execution Environment?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/yogsoth-ai-specify-execution-environment)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: specify-execution-environment
description: "Specify environment variables that materially affect interpretation or reproducibility: hardware, software, data, configuration, and versioning."
---
# specify-execution-environment
## Purpose
Specify environment variables that materially affect interpretation or reproducibility: hardware, software, data, configuration, and versioning.
## Input contract
```yaml
required: [hardware_context, software_context, data_context, configuration_context]
optional: [evidence, assumptions, prior_results]
constraints: [use named scientific objects; retain provenance and missingness; $\alpha$ = 0.05 and power = 0.8 where applicable]
```
## Procedure
1. Validate the typed inputs and state the decision this operation must support.
2. Apply the declared operation to the named object; record intermediate values that affect interpretation.
3. Check boundary conditions and counterexamples, then emit the result with uncertainty and source links.
## Output contract
```yaml
produces: [specify_execution_environment_result, evidence_trace, uncertainties]
delta_fields: [evidence_updates, uncertainties]
```
## Quality gates
- Inputs are named scientific objects with compatible schemas.
- Every material result has a derivation or source reference.
- Fixed statistical criteria remain exact where applicable: $\alpha$ 0.05 and power 0.8.
## Failure and counterexamples
Return a failed operation with the violated precondition when inputs are incomplete, assumptions are unsupported, or a counterexample defeats the result.
## Provenance map
- intermediate: experiment-execution/environment-specification
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!