@thinkingai/ae-cli 6.1.4 → 6.1.5

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

@@ -0,0 +1,27 @@
+# tracking ingest-error list
+
+Use when list tracking ingest errors for one data name.
+
+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 ingest-error list [options]
+```
+
+Capability id: `tracking.ingest_error.list`
+
+Input sends `project_id`, `data_name`, `start_time`, and `end_time`. 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 |
+| `--data-name` | See command help | Yes |
+| `--start-time` | See command help | No |
+| `--end-time` | See command help | No |
+

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

@@ -0,0 +1,26 @@
+# tracking ingest summary
+
+Use when get tracking ingest summary.
+
+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 ingest summary [options]
+```
+
+Capability id: `tracking.ingest.summary`
+
+Input sends `project_id`, `start_time`, and `end_time`. 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 |
+| `--start-time` | See command help | No |
+| `--end-time` | See command help | No |
+

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

@@ -0,0 +1,27 @@
+# tracking live-data export
+
+Use when export recent tracking live data.
+
+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 live-data export [options]
+```
+
+Capability id: `tracking.live_data.export`
+
+Input sends `project_id`, optional `data_type`, 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 |
+| `--data-type` | See command help | No |
+| `--request-id` | See command help | No |
+| `--async-timeout-seconds` | See command help | No |
+

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

@@ -0,0 +1,27 @@
+# tracking live-data list
+
+Use when list recent tracking live data.
+
+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 live-data list [options]
+```
+
+Capability id: `tracking.live_data.list`
+
+Input sends `project_id`, optional `data_type`, 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 |
+| `--data-type` | See command help | No |
+| `--request-id` | See command help | No |
+| `--timeout-seconds` | See command help | No |
+

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

@@ -7,13 +7,13 @@ Do not use it for unrelated project-management actions or for fields not present
 Command:
 
 ```bash
-ae-cli analysis project role delete --role-name <role_name> --new-role-name <new_role_name>
-ae-cli analysis project role delete --dry-run --role-name <role_name>
+ae-cli analysis project role delete --project-id <project_id> --role-name <role_name> --new-role-name <new_role_name>
+ae-cli analysis project role delete --dry-run --project-id <project_id> --role-name <role_name>
 ```
 
 Capability id: `project.role.delete`.
 
-Input sends `role_name`, `new_role_name`, `yes`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+Input sends `project_id`, `role_name`, `new_role_name`, `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.
@@ -21,5 +21,6 @@ Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok
 ## Parameters
 | Parameter | Required | Description |
 |---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
 | `--role-name` | Yes | Role name to delete. |
 | `--new-role-name` | No | Role name to migrate users to before deletion. |

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

@@ -7,17 +7,18 @@ Do not use it for unrelated project-management actions or for fields not present
 Command:
 
 ```bash
-ae-cli analysis project role get --role-name <role_name>
-ae-cli analysis project role get --dry-run --role-name <role_name>
+ae-cli analysis project role get --project-id <project_id> --role-name <role_name>
+ae-cli analysis project role get --dry-run --project-id <project_id> --role-name <role_name>
 ```
 
 Capability id: `project.role.get`.
 
-Input sends `role_name`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+Input sends `project_id`, `role_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. |
 | `--role-name` | Yes | Role name. |

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

@@ -7,17 +7,18 @@ Do not use it for unrelated project-management actions or for fields not present
 Command:
 
 ```bash
-ae-cli analysis project role-user list --role-name <role_name>
-ae-cli analysis project role-user list --dry-run --role-name <role_name>
+ae-cli analysis project role-user list --project-id <project_id> --role-name <role_name>
+ae-cli analysis project role-user list --dry-run --project-id <project_id> --role-name <role_name>
 ```
 
 Capability id: `project.role_user.list`.
 
