CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/split-io-test

Wraps Split.io (Harness FME) SDK testing patterns: hermetic localhost/offline mode with an in-memory features map (JavaScript/browser) or a YAML fixture file (Node.js server-side), getTreatment and getTreatmentWithConfig evaluation, the SDK_READY event and whenReady() promise, impression listener verification, sync.impressionsMode configuration, and CI setup. Use when writing tests for application code instrumented with the Split.io or Harness Feature Management & Experimentation SDK.

77

Quality

97%

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

92%

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

Highly actionable, well-sequenced content with executable examples for both SDKs and strong validation guidance. The only weak dimension is progressive disclosure: most detail lives inline in a long SKILL.md with just one offloaded example file.

Suggestions

Move the detailed per-pattern sections (e.g., impression listener, impressionsMode, assignment integrity) into a dedicated references file and keep SKILL.md as a concise overview that links out, improving the progressive-disclosure split.

Consider extracting the anti-patterns table and limitations into a separate reference so the main body stays a lean orientation to the workflow.

Add a one-line 'Quick start' summary near the top that points to EXAMPLE.md for a runnable end-to-end case, front-loading the most useful single reference.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious, SDK-specific behavior (localhost mode, 'control' fallback semantics, impression listener object shape, Node-vs-JS getTreatment signatures, v10.7.0 YAML requirement) rather than explaining basic concepts Claude already knows, so the prose earns its place. It is not a 2 because there is no generic padding or library basics exposition.

3 / 3

Actionability

Provides fully executable, copy-paste-ready TypeScript for both the browser and Node.js SDKs, a YAML fixture, install command, CI workflow, impression listener wiring, and teardown — meeting the 'fully executable code/commands' anchor.

3 / 3

Workflow Clarity

A clear sequenced workflow (install → offline setup → await SDK_READY/whenReady → evaluate → verify impressions → destroy → CI) with explicit validation checkpoints (await whenReady before assertions, determinism checks) and an anti-patterns table acting as a failure-mode checklist.

3 / 3

Progressive Disclosure

SKILL.md is a ~260-line document keeping all detailed patterns inline, with only one well-signaled one-level reference (EXAMPLE.md, which exists). It matches the score-2 anchor of substantial inline content that could be split into separate reference files rather than the concise-overview-plus-multiple-references score-3 pattern. It is not a 1 because the single reference is clearly signaled and one level deep.

2 / 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.

A strong, specific description that names concrete capabilities, includes an explicit 'Use when' trigger, uses third-person voice, and is clearly niched to Split.io/Harness FME. It is comprehensive without fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple specific concrete capabilities — 'hermetic localhost/offline mode with an in-memory features map (JavaScript/browser) or a YAML fixture file (Node.js server-side)', 'getTreatment and getTreatmentWithConfig evaluation', 'SDK_READY event and whenReady() promise', 'impression listener verification', 'sync.impressionsMode configuration, and CI setup' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both 'what' (the enumerated testing patterns and capabilities) and 'when' via the explicit 'Use when writing tests for application code instrumented with the Split.io or Harness Feature Management & Experimentation SDK' clause.

3 / 3

Trigger Term Quality

Covers the natural terms a user would say — 'Split.io', 'Harness FME', 'Harness Feature Management & Experimentation SDK', and 'writing tests for application code instrumented with the Split.io' — giving good coverage of natural trigger keywords rather than generic jargon.

3 / 3

Distinctiveness Conflict Risk

Clear niche tied to the Split.io/Harness FME SDK with its distinct localhost/offline mechanism and getTreatment API, making it unlikely to trigger for the wrong sibling-SDK 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