experiment-governance

Transform experiment metrics into advisory governance classifications with supporting evidence.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/EnesMeyzin98/Meridian --skill experiment-governance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: experiment-governance
Source: https://github.com/EnesMeyzin98/Meridian/tree/main/agents/skills/experiment-governance
Command: npx skills add https://github.com/EnesMeyzin98/Meridian --skill experiment-governance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains and extends the advisory governance layer that classifies experiment usefulness, concentration, noise, and scoped-candidate status from existing paper-research metrics. Use when updating experiment status rules, governance summaries, or operator-facing decision support. Never use for auto-enabling experiments or changing scorer behavior directly.

Core Features & Use Cases

  • Transform existing summary metrics into standardized governance statuses and rule triggers for experiments.
  • Support operator-facing decision-support widgets and audit trails with passive, advisory conclusions.
  • Capture explicit manual notes, defer/reject reasons, and promotion history within a shared audit model.

Quick Start

Review the current experiment metrics and generate a governance verdict with supporting evidence for operator review.

Frequently Asked Questions about experiment-governance

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

FAQPage Schema
How do I classify research metrics into advisory governance statuses?▼

This advisory governance layer transforms existing paper-research metrics into standardized classifications for experiment usefulness, concentration, noise, and scoped-candidate status. It generates explicit advisory statuses with supporting evidence for operator review.

Can I use advisory governance to automatically change experiment status at runtime?▼

No, you cannot use advisory governance to automatically change experiment status. Governance outputs remain strictly advisory, providing passive conclusions and decision-support without directly auto-enabling experiments or changing scorer behavior.

How do I maintain an audit trail for experiment defer and reject reasons?▼

You maintain an audit trail for experiment decisions by capturing explicit manual notes, defer or reject reasons, and promotion history within a shared audit model. This supports operator-facing decision workflows with documented evidence.

What is the best way to generate decision-support summaries from existing experiment metrics?▼

The best way to generate decision-support summaries is by applying standardized status rules to existing experiment metrics. This produces governance summaries and advisory verdicts with supporting evidence, keeping outputs passive for operator review.

When should I not use experiment governance classifications?▼

You should not use experiment governance classifications when you need to directly change scorer behavior or auto-enable experiments. Governance is strictly advisory and never makes runtime changes to experiment execution or scoring logic.