Individual skill

feature-flag-onboarding

Orchestrate 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.

skills/fme/feature-flag-onboarding/SKILL.md

Read pinned source

Source commit e01dc7275f7e261f390be2fe7be4559feadb74ef

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
133
Repository last updated
Oct 28, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Feature Flag Onboarding

Orchestrate a new application's first end-to-end FME setup: confirm scope, pick a safe environment, detect the codebase, delegate code integration, then prove two distinct treatments actually run live. This skill sequences and verifies; it does not re-implement flag creation, code wiring, or targeting changes — those live in `/create-feature-flag`, `/instrument-feature-flag`, and `/update-flag-targeting`.

## Tools

Works through the Harness MCP server or the Harness CLI; names are from [tool-map.md](../../../references/fme/tool-map.md). All writes are delegated to the linked skills — this skill only reads.

| Operation | MCP | CLI |
|-----------|-----|-----|
| List environments | `harness_list` · `fme_environment` · `compact: false` | `harness list fme_environment --json` |
| List flags | `harness_list` · `fme_feature_flag` · `size: 50` · `compact: false` | `harness list feature_flag --json --limit 50` |
| Get flag | `harness_get` · `fme_feature_flag` · `params.feature_flag_name` | `harness get feature_flag <name> --json` |
| Get definition | `harness_get` · `fme_feature_flag_definition` · `params: { feature_flag_name, environment_id }` | `harness get feature_flag:definition <flag> --env <env-id> --json` |
Back to top