CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

webiny-add-feature-flag

Adding a new feature flag to the Webiny system. Use this skill when creating a new feature flag (simple boolean or nested group), gating a feature at the config/admin/API level, or wiring a flag into the WCP license system. Covers IFeatureFlagsDto, KnownFeatureFlag, Zod schema, FeatureFlag.CanUse components, useFeatureFlags().isEnabled(), the API FeatureFlags abstraction, toDto(), and the LICENSE_CHECKS decorator pattern.

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

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

Highly actionable content with exact file paths, executable code for every step, and a clear decision-flow model that governs the whole document. The main improvements are adding an explicit verification step, trimming redundant restatements of the decision flow, and potentially externalizing the nested-group and license-decorator details into reference files.

Suggestions

Add a final verification step to the workflow, e.g., confirm the new flag resolves correctly by querying the featureFlags GraphQL endpoint or checking visibility in the admin UI, so the sequence includes an explicit checkpoint.

Trim the redundancy between the decision flow table, the 'Key points' bullets, and the WCP License Gating section — the rules are stated three times and could be consolidated into one authoritative section.

Consider moving the nested flag group walkthrough and the LICENSE_CHECKS decorator details (three decorator paths plus ILicense changes) into reference files to keep SKILL.md a leaner overview, since the body currently runs ~240 lines with everything inline.

DimensionReasoningScore

Conciseness

The body is dense and purposeful with no re-teaching of known concepts, but contains minor redundancy: the 'Key points' bullets restate the decision flow table, and the WCP License Gating section repeats decision-flow rules already stated above. This matches 'efficient; minor instances of over-explanation that could be trimmed' rather than the fully lean anchor.

4 / 5

Actionability

Every step gives an exact file path and copy-paste-ready TypeScript snippets, covers all three gating levels (config, admin runtime, API runtime), both flag shapes (boolean and nested group), and ends with a complete files reference table — fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

The numbered 1–6 sequence for a simple boolean flag is clear with per-step file targets, plus separate well-ordered tracks for nested groups and license gating. However, there is no explicit validation/verification step (e.g., confirming the flag via the featureFlags GraphQL query or the admin UI), matching 'clear sequence with most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

A single-file skill with well-organized sections and a files reference table, but at ~240 lines everything is inline — the nested flag group section and the LICENSE_CHECKS decorator internals could plausibly live in reference files. Good structure with minor organization gaps, short of the clear-overview-with-one-level-references anchor.

4 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

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 description with explicit 'Use when' triggers, multiple concrete actions, named technical artifacts, and a clearly distinct niche. The only gap is minor: it lacks synonyms such as 'feature toggle' that some users might naturally say.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "creating a new feature flag (simple boolean or nested group)", "gating a feature at the config/admin/API level", "wiring a flag into the WCP license system" — and names the specific artifacts involved (IFeatureFlagsDto, KnownFeatureFlag, Zod schema, LICENSE_CHECKS decorator pattern), giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

It explicitly answers both questions: the 'what' (adding feature flags and the artifacts covered) and the 'when' via the explicit trigger clause "Use this skill when creating a new feature flag..., gating a feature..., or wiring a flag into the WCP license system" with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage — "feature flag", "Webiny", "gating a feature", "license" are phrases a user would naturally say — but common synonyms like "feature toggle" or "enable a feature" are missing, matching the 'good coverage, a few natural terms missing' anchor rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The Webiny/WCP license niche is highly specific with distinct triggers (Webiny system, WCP license system, IFeatureFlagsDto), making accidental triggering by unrelated skills extremely unlikely.

5 / 5

Total

19

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

webiny/webiny-js

Path

skills/repo-skills/add-feature-flag/SKILL.md

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.