CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

80

Quality

100%

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

100%

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

A high-quality operational skill: lean, fully actionable, with a clearly sequenced workflow that handles edge cases and discloses limitations, and a properly signaled single external script reference.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious domain knowledge (the deleted_at gotcha, tombstone rename behavior, batch sizing) and assumes Claude's competence, avoiding padding with concepts Claude already knows.

3 / 3

Actionability

Provides a concrete SQL query, a concrete MCP call with exact parameters, specific batch sizes, and a copy-paste-ready script invocation — all executable rather than pseudocode.

3 / 3

Workflow Clarity

A clearly sequenced five-step workflow with explicit edge-case checkpoints (borderline cutoffs, deleted-and-restored flags, sampling disclosure, methodology reporting) that guide a fragile batch-lookup operation.

3 / 3

Progressive Disclosure

Well-organized into focused sections with a single one-level-deep, clearly signaled reference to scripts/strip_deleted_suffix.py, which exists as a real bundle file.

3 / 3

Total

12

/

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 strong, specific description with concrete actions, natural trigger phrasings, an explicit Use-when clause, and a clearly distinct niche. It also surfaces the key non-obvious gotcha without over-claiming.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — enumerating soft-deleted flags, cross-referencing the per-flag activity log, and recovering who deleted each flag and when — rather than vague language.

3 / 3

Completeness

Explicitly answers what the skill does (find soft-deleted flags + who/when) and when to use it via an explicit 'Use when...' clause with multiple triggers.

3 / 3

Trigger Term Quality

Quotes several natural phrasings a user would actually say ('what flags were deleted in the last N days', 'who deleted flag X', 'audit recent flag deletions'), giving strong trigger coverage.

3 / 3

Distinctiveness Conflict Risk

Targets a narrow, distinct niche (soft-deleted feature flags with a specific missing-timestamp gotcha) that is unlikely to trigger for the wrong skill.

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.

Repository
PostHog/posthog
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.