@thinkingai/ae-cli 6.0.30 → 6.0.32

package/skills/ae-analysis/references/project_access_detail_get.md

@@ -0,0 +1,23 @@
+# analysis project access-detail get
+
+Use when the user needs to get company project access details.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project access-detail get --company-id <company_id>
+ae-cli analysis project access-detail get --dry-run --company-id <company_id>
+```
+
+Capability id: `project.access_detail.get`.
+
+Input sends `company_id`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--company-id` | Yes | Company ID. |

package/skills/ae-analysis/references/project_data_power_delete.md

@@ -0,0 +1,26 @@
+# analysis project data-power delete
+
+Use when the user needs to delete a data power and optionally migrate users to another data power.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project data-power delete --project-id <project_id> --data-power-id <data_power_id> --new-data-power-id <new_data_power_id>
+ae-cli analysis project data-power delete --dry-run --project-id <project_id> --data-power-id <data_power_id>
+```
+
+Capability id: `project.data_power.delete`.
+
+Input sends `project_id`, `data_power_id`, `new_data_power_id`, `yes`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+For execution, dry-run first, summarize the impact, then rerun the unchanged command with global `--yes` only after explicit user confirmation. The CLI sends `yes=true` after its own high-risk gate.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--data-power-id` | Yes | Data power ID to delete. |
+| `--new-data-power-id` | No | Optional replacement data power ID for affected users. |

package/skills/ae-analysis/references/project_data_power_get.md

@@ -0,0 +1,24 @@
+# analysis project data-power get
+
+Use when the user needs to get one data power detail.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project data-power get --project-id <project_id> --data-power-id <data_power_id>
+ae-cli analysis project data-power get --dry-run --project-id <project_id> --data-power-id <data_power_id>
+```
+
+Capability id: `project.data_power.get`.
+
+Input sends `project_id`, `data_power_id`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--data-power-id` | Yes | Data power ID. |

package/skills/ae-analysis/references/project_data_power_list.md

