@thinkingai/ae-cli 6.0.30 → 6.0.31

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

@@ -1,54 +0,0 @@
-# analysis +build_heat_map_analysis_qp (Build Heatmap Analysis QP)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Model Analysis**
-
-## Use Cases
-- Build a validated heatmap-analysis QP from structured heatmap intent.
-- Heatmap analysis visualizes user interaction intensity on a 2D coordinate plane (e.g. screen position).
-- Use in the mandatory builder flow before `+query_adhoc --model_type heat_map`.
-- This command builds QP only and does not execute the analysis query.
-
-## JSON Rules
-- CLI flags use snake_case, but JSON object keys use camelCase.
-- `--heat_map` is a JSON object. Required fields: `hotEvent`, `hotAggregation`, `xProp`, `yProp`.
-- `xProp` and `yProp` must be numeric event properties (e.g. screen_width, screen_height, x_position, y_position).
-- Wrap JSON in single quotes in shell commands.
-
-## Command Syntax
-```bash
-ae-cli analysis +build_heat_map_analysis_qp --project_id <project_id> --time_range '<time_range_json>' --heat_map '<heat_map_json>'
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--authenticated_only` | No | Resolve only authenticated assets while building the QP. Do not pass this flag to `+query_adhoc`. |
-| `--time_range` | Yes | Time range JSON |
-| `--heat_map` | Yes | Heatmap intent JSON |
-
-## JSON Shape
-`--heat_map` object:
-```json
-{"hotEvent":"screen_tap","hotAggregation":"A100","xProp":"x_position","yProp":"y_position"}
-```
-
-Optional fields in `--heat_map`:
-- `hotProperty`: required when hotAggregation is property-based (A103/A104 etc.)
-- `filters`: event filters array
-- `relation`: filter relation (and / or)
-
-## Examples
-```bash
-ae-cli analysis +build_heat_map_analysis_qp --project_id 3137 --time_range '{"mode":"previous","unit":"day","value":7}' --heat_map '{"hotEvent":"screen_tap","hotAggregation":"A100","xProp":"x_position","yProp":"y_position"}'
-```
-
-## Decision Rules
-- Use `--authenticated_only true` only when the user explicitly wants authenticated assets; do not add this flag to `+query_adhoc`.
-- After successful build (`status=generated`), call `+query_adhoc --model_type heat_map --qp '<response.qp>'`.
-- If non-generated status, stop and ask user to clarify.
-
-## Recommended Chain
-- `+build_heat_map_analysis_qp` -> if `status=generated` -> `+query_adhoc --model_type heat_map --qp '<response.qp>'`

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

