instrument-feature-flag
Installation
SKILL.md
Instrument Feature Flag
Skill identifier: instrument-feature-flag. Gate application code behind an existing FME flag: inspect the real app first, prefer or design a small customer-extensible wrapper, get it approved, implement the minimal edits, and test at the wrapper and call-site boundary. Related: /create-feature-flag (new flag), /update-flag-targeting (missing/insufficient targeting), /feature-flag-onboarding (first-time setup, which delegates here for code).
Tools
Works through the Harness MCP server or the Harness CLI; names are from tool-map.md. This skill only reads Harness flag state for the selected environment — flag/definition writes are delegated to /create-feature-flag and /update-flag-targeting.
| Operation | MCP | CLI |
|---|---|---|
| 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 |
| List environments | harness_list · fme_environment · compact: false |
harness list fme_environment --json |
| List traffic types | harness_list · fme_traffic_type · compact: false |
harness list traffic_type --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 |