@thinkingai/ae-cli 1.0.1 → 1.0.3

package/skills/te-engage/references/task-stats.md

@@ -1,38 +1,38 @@
-# te-engage +task-stats
+# te-engage +task_stats
 
-> **前置条件:** 阅读 [`../../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Read [`../../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
-查询任务状态统计。
+Query task status statistics.
 
-映射命令: `te-cli te-engage +task-stats`
+Mapped command: `ae-cli engage +task_stats`
 
 ## Flags
 
-| Flag | 类型 | 必填 | 说明 |
+| Flag | Type | Required | Description |
 |------|------|------|------|
-| `--project-id` / `-p` | number | 是 | 项目 ID |
-| `--req` | json | 是 | 统计条件 JSON 对象 |
+| `--project_id` / `-p` | number | Yes | Project ID |
+| `--req` | json | Yes | statistics-condition JSON object |
 
-## `--req` 对象字段
+## `--req` Object Fields
 
-`+task-stats` 的 `--req` 结构与 `+task-list` 基本一致，常见字段包括：
+The `--req` structure of `+task_stats` is broadly the same as `+task_list`, and common fields include:
 
-| 字段 | 类型 | 必填 | 说明 |
+| Field | Type | Required | Description |
 |------|------|------|------|
-| `mappingStatus` | number | 否 | 状态过滤 |
-| `triggerType` | number | 否 | 触发类型过滤 |
-| `channelType` | number | 否 | 渠道类型过滤 |
-| `groupId` | number | 否 | 分组 ID |
-| `creator` | string | 否 | 创建人 open_id |
-| `fuzzyField` | string | 否 | 任务 ID 或任务名模糊搜索 |
-| `belongActivity` | number | 否 | 是否关联活动过滤 |
-| `expStatusList` | array | 否 | 实验状态列表 |
-| `expReleaseStatusList` | array | 否 | 实验发布状态列表 |
-| `expTypeList` | array | 否 | 实验类型列表 |
+| `mappingStatus` | number | No | status filter |
+| `triggerType` | number | No | trigger type filter |
+| `channelType` | number | No | channel type filter |
+| `groupId` | number | No | group ID |
+| `creator` | string | No | creator open_id |
+| `fuzzyField` | string | No | fuzzy search by task ID or task name |
+| `belongActivity` | number | No | activity association filter |
+| `expStatusList` | array | No | experiment status list |
+| `expReleaseStatusList` | array | No | experiment release status list |
+| `expTypeList` | array | No | experiment type list |
 
-`projectId` 会由 CLI 自动补入 `--req`。
+`projectId` is automatically injected into `--req` by the CLI.
 
-## 枚举说明
+## Enum Notes
 
 ### `req.mappingStatus`
 
@@ -63,27 +63,27 @@
 
 ### `req.belongActivity`
 
-- `0`: 全部
-- `1`: 已关联活动
-- `2`: 未关联活动
+- `0`: all
+- `1`: activity linked
+- `2`: activity not linked
 
 ### `req.expStatusList[]`
 
-- `0`: 未创建实验
-- `1`: 已创建实验
+- `0`: experiment not created
+- `1`: experiment created
 
 ### `req.expReleaseStatusList[]`
 
-- `0`: 未发布实验
-- `1`: 已发布实验
+- `0`: experiment not released
+- `1`: experiment released
 
 ### `req.expTypeList[]`
 
 - `0`: normal
 - `1`: orthogonal
 
-## 示例
+## Examples
 
 ```bash
-te-cli te-engage +task-stats --project-id 1 --req '{"pageNum":1,"pageSize":20}'
+ae-cli engage +task_stats --project_id 1 --req '{"pageNum":1,"pageSize":20}'
 ```

package/skills/te-engage/references/update-channel-status.md

@@ -1,32 +1,32 @@
-# te-engage +update-channel-status
+# te-engage +update_channel_status
 
-> **前置条件:** 阅读 [`../../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Read [`../../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
-更新 Engage 渠道状态。
+Update the status of an Engage channel.
 
-映射命令: `te-cli te-engage +update-channel-status`
+Mapped command: `ae-cli engage +update_channel_status`
 
 ## Flags
 
-| Flag | 类型 | 必填 | 说明 |
+| Flag | Type | Required | Description |
 |------|------|------|------|
-| `--project-id` / `-p` | number | 是 | 项目 ID |
-| `--channel-id` | string | 是 | 渠道 ID |
-| `--status` | number | 是 | 渠道状态 |
+| `--project_id` / `-p` | number | Yes | Project ID |
+| `--channel_id` | string | Yes | channel ID |
+| `--status` | number | Yes | channel status |
 
-## 枚举说明
+## Enum Notes
 
 ### `--status`
 
 - `0`: disabled
 - `1`: enabled
 
-## 安全约束
+## Safety Constraints
 
-此命令为 **写操作**，执行前应确认用户明确希望变更渠道状态。
+This command is a **write operation** and Before executing, confirm that the user explicitly wants to change the channel status.
 
-## 示例
+## Examples
 
 ```bash
-te-cli te-engage +update-channel-status --project-id 1 --channel-id <channel-id> --status 1
+ae-cli engage +update_channel_status --project_id 1 --channel_id <channel_id> --status 1
 ```

package/skills/te-engage/references/update-config-channel-status.md

@@ -1,32 +1,32 @@
-# te-engage +update-config-channel-status
+# te-engage +update_config_channel_status
 
-> **前置条件:** 阅读 [`../../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Read [`../../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
-更新配置通道状态。
+Update the status of a config channel.
 
-映射命令: `te-cli te-engage +update-config-channel-status`
+Mapped command: `ae-cli engage +update_config_channel_status`
 
 ## Flags
 
-| Flag | 类型 | 必填 | 说明 |
+| Flag | Type | Required | Description |
 |------|------|------|------|
-| `--project-id` / `-p` | number | 是 | 项目 ID |
-| `--channel-id` | string | 是 | 配置通道 ID |
-| `--channel-status` | number | 是 | 配置通道状态 |
+| `--project_id` / `-p` | number | Yes | Project ID |
+| `--channel_id` | string | Yes | config channel ID |
+| `--channel_status` | number | Yes | config channel status |
 
-## 枚举说明
+## Enum Notes
 
-### `--channel-status`
+### `--channel_status`
 
 - `1`: enabled
 - `2`: disabled
 
-## 安全约束
+## Safety Constraints
 
-此命令为 **写操作**，会修改配置通道状态。
+This command is a **write operation** and and modifies the config channel status.
 
-## 示例
+## Examples
 
 ```bash
-te-cli te-engage +update-config-channel-status --project-id 1 --channel-id <channel-id> --channel-status 1
+ae-cli engage +update_config_channel_status --project_id 1 --channel_id <channel_id> --channel_status 1
 ```

package/skills/te-engage/references/validate-flow-node-config.md

@@ -1,24 +1,24 @@
-# te-engage +validate-flow-node-config
+# te-engage +validate_flow_node_config
 
-> **前置条件:** 阅读 [`../../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Read [`../../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
-在保存流程前校验单个节点配置。
+Validate a single node configuration before saving a flow.
 
-映射命令: `te-cli te-engage +validate-flow-node-config`
+Mapped command: `ae-cli engage +validate_flow_node_config`
 
 ## Flags
 
-| Flag | 类型 | 必填 | 说明 |
+| Flag | Type | Required | Description |
 |------|------|------|------|
-| `--node-type` | string | 是 | 节点类型 |
-| `--config` | string | 是 | 节点配置 JSON 字符串 |
-| `--operation-mode` | string | 是 | 校验模式 |
+| `--node_type` | string | Yes | node type |
+| `--config` | string | Yes | node config JSON string |
+| `--operation_mode` | string | Yes | validation mode |
 
-## 枚举说明
+## Enum Notes
 
-### `--node-type`
+### `--node_type`
 
-常见节点类型包括：
+Common node types include:
 
 - `single_trigger`
 - `repeat_trigger`
@@ -39,14 +39,14 @@
 - `race_split_flow`
 - `exit_flow`
 
-### `--operation-mode`
+### `--operation_mode`
 
 - `save_flow`
 - `save_submit_flow`
 
-## 示例
+## Examples
 
 ```bash
-te-cli te-engage +validate-flow-node-config \
-  --node-type message_push --operation-mode save_flow --config '{}'
+ae-cli engage +validate_flow_node_config \
+  --node_type message_push --operation_mode save_flow --config '{}'
 ```

package/skills/te-engage/references/whitelist-list.md

@@ -1,19 +1,19 @@
-# te-engage +whitelist-list
+# te-engage +whitelist_list
 
-> **前置条件:** 阅读 [`../../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Read [`../../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
-查询项目下的白名单列表。
+Query the whitelist list in a project.
 
-映射命令: `te-cli te-engage +whitelist-list`
+Mapped command: `ae-cli engage +whitelist_list`
 
 ## Flags
 
-| Flag | 类型 | 必填 | 说明 |
+| Flag | Type | Required | Description |
 |------|------|------|------|
-| `--project-id` / `-p` | number | 是 | 项目 ID |
+| `--project_id` / `-p` | number | Yes | Project ID |
 
-## 示例
+## Examples
 
 ```bash
-te-cli te-engage +whitelist-list --project-id 1
+ae-cli engage +whitelist_list --project_id 1
 ```

package/skills/te-meta/SKILL.md

@@ -5,7 +5,7 @@ description: "TE metadata and tracking-plan governance: event/property managemen
 metadata:
   requires:
     bins: ["ae-cli"]
-  cliHelp: "ae-cli te_meta --help"
+  cliHelp: "ae-cli analysis_meta --help"
 ---
 
 # te-meta
@@ -27,7 +27,7 @@ When the user needs "metadata governance and project configuration" capabilities
 
 ## Command Format
 
-`ae-cli te_meta +<tool_name> [options]`
+`ae-cli analysis_meta +<tool_name> [options]`
 
 ## Tool Groups (20)
 
@@ -60,10 +60,10 @@ When the user needs "metadata governance and project configuration" capabilities
 ## Quick Verification
 
 ```bash
-ae-cli te_meta --help
-npm run verify:te-meta-tools
+ae-cli analysis_meta --help
+npm run verify:analysis-meta-tools
 # Example: use dry-run to preview the request (replace project_id with your actual project ID)
-ae-cli te_meta +list_events --project_id <YOUR_PROJECT_ID> --dry-run
+ae-cli analysis_meta +list_events --project_id <YOUR_PROJECT_ID> --dry-run
 ```
 
 ## Reference Docs

package/skills/te-meta/references/batch-create-metadata.md

@@ -1,4 +1,4 @@
-# te_meta +batch_create_metadata (Batch Create Metadata)
+# analysis_meta +batch_create_metadata (Batch Create Metadata)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -9,9 +9,9 @@ Domain: **Metadata Query**
 
 ## Commands
 ```bash
-te-cli te_meta +batch_create_metadata --project_id 1
-te-cli te_meta +batch_create_metadata --project_id 1 --events '[{"eventName":"purchase"}]' --event_properties '[{"propName":"price","selectType":"number"}]' --user_properties '[{"propName":"vip_level","selectType":"string"}]'
-te-cli te_meta +batch_create_metadata --dry-run
+ae-cli analysis_meta +batch_create_metadata --project_id 1
+ae-cli analysis_meta +batch_create_metadata --project_id 1 --events '[{"eventName":"purchase"}]' --event_properties '[{"propName":"price","selectType":"number"}]' --user_properties '[{"propName":"vip_level","selectType":"string"}]'
+ae-cli analysis_meta +batch_create_metadata --dry-run
 ```
 
 ## Parameters

package/skills/te-meta/references/batch-edit-metadata.md

@@ -1,4 +1,4 @@
-# te_meta +batch_edit_metadata (Batch Edit Metadata)
+# analysis_meta +batch_edit_metadata (Batch Edit Metadata)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -10,8 +10,8 @@ Domain: **Metadata Query**
 
 ## Command
 ```bash
-te-cli te_meta +batch_edit_metadata --project_id 1 --type event --items '[{"eventName":"purchase","eventDesc":"Purchase"}]'
-te-cli te_meta +batch_edit_metadata --dry-run
+ae-cli analysis_meta +batch_edit_metadata --project_id 1 --type event --items '[{"eventName":"purchase","eventDesc":"Purchase"}]'
+ae-cli analysis_meta +batch_edit_metadata --dry-run
 ```
 
 ## Parameters

package/skills/te-meta/references/create-metric.md

@@ -1,4 +1,4 @@
-# te_meta +create_metric (Create Metric)
+# analysis_meta +create_metric (Create Metric)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -6,7 +6,7 @@ Domain: **Metadata Query**
 
 ## Use Cases
 - Preliminary step: call `+get_analysis_query_schema` to get the structure, then call this tool.
-- When constructing real `events` / `params`, you must supplement project-native metadata; first call `te_meta +list_events` and `te_meta +list_properties`.
+- When constructing real `events` / `params`, you must supplement project-native metadata; first call `analysis_meta +list_events` and `analysis_meta +list_properties`.
 - Create a metric from analysis configuration.
 - Creates a new metric based on event or retention analysis.
 
@@ -19,17 +19,17 @@ Domain: **Metadata Query**
 
 ## Prerequisite Call Chain (Required for Constructing events/params)
 1. Determine `--model_type` first (`event` / `retention`).
-2. Read `get-analysis-query-schema.md`, then call `te-cli te_analysis +get_analysis_query_schema --model_type <event|retention>` to get the structure.
-3. Read `list-events.md`, then call `te-cli te_meta +list_events --project_id 1` to get available events.
-4. Read `list-properties.md`, then call `te-cli te_meta +list_properties --project_id 1` to get available properties.
+2. Read `get-analysis-query-schema.md`, then call `ae-cli analysis +get_analysis_query_schema --model_type <event|retention>` to get the structure.
+3. Read `list-events.md`, then call `ae-cli analysis_meta +list_events --project_id 1` to get available events.
+4. Read `list-properties.md`, then call `ae-cli analysis_meta +list_properties --project_id 1` to get available properties.
 5. Build `events` / `params` from the schema + metadata, then call `+create_metric`.
-6. If an accessible URL must be returned, apply resource-link completion according to the unified `te-common` constraints (call `te_common +get_resource_url`).
+6. If an accessible URL must be returned, apply resource-link completion according to the unified `te-common` constraints (call `analysis_common +get_resource_url`).
 
 ## Commands
 ```bash
-te-cli te_meta +create_metric --project_id 1 --name demo --display_name demo --model_type event --events '[]' --params '{}'
-te-cli te_meta +create_metric --project_id 1 --name demo --display_name demo --remark demo --model_type event --events '[]' --params '{}'
-te-cli te_meta +create_metric --dry-run
+ae-cli analysis_meta +create_metric --project_id 1 --name demo --display_name demo --model_type event --events '[]' --params '{}'
+ae-cli analysis_meta +create_metric --project_id 1 --name demo --display_name demo --remark demo --model_type event --events '[]' --params '{}'
+ae-cli analysis_meta +create_metric --dry-run
 ```
 
 ## Parameters
@@ -40,8 +40,8 @@ te-cli te_meta +create_metric --dry-run
 | `--display_name` | Yes | Metric display name |
 | `--remark` | No | Optional metric remark |
 | `--model_type` | Yes | Metric model type. Supported values: event and retention |
-| `--events` | Yes | Metric events JSON. MUST call `+get_analysis_query_schema` first, then fill event/property fields using metadata from `te_meta +list_events` / `te_meta +list_properties` in the same `project_id`. |
-| `--params` | Yes | Metric params JSON. MUST follow the schema from `+get_analysis_query_schema`; use project metadata from `te_meta +list_events` / `te_meta +list_properties` when filling referenced fields. |
+| `--events` | Yes | Metric events JSON. MUST call `+get_analysis_query_schema` first, then fill event/property fields using metadata from `analysis_meta +list_events` / `analysis_meta +list_properties` in the same `project_id`. |
+| `--params` | Yes | Metric params JSON. MUST follow the schema from `+get_analysis_query_schema`; use project metadata from `analysis_meta +list_events` / `analysis_meta +list_properties` when filling referenced fields. |
 
 ## Decision Rules
 - `events` / `params` must not be handwritten by intuition alone: they must satisfy both the schema structure and the project's real metadata constraints.
@@ -58,5 +58,5 @@ te-cli te_meta +create_metric --dry-run
 - If the result after writing does not match expectations, immediately reread the corresponding list/get interfaces for before-and-after comparison.
 
 ## Recommended Chaining
-- +get_analysis_query_schema -> te_meta +list_events -> te_meta +list_properties -> +create_metric
+- +get_analysis_query_schema -> analysis_meta +list_events -> analysis_meta +list_properties -> +create_metric
 - +list_metrics -> +create_metric -> +get_metric

package/skills/te-meta/references/create-project-mark-time.md

@@ -1,4 +1,4 @@
-# te_meta +create_project_mark_time (Create Project Date Marker)
+# analysis_meta +create_project_mark_time (Create Project Date Marker)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -10,9 +10,9 @@ Domain: **Project Configuration**
 
 ## Command
 ```bash
-te-cli te_meta +create_project_mark_time --project_id 1 --marked_at '2026-04-09 10:00' --content demo
-te-cli te_meta +create_project_mark_time --project_id 1 --marked_at '2026-04-09 10:00' --zone_offset 8 --content demo --is_visible 1
-te-cli te_meta +create_project_mark_time --dry-run
+ae-cli analysis_meta +create_project_mark_time --project_id 1 --marked_at '2026-04-09 10:00' --content demo
+ae-cli analysis_meta +create_project_mark_time --project_id 1 --marked_at '2026-04-09 10:00' --zone_offset 8 --content demo --is_visible 1
+ae-cli analysis_meta +create_project_mark_time --dry-run
 ```
 
 ## Parameters

package/skills/te-meta/references/create-virtual-event.md

@@ -1,4 +1,4 @@
-# te_meta +create_virtual_event (Create Virtual Event)
+# analysis_meta +create_virtual_event (Create Virtual Event)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -22,17 +22,17 @@ Domain: **Metadata Query**
 - Do not generate the final `events` / `filter` until the document review and prerequisite command calls above are complete.
 
 ## Prerequisite Call Chain (Required for Constructing events/filter)
-1. Read `get-filter-schema.md`, then call `te-cli te_analysis +get_filter_schema` to get the filter structure.
-2. Read `list-events.md`, then call `te-cli te_meta +list_events --project_id 1` to get available events.
-3. Read `list-properties.md`, then call `te-cli te_meta +list_properties --project_id 1` to get properties available for filtering.
+1. Read `get-filter-schema.md`, then call `ae-cli analysis +get_filter_schema` to get the filter structure.
+2. Read `list-events.md`, then call `ae-cli analysis_meta +list_events --project_id 1` to get available events.
+3. Read `list-properties.md`, then call `ae-cli analysis_meta +list_properties --project_id 1` to get properties available for filtering.
 4. Build `events` / `filter` from the schema + metadata, then call `+create_virtual_event`.
 5. Example events JSON: `[{"eventName":"purchase"},{"eventName":"add_to_cart"}]`
 
 ## Commands
 ```bash
-te-cli te_meta +create_virtual_event --project_id 1 --event_name ta@demo --event_desc demo --events '[{"eventName":"purchase"}]'
-te-cli te_meta +create_virtual_event --project_id 1 --event_name ta@demo2 --event_desc demo --remark demo --events '[{"eventName":"add_to_cart"}]' --filter '{}' --override true
-te-cli te_meta +create_virtual_event --dry-run
+ae-cli analysis_meta +create_virtual_event --project_id 1 --event_name ta@demo --event_desc demo --events '[{"eventName":"purchase"}]'
+ae-cli analysis_meta +create_virtual_event --project_id 1 --event_name ta@demo2 --event_desc demo --remark demo --events '[{"eventName":"add_to_cart"}]' --filter '{}' --override true
+ae-cli analysis_meta +create_virtual_event --dry-run
 ```
 
 ## Parameters
@@ -42,8 +42,8 @@ te-cli te_meta +create_virtual_event --dry-run
 | `--event_name` | Yes | Unique name for the virtual event (must start with 'ta@') |
 | `--event_desc` | Yes | Display name/description |
 | `--remark` | No | Optional remarks |
-| `--events` | Yes | JSON array of events to combine. MUST follow `+get_filter_schema`, and event/property fields must come from `te_meta +list_events` / `te_meta +list_properties` in the same `project_id`. |
-| `--filter` | No | Optional global filter JSON for all events. If provided, MUST follow `+get_filter_schema`, and referenced fields must come from `te_meta +list_properties`. |
+| `--events` | Yes | JSON array of events to combine. MUST follow `+get_filter_schema`, and event/property fields must come from `analysis_meta +list_events` / `analysis_meta +list_properties` in the same `project_id`. |
+| `--filter` | No | Optional global filter JSON for all events. If provided, MUST follow `+get_filter_schema`, and referenced fields must come from `analysis_meta +list_properties`. |
 | `--override` | No | Whether to override if event already exists. Default: false |
 
 ## Decision Rules
@@ -60,5 +60,5 @@ te-cli te_meta +create_virtual_event --dry-run
 - If the result after writing does not match expectations, immediately reread the corresponding list/get interfaces for before-and-after comparison.
 
 ## Recommended Chaining
-- +get_filter_schema -> te_meta +list_events -> te_meta +list_properties -> +create_virtual_event
+- +get_filter_schema -> analysis_meta +list_events -> analysis_meta +list_properties -> +create_virtual_event
 - +list_events -> +create_virtual_event

package/skills/te-meta/references/create-virtual-property.md

@@ -1,4 +1,4 @@
-# te_meta +create_virtual_property (Create Virtual Property)
+# analysis_meta +create_virtual_property (Create Virtual Property)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -23,18 +23,18 @@ Domain: **Metadata Query**
 - Do not submit the final SQL and event-association configuration until the above docs have been read and the prerequisite commands have been run.
 
 ## Prerequisite Call Chain (required for building SQL and relations)
-1. Read `list-properties.md`, then run `te-cli te_meta +list_properties --project_id 1` to get the available properties.
+1. Read `list-properties.md`, then run `ae-cli analysis_meta +list_properties --project_id 1` to get the available properties.
 2. Use `--table_type` to determine the SQL field source (event or user scope).
 3. Write `--sql_expression` using only fields confirmed in the previous step; the expression must conform to Trino syntax.
-4. If `--sql_event_relation_type=relation_by_setting`, read `list-events.md`, then run `te-cli te_meta +list_events --project_id 1` to get the available events and build `--related_events`.
+4. If `--sql_event_relation_type=relation_by_setting`, read `list-events.md`, then run `ae-cli analysis_meta +list_events --project_id 1` to get the available events and build `--related_events`.
 5. Call `+create_virtual_property` to create the virtual property.
 6. Example `sql_expression`: `property_a + property_b` or `CASE WHEN status = 1 THEN 'active' ELSE 'inactive' END`.
 
 ## Command
 ```bash
-te-cli te_meta +create_virtual_property --project_id 1 --property_name '#vp@demo' --table_type event --select_type string --sql_expression 'event_name' --sql_event_relation_type relation_default
-te-cli te_meta +create_virtual_property --project_id 1 --property_name '#vp@demo' --property_desc demo --table_type event --select_type string --sql_expression "CASE WHEN status = 1 THEN 'active' ELSE 'inactive' END" --sql_event_relation_type relation_by_setting --related_events '[{"eventName":"purchase"}]' --property_remark demo
-te-cli te_meta +create_virtual_property --dry-run
+ae-cli analysis_meta +create_virtual_property --project_id 1 --property_name '#vp@demo' --table_type event --select_type string --sql_expression 'event_name' --sql_event_relation_type relation_default
+ae-cli analysis_meta +create_virtual_property --project_id 1 --property_name '#vp@demo' --property_desc demo --table_type event --select_type string --sql_expression "CASE WHEN status = 1 THEN 'active' ELSE 'inactive' END" --sql_event_relation_type relation_by_setting --related_events '[{"eventName":"purchase"}]' --property_remark demo
+ae-cli analysis_meta +create_virtual_property --dry-run
 ```
 
 ## Parameters
@@ -45,9 +45,9 @@ te-cli te_meta +create_virtual_property --dry-run
 | `--property_desc` | No | Display name/description |
 | `--table_type` | Yes | Table type. event: create virtual event property(virtual property generated based on event or user properties), user: create virtual user property(virtual property generated based on user properties) |
 | `--select_type` | Yes | Data type: string, number, bool, datetime |
-| `--sql_expression` | Yes | SQL expression for computing the property. MUST be built from fields confirmed by `te_meta +list_properties` in the same `project_id`, and MUST conform to Trino syntax (for example, columns starting with '#' or containing '@' should be double-quoted). |
+| `--sql_expression` | Yes | SQL expression for computing the property. MUST be built from fields confirmed by `analysis_meta +list_properties` in the same `project_id`, and MUST conform to Trino syntax (for example, columns starting with '#' or containing '@' should be double-quoted). |
 | `--sql_event_relation_type` | Yes | Type of associating attributes with events, relation_default: auto; relation_always: all events; relation_by_setting: specified events |
-| `--related_events` | No | Optional JSON array of related events. When `sql_event_relation_type=relation_by_setting`, this field is required and event names MUST come from `te_meta +list_events` in the same `project_id`. |
+| `--related_events` | No | Optional JSON array of related events. When `sql_event_relation_type=relation_by_setting`, this field is required and event names MUST come from `analysis_meta +list_events` in the same `project_id`. |
 | `--property_remark` | No | Optional property remark |
 
 ## Decision Rules

package/skills/te-meta/references/delete-project-mark-times.md

@@ -1,4 +1,4 @@
-# te_meta +delete_project_mark_times (Delete Project Mark Times)
+# analysis_meta +delete_project_mark_times (Delete Project Mark Times)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -9,8 +9,8 @@ Domain: **Project Configuration**
 
 ## Commands
 ```bash
-te-cli te_meta +delete_project_mark_times --project_id 1 --mark_time_ids '[]'
-te-cli te_meta +delete_project_mark_times --dry-run
+ae-cli analysis_meta +delete_project_mark_times --project_id 1 --mark_time_ids '[]'
+ae-cli analysis_meta +delete_project_mark_times --dry-run
 ```
 
 ## Parameters

package/skills/te-meta/references/delete-track-items.md

@@ -1,4 +1,4 @@
-# te_meta +delete_track_items (Delete Track Program Items)
+# analysis_meta +delete_track_items (Delete Track Program Items)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -10,8 +10,8 @@ Domain: **Project Configuration**
 
 ## Command
 ```bash
-te-cli te_meta +delete_track_items --project_id 1 --delete_data '{}'
-te-cli te_meta +delete_track_items --dry-run
+ae-cli analysis_meta +delete_track_items --project_id 1 --delete_data '{}'
+ae-cli analysis_meta +delete_track_items --dry-run
 ```
 
 ## Parameters

package/skills/te-meta/references/get-metric.md

@@ -1,4 +1,4 @@
-# te_meta +get_metric (View Metric Details)
+# analysis_meta +get_metric (View Metric Details)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -10,8 +10,8 @@ Domain: **Metadata Query**
 
 ## Commands
 ```bash
-te-cli te_meta +get_metric --project_id 1 --metric_id 1
-te-cli te_meta +get_metric --dry-run
+ae-cli analysis_meta +get_metric --project_id 1 --metric_id 1
+ae-cli analysis_meta +get_metric --dry-run
 ```
 
 ## Parameters

package/skills/te-meta/references/get-project-config.md

@@ -1,4 +1,4 @@
-# te_meta +get_project_config (Read Project Analysis Configuration)
+# analysis_meta +get_project_config (Read Project Analysis Configuration)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -10,8 +10,8 @@ Domain: **Project Configuration**
 
 ## Command
 ```bash
-te-cli te_meta +get_project_config --project_id 1
-te-cli te_meta +get_project_config --dry-run
+ae-cli analysis_meta +get_project_config --project_id 1
+ae-cli analysis_meta +get_project_config --dry-run
 ```
 
 ## Parameters

package/skills/te-meta/references/get-track-program.md

@@ -1,4 +1,4 @@
-# te_meta +get_track_program (Read Tracking Plan Baseline)
+# analysis_meta +get_track_program (Read Tracking Plan Baseline)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -10,8 +10,8 @@ Domain: **Project Configuration**
 
 ## Commands
 ```bash
-te-cli te_meta +get_track_program --project_id 1
-te-cli te_meta +get_track_program --dry-run
+ae-cli analysis_meta +get_track_program --project_id 1
+ae-cli analysis_meta +get_track_program --dry-run
 ```
 
 ## Parameters

package/skills/te-meta/references/list-entities.md

@@ -1,4 +1,4 @@
-# te_meta +list_entities (Entity Search)
+# analysis_meta +list_entities (Entity Search)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -10,9 +10,9 @@ Domain: **Entity Query**
 
 ## Command
 ```bash
-ae-cli te_meta +list_entities --project_id 1
-ae-cli te_meta +list_entities --project_id 1 --event_name demo
-ae-cli te_meta +list_entities --dry-run
+ae-cli analysis_meta +list_entities --project_id 1
+ae-cli analysis_meta +list_entities --project_id 1 --event_name demo
+ae-cli analysis_meta +list_entities --dry-run
 ```
 
 ## Parameters