-Input sends `role_name`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+Input sends `project_id`, `role_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. |
 | `--role-name` | Yes | Role name. |

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

@@ -22,7 +22,8 @@ ae-cli analysis query create-result-cluster \
 - `--query-context-id`, `--source`, and all coordinate fragments must come from the same synchronous `adhoc run`, `report-data run`, or `dashboard-report-data run` response.
 - Match the desired visible row and column in `source.drilldown.row_options`/`column_options`, select the correct metric option, and shallow-merge only their `coordinate` fragments.
 - Never pass `target_id`, raw QP, display-only dates, option presentation fields, or data from an export/download. Exports do not create query contexts.
-- `--cluster-name` must be unique in the project and contain the backend-supported identifier characters.
+- `--cluster-name` must be unique in the project, start with a lowercase letter, contain only lowercase letters, digits, and underscores, and be at most 24 characters. This legacy result-cluster path is stricter than ordinary cluster creation.
+- `--display-name`, when provided, must be at most 80 characters.
 
 The saved cluster subject is `source.drilldown.subject` or the selected event metric's `subject`. `USER_LIST` creates a user result cluster. `ENTITY_LIST` creates a result cluster for that custom entity; do not relabel it as a user cluster.
 

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

@@ -18,7 +18,9 @@ ae-cli analysis report-data export --project-id <project_id> --report-ids '[1001
 ae-cli analysis report-data export --project-id <project_id> --report-ids '[2001]' --sql-params '[{"name":"platform","value":"ios"}]' --artifact-format jsonl
 ```
 
-Input sends `project_id`, `report_ids`, optional `request_id`, `filters`, `group_by`, `sql_params`, `start_time`, `end_time`, `time_granularity`, `use_cache`, artifact `format`, and `timeout_seconds`. Async export has no inline row limit. Runtime defaults to and is capped at 21600 seconds (6 hours); cancel earlier with `analysis query cancel --run-id <run_id>`. The routing rule lives in [`analysis_data_retrieval.md`](analysis_data_retrieval.md).
+Input sends `project_id`, `report_ids`, optional `request_id`, `filters`, `group_by`, `sql_params`, `start_time`, `end_time`, `time_granularity`, `zone_offset`, `use_cache`, artifact `format`, and `timeout_seconds`. Async export has no inline row limit. Runtime defaults to and is capped at 21600 seconds (6 hours); cancel earlier with `analysis query cancel --run-id <run_id>`. The routing rule lives in [`analysis_data_retrieval.md`](analysis_data_retrieval.md).
+
+Timezone contract is identical to `report-data run`: omit `--zone-offset` to match the current user's report UI timezone (falling back to the project default); use an enabled integer from `-12` through `14` for a fixed UTC offset; use `--zone-offset 99` for local-time mode, where rows are not converted to one fixed UTC offset. `99` is a mode identifier, not `UTC+99`, and the option is not persisted.
 
 Override model:
 

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

@@ -24,9 +24,19 @@ ae-cli analysis report-data run --project-id <project_id> --report-ids '[1001]'
 
 # SQL report, after analysis report get confirms definition.params contains platform
 ae-cli analysis report-data run --project-id <project_id> --report-ids '[2001]' --sql-params '[{"name":"platform","value":"ios"}]' --limit 20
+
+# Explicit local-time mode (not UTC+99)
+ae-cli analysis report-data run --project-id <project_id> --report-ids '[1001]' --zone-offset 99 --limit 20
 ```
 
-Input sends `project_id`, `report_ids`, optional `request_id`, `filters`, `group_by`, `sql_params`, `start_time`, `end_time`, `time_granularity`, `use_cache`, `limit`, and `timeout_seconds`. Control defaults: `--limit` default 100 / max 1000, `--timeout-seconds` default 120 / max 180. The routing rule lives in [`analysis_data_retrieval.md`](analysis_data_retrieval.md).
+Input sends `project_id`, `report_ids`, optional `request_id`, `filters`, `group_by`, `sql_params`, `start_time`, `end_time`, `time_granularity`, `zone_offset`, `use_cache`, `limit`, and `timeout_seconds`. Control defaults: `--limit` default 100 / max 1000, `--timeout-seconds` default 120 / max 180. The routing rule lives in [`analysis_data_retrieval.md`](analysis_data_retrieval.md).
+
+Timezone contract:
+
+- Omit `--zone-offset` to match the report UI for the current user. The backend uses that user's selected timezone when it is available for the project, otherwise the project default.
+- Pass an integer from `-12` through `14` for a fixed UTC offset that is enabled in the project.
+- Pass `--zone-offset 99` for local-time mode: event timestamps retain their reported local time instead of being converted to one fixed UTC offset. `99` is a mode identifier, not `UTC+99`.
+- The option changes only this execution. It does not update the saved report or the user's UI preference.
 
 Override model:
 
@@ -38,7 +48,7 @@ A homogeneous SQL request that includes `filters`, `group_by`, `start_time`, `en
 
 For a newly created or updated dynamic SQL report, omit `--sql-params` to execute the saved default first. After that succeeds, then make one second call with `--sql-params` to change only the requested value. This separates a broken saved default from a broken override and avoids repeating the same query.
 
