Skip to content
Back to skills

Evaluate Optionality

ASecurity

Evaluate the value of staging, deferral, reversible commitment, and information-gathering options under uncertainty; return decision-relevant option value and trigger conditions.

  • 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 evaluate-optionality --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Evaluate Optionality?

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

Security grade badge for Evaluate Optionality
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-evaluate-optionality/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-evaluate-optionality)

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: evaluate-optionality
description: "Evaluate the value of staging, deferral, reversible commitment, and information-gathering options under uncertainty; return decision-relevant option value and trigger conditions."
---

# evaluate-optionality
## Purpose
Evaluate staging, deferral, reversible commitment, and information-gathering options under uncertainty.
## Input contract
```yaml
required: [decision_options, uncertainty_register, time_horizon, consequence_model]
optional: [irreversibility_costs, information_actions, trigger_conditions]
constraints: [each option states timing, reversibility, information gained, and consequence range]
```
## Procedure
1. Represent immediate, deferred, staged, and information-gathering actions on a common timeline.
2. Estimate each action's reversible value, delay cost, information gain, and downside exposure.
3. Identify trigger conditions that would justify advancing, pausing, or abandoning each staged option.
4. Emit an option-value comparison and the conditions under which deferral is preferable to commitment.
## Output contract
```yaml
produces: [option_value_table, timing_policy, trigger_conditions, uncertainty_notes]
delta_fields: [findings, evidence_updates, uncertainties, decisions, recommended_jumps]
```
## Quality gates
- Each option includes at least one consequence of acting now and one consequence of waiting.
- Information value is not counted unless it can change a downstream decision.
## Failure and counterexamples
Do not call delay optionality when waiting only postpones an irreversible loss. If trigger conditions are unobservable, mark the option unresolved.
## Provenance map
- resolved: temporal-sequencing

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…