@@ -1,60 +0,0 @@
-# analysis +build_interval_analysis_qp (Build Interval Analysis QP)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Model Analysis**
-
-## Use Cases
-- Build a validated interval-analysis QP from structured interval intent.
-- Interval analysis measures the time elapsed between an initial event and a return event per user.
-- Use in the mandatory builder flow before `+query_adhoc --model_type interval`.
-- This command builds QP only and does not execute the analysis query.
-
-## JSON Rules
-- CLI flags use snake_case, but JSON object keys use camelCase.
-- `--interval` is a JSON object. Required fields: `initialEvent`, `returnEvent`, `window` (`{value, unit}`).
-- `window.unit`: second / minute / hour / day / week / month.
-- Wrap JSON in single quotes in shell commands.
-- Do not call `list_events` or `list_properties` before this builder for normal ad-hoc analysis.
-
-## Command Syntax
-```bash
-ae-cli analysis +build_interval_analysis_qp --project_id <project_id> --time_range '<time_range_json>' --interval '<interval_json>'
-ae-cli analysis +build_interval_analysis_qp --project_id <project_id> --time_range '<time_range_json>' --interval '<interval_json>' --relation and --time_particle_size day
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--authenticated_only` | No | Resolve only authenticated assets while building the QP. Do not pass this flag to `+query_adhoc`. |
-| `--time_range` | Yes | Time range JSON |
-| `--interval` | Yes | Interval intent JSON |
-| `--relation` | No | Filter relation for top-level filters. Values: and, or. Default: and. |
-| `--time_particle_size` | No | Time granularity. Allowed values: day, week, month. Defaults to day. |
-
-## JSON Shape
-`--interval` object:
-```json
-{"initialEvent":"login","returnEvent":"purchase","window":{"value":7,"unit":"day"}}
-```
-
-Optional fields in `--interval`:
-- `relationEventPropertyName`: shared relation property for both events
-- `groups`: group-by dimensions array
-- `filters`: global filters array
-- `initialFilters` / `returnFilters`: event-level filters (event properties only)
-- `initialFilterRelation` / `returnFilterRelation`: and / or
-
-## Examples
-```bash
-ae-cli analysis +build_interval_analysis_qp --project_id 3137 --time_range '{"mode":"previous","unit":"day","value":7}' --interval '{"initialEvent":"login","returnEvent":"purchase","window":{"value":7,"unit":"day"}}'
-```
-
-## Decision Rules
-- Use `--authenticated_only true` only when the user explicitly wants authenticated assets; do not add this flag to `+query_adhoc`.
-- After successful build (`status=generated`), call `+query_adhoc --model_type interval --qp '<response.qp>'`.
-- If non-generated status, stop and ask user to clarify.
-
-## Recommended Chain
-- `+build_interval_analysis_qp` -> if `status=generated` -> `+query_adhoc --model_type interval --qp '<response.qp>'`

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

@@ -1,53 +0,0 @@
-# analysis +build_path_analysis_qp (Build Path Analysis QP)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Model Analysis**
-
-## Use Cases
-- Build a validated path-analysis QP from structured path intent.
-- Path analysis visualizes user navigation flows between events within a session.
-- Use in the mandatory builder flow before `+query_adhoc --model_type path`.
-- This command builds QP only and does not execute the analysis query.
-
-## JSON Rules
-- CLI flags use snake_case, but JSON object keys use camelCase.
-- `--path` is a JSON object. Required fields: `sourceEvent`, `eventNames` (array), `sessionInterval`, `sessionUnit`.
-- `sessionUnit`: second / minute / hour.
-- `sourceType`: 0=forward path (after source event, default), 1=backward path (before source event).
-- Wrap JSON in single quotes in shell commands.
-
-## Command Syntax
-```bash
-ae-cli analysis +build_path_analysis_qp --project_id <project_id> --time_range '<time_range_json>' --path '<path_json>'
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--authenticated_only` | No | Resolve only authenticated assets while building the QP. Do not pass this flag to `+query_adhoc`. |
-| `--time_range` | Yes | Time range JSON |
-| `--path` | Yes | Path intent JSON |
-
-## JSON Shape
-`--path` object:
-```json
-{"sourceEvent":"login","eventNames":["login","view_product","purchase"],"sessionInterval":30,"sessionUnit":"minute"}
-```
-
-Optional fields in `--path`:
-- `sourceType`: 0=forward (default), 1=backward
-
-## Examples
-```bash
-ae-cli analysis +build_path_analysis_qp --project_id 3137 --time_range '{"mode":"previous","unit":"day","value":7}' --path '{"sourceEvent":"login","eventNames":["login","view_product","purchase"],"sessionInterval":30,"sessionUnit":"minute"}'
-```
-
-## Decision Rules
-- Use `--authenticated_only true` only when the user explicitly wants authenticated assets; do not add this flag to `+query_adhoc`.
-- After successful build (`status=generated`), call `+query_adhoc --model_type path --qp '<response.qp>'`.
-- If non-generated status, stop and ask user to clarify.
-
-## Recommended Chain
-- `+build_path_analysis_qp` -> if `status=generated` -> `+query_adhoc --model_type path --qp '<response.qp>'`

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

