@thinkingai/ae-cli 1.0.1 → 1.0.3

package/skills/te-analysis/references/build-event-details-sql.md

@@ -1,4 +1,4 @@
-# te_analysis +build_event_details_sql (generate event detail SQL)
+# analysis +build_event_details_sql (generate event detail SQL)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -17,16 +17,16 @@ Domain: **Event Detail SQL Queries**
 - Do not generate final `filters` / `properties` until the above docs have been read and the prerequisite commands have been called.
 
 ## Prerequisite Call Chain (required for 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 available event names.
-3. Read `list-properties.md`, then call `te-cli te_meta +list_properties --project_id 1` to get 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 1` to confirm available event names.
+3. Read `list-properties.md`, then call `ae-cli analysis_meta +list_properties --project_id 1` to get available properties.
 4. Build `filters` / `properties` based on the schema and metadata, then call `+build_event_details_sql`.
 
 ## Commands
 ```bash
-te-cli te_analysis +build_event_details_sql --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 +build_event_details_sql --project_id 1 --event_name login --relative_date_range 0-7 --filters '{}' --properties '{}' --sort_by time --sort_order desc --limit 100 --zone_offset 8
-te-cli te_analysis +build_event_details_sql --dry-run
+ae-cli analysis +build_event_details_sql --project_id 1 --event_name login --start_time '2026-04-08 00:00:00' --end_time '2026-04-08 23:59:59'
+ae-cli analysis +build_event_details_sql --project_id 1 --event_name login --relative_date_range 0-7 --filters '{}' --properties '{}' --sort_by time --sort_order desc --limit 100 --zone_offset 8
+ae-cli analysis +build_event_details_sql --dry-run
 ```
 
 ## Parameters
@@ -37,8 +37,8 @@ te-cli te_analysis +build_event_details_sql --dry-run
 | `--start_time` | No | Start time. Format: yyyy-MM-dd HH:mm:ss |
 | `--end_time` | No | End time. Format: yyyy-MM-dd HH:mm:ss |
 | `--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: 100 |
@@ -57,5 +57,5 @@ te-cli te_analysis +build_event_details_sql --dry-run
 - If `Invalid JSON` appears, first check the required filter schema fields, then verify that the event name/property name comes from metadata queried in the same `project_id`.
 
 ## Recommended Chaining
-- +get_filter_schema -> te_meta +list_events -> te_meta +list_properties -> +build_event_details_sql
+- +get_filter_schema -> analysis_meta +list_events -> analysis_meta +list_properties -> +build_event_details_sql
 - +query_entity_details -> +query_event_details -> +build_event_details_sql

package/skills/te-analysis/references/create-alert.md

@@ -1,4 +1,4 @@
-# te_analysis +create_alert (Create Alert)
+# analysis +create_alert (Create Alert)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -16,13 +16,13 @@ Domain: **Metadata queries**
 
 ## Prerequisite call chain (required for constructing definition)
 1. Read `get-alert-definition-schema.md` to understand the return structure of `+get_alert_definition_schema`.
-2. Call `ae-cli te_analysis +get_alert_definition_schema` to get the schema.
+2. Call `ae-cli analysis +get_alert_definition_schema` to get the schema.
 3. Build `definition` from the schema, then call `+create_alert`.
 
 ## Command
 ```bash
-ae-cli te_analysis +create_alert --project_id 1 --definition '{}'
-ae-cli te_analysis +create_alert --dry-run
+ae-cli analysis +create_alert --project_id 1 --definition '{}'
+ae-cli analysis +create_alert --dry-run
 ```
 
 ## Parameters

package/skills/te-analysis/references/create-dashboard.md

