AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Experiment Orchestrator

skill-luckyonetwothree-vibe-skill-experiment-orchestrator · by LuckyOneTwoThree

Use when designing or executing A/B test experiments. Experiment validation orchestrator dispatching experiment-design/execution. Keywords: A/B testing, experiment design, statistical significance, experiment execution, effect validation, AB test, controlled experiment.

No reviews yet
0 installs
20 views
0.0% view→install

Install

$ agentstack add skill-luckyonetwothree-vibe-skill-experiment-orchestrator

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-luckyonetwothree-vibe-skill-experiment-orchestrator)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Experiment Orchestrator? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Experiment Design Orchestrator

Core Principles

Experiments are the fastest way to learn

Every experiment is a controlled exploration. The goal is not to prove hypotheses correct, but to gain reliable learning as quickly as possible. The value of experiments lies in learning speed, not experiment count.

Orchestration Philosophy

  1. Design -> Execution: both stages are essential: Execution without design is blind; the execution stage includes result analysis and report generation
  2. Human review is a necessary gate for experiments: Both experiment plans and experiment reports must be reviewed by humans; the execution process can be automated
  3. Guardrail metrics have veto power: No matter how positive the primary metric, guardrail metric breaches trigger immediate pause

Orchestration Protocol

The orchestration protocol follows the unified standard in [orchestrator-protocol.md](../../../codex-templates/orchestrator-protocol.md).

Pipeline

pipeline: experiment-orchestrator
version: 8.0
post_pipeline:
  - action: stage-summary
    output: output/phase-reports/pm-metrics-ops/experiment-orchestrator.md

stages:
  - id: phase-1
    name: "Experiment Design"
    depends_on: []
    skills: [experiment-design]
    gate:
      condition: "Experiment design reviewed and confirmed by human"
      fail_action: "Block experiment launch, modify and re-review"

  - id: phase-2
    name: "Experiment Execution"
    depends_on: [phase-1]
    skills: [experiment-execution]
    gate:
      condition: "Sample size sufficient and statistical testing complete, experiment report reviewed and confirmed by human"
      fail_action: "Extend experiment period or expand traffic"

Stage Execution Plan

Invoke experiment-design
Invoke: ${experiment-design}
Input:
  hypothesis: provided by user (hypothesis statement)
  available_traffic: provided by user (available traffic)
  metrics_system: metrics-system -> metrics.json (optional)
  historical_data: analysis-funnel/analysis-retention (optional)
Output: output/pm-metrics-ops/experiment-design/
Validation: Hypothesis structured (If-Then-Because-For); primary metric directly corresponds to hypothesis; guardrail metrics cover retention, revenue, and technical dimensions; sample size calculation parameters well-founded
Mode: AI->Human
Invoke experiment-execution
Invoke: ${experiment-execution}
Input:
  experiment_design: output/pm-metrics-ops/experiment-design/experiment_design.json
  experiment_data: provided by user
  termination_conditions: output/pm-metrics-ops/experiment-design/experiment_design.json
  product_background: provided by user (optional)
Output: output/pm-metrics-ops/experiment-execution/
Validation: Experiment group traffic allocation correct; guardrail metrics not triggered; experiment data collection complete; statistical significance calculated correctly; statistical conclusions consistent with data; action recommendations consistent with conclusions; guardrail metrics fully covered; heterogeneity effects analyzed (at least 3 segment dimensions)
Mode: AI->Human

Stage Summary (post_pipeline)

Follows the stage summary protocol in [orchestrator-protocol.md](../../../codex-templates/orchestrator-protocol.md).

| Parameter | Value | |------|-----| | Sub-Skill output path | output/pm-metrics-ops/ | | Summary output path | output/phase-reports/pm-metrics-ops/experiment-orchestrator.md |

Downstream connections: primary: decision-orchestrator (experiment complete, convert experiment conclusions into decision actions) alternatives:

  • target: release-orchestrator

reason: Experiment results significant, recommend full rollout condition: Experiment results statistically significant (p Produces PRD Continue with AI-inferred values? (Inferred values confidence =0.5 | When confidence project_dir validity -> Input confidence assessment

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.