Skip to content
Back to skills

Evaluate Scenario Impact

ASecurity

Evaluate a fixed candidate, research path, or portfolio under one explicit scenario using stable criteria and return impact, tradeoffs, and failure triggers.

  • 499 stars
  • 0 votes
  • 0 copies
  • 2 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-scenario-impact --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Evaluate Scenario Impact?

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

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

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-scenario-impact
description: "Evaluate a fixed candidate, research path, or portfolio under one explicit scenario using stable criteria and return impact, tradeoffs, and failure triggers."
---

# evaluate-scenario-impact
## Purpose
Evaluate one fixed candidate, path, or portfolio under one explicit scenario.
## Input contract
```yaml
required: [candidate, scenario, evaluation_criteria]
optional: [baseline, metric_definitions, vulnerability_rules]
constraints: [criteria, units, and scenario assumptions remain fixed during evaluation]
```
## Procedure
1. Instantiate the candidate under scenario assumptions.
2. Compute or qualitatively assess each declared criterion.
3. Identify tradeoffs, vulnerabilities, and failure triggers.
4. Return impact evidence and unresolved uncertainties.

If the impact estimate depends on uncertain drivers or parameter choices, consider `assess-sensitivity` as the next tactic.

## Output contract
```yaml
produces: [impact_assessment, metric_results, tradeoffs, vulnerabilities, failure_triggers]
delta_fields: [findings, uncertainties, decisions]
```
## Quality gates
- All declared criteria are addressed with units or explicit qualitative scales.
- Vulnerable or failing members are named, not hidden in aggregate scores.
- Scenario assumptions and baseline are cited for every comparison.
## Parameterization
Caller supplies candidate schema, scenario schema, criteria, metric formulas, baseline, and vulnerability thresholds.
## Failure and counterexamples
Reject evaluations that change scenario assumptions midstream or report aggregate impact without member-level checks.
## Provenance map
- concept: convergence/portfolio-evaluation-per-scenario
- concept: experiment-execution/scenario-impact-assessment
- intermediate: Pass3/evaluate-scenario
- intermediate: Pass3/assess-scenario-impact

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…