@@ -1,4 +1,4 @@
-# te_analysis +create_dashboard (create dashboard)
+# analysis +create_dashboard (create dashboard)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -12,9 +12,9 @@ Domain: **Dashboard Management**
 
 ## Commands
 ```bash
-ae-cli te_analysis +create_dashboard --project_id 1 --dashboard_name demo
-ae-cli te_analysis +create_dashboard --project_id 1 --dashboard_name demo --space_id 1 --folder_id 1 --initial_report_id 1 --note_title demo --note_content demo --note_style '{}'
-ae-cli te_analysis +create_dashboard --project_id 1 --dashboard_name demo --dry-run
+ae-cli analysis +create_dashboard --project_id 1 --dashboard_name demo
+ae-cli analysis +create_dashboard --project_id 1 --dashboard_name demo --space_id 1 --folder_id 1 --initial_report_id 1 --note_title demo --note_content demo --note_style '{}'
+ae-cli analysis +create_dashboard --project_id 1 --dashboard_name demo --dry-run
 ```
 
 ## Parameters

package/skills/te-analysis/references/create-or-update-dashboard-note.md

@@ -1,4 +1,4 @@
-# te_analysis +create_or_update_dashboard_note (Maintain Dashboard Note)
+# analysis +create_or_update_dashboard_note (Maintain Dashboard Note)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -10,9 +10,9 @@ Domain: **Dashboard management**
 
 ## Command
 ```bash
-te-cli te_analysis +create_or_update_dashboard_note --project_id 1 --dashboard_id 1 --note_title demo
-te-cli te_analysis +create_or_update_dashboard_note --project_id 1 --dashboard_id 1 --note_id 1 --note_title demo --description demo --ui_config '{}'
-te-cli te_analysis +create_or_update_dashboard_note --dry-run
+ae-cli analysis +create_or_update_dashboard_note --project_id 1 --dashboard_id 1 --note_title demo
+ae-cli analysis +create_or_update_dashboard_note --project_id 1 --dashboard_id 1 --note_id 1 --note_title demo --description demo --ui_config '{}'
+ae-cli analysis +create_or_update_dashboard_note --dry-run
 ```
 
 ## Parameters

package/skills/te-analysis/references/create-public-access-link.md

@@ -1,4 +1,4 @@
-# te_analysis +create_public_access_link (create public access link)
+# analysis +create_public_access_link (create public access link)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -11,9 +11,9 @@ Domain: **Dashboard Management**
 
 ## Commands
 ```bash
-te-cli te_analysis +create_public_access_link --project_id 1 --resource_type dashboard --resource_id 1 --access_controls '{}' --effective_at "2026-04-09 10:00:00" --expires_at "2026-04-10 10:00:00"
-te-cli te_analysis +create_public_access_link --project_id 1 --company_id 1 --resource_type dashboard --resource_id 1 --access_controls '{}' --remark demo --effective_at "2026-04-09 10:00:00" --expires_at "2026-04-10 10:00:00"
-te-cli te_analysis +create_public_access_link --dry-run
+ae-cli analysis +create_public_access_link --project_id 1 --resource_type dashboard --resource_id 1 --access_controls '{}' --effective_at "2026-04-09 10:00:00" --expires_at "2026-04-10 10:00:00"
+ae-cli analysis +create_public_access_link --project_id 1 --company_id 1 --resource_type dashboard --resource_id 1 --access_controls '{}' --remark demo --effective_at "2026-04-09 10:00:00" --expires_at "2026-04-10 10:00:00"
+ae-cli analysis +create_public_access_link --dry-run
 ```
 
 ## Parameters

package/skills/te-analysis/references/create-report.md

@@ -1,4 +1,4 @@
-# te_analysis +create_report (Create Report)
+# analysis +create_report (Create Report)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -6,7 +6,7 @@ Domain: **Report management**
 
 ## Use Cases
 - Precondition helper: call `+get_analysis_query_schema` to get the structure before using this tool.
-- When constructing a real `analysis_query`, you must supplement it with real project metadata; first call `te_meta +list_events` and `te_meta +list_properties`.
+- When constructing a real `analysis_query`, you must supplement it with real project metadata; first call `analysis_meta +list_events` and `analysis_meta +list_properties`.
 - Create and persist a new report definition. Returns the new report ID and name without querying data or modifying existing reports.
 
 ## Mandatory prerequisites (MUST)