@@ -0,0 +1,23 @@
+# analysis project data-power list
+
+Use when the user needs to list project data powers.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project data-power list --project-id <project_id>
+ae-cli analysis project data-power list --dry-run --project-id <project_id>
+```
+
+Capability id: `project.data_power.list`.
+
+Input sends `project_id`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |

package/skills/ae-analysis/references/project_data_power_upsert.md

@@ -0,0 +1,24 @@
+# analysis project data-power upsert
+
+Use when the user needs to create or update a data power.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project data-power upsert --project-id <project_id> --payload <payload>
+ae-cli analysis project data-power upsert --dry-run --project-id <project_id> --payload <payload>
+```
+
+Capability id: `project.data_power.upsert`.
+
+Input sends `project_id`, `payload`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--payload` | Yes | Data power save payload matching DataPowerSaveRequestDTO in snake_case. |

package/skills/ae-analysis/references/project_entity_create.md

@@ -0,0 +1,27 @@
+# analysis project entity create
+
+Use when the user needs to create an analysis entity.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project entity create --project-id <project_id> --entity-name <entity_name> --column-name <column_name> --table-type <table_type> --order <order>
+ae-cli analysis project entity create --dry-run --project-id <project_id> --entity-name <entity_name> --column-name <column_name> --table-type <table_type>
+```
+
+Capability id: `project.entity.create`.
+
+Input sends `project_id`, `entity_name`, `column_name`, `table_type`, `order`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--entity-name` | Yes | Entity display name. |
+| `--column-name` | Yes | Property column name to bind. |
+| `--table-type` | Yes | Main table type: 0 for event property, 1 for user property. |
+| `--order` | No | Optional entity display order. |

package/skills/ae-analysis/references/project_entity_delete.md

@@ -0,0 +1,25 @@
+# analysis project entity delete
+
+Use when the user needs to delete an analysis entity.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project entity delete --project-id <project_id> --entity-id <entity_id>
+ae-cli analysis project entity delete --dry-run --project-id <project_id> --entity-id <entity_id>
+```
+
+Capability id: `project.entity.delete`.
+
+Input sends `project_id`, `entity_id`, `yes`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+For execution, dry-run first, summarize the impact, then rerun the unchanged command with global `--yes` only after explicit user confirmation. The CLI sends `yes=true` after its own high-risk gate.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--entity-id` | Yes | Analysis entity ID. |

package/skills/ae-analysis/references/project_entity_event_list.md

@@ -0,0 +1,24 @@
+# analysis project entity-event list
+
+Use when the user needs to list entity mappings for events.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project entity-event list --project-id <project_id> --event-names <event_names>
+ae-cli analysis project entity-event list --dry-run --project-id <project_id>
+```
+
+Capability id: `project.entity_event.list`.
+
+Input sends `project_id`, `event_names`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--event-names` | No | Optional event names JSON array to resolve entity mappings for. |

package/skills/ae-analysis/references/project_entity_get.md

@@ -0,0 +1,24 @@
+# analysis project entity get
+
+Use when the user needs to get one analysis entity.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project entity get --project-id <project_id> --entity-id <entity_id>
+ae-cli analysis project entity get --dry-run --project-id <project_id> --entity-id <entity_id>
+```
+
+Capability id: `project.entity.get`.
+
+Input sends `project_id`, `entity_id`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--entity-id` | Yes | Analysis entity ID. |

package/skills/ae-analysis/references/project_entity_list.md

@@ -0,0 +1,28 @@
+# analysis project entity list
+
+Use when the user needs to list analysis entities in a project.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project entity list --project-id <project_id> --query <query> --fields <fields> --limit <limit> --offset <offset> --event-name <event_name>
+ae-cli analysis project entity list --dry-run --project-id <project_id>
+```
+
+Capability id: `project.entity.list`.
+
+Input sends `project_id`, `query`, `fields`, `limit`, `offset`, `event_name`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--query` | No | Optional keyword filter. |
+| `--fields` | No | Optional snake_case fields to return. |
+| `--limit` | No | Optional page size. Default: 50, maximum: 200. |
+| `--offset` | No | Optional page offset. Default: 0. |
+| `--event-name` | No | Optional event name. When present, return entities related to the event. |

package/skills/ae-analysis/references/project_entity_update.md

@@ -0,0 +1,28 @@
+# analysis project entity update
+
+Use when the user needs to update an analysis entity.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project entity update --project-id <project_id> --entity-id <entity_id> --entity-name <entity_name> --column-name <column_name> --table-type <table_type> --order <order>
+ae-cli analysis project entity update --dry-run --project-id <project_id> --entity-id <entity_id> --entity-name <entity_name> --column-name <column_name> --table-type <table_type>
+```
+
+Capability id: `project.entity.update`.
+
+Input sends `project_id`, `entity_id`, `entity_name`, `column_name`, `table_type`, `order`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--entity-id` | Yes | Analysis entity ID. |
+| `--entity-name` | Yes | Entity display name. |
+| `--column-name` | Yes | Property column name to bind. |
+| `--table-type` | Yes | Main table type: 0 for event property, 1 for user property. |
+| `--order` | No | Optional entity display order. |

package/skills/ae-analysis/references/project_function_list.md

@@ -0,0 +1,24 @@
+# analysis project function list
+
+Use when the user needs to list all project-level functions.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project function list --company-id <company_id> --project-id <project_id>
+ae-cli analysis project function list --dry-run 
+```
+
+Capability id: `project.function.list`.
+
+Input sends `company_id`, `project_id`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--company-id` | No | Company ID. |
+| `--project-id` | No | Project ID. |

package/skills/ae-analysis/references/project_info_get.md

@@ -0,0 +1,23 @@
+# analysis project info get
+
+Use when the user needs to get project configuration details.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project info get --project-id <project_id>
+ae-cli analysis project info get --dry-run --project-id <project_id>
+```
+
+Capability id: `project.info.get`.
+
+Input sends `project_id`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |

package/skills/ae-analysis/references/project_info_list.md