@@ -1,124 +0,0 @@
-# analysis +build_prop_analysis_qp (build property analysis qp)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Model Analysis**
-
-## Use Cases
-- Build a validated `prop_analysis` QP from structured intent.
-- Use in the mandatory builder flow before `+query_adhoc --model_type prop_analysis`.
-- This command builds QP only and does not execute the analysis query.
-- This is the `prop_analysis` builder in the ten-model guided QP builder set.
-- Use this builder for property-analysis ad hoc requests; do not manually build prop_analysis QP through `+get_analysis_query_schema`.
-
-## JSON Rules
-- CLI flags use snake_case, but JSON object keys use camelCase DTO names.
-- `prop_analysis` does not use `time_range`; do not pass time range to this command.
-- `event_property` is not supported anywhere in `prop_analysis` fields.
-- Field types for `groups`, `filters`, and `userCrowds[].filters` are limited to `user_property`, `cluster`, and `tag`.
-- Do not run syntax examples with placeholder JSON. Fill `prop_analysis` with a valid metric and optional filters/groups before calling this command.
-- `--dry-run` still requires the same required flags as a real builder call. Never run this command as dry-run without `--project_id` and `--prop_analysis`.
-- Do not call `get_analysis_query_schema`, `list_properties`, `list_metrics`, or `get_metric` before this builder for normal ad-hoc analysis. The builder resolves user properties internally.
-- Builder commands do not accept `zone_offset`; pass `--zone_offset` to `+query_adhoc` after the builder succeeds if needed.
-- If the request misses the metric or asks for event properties, stop and ask the user to clarify.
-
-## Command Syntax
-```bash
-ae-cli analysis +build_prop_analysis_qp --project_id <project_id> --prop_analysis '<valid_prop_analysis_json>'
-ae-cli analysis +build_prop_analysis_qp --project_id <project_id> --prop_analysis '<valid_prop_analysis_json>' --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--authenticated_only` | No | Resolve only authenticated assets while building the QP. Do not pass this flag to `+query_adhoc`. |
-| `--prop_analysis` | Yes | User property analysis intent JSON |
-
-## JSON Shape
-`--prop_analysis` object:
-```json
-{
-  "metric":{"aggregation":"user_count"},
-  "groups":[{"field":{"name":"城市","type":"user_property"}}],
-  "filters":[{"field":{"name":"账户ID","type":"user_property"},"operator":"exists"}],
-  "relation":"and",
-  "userCrowds":[
-    {"name":"账户ID有值用户","filters":[{"field":{"name":"账户ID","type":"user_property"},"operator":"exists"}]}
-  ]
-}
-```
-
-Prop analysis fields:
-| Field | Required | Description |
-|---|---|---|
-| `metric` | Yes | Single metric object |
-| `groups` | No | User property / cluster / tag group-by fields |
-| `filters` | No | User property / cluster / tag filters |
-| `relation` | No | Relation between top-level filters: `and` or `or`. Default: `and`. |
-| `userCrowds` | No | Optional user crowd comparisons |
-
-Metric fields:
-| Field | Required | Description |
-|---|---|---|
-| `aggregation` | Yes | `user_count`, `sum`, `avg`, `max`, `min`, `distinct_count`, `true_count`, `false_count`, `not_empty_count`, `empty_count`, `median`, `percentile`, `variance`, `stddev` |
-| `property` | Required except `user_count` | User property display name, technical name, or remark |
-
-Field object:
-```json
-{"name":"城市","type":"user_property"}
-```
-
-Allowed field types:
-| Type | Meaning |
-|---|---|
-| `user_property` | User property |
-| `cluster` | User cluster |
-| `tag` | User tag |
-
-Filter object:
-```json
-{"field":{"name":"账户ID","type":"user_property"},"operator":"exists"}
-```
-
-User crowd object:
-```json
-{"name":"付费用户","filters":[{"field":{"name":"是否付费","type":"user_property"},"operator":"is_true"}],"relation":"and"}
-```
-
-Filter operator rules:
-| Operator | Values |
-|---|---|
-| `exists`, `not_exists`, `is_true`, `is_false` | Omit `values` |
-| `between` | Exactly two values |
-| `eq`, `neq`, `lt`, `lte`, `gt`, `gte`, `contains`, `not_contains`, `regex`, `not_regex` | Non-empty `values` array |
-| `in_cluster`, `not_in_cluster` | Cluster operator; values are not required by builder validation |
-
-## Examples
-Minimal user count:
-```bash
-ae-cli analysis +build_prop_analysis_qp --project_id 3137 --prop_analysis '{"metric":{"aggregation":"user_count"}}'
-```
-
-User property average grouped by city:
-```bash
-ae-cli analysis +build_prop_analysis_qp --project_id 3137 --prop_analysis '{"metric":{"aggregation":"avg","property":"余额"},"groups":[{"field":{"name":"城市","type":"user_property"}}],"filters":[{"field":{"name":"账户ID","type":"user_property"},"operator":"exists"}]}'
-```
-
-User crowds with OR filter:
-```bash
-ae-cli analysis +build_prop_analysis_qp --project_id 3137 --prop_analysis '{"metric":{"aggregation":"user_count"},"filters":[{"field":{"name":"账户ID","type":"user_property"},"operator":"exists"},{"field":{"name":"城市","type":"user_property"},"operator":"exists"}],"relation":"or","userCrowds":[{"name":"账户或城市有值","filters":[{"field":{"name":"账户ID","type":"user_property"},"operator":"exists"},{"field":{"name":"城市","type":"user_property"},"operator":"exists"}],"relation":"or"}]}'
-```
-
-## Decision Rules
-- Use `--authenticated_only true` only when the user explicitly wants authenticated assets; do not add this flag to `+query_adhoc`.
-- After successful build, call `+query_adhoc --model_type prop_analysis --qp '<response.qp>'`.
-- If build returns non-generated status, stop and ask user to clarify; do not call `+query_adhoc`.
-- Wrap JSON parameters in single quotes to avoid shell escaping issues.
-- Do not pre-query metrics or metadata. Pass user-provided property names to the builder and let it resolve them.
-- Do not use `event_property` in prop_analysis. If the user asks for event property analysis, switch to event/funnel/retention builder or ask for clarification.
-- If `userCrowds` is used, at most one group dimension is supported.
-- If the user gave a time zone, keep it for `+query_adhoc --zone_offset`; do not put it in the builder JSON.
-
-## Recommended Chaining
-- `+build_prop_analysis_qp` -> if `status=generated` -> `+query_adhoc --model_type prop_analysis --qp '<response.qp>'`

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

