okhp3-outcome-modeling-core

Designs outcome models that compress noisy event histories into calibrated forecasts and constrained decisions.

1|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/OKHP3/refoldec --skill okhp3-outcome-modeling-core-okhp3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: okhp3-outcome-modeling-core
Source: https://github.com/OKHP3/refoldec/tree/main/.agents/skills/okhp3-outcome-modeling-core
Command: npx skills add https://github.com/OKHP3/refoldec --skill okhp3-outcome-modeling-core-okhp3

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Many systems produce long histories of noisy events, and turning them into defensible forecasts or budget decisions is error-prone: features leak future information, accuracy is confused with calibration, and prediction is conflated with optimization. This Skill provides a structured method for building outcome models that separate the world model from the decision objective. ## Core Features & Use Cases - Event-to-State Modeling: Aggregates raw event histories into time-indexed entity state vectors with provenance, missingness, and as-of leakage controls. - Feature Compression & Validation: Tests nested feature tiers (10, 30, 60, 120, 200) against baselines using time-aware out-of-sample metrics like Brier score and log loss. - Decision Layer: Produces explicit objective functions with costs, constraints, and expected-value comparisons, plus causal and intervention checks. - Use Case: A sales leader wants to predict customer renewal from interaction events and allocate a limited retention budget. The Skill produces a time-aware model specification, calibrated forecast, and bias-aware allocation plan instead of invented numbers. ## Quick Start Ask the agent to design a time-aware outcome model for your target, horizon, and event history, separating the probability forecast from the decision objective and constraints.

Frequently Asked Questions about okhp3-outcome-modeling-core

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a forecasting model from noisy event data?▼

Aggregate raw events into a time-indexed entity state using only information available at the as-of time, then estimate probabilities with a transparent model such as logistic regression. Validate with time-based splits and calibration metrics like Brier score and log loss rather than random row splits.

How to reduce hundreds of correlated features without losing signal?▼

Build a feature inventory recording source, grain, cadence, missingness, and leakage risk, then test nested tiers such as 10, 30, 60, 120, and 200 features. Compare each tier against a simple baseline using time-aware out-of-sample metrics and stop when incremental value is negligible.

What is the difference between a forecast and a decision in outcome modeling?▼

A forecast estimates the probability of an outcome, while a decision applies an explicit objective function with costs, capacity limits, and risk constraints. This Skill keeps the two separate so the same evidence can support forecasting, ranking, budgeting, or market comparison.

Does this Skill require Python or specific libraries?▼

No external dependencies are required. The method works as portable prose, and the optional helper script uses only the Python 3.9+ standard library to compute weighted means, logistic probabilities, Brier scores, and expected values from local JSON.

When should I not use this outcome modeling approach?▼

Do not use it to invent data, current facts, or probabilities, to claim causation from correlation without a causal design, or to execute trades or bets. When domain rules matter, load a narrow domain adapter instead of relying on the generic core.

Why does my model rank well but produce bad decisions?▼

A model can rank well yet be poorly calibrated, or forecast accurately while producing a bad allocation under real costs and constraints. Check calibration, subgroup performance, drift, and the decision objective separately rather than relying on accuracy alone.