@@ -0,0 +1,26 @@
+# analysis project info list
+
+Use when the user needs to list projects accessible to the current user.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project info list --query <query> --fields <fields> --limit <limit> --offset <offset>
+ae-cli analysis project info list --dry-run 
+```
+
+Capability id: `project.info.list`.
+
+Input sends `query`, `fields`, `limit`, `offset`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--query` | No | Optional keyword filter. |
+| `--fields` | No | Optional snake_case fields to return. |
+| `--limit` | No | Optional page size. Default: 50, maximum: 200. |
+| `--offset` | No | Optional page offset. Default: 0. |

package/skills/ae-analysis/references/project_info_update.md

@@ -0,0 +1,25 @@
+# analysis project info update
+
+Use when the user needs to update project name and remark.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project info update --project-id <project_id> --project-name <project_name> --project-remark <project_remark>
+ae-cli analysis project info update --dry-run --project-id <project_id> --project-name <project_name>
+```
+
+Capability id: `project.info.update`.
+
+Input sends `project_id`, `project_name`, `project_remark`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--project-name` | Yes | New project name. |
+| `--project-remark` | No | Optional project remark. |

package/skills/ae-analysis/references/project_mark_time_create.md

@@ -0,0 +1,27 @@
+# analysis project mark-time create
+
+Use when the user needs to create a project date marker.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project mark-time create --project-id <project_id> --marked-at <marked_at> --zone-offset <zone_offset> --content <content> --is-visible <is_visible>
+ae-cli analysis project mark-time create --dry-run --project-id <project_id> --marked-at <marked_at> --content <content>
+```
+
+Capability id: `project.mark_time.create`.
+
+Input sends `project_id`, `marked_at`, `zone_offset`, `content`, `is_visible`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--marked-at` | Yes | Marker timestamp, for example yyyy-MM-dd HH:mm. |
+| `--zone-offset` | No | Marker time zone offset. |
+| `--content` | Yes | Marker content. |
+| `--is-visible` | No | Whether the marker is visible. 1 visible, 0 hidden. |

package/skills/ae-analysis/references/project_mark_time_delete.md

@@ -0,0 +1,25 @@
+# analysis project mark-time delete
+
+Use when the user needs to delete project date markers.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project mark-time delete --project-id <project_id> --mark-time-ids <mark_time_ids>
+ae-cli analysis project mark-time delete --dry-run --project-id <project_id> --mark-time-ids <mark_time_ids>
+```
+
+Capability id: `project.mark_time.delete`.
+
+Input sends `project_id`, `mark_time_ids`, `yes`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+For execution, dry-run first, summarize the impact, then rerun the unchanged command with global `--yes` only after explicit user confirmation. The CLI sends `yes=true` after its own high-risk gate.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--mark-time-ids` | Yes | Date marker IDs JSON array to delete. |

package/skills/ae-analysis/references/project_mark_time_list.md

@@ -0,0 +1,28 @@
+# analysis project mark-time list
+
+Use when the user needs to list project date markers.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project mark-time list --project-id <project_id> --query <query> --fields <fields> --limit <limit> --offset <offset> --zone-offset <zone_offset>
+ae-cli analysis project mark-time list --dry-run --project-id <project_id>
+```
+
+Capability id: `project.mark_time.list`.
+
+Input sends `project_id`, `query`, `fields`, `limit`, `offset`, `zone_offset`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--query` | No | Optional keyword filter. |
+| `--fields` | No | Optional snake_case fields to return. |
+| `--limit` | No | Optional page size. Default: 50, maximum: 200. |
+| `--offset` | No | Optional page offset. Default: 0. |
+| `--zone-offset` | No | Dashboard locked time zone offset. |

package/skills/ae-analysis/references/project_mark_time_update.md