@@ -1,63 +0,0 @@
-# analysis +build_rank_list_analysis_qp (Build Rank List Analysis QP)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Model Analysis**
-
-## Use Cases
-- Build a validated rank-list-analysis QP from structured rank list intent.
-- Rank list analysis ranks entities (users, items, etc.) by a metric value.
-- Use in the mandatory builder flow before `+query_adhoc --model_type rank_list`.
-- This command builds QP only and does not execute the analysis query.
-
-## JSON Rules
-- CLI flags use snake_case, but JSON object keys use camelCase.
-- `--rank_list` is a JSON object. Required fields: `rankDimension` (with `field`), `rankEvent`, `rankAggregation`.
-- `rankType` values: `rank`=standard (1,2,2,4), `dense_rank`=dense (1,2,2,3), `row_rank`=unique (1,2,3,4). Defaults to `row_rank`.
-- `orderBy`: `DESC`=highest first (default), `ASC`=lowest first.
-- Wrap JSON in single quotes in shell commands.
-
-## Command Syntax
-```bash
-ae-cli analysis +build_rank_list_analysis_qp --project_id <project_id> --time_range '<time_range_json>' --rank_list '<rank_list_json>'
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--authenticated_only` | No | Resolve only authenticated assets while building the QP. Do not pass this flag to `+query_adhoc`. |
-| `--time_range` | Yes | Time range JSON |
-| `--rank_list` | Yes | Rank list intent JSON |
-
-## JSON Shape
-`--rank_list` object:
-```json
-{
-  "rankDimension": {"field": {"name": "#account_id", "type": "user_property"}},
-  "rankEvent": "purchase",
-  "rankAggregation": "A103",
-  "rankProperty": "amount",
-  "orderBy": "DESC"
-}
-```
-
-Optional fields in `--rank_list`:
-- `rankProperty`: required when rankAggregation is property-based (A103/A104/A106/A107/A108 etc.)
-- `rankType`: rank / dense_rank / row_rank (default)
-- `orderBy`: DESC (default) / ASC
-- `filters`: global filters array
-- `relation`: filter relation (and / or)
-
-## Examples
-```bash
-ae-cli analysis +build_rank_list_analysis_qp --project_id 3137 --time_range '{"mode":"previous","unit":"day","value":7}' --rank_list '{"rankDimension":{"field":{"name":"#account_id","type":"user_property"}},"rankEvent":"purchase","rankAggregation":"A101","orderBy":"DESC"}'
-```
-
-## Decision Rules
-- Use `--authenticated_only true` only when the user explicitly wants authenticated assets; do not add this flag to `+query_adhoc`.
-- After successful build (`status=generated`), call `+query_adhoc --model_type rank_list --qp '<response.qp>'`.
-- If non-generated status, stop and ask user to clarify.
-
-## Recommended Chain
-- `+build_rank_list_analysis_qp` -> if `status=generated` -> `+query_adhoc --model_type rank_list --qp '<response.qp>'`

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

