CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

finding-deleted-feature-flags

Find feature flags that were soft-deleted in the active project within a recent time window. Use when the user asks "what flags were deleted in the last N days", "show me recently deleted feature flags", "who deleted flag X", "audit recent flag deletions", or anything similar. Handles the non-obvious gotcha that system.feature_flags exposes the deleted boolean but does not expose a deletion timestamp — the actual deleted-at time lives in the per-flag activity log and must be cross-referenced.

70

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

—

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 well-structured, highly actionable skill body with concrete SQL/MCP/bash examples and clear sequencing. Its main defect is that the one bundled script it directs the reader to (`scripts/strip_deleted_suffix.py`) is absent from the skill bundle.

Suggestions

Ship the missing `scripts/strip_deleted_suffix.py` referenced in step 5, the example, and the Scripts section — the body instructs the reader to pipe data through it, so its absence breaks the workflow.

Add an explicit validation/verification checkpoint in the workflow (e.g., confirm each activity-log response actually contains an `activity: deleted` entry before filtering) to strengthen the feedback loop for the batch fan-out.

Tighten the step-2 rationale paragraph (the created_at-DESC heuristic) so it reads as a brief note rather than a multi-clause justification.

DimensionReasoningScore

Conciseness

Mostly lean and efficient; the deleted_at gotcha and rename behavior are genuine non-obvious domain knowledge that earns their tokens rather than padding Claude already knows. Not a 5 because a few prose passages (e.g., the heuristic rationale in step 2) could be tightened further.

4 / 5

Actionability

Fully executable guidance throughout: a concrete SQL query, a concrete MCP call with parameters, and a copy-paste bash command with sample input/output. Specific examples cover the common cases.

5 / 5

Workflow Clarity

Five clearly sequenced steps with explicit edge-case handling (borderline-cutoff surfacing, methodology/coverage disclosure, the don't-trust-created_at watch-out). Not a 5 because there is no explicit validate→fix→retry feedback loop, though the read-only audit nature means the destructive-batch cap does not force a 3.

4 / 5

Progressive Disclosure

Sections are well organized and the lone external reference is single-level and clearly signaled, but the referenced `./scripts/strip_deleted_suffix.py` does not exist in the bundle — a broken reference that undermines navigation. Not a 4 because a promised reference file is missing rather than a minor organization gap.

3 / 5

Total

16

/

20

Passed

Description

95%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, specific description that clearly states the capability, supplies multiple natural trigger phrases, and surfaces the non-obvious gotcha that distinguishes this skill. Both the what and when are explicit and concrete.

DimensionReasoningScore

Specificity

Lists several concrete actions ("Find feature flags that were soft-deleted", cross-reference the per-flag activity log for the deletion timestamp, identify who/when) with only minor gaps in coverage. Not a 5 because it stops short of naming the full output/recovery actions detailed in the body.

4 / 5

Completeness

Explicitly answers both what (find soft-deleted flags + who/when within a time window) and when ("Use when the user asks...") with concrete trigger phrases. Voice is third person ("Find", "Handles"), so no voice penalty.

5 / 5

Trigger Term Quality

Quotes natural phrases a user would actually say — "what flags were deleted in the last N days", "show me recently deleted feature flags", "who deleted flag X", "audit recent flag deletions" — plus the generic "or anything similar", giving comprehensive coverage including synonyms.

5 / 5

Distinctiveness Conflict Risk

A clear narrow niche (recently soft-deleted feature flags in a time window) with distinct, specific triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

14

/

16

Passed

Repository

PostHog/posthog

Path

products/feature_flags/skills/finding-deleted-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.