@@ -18,16 +18,16 @@ Domain: **Report management**
 
 ## Prerequisite call chain (required for constructing analysis_query)
 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`.
-4. Read `list-properties.md`, then call `te-cli te_meta +list_properties --project_id 1`.
+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 1`.
+4. Read `list-properties.md`, then call `ae-cli analysis_meta +list_properties --project_id 1`.
 5. Build `analysis_query` from the schema + metadata, then call `+create_report`.
 
 ## Command
 ```bash
-te-cli te_analysis +create_report --project_id 1 --report_name demo --model_type event --analysis_query '{}'
-te-cli te_analysis +create_report --project_id 1 --report_name demo --model_type event --analysis_query '{}' --description demo --cache_seconds 8 --query_duration_ms 8 --dashboard_ids '[]'
-te-cli te_analysis +create_report --dry-run
+ae-cli analysis +create_report --project_id 1 --report_name demo --model_type event --analysis_query '{}'
+ae-cli analysis +create_report --project_id 1 --report_name demo --model_type event --analysis_query '{}' --description demo --cache_seconds 8 --query_duration_ms 8 --dashboard_ids '[]'
+ae-cli analysis +create_report --dry-run
 ```
 
 ## Parameters
@@ -36,7 +36,7 @@ te-cli te_analysis +create_report --dry-run
 | `--project_id` / `-p` | Yes | Project ID |
 | `--report_name` | Yes | Report name. Length: 1-80 characters |
 | `--model_type` | Yes | Report model type. Supported values: event, retention, funnel, prop_analysis, path, distribution, sql, interval, attribution |
-| `--analysis_query` | Yes | Report analysis query 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`. |
+| `--analysis_query` | Yes | Report analysis query 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`. |
 | `--description` | No | Optional report description |
 | `--cache_seconds` | No | Optional cache duration in seconds |
 | `--query_duration_ms` | No | Optional query duration in milliseconds |
@@ -56,5 +56,5 @@ te-cli te_analysis +create_report --dry-run
 - If the result after writing does not match expectations, immediately read back the corresponding list/get interface to compare before and after.
 
 ## Recommended chaining
-- +get_analysis_query_schema -> te_meta +list_events -> te_meta +list_properties -> +create_report
+- +get_analysis_query_schema -> analysis_meta +list_events -> analysis_meta +list_properties -> +create_report
 - +list_reports -> +get_report_definition -> +query_report_data

package/skills/te-analysis/references/create-result-cluster.md

@@ -1,4 +1,4 @@
-# te_analysis +create_result_cluster (create result cluster)
+# analysis +create_result_cluster (create result cluster)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -27,9 +27,9 @@ Domain: **Model Analysis**
 
 ## Commands
 ```bash
-te-cli te_analysis +create_result_cluster --project_id 1 --cluster_name demo --model_type event --qp '{}'
-te-cli te_analysis +create_result_cluster --project_id 1 --cluster_name demo --display_name demo --model_type event --qp '{}' --zone_offset 8 --drilldown_date 2026-04-08 --drilldown_groups '[]' --event_index 8 --is_lost true --retention_days 8 --is_churned_user true --funnel_step 8 --interval demo --distribution_bucket 8 --compare_index 8 --include_total true --relation_val demo
-te-cli te_analysis +create_result_cluster --dry-run
+ae-cli analysis +create_result_cluster --project_id 1 --cluster_name demo --model_type event --qp '{}'
+ae-cli analysis +create_result_cluster --project_id 1 --cluster_name demo --display_name demo --model_type event --qp '{}' --zone_offset 8 --drilldown_date 2026-04-08 --drilldown_groups '[]' --event_index 8 --is_lost true --retention_days 8 --is_churned_user true --funnel_step 8 --interval demo --distribution_bucket 8 --compare_index 8 --include_total true --relation_val demo
+ae-cli analysis +create_result_cluster --dry-run
 ```
 
 ## Parameters

package/skills/te-analysis/references/drilldown-user-events.md

@@ -1,4 +1,4 @@
-# te_analysis +drilldown_user_events (Single-User Event Sequence Drilldown)
+# analysis +drilldown_user_events (Single-User Event Sequence Drilldown)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -25,14 +25,14 @@ Domain: **Model analysis**
 ## Prerequisite call chain (required for executing single-user event drilldown)
 1. First execute `+drilldown_users` and obtain the target user and drilldown context.
 2. Confirm the `user_id`, candidate events, and target discrete time points from the previous step result.