@@ -1,143 +0,0 @@
-# analysis +build_retention_analysis_qp (build retention analysis qp)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Model Analysis**
-
-## Use Cases
-- Build a validated retention-analysis QP from structured intent.
-- Use in the mandatory builder flow before `+query_adhoc --model_type retention`.
-- This command builds QP only and does not execute the analysis query.
-- This is the `retention` builder in the ten-model guided QP builder set.
-- Use this builder for retention ad hoc requests; do not manually build retention QP through `+get_analysis_query_schema`.
-
-## JSON Rules
-- CLI flags use snake_case, but JSON object keys use camelCase DTO names.
-- Correct nested keys: `initialEvent`, `returnEvent`, `unitNum`, `rtnRateOrNum`, `relationEventPropertyName`, `initialFilters`, `returnFilters`, `initialFilterRelation`, `returnFilterRelation`.
-- Initial/return event filters are event-property-only and use `eventPropertyName`; they do not use the generic `field` object.
-- Retention global filters and groups use the generic `field` object.
-- Do not run syntax examples with placeholder JSON. Fill `time_range` and `retention` with valid nested fields before calling this command.
-- `--dry-run` still requires the same required flags as a real builder call. Never run this command as dry-run without `--project_id`, `--time_range`, and `--retention`.
-- Do not call `get_analysis_query_schema`, `list_events`, `list_properties`, `list_metrics`, or `get_metric` before this builder for normal ad-hoc analysis. The builder resolves events and properties internally.
-- Builder commands do not accept `zone_offset`; pass `--zone_offset` to `+query_adhoc` after the builder succeeds.
-- If the request misses time range, initial event, return event, or retention interval, stop and ask the user to clarify.
-
-## Command Syntax
-```bash
-ae-cli analysis +build_retention_analysis_qp --project_id <project_id> --time_range '<valid_time_range_json>' --retention '<valid_retention_json>'
-ae-cli analysis +build_retention_analysis_qp --project_id <project_id> --time_range '<valid_time_range_json>' --retention '<valid_retention_json>' --relation and --time_particle_size day
-ae-cli analysis +build_retention_analysis_qp --project_id <project_id> --time_range '<valid_time_range_json>' --retention '<valid_retention_json>' --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--authenticated_only` | No | Resolve only authenticated assets while building the QP. Do not pass this flag to `+query_adhoc`. |
-| `--time_range` | Yes | Retention analysis time range JSON |
-| `--retention` | Yes | Retention intent JSON |
-| `--relation` | No | Top-level retention filter relation. Supported values: and, or. Default: and |
-| `--time_particle_size` | No | Time granularity. Supported values: day, week, month |
-
-## JSON Shape
-`--time_range` object:
-```json
-{"mode":"start_to_yesterday","startTime":"2021-05-18"}
-```
-
-Time range fields:
-| Field | Required | Description |
-|---|---|---|
-| `mode` | Yes | `recent`, `previous`, `custom`, `start_to_today`, `start_to_yesterday` |
-| `unit` | For `recent`/`previous` | `day`, `week`, `month`, `quarter`, `year` |
-| `value` | For `recent`/`previous` | Unit count. `{"mode":"previous","unit":"day","value":1}` means yesterday. |
-| `startTime` | For `custom`/`start_to_*` | `yyyy-MM-dd` or `yyyy-MM-dd HH:mm:ss` |
-| `endTime` | For `custom` only | `yyyy-MM-dd` or `yyyy-MM-dd HH:mm:ss` |
-
-`--retention` object:
-```json
-{
-  "initialEvent":"注册",
-  "returnEvent":"商品购买",
-  "unitNum":7,
-  "statType":"retention",
-  "rtnRateOrNum":"R0",
-  "relationEventPropertyName":"账户ID",
-  "initialFilters":[{"eventPropertyName":"账户ID","operator":"exists"}],
-  "returnFilters":[{"eventPropertyName":"账户ID","operator":"exists"}],
-  "filters":[{"field":{"name":"城市","type":"event_property"},"operator":"exists"}],
-  "groups":[{"field":{"name":"渠道","type":"user_property"}}]
-}
-```
-
-Retention fields:
-| Field | Required | Description |
-|---|---|---|
-| `initialEvent` | Yes | Initial event display name, technical name, or remark |
-| `returnEvent` | Yes | Return event display name, technical name, or remark |
-| `unitNum` | Yes | Retention interval count, such as `1` for day-1 or `7` for day-7 |
-| `statType` | No | `retention` for retained users or `lost` for lost users |
-| `rtnRateOrNum` | No | `R0`, `rate`, or `retention` for rate; `R1`, `number`, or `count` for user count. Default: `R0`. |
-| `relationEventPropertyName` | No | Event property shared by initial event, return event, and simultaneous metrics |
-| `simultaneousMetrics` | No | Extra retention display metrics |
-| `groups` | No | Generic group-by dimensions |
-| `filters` | No | Generic retention filters |
-| `initialFilters` | No | Event-property-only filters for initial event |
-| `initialFilterRelation` | No | Relation for `initialFilters`: `and` or `or` |
-| `returnFilters` | No | Event-property-only filters for return event |
-| `returnFilterRelation` | No | Relation for `returnFilters`: `and` or `or` |
-
-Initial/return event filter object:
-```json
-{"eventPropertyName":"账户ID","operator":"exists"}
-```
-
-Generic filter object for `retention.filters`:
-```json
-{"field":{"name":"城市","type":"event_property"},"operator":"exists"}
-```
-
-Group object:
-```json
-{"field":{"name":"渠道","type":"user_property"}}
-```
-
-Metric object for `simultaneousMetrics`:
-```json
-{"event":"商品购买","aggregation":"user_count"}
-```
-
-Supported aggregations:
-`total_count`, `user_count`, `per_user_count`, `sum`, `avg`, `avg_per_user`, `max`, `min`, `distinct_count`, `true_count`, `false_count`, `not_empty_count`, `empty_count`, `median`, `percentile`, `variance`, `stddev`.
-
-Filter operator rules:
-| Operator | Values |
-|---|---|
-| `exists`, `not_exists`, `is_true`, `is_false` | Omit `values` |
-| `between` | Exactly two values |
-| `eq`, `neq`, `lt`, `lte`, `gt`, `gte`, `contains`, `not_contains`, `regex`, `not_regex` | Non-empty `values` array |
-| `in_cluster`, `not_in_cluster` | Cluster operator; values are not required by builder validation |
-
-## Examples
-Minimal day-7 retention:
-```bash
-ae-cli analysis +build_retention_analysis_qp --project_id 3137 --time_range '{"mode":"previous","unit":"day","value":7}' --retention '{"initialEvent":"注册","returnEvent":"商品购买","unitNum":7}'
-```
-
-Retention with relation property and event-level filters:
-```bash
-ae-cli analysis +build_retention_analysis_qp --project_id 3137 --time_range '{"mode":"start_to_yesterday","startTime":"2021-05-18"}' --retention '{"initialEvent":"special_data","returnEvent":"商品购买","unitNum":7,"relationEventPropertyName":"账户ID","initialFilters":[{"eventPropertyName":"账户ID","operator":"exists"}],"returnFilters":[{"eventPropertyName":"账户ID","operator":"exists"},{"eventPropertyName":"城市","operator":"exists"}],"returnFilterRelation":"or","filters":[{"field":{"name":"账户ID","type":"event_property"},"operator":"exists"},{"field":{"name":"城市","type":"event_property"},"operator":"exists"}],"groups":[{"field":{"name":"账户ID","type":"event_property"}}]}' --relation or --time_particle_size day
-```
-
-## Decision Rules
-- Use `--authenticated_only true` only when the user explicitly wants authenticated assets; do not add this flag to `+query_adhoc`.
-- After successful build, call `+query_adhoc --model_type retention --qp '<response.qp>'`.
-- If build returns non-generated status, stop and ask user to clarify; do not call `+query_adhoc`.
-- Wrap JSON parameters in single quotes to avoid shell escaping issues.
-- Do not pre-query metrics or metadata. Pass user-provided event/property names to the builder and let it resolve them.
-- Do not put global filter relation inside `retention`; pass it as top-level CLI flag `--relation`.
-- For overall/totals retention, omit `--time_particle_size`; only set it when user asks for day/week/month breakdown.
-- If the user gave a time zone, keep it for `+query_adhoc --zone_offset`; do not put it in the builder JSON.
-
-## Recommended Chaining
-- `+build_retention_analysis_qp` -> if `status=generated` -> `+query_adhoc --model_type retention --qp '<response.qp>'`

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

