CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

what-if-oracle

Supports structured what-if scenario analysis for research planning, experimental contingencies, and scientific project decisions. Explores favorable, reference, adverse, wild-card, contrarian, and second-order scenarios with explicit assumptions, evidence, and decision triggers. Use to stress-test a research plan under uncertainty; scenario narratives do not estimate causal effects or calibrated forecast probabilities.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A disciplined, well-structured instructional skill: four sequenced phases, a copy-paste scenario record, explicit trigger and stopping rules, and clean one-level-deep disclosure into a real references file. Its main costs are verbosity — probability rules and epistemic caveats Claude already knows are explained and repeated across sections — and a final validation step that is implied rather than explicit.

Suggestions

Consolidate the probability guidance that is currently split across Phase 3's Likelihood field, the 'Probability and confidence' section, and the Modes 'Scenario chain' entry into a single section, keeping one canonical statement.

Compress explanations of concepts Claude already knows — the P(A and B) = P(A) × P(B given A) chain rule and the mutually exclusive / collectively exhaustive partition example — into one-line rules or pointers, trusting Claude's competence.

Add an explicit validation step at the end of Phase 4 (e.g., re-check that scenarios are genuinely distinct, ledger statuses are applied consistently across branches, and each trigger has a threshold and owner) with an instruction to revisit assumptions when the check fails.

DimensionReasoningScore

Conciseness

The body is mostly efficient and skill-specific, but repeatedly explains things Claude already knows — 'P(A and B) = P(A) × P(B given A)', the 0–59/60–79/80–100 outcome-partition example, the IPCC confidence-vs-likelihood distinction — and restates the same 'not estimated / not a probability' caveat across Phase 3's Likelihood field, the 'Probability and confidence' section, and Modes. That is more than anchor 4's 'minor instances of over-explanation that could be trimmed', but far from anchor 2's pervasive padding.

3 / 5

Actionability

Concrete, template-driven guidance throughout: 'Write one operational question containing:' five enumerated elements with an inline example question, an 11-field copy-paste scenario record in Phase 3, and a six-lens table with a 'What to examine' column. It falls short of anchor 5 only because the complete worked example is deferred to references/scenario-templates.md and some record fields ('Evidence confidence: [reasoned assessment...]') are loosely specified; it is well above anchor 3's pseudocode-level vagueness.

4 / 5

Workflow Clarity

Four clearly sequenced phases (Frame → Explore → Analyze → Compare) each with defined outputs, and the Phase 3 record functions as a per-scenario checklist with built-in checkpoint fields ('Discriminating observation', 'Trigger and response', 'Residual risk'). Not anchor 5 because there is no explicit validation/feedback step on the final deliverable — re-checking that scenarios are distinct or that ledger statuses are applied consistently across branches is implied rather than stated as a step with a revisit-on-failure loop.

4 / 5

Progressive Disclosure

A well-sectioned overview body with exactly one clearly signaled, one-level-deep reference — 'For research-specific prompts and a worked example, see references/scenario-templates.md' — which exists as a real file containing the per-question templates and worked example, with no nested skill references inside it. The process overview and the detailed templates are appropriately split, matching anchor 5's 'clear overview with well-signaled one-level-deep references'.

5 / 5

Total

16

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person voice, concrete enumerated capabilities, an explicit 'Use to' trigger clause, tight domain scoping to research planning, and a well-drawn boundary against causal-effect estimation and forecasting. The only weaknesses are minor — it omits the deliverable artifacts and lacks a few natural synonyms such as 'scenario planning' or 'contingency planning'.

DimensionReasoningScore

Specificity

Names several concrete actions — 'Supports structured what-if scenario analysis', 'Explores favorable, reference, adverse, wild-card, contrarian, and second-order scenarios with explicit assumptions, evidence, and decision triggers', 'stress-test a research plan under uncertainty'. It stops short of anchor 5 because it never names the skill's output artifacts (scenario comparison, evidence ledger, contingency plan), leaving a minor coverage gap; it is well above anchor 3's '1-2 concrete actions'.

4 / 5

Completeness

Explicitly answers both parts: what ('Supports structured what-if scenario analysis... Explores... scenarios with explicit assumptions, evidence, and decision triggers') and when ('Use to stress-test a research plan under uncertainty'), with a concrete trigger phrase and an additional boundary statement ('scenario narratives do not estimate causal effects or calibrated forecast probabilities'). This matches the anchor 5 example's structure of what + explicit 'Use when/Use to' trigger.

5 / 5

Trigger Term Quality

Good natural-term coverage: 'what-if scenario analysis', 'research planning', 'experimental contingencies', 'scientific project decisions', 'stress-test', 'uncertainty'. Missing common variations users might say such as 'scenario planning', 'contingency planning', or 'risk assessment', so it does not reach anchor 5's comprehensive synonym coverage, but it clearly exceeds anchor 3's 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

Clear niche — research/scientific scenario planning — with distinct triggers ('stress-test a research plan', 'what-if scenario analysis') and an explicit scope boundary that separates it from forecasting, causal-inference, or statistics skills. Minimal conflict risk, matching anchor 5's 'clear niche with distinct triggers'.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

K-Dense-AI/scientific-agent-skills

Path

skills/what-if-oracle/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.