-3. If additional property display is needed, first call `te_meta +list_properties --project_id 1` to verify property names.
+3. If additional property display is needed, first call `analysis_meta +list_properties --project_id 1` to verify property names.
 4. Call `+drilldown_user_events` to query the event sequence.
 
 ## Command
 ```bash
-te-cli te_analysis +drilldown_user_events --project_id 1 --user_id u_123 --event_names '["login"]' --target_dates '["2026-04-08 00:00:00"]'
-te-cli te_analysis +drilldown_user_events --project_id 1 --user_id u_123 --event_names '["login"]' --target_dates '["2026-04-08 00:00:00"]' --zone_offset 8 --use_cache true --page_num 1 --page_size 100
-te-cli te_analysis +drilldown_user_events --dry-run
+ae-cli analysis +drilldown_user_events --project_id 1 --user_id u_123 --event_names '["login"]' --target_dates '["2026-04-08 00:00:00"]'
+ae-cli analysis +drilldown_user_events --project_id 1 --user_id u_123 --event_names '["login"]' --target_dates '["2026-04-08 00:00:00"]' --zone_offset 8 --use_cache true --page_num 1 --page_size 100
+ae-cli analysis +drilldown_user_events --dry-run
 ```
 
 ## Parameters
@@ -40,7 +40,7 @@ te-cli te_analysis +drilldown_user_events --dry-run
 |---|---|---|
 | `--project_id` / `-p` | Yes | Project ID |
 | `--user_id` | Yes | User ID from drilldown_users. It must come from drilldown_users and must not be guessed. |
-| `--event_names` | Yes | JSON array of event names. Values should come from upstream drilldown context or `te_meta +list_events` in the same `project_id`. |
+| `--event_names` | Yes | JSON array of event names. Values should come from upstream drilldown context or `analysis_meta +list_events` in the same `project_id`. |
 | `--target_dates` | Yes | JSON array of discrete target dates from upstream drilldown context. Not a start/end range. |
 | `--zone_offset` | No | Time zone offset. For example, UTC+8 is 8 |
 | `--properties` | No | Optional event properties JSON array |

package/skills/te-analysis/references/drilldown-users.md

@@ -1,4 +1,4 @@
-# te_analysis +drilldown_users (drill down analysis results to users)
+# analysis +drilldown_users (drill down analysis results to users)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -29,9 +29,9 @@ Domain: **Model Analysis**
 
 ## Commands
 ```bash
-ae-cli te_analysis +drilldown_users --project_id 1 --model_type event --qp '{}'
-ae-cli te_analysis +drilldown_users --project_id 1 --model_type retention --qp '{}' --drilldown_date 2026-04-08 --drilldown_groups '[]' --event_index 8 --is_lost true --retention_days 8 --is_churned_user true --funnel_step 8 --interval demo --distribution_bucket 8 --compare_index 8 --include_total true --relation_val demo
-ae-cli te_analysis +drilldown_users --dry-run
+ae-cli analysis +drilldown_users --project_id 1 --model_type event --qp '{}'
+ae-cli analysis +drilldown_users --project_id 1 --model_type retention --qp '{}' --drilldown_date 2026-04-08 --drilldown_groups '[]' --event_index 8 --is_lost true --retention_days 8 --is_churned_user true --funnel_step 8 --interval demo --distribution_bucket 8 --compare_index 8 --include_total true --relation_val demo
+ae-cli analysis +drilldown_users --dry-run
 ```
 
 ## Parameters

package/skills/te-analysis/references/get-alert-definition-schema.md

@@ -1,4 +1,4 @@
-# te_analysis +get_alert_definition_schema (Get Alert Definition Schema)
+# analysis +get_alert_definition_schema (Get Alert Definition Schema)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -13,8 +13,8 @@ Domain: **Metadata queries**
 
 ## Command
 ```bash
-te-cli te_analysis +get_alert_definition_schema
-te-cli te_analysis +get_alert_definition_schema --dry-run
+ae-cli analysis +get_alert_definition_schema
+ae-cli analysis +get_alert_definition_schema --dry-run
 ```
 
 ## Parameters

package/skills/te-analysis/references/get-alert.md

@@ -1,4 +1,4 @@
-# te_analysis +get_alert (view alert definition)
+# analysis +get_alert (view alert definition)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -9,8 +9,8 @@ Domain: **Metadata Lookup**
 
 ## Commands
 ```bash
-te-cli te_analysis +get_alert --project_id 1 --alert_id 1
-te-cli te_analysis +get_alert --dry-run
+ae-cli analysis +get_alert --project_id 1 --alert_id 1
+ae-cli analysis +get_alert --dry-run
 ```
 
 ## Parameters

package/skills/te-analysis/references/get-analysis-query-schema.md

@@ -1,10 +1,10 @@
-# te_analysis +get_analysis_query_schema (Get Analysis Query Schema)
+# analysis +get_analysis_query_schema (Get Analysis Query Schema)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
 Domain: **Model schema queries**
 
-- This is the documentation for the `+get_analysis_query_schema` command; read it before running `ae-cli te_analysis +get_analysis_query_schema`.
+- This is the documentation for the `+get_analysis_query_schema` command; read it before running `ae-cli analysis +get_analysis_query_schema`.
 - Get the query schema for the specified analysis model type. Different model types use different schema structures. This tool returns field definitions and examples.
 
 ## Use Cases
@@ -16,8 +16,8 @@ Domain: **Model schema queries**
 
 ## Command
 ```bash
-ae-cli te_analysis +get_analysis_query_schema --model_type event
-ae-cli te_analysis +get_analysis_query_schema --model_type event --dry-run
+ae-cli analysis +get_analysis_query_schema --model_type event
+ae-cli analysis +get_analysis_query_schema --model_type event --dry-run
 ```
 
 ## Parameters

package/skills/te-analysis/references/get-filter-schema.md

@@ -1,4 +1,4 @@
-# te_analysis +get_filter_schema (get filter schema)
+# analysis +get_filter_schema (get filter schema)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -13,8 +13,8 @@ Domain: **Schema Queries**
 
 ## Commands
 ```bash
-te-cli te_analysis +get_filter_schema
-te-cli te_analysis +get_filter_schema --dry-run
+ae-cli analysis +get_filter_schema
+ae-cli analysis +get_filter_schema --dry-run
 ```
 
 ## Parameters

package/skills/te-analysis/references/get-groupby-schema.md

@@ -1,4 +1,4 @@
-# te_analysis +get_groupby_schema (Get Group-By Schema)
+# analysis +get_groupby_schema (Get Group-By Schema)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -13,8 +13,8 @@ Domain: **Schema queries**
 
 ## Command
 ```bash
-te-cli te_analysis +get_groupby_schema
-te-cli te_analysis +get_groupby_schema --dry-run
+ae-cli analysis +get_groupby_schema
+ae-cli analysis +get_groupby_schema --dry-run
 ```
 
 ## Parameters

package/skills/te-analysis/references/get-report-definition.md

@@ -1,4 +1,4 @@
-# te_analysis +get_report_definition (read report definition)
+# analysis +get_report_definition (read report definition)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -11,8 +11,8 @@ Domain: **Report Management**
 
 ## Commands
 ```bash
-te-cli te_analysis +get_report_definition --project_id 1 --report_id 1
-te-cli te_analysis +get_report_definition --dry-run
+ae-cli analysis +get_report_definition --project_id 1 --report_id 1
+ae-cli analysis +get_report_definition --dry-run
 ```
 
 ## Parameters

package/skills/te-analysis/references/get-table-columns.md

@@ -1,4 +1,4 @@
-# te_analysis +get_table_columns (Read Underlying Table Columns)
+# analysis +get_table_columns (Read Underlying Table Columns)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -14,8 +14,8 @@ Domain: **Model analysis**
 
 ## Command
 ```bash
-te-cli te_analysis +get_table_columns --project_id 1 --catalog demo --schema demo --table demo
-te-cli te_analysis +get_table_columns --dry-run
+ae-cli analysis +get_table_columns --project_id 1 --catalog demo --schema demo --table demo
+ae-cli analysis +get_table_columns --dry-run
 ```
 
 ## Parameters

package/skills/te-analysis/references/list-alerts.md

@@ -1,4 +1,4 @@
-# te_analysis +list_alerts (alert strategy search)
+# analysis +list_alerts (alert strategy search)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -10,9 +10,9 @@ Domain: **Metadata Lookup**
 
 ## Commands
 ```bash
-te-cli te_analysis +list_alerts --project_id 1
-te-cli te_analysis +list_alerts --project_id 1 --query demo
-te-cli te_analysis +list_alerts --dry-run
+ae-cli analysis +list_alerts --project_id 1
+ae-cli analysis +list_alerts --project_id 1 --query demo
+ae-cli analysis +list_alerts --dry-run
 ```
 
 ## Parameters

package/skills/te-analysis/references/list-dashboards.md

@@ -1,4 +1,4 @@
-# te_analysis +list_dashboards (List Dashboards)
+# analysis +list_dashboards (List Dashboards)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -10,9 +10,9 @@ Domain: **Dashboard management**
 
 ## Command
 ```bash
-ae-cli te_analysis +list_dashboards --project_id 1
-ae-cli te_analysis +list_dashboards --project_id 1 --query demo
-ae-cli te_analysis +list_dashboards --dry-run
+ae-cli analysis +list_dashboards --project_id 1
+ae-cli analysis +list_dashboards --project_id 1 --query demo
+ae-cli analysis +list_dashboards --dry-run
 ```
 
 ## Parameters

package/skills/te-analysis/references/list-public-access-links.md

@@ -1,4 +1,4 @@
-# te_analysis +list_public_access_links (public link search)
+# analysis +list_public_access_links (public link search)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -10,8 +10,8 @@ Domain: **Dashboard Management**
 
 ## Commands
 ```bash
-te-cli te_analysis +list_public_access_links --project_id 1
-te-cli te_analysis +list_public_access_links --dry-run
+ae-cli analysis +list_public_access_links --project_id 1
+ae-cli analysis +list_public_access_links --dry-run
 ```
 
 ## Parameters

package/skills/te-analysis/references/list-reports.md

@@ -1,4 +1,4 @@
-# te_analysis +list_reports (List Reports)
+# analysis +list_reports (List Reports)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -10,9 +10,9 @@ Domain: **Report management**
 
 ## Command
 ```bash
-ae-cli te_analysis +list_reports --project_id 1
-ae-cli te_analysis +list_reports --project_id 1 --query demo
-ae-cli te_analysis +list_reports --dry-run
+ae-cli analysis +list_reports --project_id 1
+ae-cli analysis +list_reports --project_id 1 --query demo
+ae-cli analysis +list_reports --dry-run
 ```
 
 ## Parameters

package/skills/te-analysis/references/load-filters.md

@@ -1,4 +1,4 @@
-# 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)
 
@@ -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 1 --quot demo --table_type event
+ae-cli 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
+ae-cli analysis +load_filters --dry-run
 ```
 
 ## Parameters

package/skills/te-analysis/references/query-adhoc.md

@@ -1,4 +1,4 @@
-# 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)
 
@@ -6,7 +6,7 @@ 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.
@@ -29,16 +29,16 @@ Domain: **Model analysis**
 
 ## 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 1` to get the available events.
+4. Read `list-properties.md`, then call `ae-cli analysis_meta +list_properties --project_id 1` 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 1 --model_type event --qp '{}'
+ae-cli 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
+ae-cli analysis +query_adhoc --dry-run
 ```
 
 ## Parameters
@@ -46,7 +46,7 @@ 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 |
@@ -67,5 +67,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

@@ -1,4 +1,4 @@
-# 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)
 
@@ -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 1 --dashboard_id 1
+ae-cli analysis +query_dashboard_detail --dry-run
 ```
 
 ## Parameters

package/skills/te-analysis/references/query-dashboard-report-data.md

@@ -1,4 +1,4 @@
-# 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)
 
@@ -18,16 +18,16 @@ Domain: **Dashboard management**
 - 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 1`.
+3. Read `list-properties.md`, then call `ae-cli analysis_meta +list_properties --project_id 1`.
 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 1 --dashboard_id 1
+ae-cli 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]'
+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