@@ -0,0 +1,28 @@
+# analysis project mark-time update
+
+Use when the user needs to update a project date marker.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project mark-time update --project-id <project_id> --mark-time-id <mark_time_id> --marked-at <marked_at> --zone-offset <zone_offset> --content <content> --is-visible <is_visible>
+ae-cli analysis project mark-time update --dry-run --project-id <project_id> --mark-time-id <mark_time_id> --marked-at <marked_at> --content <content>
+```
+
+Capability id: `project.mark_time.update`.
+
+Input sends `project_id`, `mark_time_id`, `marked_at`, `zone_offset`, `content`, `is_visible`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--mark-time-id` | Yes | Date marker ID. |
+| `--marked-at` | Yes | Marker timestamp, for example yyyy-MM-dd HH:mm. |
+| `--zone-offset` | No | Marker time zone offset. |
+| `--content` | Yes | Marker content. |
+| `--is-visible` | No | Whether the marker is visible. 1 visible, 0 hidden. |

package/skills/ae-analysis/references/project_member_add.md

@@ -0,0 +1,25 @@
+# analysis project member add
+
+Use when the user needs to add project members.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project member add --project-id <project_id> --payload <payload> --type <type>
+ae-cli analysis project member add --dry-run --project-id <project_id> --payload <payload> --type <type>
+```
+
+Capability id: `project.member.add`.
+
+Input sends `project_id`, `payload`, `type`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--payload` | Yes | Member add payload. Must include user_roles array matching UserRolePo in snake_case. |
+| `--type` | Yes | Add type accepted by ProjMemberAddTypeEnum. |

package/skills/ae-analysis/references/project_member_batch_update.md

@@ -0,0 +1,24 @@
+# analysis project member batch-update
+
+Use when the user needs to batch update project members.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project member batch-update --project-id <project_id> --payload <payload>
+ae-cli analysis project member batch-update --dry-run --project-id <project_id> --payload <payload>
+```
+
+Capability id: `project.member.batch_update`.
+
+Input sends `project_id`, `payload`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--payload` | Yes | Batch member edit payload matching EditBatchMembersReq in snake_case. |

package/skills/ae-analysis/references/project_member_candidate_list.md

@@ -0,0 +1,25 @@
+# analysis project member-candidate list
+
+Use when the user needs to list candidate users and role/data-power options for adding project members.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project member-candidate list --project-id <project_id> --type <type> --login-names <login_names>
+ae-cli analysis project member-candidate list --dry-run --project-id <project_id> --type <type>
+```
+
+Capability id: `project.member_candidate.list`.
+
+Input sends `project_id`, `type`, `login_names`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--type` | Yes | Add type accepted by ProjMemberAddTypeEnum. |
+| `--login-names` | No | Comma-separated login names when checking new users. |

package/skills/ae-analysis/references/project_member_handover_export.md

@@ -0,0 +1,27 @@
+# analysis project member-handover export
+
+Use when the user needs to run batch project member asset handover and export the generated detail file as a CLI artifact.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project member-handover export --project-id <project_id> --payload <payload> --request-id <request_id>
+ae-cli analysis project member-handover export --dry-run --project-id <project_id> --payload <payload>
+```
+
+Capability id: `project.member_handover.export`.
+
+Input sends `project_id`, `payload`, `request_id`, `yes`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+For execution, dry-run first, summarize the impact, then rerun the unchanged command with global `--yes` only after explicit user confirmation. The CLI sends `yes=true` after its own high-risk gate.
+This is an artifact capability. Preserve the returned `run_id` and `artifact_id`; download only through `analysis artifact download` using the same response metadata.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--payload` | Yes | Batch asset handover payload matching AssetBatchHandoverReq in snake_case. single_submit must be false or omitted. |
+| `--request-id` | No | Optional caller-supplied cli_<32 lowercase hex> lifecycle ID. |

package/skills/ae-analysis/references/project_member_handover_run.md

@@ -0,0 +1,24 @@
+# analysis project member-handover run
+
+Use when the user needs to run project member asset handover.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project member-handover run --project-id <project_id> --payload <payload>
+ae-cli analysis project member-handover run --dry-run --project-id <project_id> --payload <payload>
+```
+
+Capability id: `project.member_handover.run`.
+
+Input sends `project_id`, `payload`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--payload` | Yes | Asset handover payload matching AssetBatchHandoverReq in snake_case. |