CtrlK
BlogDocsLog inGet started
Tessl Logo

add-feature-flag

Add a runtime feature flag (AppConfig-backed on prod, secret fallback off-prod), global by default or optionally gated by workspace id, org id, user id, or platform admin

66

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/add-feature-flag/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

93%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.

The body is an exemplary self-contained procedural skill: lean, project-specific, and executable, with concrete code for both flag modes, precise file paths, and a clean six-step workflow including rollout cleanup. The only minor gap is an explicit verification command at the end of the workflow.

DimensionReasoningScore

Conciseness

The body is lean and every token carries project-specific information ('Critically, none of this is expressible in code', 'The admin check reads the DB replica (`dbReplica`) and is resolved lazily') — nothing explains concepts Claude already knows. Anchor 5 fits; there is no padding to trim for anchor 4.

5 / 5

Actionability

Copy-paste-ready code for the registry entry and both call-site modes (global and scoped) with imports, exact file paths, and the typecheck failure consequence ('it won't typecheck otherwise'). Covers the common cases completely; there are no gaps that would drop it to anchor 4.

5 / 5

Workflow Clarity

Six well-sequenced steps with a confirm-before-editing checkpoint (step 1) and a typecheck feedback loop, but no explicit command to run tests or verify the result at the end — anchor 4 ('most checkpoints present; minor validation gaps') rather than 5's explicit validation steps. This is not a destructive/batch operation, so the cap-at-3 rule does not apply.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed: the skill is a single focused procedure (~90 lines with code) with well-organized sections and one clearly signaled one-level-deep pointer ('see the AppConfig runbook in the infra README'). Easy to navigate, nothing that should be split; anchor 5 fits better than 4.

5 / 5

Total

19

/

20

Passed

Description

66%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.

The description is specific and technically precise, clearly conveying what the flag system does and its scoping options in a third-person voice. Its main weakness is the absence of any explicit 'when to use' trigger clause, which both caps completeness and limits natural trigger-term coverage.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to add a feature flag, gate a feature, or control a runtime rollout.'

Include natural synonyms users might say — 'rollout', 'toggle', 'kill switch' — alongside 'feature flag' to broaden trigger matching.

Add a one-line disambiguator against the sibling env-flag concept, e.g. 'For fixed deploy-time toggles use env-flags instead.'

DimensionReasoningScore

Specificity

Concrete mechanics are stated ('Add a runtime feature flag', 'AppConfig-backed on prod', 'secret fallback off-prod', 'gated by workspace id, org id, user id, or platform admin'), but it describes one action with modes rather than the multiple distinct actions anchor 5 requires.

4 / 5

Completeness

The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural developer phrasing is present ('feature flag', 'runtime', 'gated', 'workspace id', 'platform admin'), but common synonyms like 'rollout', 'toggle', or 'kill switch' are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

'Runtime', 'AppConfig-backed', and 'secret fallback' clearly distinguish it from the sibling env-flag concept, though a bare 'add a flag' request could still route to the deploy-time env-flag path — minor overlap with a closely related skill.

4 / 5

Total

15

/

20

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.

Validation — 15 / 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
simstudioai/sim
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.