@thinkingai/ae-cli 6.0.31 → 6.0.33

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

@@ -3,6 +3,7 @@
 Use when the user needs to get metric definition, events, and params.
 
 Do not use it to query metric values or trends; it returns the saved metric definition only.
+Do not call it just to expand a saved metric before normal ad-hoc analysis. If the user asks to query a saved metric, pass the metric display/name/remark directly in `analysis adhoc run --definition`; the backend compiler resolves saved metrics internally.
 
 Command:
 
@@ -22,3 +23,8 @@ Output `data.metric` contains the saved metric definition, or no metric when the
 |---|---|---|
 | `--project-id` | Yes | Numeric project ID. |
 | `--metric-id` | Yes | Metric ID. |
+
+## Recommended Chaining
+
+- analysis-meta metric get -> analysis-meta metric update
+- For ad-hoc saved metric query: analysis adhoc run/export

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

@@ -1,24 +1,37 @@
 # analysis-meta metric list
 
-Use when the user needs to list project metrics.
+Use when the user needs to list, search, page, or field-project project metrics.
 
 Do not use it to calculate metric values; use report/dashboard/ad-hoc data routing for result queries.
 
 Command:
 
 ```bash
+ae-cli analysis-meta metric list --project-id <project_id>
 ae-cli analysis-meta metric list --project-id <project_id> --ignore-authentication true
+ae-cli analysis-meta metric list --project-id <project_id> --query pay
+ae-cli analysis-meta metric list --project-id <project_id> --query pay --fields '["metric_name","authentication_status"]' --limit 10 --offset 0 --authenticated-only true
 ae-cli analysis-meta metric list --dry-run
 ```
 
 Capability id: `metadata.metric.list`.
 
-Input sends `project_id`, `ignore_authentication`.
+Input sends `project_id`, `ignore_authentication`, `query`, `fields`, `limit`, `offset`, and `authenticated_only`.
 
-Output `data.metrics[]` contains project metric summaries and authentication decoration unless explicitly skipped.
+Output `data.metrics[]` contains project metric summaries. When `limit` or `offset` is present, output also includes `total`, `limit`, `offset`, and `has_more`.
 
 ## Parameters
 | Parameter | Required | Description |
 |---|---|---|
 | `--project-id` | Yes | Numeric project ID. |
 | `--ignore-authentication` | No | Whether to skip asset authentication status decoration. |
+| `--query` | No | Optional keyword filter. Fuzzy match on `metric_name`, `metric_desc`, and `metric_remark`. |
+| `--fields` | No | Optional result field projection JSON array. Supported fields: `metric_id`, `metric_name`, `metric_desc`, `metric_remark`, `metric_mode`, `authentication_status`, `open_id`, `creator`, `creator_login_name`, `update_open_id`, `update_creator`, `update_login_name`, `create_time`, `update_time`. |
+| `--limit` | No | Optional page size. Default: 20 when pagination is used, maximum: 50. |
+| `--offset` | No | Optional zero-based result offset. Default: 0. |
+| `--authenticated-only` | No | When true, return only authenticated metrics. |
+
+## Decision Rules
+- Do not call this just to prepare normal ad-hoc analysis. Pass saved metric wording directly in `analysis adhoc run/export --definition`; the backend compiler resolves saved metric names internally.
+- Use `--fields` to keep discovery responses compact.
+- Use `analysis-meta metric get` after this command when a full metric definition is needed.

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

@@ -2,12 +2,16 @@
 
 Use when the user needs to update metric definition, name, and remark.
 
-Do not use it to query metric values. Use `analysis_meta +update_metric` only when the gateway capability is unavailable.
+Do not use it to query metric values.
+
+Before updating `--metric-events` / `--metric-params`, validate the event and property names with `analysis-meta event list` and `analysis-meta property list` in the same `project_id`.
 
 Command:
 
 ```bash
 ae-cli analysis-meta metric update --project-id <project_id> --metric-id <metric_id> --metric-desc 'New display name' --metric-remark 'New remark'
+ae-cli analysis-meta metric update --project-id <project_id> --metric-id <metric_id> --metric-name demo --metric-desc demo --model-type event --metric-events '[]'
+ae-cli analysis-meta metric update --project-id <project_id> --metric-id <metric_id> --metric-name demo --metric-desc demo --metric-remark demo --model-type retention --metric-events '[]' --metric-params '{}'
 ae-cli analysis-meta metric update --project-id <project_id> --metric-id <metric_id> --metric-desc 'New display name' --dry-run
 ```
 
@@ -26,5 +30,12 @@ Output `data.metric` contains the updated summary for a full-definition update c
 | `--metric-desc` | No | Metric display name. |
 | `--metric-remark` | No | Metric remark. |
 | `--metric-mode` | No | Metric model mode for a full-definition update. |
+| `--model-type` | No | Semantic metric model type: `event` or `retention`. Prefer this over `--metric-mode`. |
 | `--metric-events` | No | Metric event-analysis QP JSON array for a full-definition update. |
 | `--metric-params` | No | Metric params JSON object. |
