CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/optimizely-test

Wraps Optimizely Feature Experimentation SDK testing patterns - client init from a fixture datafile (offline-friendly), the decide / decideAll v5 API, forced-decisions for per-test arm pinning (fixing which variation a user gets), OptimizelyUserContext + activate/track events, assignment-integrity (deterministic bucketing) tests. Use when writing A/B tests or feature-flag tests for Optimizely-instrumented application code. For another experimentation SDK use the matching harness - statsig-test, vwo-test, amplitude-experiment-test, or split-io-test; for experiment DESIGN gates not SDK code use ab-test-validity-checklist.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

100%

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

A well-structured, executable skill body: lean code-forward sections, a sequenced how-to with an explicit validation checkpoint, and a single clearly-signaled reference file for extended recipes. It assumes Claude's competence while remaining copy-paste ready.

DimensionReasoningScore

Conciseness

The body is code-forward and section-dense — install, init, user-context, and forced-decision code blocks plus an anti-pattern table and tight limitations. The single Overview sentence on the datafile mechanism directly supports the offline-testing pattern that is the skill's core value, so it earns its place rather than padding concepts Claude already knows.

3 / 3

Actionability

Provides copy-paste-ready, executable guidance: 'pip install optimizely-sdk', the datafile-based init block, create_user_context/decide assertions, and set_forced_decision pinning. Concrete commands and runnable code match the score-3 anchor rather than the pseudocode/vague anchors.

3 / 3

Workflow Clarity

The 8-step 'How to use' is clearly sequenced and includes an explicit validation checkpoint with a feedback loop — step 5 verifies the fixture drives a real decision and says to re-export and re-run if it fails. This explicit validate-then-recover pattern matches the score-3 anchor.

3 / 3

Progressive Disclosure

Keeps the core spine (install, init, decide, forced decisions) inline and signals a single one-level-deep reference — 'Extended recipes ... are in references/optimizely-recipes.md' — which exists as a real, well-scoped bundle file. Content is appropriately split with clear navigation, matching the score-3 anchor.

3 / 3

Total

12

/

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.

A strong, third-person description that pairs concrete SDK testing capabilities with an explicit 'Use when' trigger and clear sibling-skill disambiguation. It is specific, complete, and low-conflict.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'client init from a fixture datafile', 'decide / decideAll v5 API', 'forced-decisions for per-test arm pinning', 'OptimizelyUserContext + activate/track events', 'assignment-integrity (deterministic bucketing) tests'. This is comprehensive, not merely a domain plus a few actions, so it exceeds the score-2 anchor.

3 / 3

Completeness

Answers both what (the wrapped testing patterns) and when via the explicit 'Use when writing A/B tests or feature-flag tests for Optimizely-instrumented application code' clause. The explicit 'Use when...' trigger satisfies the score-3 anchor and avoids the score-2 cap for a missing trigger clause.

3 / 3

Trigger Term Quality

Includes natural terms a user would actually say — 'A/B tests', 'feature-flag tests', 'Optimizely-instrumented application code' — alongside the technical API names. Coverage of natural phrasing matches the score-3 anchor rather than the jargon-only or partial-coverage anchors.

3 / 3

Distinctiveness Conflict Risk

Has a clear Optimizely niche and explicitly disambiguates from sibling SDK harnesses ('statsig-test, vwo-test, amplitude-experiment-test, or split-io-test') and from design-gate work ('ab-test-validity-checklist'). This distinct-trigger niche matches the score-3 anchor and is unlikely to fire for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents