@thinkingai/ae-cli 1.0.1 → 1.0.15

package/skills/{te-audience/references/list-tag-members.md → ae-analysis/references/list_tag_members.md}

@@ -1,17 +1,20 @@
-# te_audience +list_tag_members (View Tag Members)
+# analysis_audience +list_tag_members (View Tag Members)
 
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
 
 Domain: **Tag Management**
 
 ## Use Cases
-- List members in the specified tag. Returns member information such as user property values and total user count for the selected snapshot date.
+- List members in the specified tag.
+- Supports payload governance parameters: `query`, `fields`, `limit`, `offset`.
+- Returns a paginated envelope (items + total + limit + offset + hasMore) for the selected snapshot date.
 
 ## Commands
 ```bash
-te-cli te_audience +list_tag_members --project_id 1 --tag_name demo
-te-cli te_audience +list_tag_members --project_id 1 --tag_name demo --snapshot_date 2026-04-01 --property_names '["#user_id","name"]' --use_cache false
-te-cli te_audience +list_tag_members --dry-run
+ae-cli analysis_audience +list_tag_members --project_id <project_id> --tag_name demo
+ae-cli analysis_audience +list_tag_members --project_id <project_id> --tag_name demo --snapshot_date 2026-04-01 --property_names '["#user_id","name"]' --use_cache false
+ae-cli analysis_audience +list_tag_members --project_id <project_id> --tag_name demo --query user_001 --fields '["#user_id","name"]' --limit 20 --offset 0
+ae-cli analysis_audience +list_tag_members --dry-run
 ```
 
 ## Parameters
@@ -22,6 +25,10 @@ te-cli te_audience +list_tag_members --dry-run
 | `--snapshot_date` | No | Optional tag snapshot date. Format: YYYY-MM-DD |
 | `--property_names` | No | Optional list of user property names (JSON array) |
 | `--use_cache` | No | Whether to use cache. Default: true |
+| `--query` | No | Optional keyword filter on `#user_id` and selected properties. |
+| `--fields` | No | Optional return field list (JSON array). Invalid fields will fail with `INVALID_FIELDS`. |
+| `--limit` | No | Optional page size. Default: 20, max: 50. |
+| `--offset` | No | Optional page offset. Default: 0. |
 
 ## Decision Rules
 - For the first execution, it is recommended to pass only the required parameters (`--project_id`, `--tag_name`) and add optional parameters after confirming the path works.

package/skills/{te-audience/references/list-tags.md → ae-analysis/references/list_tags.md}

@@ -1,17 +1,20 @@
-# te_audience +list_tags (Tag Search)
+# analysis_audience +list_tags (Tag Search)
 
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
 
 Domain: **Tag Management**
 
 ## Use Cases
-- List tag metadata accessible to the current user in the project. Supports keyword filtering and returns tag names, display names, types, status, user counts, and related metadata, but not tag members.
+- List tag metadata accessible to the current user in the project.
+- Supports payload governance parameters: `query`, `fields`, `limit`, `offset`.
+- Returns a paginated envelope (items + total + limit + offset + hasMore), not tag members.
 
 ## Commands
 ```bash
-te-cli te_audience +list_tags --project_id 1
-te-cli te_audience +list_tags --project_id 1 --query demo
-te-cli te_audience +list_tags --dry-run
+ae-cli analysis_audience +list_tags --project_id <project_id>
+ae-cli analysis_audience +list_tags --project_id <project_id> --query demo
+ae-cli analysis_audience +list_tags --project_id <project_id> --fields '["id","clusterName","usersNum"]' --limit 20 --offset 0
+ae-cli analysis_audience +list_tags --dry-run
 ```
 
 ## Parameters
@@ -19,6 +22,9 @@ te-cli te_audience +list_tags --dry-run
 |---|---|---|
 | `--project_id` / `-p` | Yes | Project ID |
 | `--query` / `-q` | No | Optional keyword filter. Performs fuzzy matching against tag names, display names, and remarks; if omitted, all tags are returned. |
+| `--fields` | No | Optional return field list (JSON array). Invalid fields will fail with `INVALID_FIELDS`. |
+| `--limit` | No | Optional page size. Default: 20, max: 50. |
+| `--offset` | No | Optional page offset. Default: 0. |
 
 ## Decision Rules
 - For the first execution, it is recommended to pass only the required parameters (`--project_id`) and add optional parameters after confirming the path works.

package/skills/{te-analysis/references/load-filters.md → ae-analysis/references/load_filters.md}

@@ -1,6 +1,6 @@
-# te_analysis +load_filters (load filter candidate values)
+# analysis +load_filters (load filter candidate values)
 
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
 
 Domain: **Model Analysis**
 
@@ -14,9 +14,9 @@ Domain: **Model Analysis**
 
 ## Commands
 ```bash
-te-cli te_analysis +load_filters --project_id 1 --quot demo --table_type event
-te-cli te_analysis +load_filters --project_id 1 --quot demo --table_type event --event_name demo --inputdata demo --zone_offset 8 --cluster_date_policy SPECIFIED --specified_cluster_date 2026-04-08 --is_report true
-te-cli te_analysis +load_filters --dry-run
+ae-cli analysis +load_filters --project_id <project_id> --quot demo --table_type event
+ae-cli analysis +load_filters --project_id <project_id> --quot demo --table_type event --event_name demo --inputdata demo --zone_offset 8 --cluster_date_policy SPECIFIED --specified_cluster_date 2026-04-08 --is_report true
+ae-cli analysis +load_filters --dry-run
 ```
 
 ## Parameters

package/skills/{te-analysis/references/query-adhoc.md → ae-analysis/references/query_adhoc.md}

@@ -1,12 +1,12 @@
-# te_analysis +query_adhoc (Ad Hoc Analysis Execution)
+# analysis +query_adhoc (Ad Hoc Analysis Execution)
 
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
 
 Domain: **Model analysis**
 
 ## Use Cases
 - Precondition helper: call `+get_analysis_query_schema` to get the structure before using this tool.
-- When constructing a real `qp`, you must supplement it with real project metadata; first call `te_meta +list_events` and `te_meta +list_properties`.
+- When constructing a real `qp`, you must supplement it with real project metadata; first call `analysis_meta +list_events` and `analysis_meta +list_properties`.
 - Event analysis: metrics such as event trigger counts, user counts, sums, averages, and more.
 - Retention analysis: metrics such as user churn and retention.
 - Funnel analysis: metrics such as multi-step conversion.
@@ -22,23 +22,23 @@ Domain: **Model analysis**
 
 ## Mandatory prerequisites (MUST)
 - Before constructing `--qp`, you must first read and follow these reference documents:
-  - [`./get-analysis-query-schema.md`](./get-analysis-query-schema.md)
-  - [`../../te-meta/references/list-events.md`](../../te-meta/references/list-events.md)
-  - [`../../te-meta/references/list-properties.md`](../../te-meta/references/list-properties.md)
+  - [`./get_analysis_query_schema.md`](./get_analysis_query_schema.md)
+  - [`./list_events.md`](./list_events.md)
+  - [`./list_properties.md`](./list_properties.md)
 - Do not generate the final `qp` until the documentation review and prerequisite command calls are complete.
 
 ## Prerequisite call chain (required for constructing qp)
 1. First determine `--model_type`.
-2. Read `get-analysis-query-schema.md`, then call `te-cli te_analysis +get_analysis_query_schema --model_type <model_type>` to get the structure.
-3. Read `list-events.md`, then call `te-cli te_meta +list_events --project_id 1` to get the available events.
-4. Read `list-properties.md`, then call `te-cli te_meta +list_properties --project_id 1` to get the available properties.
+2. Read `get_analysis_query_schema.md`, then call `ae-cli analysis +get_analysis_query_schema --model_type <model_type>` to get the structure.
+3. Read `list_events.md`, then call `ae-cli analysis_meta +list_events --project_id <project_id>` to get the available events.
+4. Read `list_properties.md`, then call `ae-cli analysis_meta +list_properties --project_id <project_id>` to get the available properties.
 5. Build `qp` from the schema + metadata, then call `+query_adhoc`.
 
 ## Command
 ```bash
-te-cli te_analysis +query_adhoc --project_id 1 --model_type event --qp '{}'
-te-cli te_analysis +query_adhoc --project_id 1 --model_type event --qp '{}' --zone_offset 8 --request_id demo --use_cache true --is_sort_by_columns true --resolve_recent_day true --timeout_minutes 8
-te-cli te_analysis +query_adhoc --dry-run
+ae-cli analysis +query_adhoc --project_id <project_id> --model_type event --qp '{}'
+ae-cli analysis +query_adhoc --project_id <project_id> --model_type event --qp '{}' --fields '["date","event"]' --limit 10 --offset 0 --zone_offset 8 --request_id demo --use_cache true --is_sort_by_columns true --resolve_recent_day true --timeout_minutes 8
+ae-cli analysis +query_adhoc --dry-run
 ```
 
 ## Parameters
@@ -46,16 +46,21 @@ te-cli te_analysis +query_adhoc --dry-run
 |---|---|---|
 | `--project_id` / `-p` | Yes | Project ID used to identify the analysis project |
 | `--model_type` | Yes | Model type. Supported values: event, retention, funnel, distribution, attribution, heat_map, interval, path, rank_list, prop_analysis, sql. |
-| `--qp` | Yes | Query parameter JSON. MUST call `+get_analysis_query_schema` first, and use event/property metadata from `te_meta +list_events` / `te_meta +list_properties` in the same `project_id`. |
+| `--qp` | Yes | Query parameter JSON. MUST call `+get_analysis_query_schema` first, and use event/property metadata from `analysis_meta +list_events` / `analysis_meta +list_properties` in the same `project_id`. |
 | `--request_id` | No | Optional unique request ID used for tracking and deduplication. Generated automatically if omitted. |
 | `--use_cache` | No | Whether to use result cache. Default: true |
 | `--zone_offset` | No | Time zone offset in hours. For example, UTC+8 is 8 and UTC-5 is -5 |
 | `--is_sort_by_columns` | No | Whether to sort query results by columns. Default: false |
 | `--resolve_recent_day` | No | Whether to resolve relative time expressions such as "last 7 days". Default: false |
+| `--fields` | No | Optional fields to return. Must match column names in result. Invalid fields cause INVALID_FIELDS error. |
+| `--limit` | No | Optional limit. Default: 20, maximum: 50. |
+| `--offset` | No | Optional offset. Default: 0. |
 | `--timeout_minutes` | No | Query timeout in minutes. If the query exceeds this time, it will be cancelled automatically. |
 
 ## Decision Rules
 - On the first run, start with only the required parameters (`--project_id`,`--model_type`,`--qp`), and add optional parameters after confirming the path works.
+- For pagination, use `--limit` and `--offset` together. Default limit is 20.
+- Use `--fields` to select specific columns for lighter response payloads.
 - `qp` cannot be written from experience alone: it must satisfy both the schema structure and the project metadata constraints.
 - Before calling `list_events` / `list_properties`, you must first study the corresponding reference documents.
 - Wrap JSON parameters in single quotes (for example `--qp '{}'`) to avoid shell escaping issues.
@@ -67,5 +72,5 @@ te-cli te_analysis +query_adhoc --dry-run
 - If the query times out or results are abnormal, first narrow the time range / grouping dimensions, then split the subqueries to locate the issue.
 
 ## Recommended chaining
-- +get_analysis_query_schema -> te_meta +list_events -> te_meta +list_properties -> +query_adhoc
+- +get_analysis_query_schema -> analysis_meta +list_events -> analysis_meta +list_properties -> +query_adhoc
 - +list_events -> +list_properties -> +query_adhoc -> +drilldown_users -> +drilldown_user_events

package/skills/{te-analysis/references/query-dashboard-detail.md → ae-analysis/references/query_dashboard_detail.md}

@@ -1,6 +1,6 @@
-# te_analysis +query_dashboard_detail (read dashboard structure)
+# analysis +query_dashboard_detail (read dashboard structure)
 
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
 
 Domain: **Dashboard Management**
 
@@ -13,8 +13,8 @@ Domain: **Dashboard Management**
 
 ## Commands
 ```bash
-te-cli te_analysis +query_dashboard_detail --project_id 1 --dashboard_id 1
-te-cli te_analysis +query_dashboard_detail --dry-run
+ae-cli analysis +query_dashboard_detail --project_id <project_id> --dashboard_id 1
+ae-cli analysis +query_dashboard_detail --dry-run
 ```
 
 ## Parameters

package/skills/{te-analysis/references/query-dashboard-report-data.md → ae-analysis/references/query_dashboard_report_data.md}

@@ -1,6 +1,6 @@
-# te_analysis +query_dashboard_report_data (Batch Query Dashboard Report Data)
+# analysis +query_dashboard_report_data (Batch Query Dashboard Report Data)
 
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
 
 Domain: **Dashboard management**
 
@@ -12,22 +12,22 @@ Domain: **Dashboard management**
 
 ## Mandatory prerequisites (MUST)
 - Before constructing `--filters`, you must first read and follow these reference documents:
-  - [`./get-filter-schema.md`](./get-filter-schema.md)
-  - [`../../te-meta/references/list-events.md`](../../te-meta/references/list-events.md)
-  - [`../../te-meta/references/list-properties.md`](../../te-meta/references/list-properties.md)
+  - [`./get_filter_schema.md`](./get_filter_schema.md)
+  - [`./list_events.md`](./list_events.md)
+  - [`./list_properties.md`](./list_properties.md)
 - Do not generate the final `filters` until the documentation review and prerequisite command calls are complete.
 
 ## Prerequisite call chain (required for constructing filters)
-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`.
-3. Read `list-properties.md`, then call `te-cli te_meta +list_properties --project_id 1`.
+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 <project_id>`.
+3. Read `list_properties.md`, then call `ae-cli analysis_meta +list_properties --project_id <project_id>`.
 4. Build `filters` from the schema + metadata, then call `+query_dashboard_report_data`.
 
 ## Command
 ```bash
-te-cli te_analysis +query_dashboard_report_data --project_id 1 --dashboard_id 1
-te-cli te_analysis +query_dashboard_report_data --project_id 1 --dashboard_id 1 --filters '{}' --start_date 2026-04-08 --end_date 2026-04-08 --time_granularity day --use_cache true --report_ids '[1001]'
-te-cli te_analysis +query_dashboard_report_data --dry-run
+ae-cli analysis +query_dashboard_report_data --project_id <project_id> --dashboard_id 1
+ae-cli analysis +query_dashboard_report_data --project_id <project_id> --dashboard_id 1 --filters '{}' --start_date 2026-04-08 --end_date 2026-04-08 --time_granularity day --use_cache true --report_ids '[1001]'
+ae-cli analysis +query_dashboard_report_data --dry-run
 ```
 
 ## Parameters
@@ -35,7 +35,7 @@ te-cli te_analysis +query_dashboard_report_data --dry-run
 |---|---|---|
 | `--project_id` / `-p` | Yes | Project ID |
 | `--dashboard_id` / `-d` | Yes | Dashboard ID |
-| `--filters` | No | Optional filter JSON. If provided, MUST follow `+get_filter_schema`, and referenced fields must come from `te_meta +list_properties` in the same `project_id`. |
+| `--filters` | No | Optional filter JSON. If provided, MUST follow `+get_filter_schema`, and referenced fields must come from `analysis_meta +list_properties` in the same `project_id`. |
 | `--start_date` | No | Optional start date. Format: yyyy-MM-dd |
 | `--end_date` | No | Optional end date. Format: yyyy-MM-dd |
 | `--time_granularity` | No | Optional time granularity used to override the report default. Supported values: minute, minute5, minute10, hour, day, week, month, quarter, year, total. |
@@ -56,5 +56,5 @@ te-cli te_analysis +query_dashboard_report_data --dry-run
 - If the query times out or results are abnormal, first narrow the time range / grouping dimensions, then split the subqueries to locate the issue.
 
 ## Recommended chaining
-- +get_filter_schema -> te_meta +list_events -> te_meta +list_properties -> +query_dashboard_report_data
+- +get_filter_schema -> analysis_meta +list_events -> analysis_meta +list_properties -> +query_dashboard_report_data
 - +list_dashboards -> +query_dashboard_detail -> +query_dashboard_report_data

package/skills/{te-analysis/references/query-entity-details.md → ae-analysis/references/query_entity_details.md}

@@ -1,6 +1,6 @@
-# te_analysis +query_entity_details (query entity details)
+# analysis +query_entity_details (query entity details)
 
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
 
 Domain: **Entity Detail Queries**
 
@@ -11,23 +11,23 @@ Domain: **Entity Detail Queries**
 
 ## Mandatory Prerequisites (MUST)
 - Before building `--definition` / `--properties`, you must first read and follow the following reference docs:
-  - [`../../te-audience/references/get-cluster-definition-schema.md`](../../te-audience/references/get-cluster-definition-schema.md)
-  - [`../../te-meta/references/list-events.md`](../../te-meta/references/list-events.md)
-  - [`../../te-meta/references/list-properties.md`](../../te-meta/references/list-properties.md)
+  - [`./get_cluster_definition_schema.md`](./get_cluster_definition_schema.md)
+  - [`./list_events.md`](./list_events.md)
+  - [`./list_properties.md`](./list_properties.md)
 - Do not generate final `definition` / `properties` until the above docs have been read and the prerequisite commands have been called.
 
 ## Prerequisite Call Chain (required for building definition/properties)
 1. First confirm the cluster type (condition / sql).
-2. Read `get-cluster-definition-schema.md`, then call `ae-cli te_audience +get_cluster_definition_schema --cluster_type <condition|sql>` to get the structure.
-3. Read `list-events.md`, then call `ae-cli te_meta +list_events --project_id 1`.
-4. Read `list-properties.md`, then call `ae-cli te_meta +list_properties --project_id 1`.
+2. Read `get_cluster_definition_schema.md`, then call `ae-cli analysis_audience +get_cluster_definition_schema --cluster_type <condition|sql>` to get the structure.
+3. Read `list_events.md`, then call `ae-cli analysis_meta +list_events --project_id <project_id>`.
+4. Read `list_properties.md`, then call `ae-cli analysis_meta +list_properties --project_id <project_id>`.
 5. Build `definition` (and optional `properties`) based on the schema and metadata, then call `+query_entity_details`.
 
 ## Commands
 ```bash
-ae-cli te_analysis +query_entity_details --project_id 1 --definition '{}'
-ae-cli te_analysis +query_entity_details --project_id 1 --entity_id 1001 --definition '{}' --properties '{}' --sort_by time --sort_order desc --limit 100 --zone_offset 8 --use_cache true
-ae-cli te_analysis +query_entity_details --dry-run
+ae-cli analysis +query_entity_details --project_id <project_id> --definition '{}'
+ae-cli analysis +query_entity_details --project_id <project_id> --entity_id 1001 --definition '{}' --properties '{}' --sort_by time --sort_order desc --limit 20 --zone_offset 8 --use_cache true
+ae-cli analysis +query_entity_details --dry-run
 ```
 
 ## Parameters
@@ -35,11 +35,11 @@ ae-cli te_analysis +query_entity_details --dry-run
 |---|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | `--project_id` / `-p` | Yes | Project ID                                                                                                                                                                                                                              |
 | `--entity_id` | No | Optional entity ID used in multi-entity scenarios. If omitted, the default user entity is used.                                                                                                                                         |
-| `--definition` | Yes | Cluster definition JSON. MUST call `+get_cluster_definition_schema` first, then fill valid event/property names from `te_meta +list_events` / `te_meta +list_properties` in the same `project_id`.                                      |
-| `--properties` | No | Optional display properties JSON, for example `[{"columnName":"#user_id","tableType":"0"},{"columnName":"device_id","tableType":"0"}]`. If provided, property names should come from `te_meta +list_properties` in the same `project_id`. |
+| `--definition` | Yes | Cluster definition JSON. MUST call `+get_cluster_definition_schema` first, then fill valid event/property names from `analysis_meta +list_events` / `analysis_meta +list_properties` in the same `project_id`.                                      |
+| `--properties` | No | Optional display properties JSON, for example `[{"columnName":"#user_id","tableType":"0"},{"columnName":"device_id","tableType":"0"}]`. If provided, property names should come from `analysis_meta +list_properties` in the same `project_id`. |
 | `--sort_by` | No | Optional sort field                                                                                                                                                                                                                     |
 | `--sort_order` | No | Optional sort order. Supported values: asc and desc                                                                                                                                                                                     |
-| `--limit` | No | Optional result limit. Default: 1000, maximum: 10000                                                                                                                                                                                    |
+| `--limit` | No | Optional result limit. Default: 20, maximum: 50                                                                                                                                                                                         |
 | `--zone_offset` | No | Time zone offset. For example, UTC+8 is 8                                                                                                                                                                                               |
 | `--use_cache` | No | Whether to use cache. Default: true                                                                                                                                                                                                     |
 
@@ -56,5 +56,5 @@ ae-cli te_analysis +query_entity_details --dry-run
 - If the query times out or the result is abnormal, first reduce the time range/grouping dimensions, then split the query to locate the issue.
 
 ## Recommended Chaining
-- +get_cluster_definition_schema -> te_meta +list_events -> te_meta +list_properties -> +query_entity_details
+- +get_cluster_definition_schema -> analysis_meta +list_events -> analysis_meta +list_properties -> +query_entity_details
 - +query_entity_details -> +query_event_details -> +build_event_details_sql

package/skills/{te-analysis/references/query-event-details.md → ae-analysis/references/query_event_details.md}

@@ -1,32 +1,32 @@
-# te_analysis +query_event_details (Query Event Details)
+# analysis +query_event_details (Query Event Details)
 
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
 
 Domain: **Event detail queries**
 
 ## Use Cases
 - When constructing `filters` / `properties`, you must first obtain the filter schema and the project metadata for real events/properties.
 - Query event detail data. Supports time range, filters, display properties, sorting, and result limits.
-- Query event detail data.
+- Time can be specified via `--relative_date_range` OR (`--start_time` AND `--end_time`).
 
 ## Mandatory prerequisites (MUST)
 - Before constructing `--filters` / `--properties`, you must first read and follow these reference documents:
-  - [`./get-filter-schema.md`](./get-filter-schema.md)
-  - [`../../te-meta/references/list-events.md`](../../te-meta/references/list-events.md)
-  - [`../../te-meta/references/list-properties.md`](../../te-meta/references/list-properties.md)
+  - [`./get_filter_schema.md`](./get_filter_schema.md)
+  - [`./list_events.md`](./list_events.md)
+  - [`./list_properties.md`](./list_properties.md)
 - Do not generate the final `filters` / `properties` until the documentation review and prerequisite command calls are complete.
 
 ## Prerequisite call chain (required for constructing filters/properties)
-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 confirm the available event names.
-3. Read `list-properties.md`, then call `te-cli te_meta +list_properties --project_id 1` to get the available properties.
+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 <project_id>` to confirm the available event names.
+3. Read `list_properties.md`, then call `ae-cli analysis_meta +list_properties --project_id <project_id>` to get the available properties.
 4. Build `filters` / `properties` from the schema + metadata, then call `+query_event_details`.
 
 ## Command
 ```bash
-te-cli te_analysis +query_event_details --project_id 1 --event_name login --start_time '2026-04-08 00:00:00' --end_time '2026-04-08 23:59:59'
-te-cli te_analysis +query_event_details --project_id 1 --event_name login --relative_date_range 0-7 --filters '{}' --properties '{}' --sort_by time --sort_order desc --limit 100 --zone_offset 8 --use_cache true
-te-cli te_analysis +query_event_details --dry-run
+ae-cli analysis +query_event_details --project_id <project_id> --event_name login --start_time '2026-04-08 00:00:00' --end_time '2026-04-08 23:59:59'
+ae-cli analysis +query_event_details --project_id <project_id> --event_name login --relative_date_range 0-7 --filters '{}' --properties '{}' --sort_by time --sort_order desc --limit 20 --zone_offset 8 --use_cache true
+ae-cli analysis +query_event_details --dry-run
 ```
 
 ## Parameters
@@ -34,11 +34,11 @@ te-cli te_analysis +query_event_details --dry-run
 |---|---|---|
 | `--project_id` / `-p` | Yes | Project ID |
 | `--event_name` | Yes | Event name |
-| `--start_time` | No | Start time. Format: yyyy-MM-dd HH:mm:ss |
-| `--end_time` | No | End time. Format: yyyy-MM-dd HH:mm:ss |
+| `--start_time` | No | Start time. Format: yyyy-MM-dd HH:mm:ss. Required if not using relative_date_range. |
+| `--end_time` | No | End time. Format: yyyy-MM-dd HH:mm:ss. Required if not using relative_date_range. |
 | `--relative_date_range` | No | Optional relative date range in m-n format. For example, 0-7 means the most recent 7 days including today. Use either this field or start_time/end_time. |
-| `--filters` | No | Optional filter JSON. If provided, MUST follow `+get_filter_schema`, and referenced fields must come from `te_meta +list_properties` in the same `project_id`. |
-| `--properties` | No | Optional display properties JSON, for example `[{"columnName":"#user_id","tableType":"0"},{"columnName":"device_id","tableType":"0"}]`. If provided, property names should come from `te_meta +list_properties` in the same `project_id`. |
+| `--filters` | No | Optional filter JSON. If provided, MUST follow `+get_filter_schema`, and referenced fields must come from `analysis_meta +list_properties` in the same `project_id`. |
+| `--properties` | No | Optional display properties JSON, for example `[{"columnName":"#user_id","tableType":"0"},{"columnName":"device_id","tableType":"0"}]`. If provided, property names should come from `analysis_meta +list_properties` in the same `project_id`. |
 | `--sort_by` | No | Optional sort field |
 | `--sort_order` | No | Optional sort order. Supported values: asc and desc |
 | `--limit` | No | Optional result limit. Default: 1000 |
@@ -59,5 +59,5 @@ te-cli te_analysis +query_event_details --dry-run
 - If the query times out or results are abnormal, first narrow the time range / grouping dimensions, then split the subqueries to locate the issue.
 
 ## Recommended chaining
-- +get_filter_schema -> te_meta +list_events -> te_meta +list_properties -> +query_event_details
+- +get_filter_schema -> analysis_meta +list_events -> analysis_meta +list_properties -> +query_event_details
 - +query_entity_details -> +query_event_details -> +build_event_details_sql

package/skills/{te-analysis/references/query-report-data.md → ae-analysis/references/query_report_data.md}

@@ -1,6 +1,6 @@
-# te_analysis +query_report_data (query data by report)
+# analysis +query_report_data (query data by report)
 
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
 
 Domain: **Report Management**
 
@@ -13,24 +13,24 @@ Domain: **Report Management**
 
 ## Mandatory Prerequisites (MUST)
 - Before building `--filters` / `--group_by`, you must first read and follow the following reference docs:
-  - [`./get-filter-schema.md`](./get-filter-schema.md)
-  - [`./get-groupby-schema.md`](./get-groupby-schema.md)
-  - [`../../te-meta/references/list-events.md`](../../te-meta/references/list-events.md)
-  - [`../../te-meta/references/list-properties.md`](../../te-meta/references/list-properties.md)
+  - [`./get_filter_schema.md`](./get_filter_schema.md)
+  - [`./get_groupby_schema.md`](./get_groupby_schema.md)
+  - [`./list_events.md`](./list_events.md)
+  - [`./list_properties.md`](./list_properties.md)
 - Do not generate final `filters` / `group_by` until the above docs have been read and the prerequisite commands have been called.
 
 ## Prerequisite Call Chain (required for building filters/group_by)
-1. Read `get-filter-schema.md`, then call `ae-cli te_analysis +get_filter_schema` to get the filter structure.
-2. Read `get-groupby-schema.md`, then call `ae-cli te_analysis +get_groupby_schema` to get the grouping structure.
-3. Read `list-events.md`, then call `ae-cli te_meta +list_events --project_id 1`.
-4. Read `list-properties.md`, then call `ae-cli te_meta +list_properties --project_id 1`.
+1. Read `get_filter_schema.md`, then call `ae-cli analysis +get_filter_schema` to get the filter structure.
+2. Read `get_groupby_schema.md`, then call `ae-cli analysis +get_groupby_schema` to get the grouping structure.
+3. Read `list_events.md`, then call `ae-cli analysis_meta +list_events --project_id <project_id>`.
+4. Read `list_properties.md`, then call `ae-cli analysis_meta +list_properties --project_id <project_id>`.
 5. Build `filters` / `group_by` based on the schema and metadata, then call `+query_report_data`.
 
 ## Commands
 ```bash
-ae-cli te_analysis +query_report_data --project_id 1 --report_ids '[1001]'
-ae-cli te_analysis +query_report_data --project_id 1 --report_ids '[1001]' --filters '{}' --group_by '[]' --request_id demo --use_cache true --start_date 2026-04-08 --end_date 2026-04-08 --time_granularity day --timeout_minutes 8
-ae-cli te_analysis +query_report_data --dry-run
+ae-cli analysis +query_report_data --project_id <project_id> --report_ids '[1001]'
+ae-cli analysis +query_report_data --project_id <project_id> --report_ids '[1001]' --filters '{}' --group_by '[]' --request_id demo --use_cache true --start_date 2026-04-08 --end_date 2026-04-08 --time_granularity day --timeout_minutes 8
+ae-cli analysis +query_report_data --dry-run
 ```
 
 ## Parameters
@@ -38,8 +38,8 @@ ae-cli te_analysis +query_report_data --dry-run
 |---|---|---|
 | `--project_id` / `-p` | Yes | Project ID |
 | `--report_ids` | Yes | List of report IDs |
-| `--filters` | No | Optional filter JSON. If provided, MUST follow `+get_filter_schema`, and referenced fields must come from `te_meta +list_properties` in the same `project_id`. |
-| `--group_by` | No | Optional group-by JSON array. If provided, MUST follow `+get_groupby_schema`, and referenced fields must come from `te_meta +list_properties` in the same `project_id`. |
+| `--filters` | No | Optional filter JSON. If provided, MUST follow `+get_filter_schema`, and referenced fields must come from `analysis_meta +list_properties` in the same `project_id`. |
+| `--group_by` | No | Optional group-by JSON array. If provided, MUST follow `+get_groupby_schema`, and referenced fields must come from `analysis_meta +list_properties` in the same `project_id`. |
 | `--request_id` | No | Optional unique request ID. Generated automatically if omitted. |
 | `--use_cache` | No | Whether to use cache. Default: true |
 | `--start_date` | No | Optional start date in yyyy-MM-dd format |
@@ -61,5 +61,5 @@ ae-cli te_analysis +query_report_data --dry-run
 - If the query times out or the result is abnormal, first reduce the time range/grouping dimensions, then split the query to locate the issue.
 
 ## Recommended Chaining
-- +get_filter_schema -> +get_groupby_schema -> te_meta +list_events -> te_meta +list_properties -> +query_report_data
+- +get_filter_schema -> +get_groupby_schema -> analysis_meta +list_events -> analysis_meta +list_properties -> +query_report_data
 - +list_reports -> +get_report_definition -> +query_report_data

package/skills/{te-audience/references/refresh-cluster.md → ae-analysis/references/refresh_cluster.md}

@@ -1,6 +1,6 @@
-# te_audience +refresh_cluster (Trigger Cluster Recompute)
+# analysis_audience +refresh_cluster (Trigger Cluster Recompute)
 
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
 
 Domain: **Cluster Management**
 
@@ -9,8 +9,8 @@ Domain: **Cluster Management**
 
 ## Commands
 ```bash
-te-cli te_audience +refresh_cluster --project_id 1 --cluster_name demo
-te-cli te_audience +refresh_cluster --dry-run
+ae-cli analysis_audience +refresh_cluster --project_id <project_id> --cluster_name demo
+ae-cli analysis_audience +refresh_cluster --dry-run
 ```
 
 ## Parameters

package/skills/{te-audience/references/refresh-tag.md → ae-analysis/references/refresh_tag.md}

@@ -1,6 +1,6 @@
-# te_audience +refresh_tag (Trigger Tag Recompute)
+# analysis_audience +refresh_tag (Trigger Tag Recompute)
 
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
 
 Domain: **Tag Management**
 
@@ -9,8 +9,8 @@ Domain: **Tag Management**
 
 ## Commands
 ```bash
-te-cli te_audience +refresh_tag --project_id 1 --tag_name demo
-te-cli te_audience +refresh_tag --dry-run
+ae-cli analysis_audience +refresh_tag --project_id <project_id> --tag_name demo
+ae-cli analysis_audience +refresh_tag --dry-run
 ```
 
 ## Parameters

package/skills/{te-meta/references/save-track-items.md → ae-analysis/references/save_track_items.md}

@@ -1,6 +1,6 @@
-# te_meta +save_track_items (Save Track Program Items)
+# analysis_meta +save_track_items (Save Track Program Items)
 
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
 
 Domain: **Project Configuration**
 
@@ -10,8 +10,8 @@ Domain: **Project Configuration**
 
 ## Command
 ```bash
-te-cli te_meta +save_track_items --project_id 1 --track_data '{}'
-te-cli te_meta +save_track_items --dry-run
+ae-cli analysis_meta +save_track_items --project_id <project_id> --track_data '{}'
+ae-cli analysis_meta +save_track_items --dry-run
 ```
 
 ## Parameters

package/skills/{te-analysis/references/update-alert.md → ae-analysis/references/update_alert.md}

@@ -1,6 +1,6 @@
-# te_analysis +update_alert (Update Alert)
+# analysis +update_alert (Update Alert)
 
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
 
 Domain: **Metadata queries**
 
@@ -11,18 +11,18 @@ Domain: **Metadata queries**
 
 ## Mandatory prerequisites (MUST)
 - Before constructing a new `--definition`, you must first read and follow:
-  - [`./get-alert-definition-schema.md`](./get-alert-definition-schema.md)
+  - [`./get_alert_definition_schema.md`](./get_alert_definition_schema.md)
 - Do not submit the new `definition` until the documentation review and schema call are complete.
 
 ## Prerequisite call chain (required for updating definition)
-1. Read `get-alert-definition-schema.md` to understand the return structure of `+get_alert_definition_schema`.
-2. Call `te-cli te_analysis +get_alert_definition_schema` to get the schema.
+1. Read `get_alert_definition_schema.md` to understand the return structure of `+get_alert_definition_schema`.
+2. Call `ae-cli analysis +get_alert_definition_schema` to get the schema.
 3. Build a new `definition` from the schema, then call `+update_alert`.
 
 ## Command
 ```bash
-te-cli te_analysis +update_alert --project_id 1 --alert_id 1 --definition '{}'
-te-cli te_analysis +update_alert --dry-run
+ae-cli analysis +update_alert --project_id <project_id> --alert_id 1 --definition '{}'
+ae-cli analysis +update_alert --dry-run
 ```
 
 ## Parameters