+
+## Decision Rules
+- For full-definition updates, pass `--metric-name`, `--metric-desc`, one of `--model-type` / `--metric-mode`, and `--metric-events` together.
+- If both `--model-type` and `--metric-mode` are present, they must match: `event -> 0`, `retention -> 1`.
+- Use `analysis-meta metric get` before updating if the current definition needs to be preserved and edited.
+- This is an ordinary write operation; execute it without the high-risk confirmation flag.

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

@@ -0,0 +1,27 @@
+# tracking plan-change-log export
+
+Use when export one tracking plan change log.
+
+Do not use for commands listed under the sheet's non-CLI section or for unrelated metadata/report operations. If the command needs a complex JSON object, read the backend schema or existing asset first and send snake_case fields only.
+
+Command:
+
+```bash
+ae-cli tracking plan-change-log export [options]
+```
+
+Capability id: `tracking.plan_change_log.export`
+
+Input sends `project_id`, `log_id`, optional `request_id`, and optional `timeout_seconds`. Do not send camelCase aliases.
+
+Output is the capability gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Export commands return lifecycle data such as `run_id` and `artifact_id` for inspect/download.
+
+Parameters:
+
+| Parameter | Description | Required |
+| --- | --- | --- |
+| `--project-id` | See command help | Yes |
+| `--log-id` | See command help | Yes |
+| `--request-id` | See command help | No |
+| `--async-timeout-seconds` | See command help | No |
+

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

@@ -0,0 +1,24 @@
+# tracking plan-change-log list
+
+Use when list tracking plan change logs.
+
+Do not use for commands listed under the sheet's non-CLI section or for unrelated metadata/report operations. If the command needs a complex JSON object, read the backend schema or existing asset first and send snake_case fields only.
+
+Command:
+
+```bash
+ae-cli tracking plan-change-log list [options]
+```
+
+Capability id: `tracking.plan_change_log.list`
+
+Input sends `project_id`. Do not send camelCase aliases.
+
+Output is the capability gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Export commands return lifecycle data such as `run_id` and `artifact_id` for inspect/download.
+
+Parameters:
+
+| Parameter | Description | Required |
+| --- | --- | --- |
+| `--project-id` | See command help | Yes |
+

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

@@ -0,0 +1,30 @@
+# tracking plan delete-items
+
+Use when delete tracking plan items.
+
+Do not use for commands listed under the sheet's non-CLI section or for unrelated metadata/report operations. If the command needs a complex JSON object, read the backend schema or existing asset first and send snake_case fields only.
+
+Command:
+
+```bash
+ae-cli tracking plan delete-items --project-id <project_id> [--events '<json_array>'] [--event-prop-names '<json_array>'] [--user-prop-names '<json_array>'] [--common-event-prop-names '<json_array>'] --confirm true --dry-run
+# Summarize the target and impact, then wait for explicit user confirmation.
+ae-cli tracking plan delete-items --project-id <project_id> [--events '<json_array>'] [--event-prop-names '<json_array>'] [--user-prop-names '<json_array>'] [--common-event-prop-names '<json_array>'] --confirm true --yes
+```
+
+Capability id: `tracking.plan.delete_items`
+
+Input sends `project_id`, the provided name arrays, and `yes` mapped from `--confirm`. At least one name array must be non-empty. Do not send camelCase aliases.
+
+Output is the capability gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Export commands return lifecycle data such as `run_id` and `artifact_id` for inspect/download.
+
+Parameters:
+
+| Parameter | Description | Required |
+| --- | --- | --- |
+| `--project-id` | Numeric project ID. | Yes |
+| `--events` | Event names to delete. | No |
+| `--event-prop-names` | Event property names to delete. | No |
+| `--user-prop-names` | User property names to delete. | No |
+| `--common-event-prop-names` | Common event property names to delete. | No |
+| `--confirm` | Must be `true`; execution also follows the global high-risk confirmation gate. | Yes |

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

@@ -0,0 +1,26 @@
+# tracking plan export
+
+Use when export the tracking plan as an artifact.
+
+Do not use for commands listed under the sheet's non-CLI section or for unrelated metadata/report operations. If the command needs a complex JSON object, read the backend schema or existing asset first and send snake_case fields only.
+
+Command:
+
+```bash
+ae-cli tracking plan export [options]
+```
+
+Capability id: `tracking.plan.export`
+
+Input sends `project_id`. Do not send camelCase aliases.
+
+Output is the capability gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Export commands return lifecycle data such as `run_id` and `artifact_id` for inspect/download.
+
+Parameters:
+
+| Parameter | Description | Required |
+| --- | --- | --- |
+| `--project-id` | See command help | Yes |
+| `--request-id` | See command help | No |
+| `--async-timeout-seconds` | See command help | No |
+

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