-Output is the gateway envelope. `data` contains bounded inline report result items plus `query_context_id` and `sources[].drilldown` when the returned preview exposes follow-up actions. Each source is evaluated independently; SQL and other unsupported models have no actions.
+Output is the gateway envelope. `data` contains bounded inline report result items plus `query_context_id` and `sources[]`. Each source includes `effective_zone_offset`, the timezone value actually used for that query. When `zone_offset` is omitted, this is the resolved current-user timezone when available, otherwise the project default; when `zone_offset` is explicit, this is its resolved effective value. `sources[].drilldown` is present when the returned preview exposes follow-up actions. Each source is evaluated independently; SQL and other unsupported models have no actions.
 
 An empty batch or report result with no rows is a successful query: it means the requested time range has no data. The command fails only when every returned report entry contains an explicit execution error. Mixed batches keep successful items and return `meta.partial`, counts, and per-report `meta.failures` for partial-result handling.
 

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

@@ -0,0 +1,24 @@
+# tracking sdk-sample generate
+
+Use when submit an AI SDK sample 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 sdk-sample generate --project-id <project_id> --sdk-types '<json_array>'
+```
+
+Capability id: `tracking.sdk_sample.generate`
+
+Input sends `project_id` and `sdk_types`. The backend resolves company ID, app ID, and receiver URL from the authorized project. 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 |
+| `--sdk-types` | SDK type array. Supported values include `android-java`, `ios-swift`, `web-js`, `server-java`, `server-python`, `server-nodejs`, `unity-csharp`, and the other values listed by command help/schema. | Yes |

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

@@ -8,6 +8,8 @@ The response reports this directly: `computation.triggered_automatically=true`,
 
 Flags: `--project-id`, `--cluster-name`, `--display-name`, `--definition-request` required. Optional: `--authenticated-only`, `--zone-offset`, `--entity-id`. The cluster type comes from `definition_request.type`.
 
+`cluster_name` is a machine identifier: 1-80 characters, starts with a letter, and contains only letters, digits, or underscores. `display_name` is 1-80 characters. The CLI rejects violations before dispatch.
+
 Read `user_cluster_models.md` before constructing `--definition-request`. Create does not accept `--remark`; set it later with `user-cluster update` when needed.
 
 The backend validates and compiles the definition inside the create operation; if metadata is ambiguous or missing, creation fails without creating the cluster. Condition clusters are saved as mixed-condition clusters (`clusterType=CONDITION`, `clusterSubType=MIX_CONDITION`).

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

@@ -4,6 +4,8 @@ Create a cluster by mapping imported values to an analysis entity.
 
 Flags: `--project-id`, `--display-name`, and `--entity-id` are required. Prefer `--input-file <local_csv>`; the CLI uploads it automatically. `--input-file-id` resumes from an existing upload, while `--file-content` is only for small local tests. Exactly one of the three is allowed. Optional: `--cluster-name`, `--remarks`, and conditional `--association-property`.
 
+When supplied, `cluster_name` follows the same 1-80 character machine-name rule as condition/SQL clusters. `display_name` is 1-80 characters and `remarks` is at most 400 characters.
+
 Use `--input-file` for real local files; use `--input-file-id` only when resuming from an existing upload. Do not inline large ID lists.
 
 Run `analysis entity id-import-options` first. For the primary user entity, pass an allowed `--association-property` and put its real values in the single CSV column; `#user_id` is forbidden. For a non-primary entity, omit the flag and put that entity's own IDs in the single column. Every row must be non-empty.

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

@@ -8,6 +8,8 @@ The response distinguishes both paths. A definition update returns `computation.
 
 Flags: `--project-id`, `--cluster-name` required. Optional: `--display-name`, `--definition-request`, `--authenticated-only`, `--remark`, `--zone-offset`. The cluster type comes from `definition_request.type` when the definition changes.
 
+`display_name` is at most 80 characters and `remark` is at most 400 characters. The CLI rejects violations before dispatch. `cluster_name` is an existing exact identifier and cannot be renamed by update.
+
 Read `user_cluster_models.md` before changing the definition. The backend validates and compiles `definition_request` inside update and refuses to modify the cluster if clarification is required. Condition definitions are saved as mixed-condition clusters.
 
 ```bash

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

