Recommend post test decision

Skill alexe-ev/product-plugins/experimentation/skills/recommend-post-test-decision

Recommend what to do after an experiment based on the result quality, effect size, and business context. Use this skill when the user has a completed experiment and needs a practical product decision such as roll out, rerun, iterate, segment-rollout, or reject.From its SKILL.md

Install

npx -y skills add alexe-ev/product-plugins --skill recommend-post-test-decision

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.5 KB, 683 tokens by cl100k_base, as published. Nobody here has run it

Recommend Post-Test Decision

Purpose

Turn experiment evidence into a practical product action.

Skill type

Conceptual decision skill informed by quality and analysis outputs

Required inputs

Experiment result summary
Quality / validity assessment

Optional inputs

Business context
Engineering cost
Strategic priority
Rollout risk
Segment-specific effects
Guardrail performance

Additional resources

Use examples/ when

you need to see what good input/output looks like
you need to match the expected output structure
you need to see how this skill behaves under rich, light, or poor context

Use REFERENCE.md when

this skill includes one and you need additional decision rules
you need deeper context-handling guidance
you need edge cases or caveats not included in the main instructions

Resource priority

Read this Skill.md first
Use examples/ for behavior patterns and output structure
Use REFERENCE.md for deeper rules, caveats, and edge cases

Upstream context

This skill works best when the following already exist:

experiment result summary
experiment quality assessment
effect size or practical result signal
guardrail review
at least some business context

If upstream context is missing

If quality assessment or guardrails are missing, avoid strong rollout recommendations. If business value, cost, or rollout risk is unclear, make only a conditional recommendation and list what must be confirmed.

Downstream handoff

A strong output from this skill should be usable as:

a rollout decision memo
a rerun recommendation
an iteration plan
a segment rollout recommendation

A good handoff includes:

recommended action
rationale
trade-offs
risks
next step
missing business inputs that weaken the recommendation

Context collection rules

Context-rich

Make a concrete action recommendation grounded in business value, risk, and implementation cost.

Context-light

Make a conditional recommendation and state what assumptions it depends on.

Context-poor

Do not over-recommend. Choose only a cautious action pattern and list what must be known before a stronger decision.

Minimum context to collect before a strong rollout recommendation

trustworthy analysis
quality verdict
practical size of the effect
business relevance of the effect
side effects or guardrails
rollout risk or implementation cost

Decision rules

Check whether the result is trustworthy enough for decision-making.
Consider effect size, not just significance.
Consider business value, implementation cost, and risk.
Review guardrails and negative side effects.
Recommend one of the following:
- Full rollout
- Partial rollout
- Segment rollout
- Iterate and retest
- Rerun
- Reject
Explain trade-offs clearly.
If the evidence is weak or invalid, say so directly.

Output

Provide:

Recommended action
Why this action is appropriate
Risks
What should happen next
Which missing business inputs limit recommendation strength