@@ -0,0 +1,27 @@
+# tracking plan generate
+
+Use when submit an AI tracking plan generation task.
+
+Do not use for commands listed under the sheet's non-CLI section or for unrelated metadata/report operations. If the command needs a complex JSON object, read the backend schema or existing asset first and send snake_case fields only.
+
+Command:
+
+```bash
+ae-cli tracking plan generate --project-id <project_id> --language <zh-CN|en-US|ja-JP|ko-KR> --form-data '<json_object>' [--development-carrier '<json_array>'] [--predefined-event '<json_array>']
+```
+
+Capability id: `tracking.plan.generate`
+
+Input sends `project_id`, `language`, `form_data`, optional `development_carrier`, and optional `predefined_event`. The backend resolves `company_id` from the authorized project. `form_data` is the intentionally open business-context object; all surrounding fields are explicit. Do not send camelCase aliases.
+
+Output is the capability gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Export commands return lifecycle data such as `run_id` and `artifact_id` for inspect/download.
+
+Parameters:
+
+| Parameter | Description | Required |
+| --- | --- | --- |
+| `--project-id` | Numeric project ID. | Yes |
+| `--language` | Generation language: `zh-CN`, `en-US`, `ja-JP`, or `ko-KR`. | Yes |
+| `--form-data` | Structured business context, for example account system, revenue model, core gameplay, currency system, and main entries. | Yes |
+| `--development-carrier` | Development platforms such as Android, iOS, or Unity. | No |
+| `--predefined-event` | Predefined event names such as install, start, or close. | No |

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

@@ -0,0 +1,24 @@
+# tracking plan get
+
+Use when get the tracking plan for one project.
+
+Do not use for commands listed under the sheet's non-CLI section or for unrelated metadata/report operations. If the command needs a complex JSON object, read the backend schema or existing asset first and send snake_case fields only.
+
+Command:
+
+```bash
+ae-cli tracking plan get [options]
+```
+
+Capability id: `tracking.plan.get`
+
+Input sends `project_id`. Do not send camelCase aliases.
+
+Output is the capability gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Export commands return lifecycle data such as `run_id` and `artifact_id` for inspect/download.
+
+Parameters:
+
+| Parameter | Description | Required |
+| --- | --- | --- |
+| `--project-id` | See command help | Yes |
+

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

@@ -0,0 +1,26 @@
+# tracking plan import-excel
+
+Use when import a tracking plan Excel file that was uploaded as an input file.
+
+Do not use for commands listed under the sheet's non-CLI section or for unrelated metadata/report operations. If the command needs a complex JSON object, read the backend schema or existing asset first and send snake_case fields only.
+
+Command:
+
+```bash
+ae-cli tracking plan import-excel [options]
+```
+
+Capability id: `tracking.plan.import_excel`
+
+Input sends `project_id`, `input_file_id`, and optional `lang`. Do not send camelCase aliases.
+
+Output is the capability gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Export commands return lifecycle data such as `run_id` and `artifact_id` for inspect/download.
+
+Parameters:
+
+| Parameter | Description | Required |
+| --- | --- | --- |
+| `--project-id` | See command help | Yes |
+| `--input-file-id` | See command help | Yes |
+| `--lang` | See command help | No |
+

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

@@ -0,0 +1,27 @@
+# tracking plan save-items
+
+Use when save tracking plan items.
+
+Do not use for commands listed under the sheet's non-CLI section or for unrelated metadata/report operations. If the command needs a complex JSON object, read the backend schema or existing asset first and send snake_case fields only.
+
+Command:
+
+```bash
+ae-cli tracking plan save-items --project-id <project_id> [--events '<json_array>'] [--event-props '<json_array>'] [--user-props '<json_array>'] [--common-event-props '<json_array>']
+```
+
+Capability id: `tracking.plan.save_items`
+
+Input sends `project_id` and the provided `events`, `event_props`, `user_props`, and `common_event_props` arrays. At least one item array must be non-empty. Event/property objects use the existing tracking-plan snake_case contract; do not send camelCase aliases.
+
+Output is the capability gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Export commands return lifecycle data such as `run_id` and `artifact_id` for inspect/download.
+
+Parameters:
+
+| Parameter | Description | Required |
+| --- | --- | --- |
+| `--project-id` | Numeric project ID. | Yes |
+| `--events` | Event objects with fields such as `event_name`, `display_name`, `event_desc`, `event_tag`, `data_origin`, and `props`. | No |
+| `--event-props` | Event property objects with fields such as `name`, `display_name`, `type`, and `desc`. | No |
+| `--user-props` | User property objects with fields such as `name`, `display_name`, `type`, `update_type`, `prop_tag`, and `desc`. | No |
+| `--common-event-props` | Common event property objects. | No |

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

@@ -0,0 +1,24 @@
+# tracking plan sync-from-meta
+
+Use when synchronize tracking plan from project metadata.
+
+Do not use for commands listed under the sheet's non-CLI section or for unrelated metadata/report operations. If the command needs a complex JSON object, read the backend schema or existing asset first and send snake_case fields only.
+
+Command:
+
+```bash
+ae-cli tracking plan sync-from-meta [options]
+```
+
+Capability id: `tracking.plan.sync_from_meta`
+
+Input sends `project_id`. Do not send camelCase aliases.
+
+Output is the capability gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Export commands return lifecycle data such as `run_id` and `artifact_id` for inspect/download.
+
+Parameters:
+
+| Parameter | Description | Required |
+| --- | --- | --- |
+| `--project-id` | See command help | Yes |
+

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