CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

feature-flags

Gate a Sentry feature behind a FlagPole feature flag. Use when adding a feature flag, registering a flag in temporary.py, checking a flag from Python or the frontend, enabling a flag in tests, or asking where FlagPole rollout config lives. Trigger on "add a feature flag", "gate this behind a flag", "register a flag", "features.has", "api_expose", "OrganizationFeature", "ProjectFeature", "FlagPole".

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

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.

A tight, actionable reference that walks through the full feature-flag lifecycle with copy-paste code and well-organized sections. The only gap is the absence of an explicit validation/feedback loop, which keeps workflow clarity at 4 rather than 5.

DimensionReasoningScore

Conciseness

Lean and efficient: a one-line intro plus minimal copy-paste snippets with no explanation of what feature flags are; every token earns its place. Not below 5 because there is no padding or over-explanation.

5 / 5

Actionability

Fully executable, copy-paste-ready code covers the common cases — registration, Python check, frontend check, and test gating — plus concrete pointers for rollout and removal; not 4 because no common case lacks concrete code.

5 / 5

Workflow Clarity

A clear numbered 1–6 sequence with step 4 (Tests) acting as a checkpoint, but there is no explicit validate→fix→retry feedback loop; not 5 because anchors at 5 require explicit validation steps with error-recovery loops, and not 3 because the sequence and the test checkpoint are well-defined.

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files; well-organized numbered sections plus one-level-deep pointers to the remove-option-or-flag skill and the external docs URL, matching the simple-skill exception that allows a 5 with just well-organized sections.

5 / 5

Total

19

/

20

Passed

Description

100%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 highly specific, third-person description that clearly states the capability and provides explicit, natural trigger phrases plus exact code symbols. It scores maximally across all four dimensions with no vague padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Gate a Sentry feature behind a FlagPole feature flag', 'registering a flag in temporary.py', 'checking a flag from Python or the frontend', 'enabling a flag in tests' — giving comprehensive coverage; not 4 because there are no real gaps in the core actions.

5 / 5

Completeness

Explicitly answers both 'what' ('Gate a Sentry feature behind a FlagPole feature flag') and 'when' ('Use when adding a feature flag, registering a flag...') with concrete trigger phrases; not below 5 because neither axis is missing or vague.

5 / 5

Trigger Term Quality

Combines natural user phrases ('add a feature flag', 'gate this behind a flag', 'register a flag') with the exact technical symbols users would quote ('features.has', 'api_expose', 'FlagPole'); comprehensive coverage including synonyms.

5 / 5

Distinctiveness Conflict Risk

Narrow Sentry/FlagPole niche with highly specific triggers ('temporary.py', 'FlagPole', 'OrganizationFeature') makes conflict with unrelated skills minimal.

5 / 5

Total

20

/

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

getsentry/sentry

Path

.agents/skills/feature-flags/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.