@@ -1,65 +0,0 @@
-# analysis_audience +build_tag_definition (Build Tag Definition)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Tag Management**
-
-## Use Cases
-
-- Build a tag definition JSON from structured intent. Call this before `+create_tag` or `+update_tag` to generate the `definition` field.
-- Supported types: `condition` (multi-value), `metric` (event metric), `first_last` (first/last occurrence), `sql`.
-- For condition/metric/first_last types, event and property names are resolved from project metadata — do not guess.
-- On success, pass the returned definition to `+create_tag` or `+update_tag`.
-
-## Required Prerequisites (MUST)
-
-- Before calling this command, you must first read and follow these reference docs:
-  - [`./get_tag_definition_schema.md`](./get_tag_definition_schema.md)
-  - [`./list_events.md`](./list_events.md)
-  - [`./list_properties.md`](./list_properties.md)
-- Do not construct `--condition_values` / `--metric` / `--first_last` until the schema has been read and metadata has been verified for the same `project_id`.
-
-## Commands
-
-```bash
-ae-cli analysis_audience +build_tag_definition --project_id <project_id> --type condition --condition_values '[]'
-ae-cli analysis_audience +build_tag_definition --project_id <project_id> --type metric --metric '{}'
-ae-cli analysis_audience +build_tag_definition --project_id <project_id> --type first_last --first_last '{}'
-ae-cli analysis_audience +build_tag_definition --project_id <project_id> --type sql --sql 'SELECT "#user_id", tag_value FROM ...'
-ae-cli analysis_audience +build_tag_definition --dry-run
-```
-
-## Parameters
-
-| Parameter             | Required | Description                                                                                                                                                                       |
-| --------------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--project_id` / `-p` | Yes      | Project ID                                                                                                                                                                        |
-| `--authenticated_only` | No | Resolve only authenticated assets while building the definition. |
-| `--type`              | Yes      | Tag type. Supported values: `condition`, `metric`, `first_last`, `sql`                                                                                                            |
-| `--condition_values`  | No       | For type=condition: list of tag value definitions JSON array. Each item defines a segment label and its conditions. See `+get_tag_definition_schema` for the structure.            |
-| `--metric`            | No       | For type=metric: metric definition JSON. Fields: `eventName`, `analysis`, `quota` (property name), `recentDay`/`startTime`/`endTime`.                                             |
-| `--first_last`        | No       | For type=first_last: first/last occurrence definition JSON. Fields: `eventName`, `firstEvent` (true=first, false=last), `calcPropType`, `property`, `recentDay`/`startTime`/`endTime`. |
-| `--sql`               | No       | For type=sql: SQL query returning two columns: `#user_id` and the tag value.                                                                                                      |
-
-## Decision Rules
-- Use `--authenticated_only true` when the definition should only resolve authenticated events/properties/metrics/clusters/tags.
-
-- Determine `--type` first, then pass only the corresponding parameter.
-- For type=condition, `--condition_values` is effectively required.
-- For type=metric, `--metric` is effectively required.
-- For type=first_last, `--first_last` is effectively required.
-- For type=sql, only `--sql` is needed; other type-specific parameters are ignored.
-- Event and property names must come from session-verified metadata (`analysis_meta +list_events` / `+list_properties` for the same `project_id`).
-- Do not guess event or property names — always verify against real metadata first.
-- Wrap JSON parameters in single quotes (e.g. `--condition_values '[]'`) to avoid shell escaping issues.
-- Run `--dry-run` first to inspect the request mapping before making the actual call.
-
-## Next Step on Failure
-
-- If required parameters are missing, check that `--project_id` and `--type` are provided.
-- If the returned definition is rejected by `+create_tag` or `+update_tag`, re-read `+get_tag_definition_schema` with `--response_mode examples` and verify metadata names again.
-
-## Recommended Chain
-
-- `+get_tag_definition_schema` → (first build/update in session or refresh) `analysis_meta +list_events` → `analysis_meta +list_properties` → `+build_tag_definition` → `+create_tag`
-- `+get_tag_definition_schema` → (first build/update in session or refresh) `analysis_meta +list_events` → `analysis_meta +list_properties` → `+build_tag_definition` → `+update_tag`

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

