manage-segments
Create, inspect, and maintain Harness FME segments (STANDARD, LARGE, RULE_BASED). Manage metadata, select type-specific definition and membership workflows, and check referencing flags before every mutation. Use when asked to create a segment, add keys to a segment, list segments, update segment metadata, remove keys, replace keys, check segment usage, or delete segments. Do not use for making a flag USE a segment (update-flag-targeting), flag CRUD (create-feature-flag, manage-flag-lifecycle), or flag discovery (discover-feature-flags). Trigger phrases: create segment, add keys, list segments, segment membership, segment targeting, update segment, remove keys, replace segment keys, segment definition, check segment usage, delete segment.
Harness · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add harness/harness-skills --skill manage-segments技能说明
name: manage-segments description: >- Create, inspect, and maintain Harness FME segments (STANDARD, LARGE, RULE_BASED). Manage metadata, select type-specific definition and membership workflows, and check referencing flags before every mutation. Use when asked to create a segment, add keys to a segment, list segments, update segment metadata, remove keys, replace keys, check segment usage, or delete segments. Do not use for making a flag USE a segment (update-flag-targeting), flag CRUD (create-feature-flag, manage-flag-lifecycle), or flag discovery (discover-feature-flags). Trigger phrases: create segment, add keys, list segments, segment membership, segment targeting, update segment, remove keys, replace segment keys, segment definition, check segment usage, delete segment. metadata: author: Harness version: 1.3.1 mcp-server: harness-mcp summary: Segment metadata, STANDARD membership, and RULE_BASED editor workflows with mandatory pre-write reference checks license: Apache-2.0 compatibility: Requires Harness MCP or CLI; RULE_BASED rule changes use the Harness rule editor
Manage Segments
Manage metadata for STANDARD, LARGE, and RULE_BASED segments, STANDARD membership, and approved RULE_BASED editor changes. Every mutation requires a complete reference-impact check and explicit approval. LARGE bulk membership operations are outside this skill's scope.
Tools
Works through Harness MCP or CLI with equivalent scope, confirmation and verification requirements. Discover exact CLI action syntax through command help; use tool-map.md for mappings. STANDARD in metadata examples stands for the selected type; definition/key rows apply only to STANDARD.
| Operation | MCP | CLI |
|---|---|---|
| List traffic types | harness_list · fme_traffic_type · compact: false | harness list traffic_type --json |
| 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 |
| List experiments | harness_list · fme_experiment · filters: { parent_type: "FEATURE_FLAG", parent_name, environment_id, status: ["ACTIVE", "PAUSED"], offset: 0, limit: 100 } · compact: false | harness list experiment --parent-type FEATURE_FLAG --parent-name <flag> --env <env-id> --status ACTIVE --json, then PAUSED; fully paginate both |
| List flag definitions | harness_list · fme_feature_flag_definition · params: { feature_flag_name } · filters: { offset: 0, limit: 100 } · compact: false | harness list feature_flag:definition <flag> --json |
| List segments | harness_list · fme_segment · filters: { segment_type, status?, offset: 0, limit: 100 } · compact: false | harness list segment --segment-type STANDARD --json; safety gates list ACTIVE and ARCHIVED using declared status filters |
| Get segment | harness_get · fme_segment · params: { segment_name, segment_type } | harness get segment <name> --segment-type STANDARD --json |
| Create segment | harness_create · fme_segment · body: { name, trafficType, segmentType, description?, tags?, owners? } | harness create segment <name> --traffic-type user --segment-type STANDARD |
| Update segment | harness_update · fme_segment · params: { segment_name, segment_type } · body: { description?, tags?, owners? } | harness update segment <name> --segment-type STANDARD --set description=foo |
| Delete segment | harness_delete · fme_segment · params: { segment_name, segment_type } | harness delete segment <name> --segment-type STANDARD |
| List definitions | harness_list · fme_segment_definition · filters: { environment_id, status?, offset: 0, limit: 100 } · compact: false | harness list segment:definition --env <env-id> --json |
| Get definition | harness_get · fme_segment_definition · params: { segment_name, environment_id } | harness get segment:definition <name> --env <env-id> --json |
| Create definition | harness_create · fme_segment_definition · params: { segment_name, environment_id } · body: { description? }? | harness create segment:definition <name> --env <env-id> |
| Update definition | harness_update · fme_segment_definition · params: { segment_name, environment_id } · body: { description? } | harness update segment:definition <name> --env <env-id> --set description=foo |
| Delete definition | harness_delete · fme_segment_definition · params: { segment_name, environment_id } | harness delete segment:definition <name> --env <env-id> |
| List keys | harness_execute · fme_segment_definition · action="list_keys" · params: { segment_name, environment_id, offset?, limit? } | Discover the key-list action and pagination arguments through CLI help |
| Add keys | harness_execute · fme_segment_definition · action="add_keys" · params: { segment_name, environment_id, replace? } · body: { keys, comment?, title? } | Discover the key-add action and replacement argument through CLI help |
| Remove keys | harness_execute · fme_segment_definition · action="remove_keys" · params: { segment_name, environment_id } · body: { keys, comment?, title? } | Discover the key-remove action through CLI help |
Instructions
Load references on demand:
- concepts.md — segments section explains STANDARD vs LARGE vs RULE_BASED and how flags reference segments
- write-safety.md — confirm-before-write protocol (production gates, verify before/after)
Phase 1: Establish scope
Follow scope-establishment.md. Ask for the org and project if missing. Restate: Working in org=..., project=...