discover-feature-flags
From the author
Audit Harness FME feature flags across a project. Read-only; never writes. Four modes: inventory (list flags with metadata), rollout-report (per-env rollout state with stalled-promotion detection across a confirmed env sequence), stale-audit (find flags with no impressions via lastImpressionAt), pattern-search (find flags whose rule conditions structurally match an attribute name, matcher type, literal value, segment reference, or flag dependency — not a text grep). Use when asked to "show me all flags", "which flags are stale", "what flags are rolled out", "flag inventory", "flag health", "cleanup candidates", "find flags targeting segment X", "which flags depend on flag Y", or "find flags with rule matching attribute Z". Do not use for single-flag deep dive (explain-flag), creating flags (create-feature-flag), updating targeting (update-flag-targeting), archiving/deleting (manage-flag-lifecycle), pipeline rollouts (fme-pipeline), or code removal (cleanup-feature-flags).
Install
npx skills add harness/harness-skills --skill discover-feature-flags -a claude-code
Installs to .claude/skills/discover-feature-flags/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- create-feature-flagharness/harness-skillsCreate a new Harness FME feature flag and its per-environment definitions with a safe default, following the project's naming and tagging conventions. Use when asked to create a feature flag, add a flag, set up a new FME flag, or initialize flag targeting. Flag/definition writes only: does not gate application code (instrument-feature-flag) and is not a first-time onboarding entry point (feature-flag-onboarding). Do not use for updating existing flag targeting (update-flag-targeting), deep analysis of a single flag (explain-flag), listing/discovering flags (discover-feature-flags), flag lifecycle like archive/delete (manage-flag-lifecycle), segments (manage-segments), experiments (manage-experiments), pipeline rollouts (fme-pipeline), or removing flags from code (cleanup-feature-flags). Trigger phrases: create feature flag, add flag, new flag, set up flag, FME flag create, initialize flag.Writing★ 125
- feature-flag-onboardingharness/harness-skillsOrchestrate first-time Harness FME onboarding for one application. Confirm an already-enabled FME account/project, then pick one verified non-production environment; if none exists, hand off to an admin, not creating one. Detect the codebase's language and framework, then delegate code integration to instrument-feature-flag — never duplicating its wrapper design or creating the same flag twice. Verify two distinct named-treatment outcomes live through separately approved targeting changes when needed, not just default/fallback responses. Resumes from live state and a non-secret progress summary instead of a checkpoint file; never recreates a flag from uncertain absence or reuses a stale approval. Use when asked to onboard FME for an app, set up feature flags end-to-end, or prove a flag works live. Not for flag creation alone (create-feature-flag), code gating alone (instrument-feature-flag), targeting alone (update-flag-targeting), or metric/experiment setup.Design★ 125
- instrument-feature-flagharness/harness-skillsGate application code behind an existing Harness FME feature flag. Detect the app's language, framework and any existing flag wrapper first; ask only what that can't resolve (target app, subject identity, gating point, treatment/config/fallback names, extension needs). Prefer an existing wrapper; otherwise propose a thin, customer-extensible facade or hook — never a new framework or second SDK client — approved before editing. Map named treatments to branches with a safe, non-boolean-coerced fallback, then add tests at the wrapper and call-site boundary. New flags delegate to create-feature-flag with the one environment actually selected; missing targeting delegates to update-flag-targeting under fresh approval. Not for flag creation alone, metrics (choose-metric, create-metric, instrument-metric), or first-time onboarding (feature-flag-onboarding). Trigger phrases: gate this code behind a flag, add flag check, wire up getTreatment, add SDK evaluation call.Testing★ 125
- explain-flagharness/harness-skillsExplain a single FME feature flag in plain language: purpose, default rule, and per-environment targeting state, flagging inconsistencies across environments inline. A quick-lookup/explain capability, not a search across many flags - disambiguates when the name/key given is ambiguous. Doesn't create, kill, or modify anything - see update-flag-targeting for targeting changes, manage-flag-lifecycle for metadata/archive, discover-feature-flags for multi-flag questions, manage-experiments for experiments. Trigger phrases: what does this flag do, explain this flag, how is X configured, is X on in prod, what's targeted for X.Other★ 125
- Feature Flag TestingPramodDutta/qaskillsTesting feature flag implementations including flag evaluation, gradual rollout verification, fallback behavior, and flag cleanup detection.Testing★ 240
- update-flag-targetingharness/harness-skillsChange how a Harness FME feature flag serves traffic in environments. Covers percentage rollout, individual targets, targeting rules (attribute/segment/flag-dependency), defaultTreatment, trafficAllocation, treatments, kill/restore, and copying or initializing a definition in an environment. Use when asked to ramp a flag, add rules/users, change allocation, kill/restore, or promote config. Not for creating flags (create-feature-flag), metadata like tags/owners/archive (manage-flag-lifecycle), segment keys (manage-segments), pipeline rollouts (fme-pipeline), or flag analysis (explain-flag). Trigger phrases: update targeting, ramp flag, percentage rollout, add rule, add users, kill flag, restore, copy config.Other★ 125
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in