choose-metric
Installation
SKILL.md
Choose Metric
Recommend metrics for an FME experiment or feature-flag rollout: which is primary, which are guardrails/supporting, and which existing candidates are healthy enough to trust, judged against what makes a good metric. Related: /manage-experiments attaches metrics to experiments; /create-metric creates new metrics; /instrument-metric adds tracking calls.
Tools
Works through the Harness MCP server or the Harness CLI; names are from tool-map.md.
| Operation | MCP | CLI |
|---|---|---|
| Get flag | harness_get · fme_feature_flag · params: { feature_flag_name } |
harness get feature_flag <name> --json |
| Get experiment | harness_get · fme_experiment · params: { experiment_id } |
harness get experiment <id> --json |
| List metrics | harness_list · fme_metric · filters: { traffic_type_id?, name?, limit } · compact: false |
harness list metric --traffic-type-id <id> --name <substring> --json |
| List traffic types | harness_list · fme_traffic_type · compact: false |
harness list traffic_type --json |
| List event types | harness_list · fme_event_type · filters: { traffic_type?, name? } · compact: false |
harness list event_type --traffic-type <name or id> --name <substring> --json |
| Get event type | harness_get · fme_event_type · params: { event_type_id } |
harness get event_type <event-name> --json |