CtrlK
BlogDocsLog inGet started
Tessl Logo

experimentation-platform-orchestrator

A platform decision framework for experimentation. When to use Statsig vs PostHog vs GrowthBook vs Optimizely vs Amplitude vs Eppo vs Kameleoon. How to migrate between them. How to coordinate when multi-platform is genuinely warranted. The decisions that compound for years and the ones you can defer. Triggers on which experimentation platform, choose Statsig vs PostHog, evaluate experimentation tools, switch experimentation platform, migrate from Optimizely, consolidate experimentation tools, multi-platform experimentation, experimentation platform decision, ab test platform selection, feature flag platform vs experiment platform, warehouse-native experiments, vendor lock-in experimentation. Also triggers when a team is asking about cost, governance, or migration cost across experimentation tools, or when an evaluation is starting.

74

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body is a well-structured, actionable decision framework with strong progressive disclosure and clear migration/decision workflows backed by real reference files. Its main weakness is conciseness: the 7- and 11-consideration lists duplicate each other and some editorial prose could be cut.

Suggestions

Collapse the '7 considerations' and '11 considerations' sections into a single ordered list to remove the substantial overlap between lines 29-45 and 248-262.

Trim editorializing prose such as 'Picking an experimentation platform is one of those decisions that looks easy at the start and compounds for years afterward' that does not change the actionable guidance.

Move any platform-by-platform detail that is not needed for the headline decision into the reference files, keeping the body as a concise overview that points outward.

DimensionReasoningScore

Conciseness

Mostly information-dense content Claude would not already know (platform pricing, effort estimates), but the '7 considerations' (lines 29-45) and '11 considerations' (lines 248-262) lists overlap substantially, and editorial prose such as 'Picking an experimentation platform is one of those decisions that looks easy at the start...' could be trimmed.

2 / 3

Actionability

Concrete, specific guidance throughout: per-context platform recommendations ('Pure SaaS... Choose Statsig'), migration effort ranges in engineer-weeks with explicit steps ('Migrate experiments before flags. Retire Optimizely only after all in-flight experiments complete'), and a defined output contract (primary recommendation / short list of two / defer).

3 / 3

Workflow Clarity

Sequenced processes with explicit validation: the 7 considerations have a stated order ('Answer them honestly first, then read the per-platform profiles, then consult the decision matrix'), and migrations include a feedback loop ('Parallel-run for 4 to 8 weeks, validate experiments produce the same results on both, cut over once trust is established').

3 / 3

Progressive Disclosure

Well-organized overview body with inline links to seven reference files, each summarized in a dedicated 'Reference files' section; all seven referenced paths exist in ./references/ and are one level deep with clear signaling.

3 / 3

Total

11

/

12

Passed

Description

100%

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

The description is specific, trigger-rich, and complete: it states concrete actions, lists natural trigger terms, answers both what and when, and carves out a distinct niche with explicit boundaries against adjacent skills. Third-person voice is maintained throughout.

DimensionReasoningScore

Specificity

Names concrete actions across a clearly bounded domain: 'When to use Statsig vs PostHog vs GrowthBook...', 'How to migrate between them', 'How to coordinate when multi-platform is genuinely warranted' — multiple specific concrete actions, not vague language.

3 / 3

Completeness

Explicitly answers both what ('A platform decision framework... How to migrate... How to coordinate...') and when ('Triggers on... Also triggers when a team is asking about cost, governance, or migration cost...').

3 / 3

Trigger Term Quality

Strong coverage of natural phrasings a user would actually say: 'choose Statsig vs PostHog', 'migrate from Optimizely', 'switch experimentation platform', 'ab test platform selection', 'consolidate experimentation tools', plus 'cost, governance, or migration cost'.

3 / 3

Distinctiveness Conflict Risk

Clear niche (experimentation platform selection/migration) with distinct named-platform triggers; the body explicitly excludes experiment design, result interpretation, and feature flag operations, so it is unlikely to fire for adjacent skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
rampstackco/claude-skills
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.