@@ -1,33 +0,0 @@
-# analysis +copy_dashboard (Copy Dashboard)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Dashboard Management**
-
-## Use Cases
-- Copy a dashboard to a new dashboard, optionally copying its associated reports.
-- To place the copy in a specific space or folder, provide `--to_space_id` or `--to_folder_id`. Use `+list_spaces` to resolve these IDs.
-
-## Commands
-```bash
-ae-cli analysis_audience +copy_dashboard --project_id <project_id> --dashboard_id <dashboard_id> --dashboard_name "Copy of Dashboard"
-ae-cli analysis_audience +copy_dashboard --project_id <project_id> --dashboard_id <dashboard_id> --dashboard_name "Copy of Dashboard" --report_copy true --to_space_id <space_id>
-ae-cli analysis_audience +copy_dashboard --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--dashboard_id` | Yes | Source dashboard ID to copy |
-| `--dashboard_name` | Yes | Name for the new copied dashboard |
-| `--report_copy` | No | Whether to also copy associated reports. Defaults to false. |
-| `--to_space_id` | No | Target space ID. Omit to use the default location. |
-| `--to_folder_id` | No | Target folder ID inside the target space. Omit to place at the space root. |
-
-## Decision Rules
-- Call `+list_spaces` first when the user wants to place the copy in a specific space or folder.
-- Returns the new dashboard ID and name on success.
-
-## Recommended Chain
-- `+list_dashboards` -> `+list_spaces` -> `+copy_dashboard` -> `analysis_common +get_resource_url`