@@ -1,5 +1,7 @@
 # analysis user-cluster update-id
 
+`display_name` is at most 80 characters and `remarks` is at most 400 characters. The CLI rejects violations before uploading or dispatching the replacement file.
+
 Update a cluster by remapping imported values to its analysis entity.
 
 Do not use it for a condition/SQL cluster. The existing entity binding cannot be changed by this command.

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

@@ -8,6 +8,8 @@ The response reports this directly: `computation.triggered_automatically=true`,
 
 Flags: `--project-id`, `--tag-name`, `--display-name`, `--definition-request` required. Optional: `--authenticated-only`, `--zone-offset`, `--entity-id`. The tag type comes from `definition_request.type`.
 
+`tag_name` is a machine identifier: 1-80 characters, starts with a letter, and contains only letters, digits, or underscores. `display_name` is 1-80 characters. The CLI rejects violations before dispatch.
+
 Read `user_tag_models.md` before constructing `--definition-request`. Create does not accept `--remark`; set it later with `user-tag update` when needed.
 
 The backend validates and compiles the definition inside the create operation; if metadata is ambiguous or missing, creation fails without creating the tag.

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

@@ -4,6 +4,8 @@ Create a tag by mapping imported values to an analysis entity.
 
 Flags: `--project-id`, `--display-name`, and `--entity-id` are required. Prefer `--input-file <local_csv>`; the CLI uploads it automatically. `--input-file-id` resumes from an existing upload, while `--file-content` is only for small local tests. Exactly one of the three is allowed. Optional: `--tag-name`, `--remarks`, and conditional `--association-property`.
 
+When supplied, `tag_name` follows the same 1-80 character machine-name rule as calculated tags. `display_name` is 1-80 characters and `remarks` is at most 400 characters.
+
 Use `--input-file` for real local files; use `--input-file-id` only when resuming from an existing upload. Do not inline large ID lists.
 
 Run `analysis entity id-import-options` first. For the primary user entity, column 1 is a real value of the selected `--association-property`; for a non-primary entity, it is that entity's own ID. Column 2 is `tag_value`. The headerless UTF-8 CSV must contain exactly two non-empty columns in every row.

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

@@ -8,6 +8,8 @@ The response distinguishes both paths. A definition update returns `computation.
 
 Flags: `--project-id`, `--tag-name` required. Optional: `--display-name`, `--definition-request`, `--authenticated-only`, `--remark`, `--zone-offset`. The tag type comes from `definition_request.type` when the definition changes.
 
+`display_name` is at most 80 characters and `remark` is at most 400 characters. The CLI rejects violations before dispatch. `tag_name` is an existing exact identifier and cannot be renamed by update.
+
 Read `user_tag_models.md` before changing the definition. The backend validates and compiles `definition_request` inside update and refuses to modify the tag if clarification is required.
 
 ```bash

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

@@ -1,5 +1,7 @@
 # analysis user-tag update-id
 
+`display_name` is at most 80 characters and `remarks` is at most 400 characters. The CLI rejects violations before uploading or dispatching the replacement file.
+
 Update a tag by remapping imported values to its analysis entity.
 
 Do not use it for condition/metric/first-last/SQL definition changes.

package/skills/ae-analysis-global/SKILL.md

@@ -27,6 +27,8 @@ For commands added only by this overlay, read this skill's matching reference fi
 
 Every command accepts `--host <url>` to override the active AE host, and it may be placed after the subcommand (e.g. `ae-cli analysis +list_query_clusters --project_id <id> --host <url>`). Host selection is independent of `--cluster_query_scope`: `--host` chooses which AE instance to call, while `--cluster_query_scope` / `--slave_cluster_id` choose which cluster within global mode.
 
+**CRITICAL — Host compat (do this first):** After each `ae-cli` run, check stderr and `_notice.host_compat`. If either is present, open the user reply with a short ⚠️ version warning and **quote the `npm i -g` / `npx skills add` (or update-cluster) lines verbatim**, then present the business result. Soft tip; `ok: true` can still carry the notice. (Also covered by `ae-analysis` Global Rules when both skills are loaded.)
+
 ## Routing Rules
 
 - In this overlay, **query cluster / service cluster / deployment cluster** means multi-cluster routing for analysis queries. **audience/user segment cluster** means user membership assets under `analysis user-cluster`.