CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/flagsmith-testing

Wraps Flagsmith server-side SDK testing patterns (feature flags / feature toggles) so tests run without calling the Flagsmith API: offline mode with LocalFileHandler + a downloaded environment.json snapshot, local-evaluation mode (no per-request network), and default_flag_handler for per-feature mocked fallbacks, via the get_environment_flags / get_identity_flags evaluation paths. Use when writing feature-flag tests for code that uses Flagsmith, mocking flag values, or testing feature toggles offline in CI.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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

A well-structured, highly actionable skill body with a clear sequenced workflow, an explicit verification step, and clean one-level-deep progressive disclosure. The main drag on token efficiency is the 'Worked example' section, which re-narrates steps and code already presented earlier.

Suggestions

Drop or compress the 'Worked example' section to a single sentence — it restates steps 2–4 and snippets already shown in 'How to use' and 'Evaluate flags', adding tokens without new information.

Show the offline-client construction once (either as step 3's code or in 'Offline mode with LocalFileHandler') rather than narrating it in step 3 and re-rendering it as a separate snippet.

DimensionReasoningScore

Conciseness

Prose is lean and avoids explaining concepts Claude already knows, but the 'Worked example' section restates steps 2–4 and code already shown in 'How to use' and 'Evaluate flags', and the offline-client setup is narrated in step 3 then re-shown as a standalone snippet — content that could be tightened.

2 / 3

Actionability

Provides copy-paste-ready, executable guidance throughout: install commands, the flagsmith CLI download command, offline-client construction, evaluate/identity/integrity test code, and a CI yaml block.

3 / 3

Workflow Clarity

An explicit 8-step sequence culminating in a verification checkpoint (step 7: assert zero network calls, with a diagnose-and-re-run feedback loop if it raises), satisfying the validation-required anchor for the workflow.

3 / 3

Progressive Disclosure

Body is an overview that keeps the default offline mode inline and pushes secondary modes, anti-patterns, and limitations to a single one-level-deep, clearly linked reference file (references/flagsmith-modes.md) that exists and links only back to SKILL.md.

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.

A dense but precise description that names concrete capabilities, natural trigger terms, an explicit use-when clause, and a clearly bounded Flagsmith-only niche in third person. Its only weakness is that it packs a lot into one sentence, but nothing reads as fluff or over-claim.

DimensionReasoningScore

Specificity

Names multiple concrete actions and APIs — 'offline mode with LocalFileHandler + a downloaded environment.json snapshot', 'local-evaluation mode', 'default_flag_handler for per-feature mocked fallbacks', 'get_environment_flags / get_identity_flags evaluation paths' — rather than vague language.

3 / 3

Completeness

Explicitly answers what it does (wraps three test modes and the evaluation paths) and when to use it via a literal 'Use when writing feature-flag tests... mocking flag values, or testing feature toggles offline in CI' clause.

3 / 3

Trigger Term Quality

Covers natural terms a user would say — 'feature flags / feature toggles', 'mocking flag values', 'testing feature toggles offline in CI' — alongside the product name, matching the good-coverage anchor.

3 / 3

Distinctiveness Conflict Risk

Scoped to Flagsmith-specific server-side SDK testing with a distinct trigger ('code that uses Flagsmith'), so it is unlikely to fire for unrelated or sibling-product skills.

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