@thinkingai/ae-cli 1.0.1 → 1.0.3

package/skills/te-analysis/references/query-entity-details.md

@@ -1,4 +1,4 @@
-# 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)
 
@@ -18,16 +18,16 @@ Domain: **Entity Detail Queries**
 
 ## 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 1`.
+4. Read `list-properties.md`, then call `ae-cli analysis_meta +list_properties --project_id 1`.
 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 1 --definition '{}'
+ae-cli 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 analysis +query_entity_details --dry-run
 ```
 
 ## Parameters
@@ -35,8 +35,8 @@ 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                                                                                                                                                                                    |
@@ -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

@@ -1,4 +1,4 @@
-# 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)
 
@@ -17,16 +17,16 @@ Domain: **Event detail queries**
 - 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 1` to confirm the available event names.
+3. Read `list-properties.md`, then call `ae-cli analysis_meta +list_properties --project_id 1` 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 1 --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 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
+ae-cli analysis +query_event_details --dry-run
 ```
 
 ## Parameters
@@ -37,8 +37,8 @@ te-cli te_analysis +query_event_details --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: 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

@@ -1,4 +1,4 @@
-# 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)
 
@@ -20,17 +20,17 @@ Domain: **Report Management**
 - 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 1`.
+4. Read `list-properties.md`, then call `ae-cli analysis_meta +list_properties --project_id 1`.
 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 1 --report_ids '[1001]'
+ae-cli 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 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-analysis/references/update-alert.md

@@ -1,4 +1,4 @@
-# te_analysis +update_alert (Update Alert)
+# analysis +update_alert (Update Alert)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -16,13 +16,13 @@ Domain: **Metadata queries**
 
 ## 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.
+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 1 --alert_id 1 --definition '{}'
+ae-cli analysis +update_alert --dry-run
 ```
 
 ## Parameters

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

@@ -1,4 +1,4 @@
-# te_analysis +update_dashboard (update dashboard)
+# analysis +update_dashboard (update dashboard)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -16,9 +16,9 @@ Domain: **Dashboard Management**
 
 ## Commands
 ```bash
-ae-cli te_analysis +update_dashboard --project_id 1 --dashboard_id 1
-ae-cli te_analysis +update_dashboard --project_id 1 --dashboard_id 1 --dashboard_name demo --report_ids '[1001]' --member_authorities '{"1001":"READ"}'
-ae-cli te_analysis +update_dashboard --dry-run
+ae-cli analysis +update_dashboard --project_id 1 --dashboard_id 1
+ae-cli analysis +update_dashboard --project_id 1 --dashboard_id 1 --dashboard_name demo --report_ids '[1001]' --member_authorities '{"1001":"READ"}'
+ae-cli analysis +update_dashboard --dry-run
 ```
 
 ## Parameters

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

@@ -1,4 +1,4 @@
-# te_analysis +update_public_access_link (Update Public Access Link)
+# analysis +update_public_access_link (Update Public Access Link)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -10,9 +10,9 @@ Domain: **Dashboard management**
 
 ## Command
 ```bash
-ae-cli te_analysis +update_public_access_link --project_id 1 --link_id 1 --access_controls '{}' --effective_at "2026-04-09 10:00:00" --expires_at "2026-04-10 10:00:00"
-ae-cli te_analysis +update_public_access_link --project_id 1 --company_id 1 --link_id 1 --access_controls '{}' --remark demo --effective_at "2026-04-09 10:00:00" --expires_at "2026-04-10 10:00:00"
-ae-cli te_analysis +update_public_access_link --dry-run
+ae-cli analysis +update_public_access_link --project_id 1 --link_id 1 --access_controls '{}' --effective_at "2026-04-09 10:00:00" --expires_at "2026-04-10 10:00:00"
+ae-cli analysis +update_public_access_link --project_id 1 --company_id 1 --link_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 +update_public_access_link --dry-run
 ```
 
 ## Parameters

package/skills/te-audience/SKILL.md

@@ -5,7 +5,7 @@ description: "TE audience operations and targeting: create, update, query, recom
 metadata:
   requires:
     bins: ["ae-cli"]
-  cliHelp: "ae-cli te_audience --help"
+  cliHelp: "ae-cli analysis_audience --help"
 ---
 
 # te-audience
@@ -25,7 +25,7 @@ Use `te-audience` when the user needs cluster and tag capabilities:
 
 ## Command Format
 
-`ae-cli te_audience +<tool_name> [options]`
+`ae-cli analysis_audience +<tool_name> [options]`
 
 ## Tool Groups (14)
 
@@ -52,10 +52,10 @@ Use `te-audience` when the user needs cluster and tag capabilities:
 ## Quick Validation
 
 ```bash
-ae-cli te_audience --help
-npm run verify:te-audience-tools
+ae-cli analysis_audience --help
+npm run verify:analysis-audience-tools
 # Example: preview the request with dry-run (replace project_id with your actual project ID)
-ae-cli te_audience +list_clusters --project_id <YOUR_PROJECT_ID> --dry-run
+ae-cli analysis_audience +list_clusters --project_id <YOUR_PROJECT_ID> --dry-run
 ```
 
 ## Reference Docs

package/skills/te-audience/references/create-cluster.md

@@ -1,4 +1,4 @@
-# te_audience +create_cluster (Create Cluster)
+# analysis_audience +create_cluster (Create Cluster)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -6,7 +6,7 @@ Domain: **Cluster Management**
 
 ## Use Cases
 - Prerequisite helper: first call `+get_cluster_definition_schema` to obtain the `definition` structure, then call this tool.
-- When building a real `definition`, you must supplement it with real project metadata: first call `te_meta +list_events` and `te_meta +list_properties`, then fill in event names/property names.
+- When building a real `definition`, you must supplement it with real project metadata: first call `analysis_meta +list_events` and `analysis_meta +list_properties`, then fill in event names/property names.
 - Create a user cluster definition. Supports the condition and sql cluster types. Returns cluster information without cluster members.
 
 ## Required Prerequisites (MUST)
@@ -19,20 +19,20 @@ Domain: **Cluster Management**
 ## Prerequisite Call Chain (Required for Building Definition)
 1. Read `get-cluster-definition-schema.md` to understand the input and output structure of `+get_cluster_definition_schema`.
 2. Obtain the schema structure (by cluster type):
-   `te-cli te_audience +get_cluster_definition_schema --cluster_type condition`
+   `ae-cli analysis_audience +get_cluster_definition_schema --cluster_type condition`
 3. Read `list-events.md` to understand the parameters and return structure of `+list_events`.
 4. Get the event list (for `event_name` and other fields):
-   `te-cli te_meta +list_events --project_id 1`
+   `ae-cli analysis_meta +list_events --project_id 1`
 5. Read `list-properties.md` to understand the parameters and return structure of `+list_properties`.
 6. Get the property list (for property filters, grouping, and comparison fields):
-   `te-cli te_meta +list_properties --project_id 1`
+   `ae-cli analysis_meta +list_properties --project_id 1`
 7. Build `definition` based on the schema + metadata, then call `+create_cluster`.
 
 ## Commands
 ```bash
-te-cli te_audience +create_cluster --project_id 1 --cluster_name demo --display_name demo --definition '{}'
-te-cli te_audience +create_cluster --project_id 1 --cluster_name demo --display_name demo --type condition --definition '{}' --zone_offset 8 --entity_id 1001
-te-cli te_audience +create_cluster --dry-run
+ae-cli analysis_audience +create_cluster --project_id 1 --cluster_name demo --display_name demo --definition '{}'
+ae-cli analysis_audience +create_cluster --project_id 1 --cluster_name demo --display_name demo --type condition --definition '{}' --zone_offset 8 --entity_id 1001
+ae-cli analysis_audience +create_cluster --dry-run
 ```
 
 ## Parameters
@@ -42,7 +42,7 @@ te-cli te_audience +create_cluster --dry-run
 | `--cluster_name` | Yes | Cluster name. Must start with a letter and contain only letters, digits, and underscores. Length: 1-80 |
 | `--display_name` | Yes | Cluster display name. Length: 1-80 |
 | `--type` | No | Cluster type. Supported values: condition and sql. Default: condition |
-| `--definition` | Yes | Cluster definition JSON. MUST call `+get_cluster_definition_schema` first to learn the exact structure, then use `te_meta +list_events` / `te_meta +list_properties` to fill valid event/property names from the target project. |
+| `--definition` | Yes | Cluster definition JSON. MUST call `+get_cluster_definition_schema` first to learn the exact structure, then use `analysis_meta +list_events` / `analysis_meta +list_properties` to fill valid event/property names from the target project. |
 | `--zone_offset` | No | Optional time zone offset for cluster computation. Valid range: -12 to 14 (supports decimals like 5.5). If the user does not specify a timezone, omit this parameter. When a timezone is specified, call get_project_config first to check whether the project supports time zones (timeZoneEnabled) and available values (availableTimeZones). |
 | `--entity_id` | No | Optional entity ID for cluster definition. Use list_entities to query available entities. |
 
@@ -61,5 +61,5 @@ te-cli te_audience +create_cluster --dry-run
 - If the result after writing is not as expected, immediately re-read the corresponding list/get interfaces and compare before and after.
 
 ## Recommended Chain
-- +get_cluster_definition_schema -> te_meta +list_events -> te_meta +list_properties -> +create_cluster
+- +get_cluster_definition_schema -> analysis_meta +list_events -> analysis_meta +list_properties -> +create_cluster
 - +list_clusters -> +get_clusters_by_name -> +update_cluster

package/skills/te-audience/references/create-tag.md

@@ -1,4 +1,4 @@
-# te_audience +create_tag (Create Tag)
+# analysis_audience +create_tag (Create Tag)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -6,7 +6,7 @@ Domain: **Tag Management**
 
 ## Use Cases
 - Prerequisite helper: first call `+get_tag_definition_schema` to obtain the structure, then call this tool.
-- When building a real `definition`, you must supplement it with real project metadata; at minimum, first call `te_meta +list_events` and `te_meta +list_properties`.
+- When building a real `definition`, you must supplement it with real project metadata; at minimum, first call `analysis_meta +list_events` and `analysis_meta +list_properties`.
 - Create a user tag definition. Supports the condition, metric, first_last, and sql tag types. Returns the new tag ID without tag members.
 
 ## Required Prerequisites (MUST)
@@ -19,16 +19,16 @@ Domain: **Tag Management**
 ## Prerequisite Call Chain (Required for Building Definition)
 1. First determine `--type` (condition / metric / first_last / sql).
 2. Read `get-tag-definition-schema.md` to understand the return structure of `+get_tag_definition_schema`.
-3. Call `te-cli te_audience +get_tag_definition_schema` to obtain the schema.
-4. Read `list-events.md`, then call `te-cli te_meta +list_events --project_id 1` to get available events.
-5. Read `list-properties.md`, then call `te-cli te_meta +list_properties --project_id 1` to get available properties.
+3. Call `ae-cli analysis_audience +get_tag_definition_schema` to obtain the schema.
+4. Read `list-events.md`, then call `ae-cli analysis_meta +list_events --project_id 1` to get available events.
+5. Read `list-properties.md`, then call `ae-cli analysis_meta +list_properties --project_id 1` to get available properties.
 6. Build `definition` based on the schema + metadata, then call `+create_tag`.
 
 ## Commands
 ```bash
-te-cli te_audience +create_tag --project_id 1 --tag_name demo --display_name demo --definition '{}'
-te-cli te_audience +create_tag --project_id 1 --tag_name demo --display_name demo --type condition --definition '{}' --zone_offset 8 --entity_id 1001
-te-cli te_audience +create_tag --dry-run
+ae-cli analysis_audience +create_tag --project_id 1 --tag_name demo --display_name demo --definition '{}'
+ae-cli analysis_audience +create_tag --project_id 1 --tag_name demo --display_name demo --type condition --definition '{}' --zone_offset 8 --entity_id 1001
+ae-cli analysis_audience +create_tag --dry-run
 ```
 
 ## Parameters
@@ -38,7 +38,7 @@ te-cli te_audience +create_tag --dry-run
 | `--tag_name` | Yes | Tag name. Must start with a letter and contain only letters, digits, and underscores. Length: 1-80 |
 | `--display_name` | Yes | Tag display name. Length: 1-80 |
 | `--type` | No | Tag type. Supported values: condition, metric, first_last, sql |
-| `--definition` | Yes | Tag definition JSON. MUST call `+get_tag_definition_schema` first, then fill valid event/property names from `te_meta` metadata commands in the same `project_id`. |
+| `--definition` | Yes | Tag definition JSON. MUST call `+get_tag_definition_schema` first, then fill valid event/property names from `analysis_meta` metadata commands in the same `project_id`. |
 | `--zone_offset` | No | Optional time zone offset for tag computation. Valid range: -12 to 14 (supports decimals like 5.5). If the user does not specify a timezone, omit this parameter. When a timezone is specified, call get_project_config first to check whether the project supports time zones (timeZoneEnabled) and available values (availableTimeZones). |
 | `--entity_id` | No | Optional entity ID for tag definition. Use list_entities to query available entities. |
 
@@ -56,5 +56,5 @@ te-cli te_audience +create_tag --dry-run
 - If the result after writing is not as expected, immediately re-read the corresponding list/get interfaces and compare before and after.
 
 ## Recommended Chain
-- +get_tag_definition_schema -> te_meta +list_events -> te_meta +list_properties -> +create_tag
+- +get_tag_definition_schema -> analysis_meta +list_events -> analysis_meta +list_properties -> +create_tag
 - +list_tags -> +get_tags_by_name -> +update_tag

package/skills/te-audience/references/get-cluster-definition-schema.md

@@ -1,4 +1,4 @@
-# te_audience +get_cluster_definition_schema (Get Cluster Definition Schema)
+# analysis_audience +get_cluster_definition_schema (Get Cluster Definition Schema)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -6,14 +6,14 @@ Domain: **Schema Query**
 
 ## Use Cases
 - Support tool positioning: the current command provides the structure definition (schema) and should be used as a prerequisite step.
-- Recommended sequence: first call this schema tool to get the structure, then call `te_meta +list_events` / `te_meta +list_properties` to obtain real metadata, and finally create or update clusters.
+- Recommended sequence: first call this schema tool to get the structure, then call `analysis_meta +list_events` / `analysis_meta +list_properties` to obtain real metadata, and finally create or update clusters.
 - Get the cluster definition schema. Supports the condition and sql cluster types and returns field definitions, enum descriptions, and examples.
 
 ## Commands
 ```bash
-te-cli te_audience +get_cluster_definition_schema --cluster_type condition
-te-cli te_audience +get_cluster_definition_schema --cluster_type sql
-te-cli te_audience +get_cluster_definition_schema --dry-run
+ae-cli analysis_audience +get_cluster_definition_schema --cluster_type condition
+ae-cli analysis_audience +get_cluster_definition_schema --cluster_type sql
+ae-cli analysis_audience +get_cluster_definition_schema --dry-run
 ```
 
 ## Parameters
@@ -24,8 +24,8 @@ te-cli te_audience +get_cluster_definition_schema --dry-run
 ## Decision Rules
 - `--cluster_type` must be explicitly set to `condition` or `sql`.
 - It is recommended to run `--dry-run` first to inspect the request mapping before making the actual call.
-- The current command returns only structure constraints; it does not guarantee that the field values are available in the target project. Event names and property names must be confirmed again with `te_meta` metadata interfaces.
-- Before calling `te_meta +list_events` / `te_meta +list_properties`, first read their reference docs to confirm the parameter and return-field meanings.
+- The current command returns only structure constraints; it does not guarantee that the field values are available in the target project. Event names and property names must be confirmed again with `analysis_meta` metadata interfaces.
+- Before calling `analysis_meta +list_events` / `analysis_meta +list_properties`, first read their reference docs to confirm the parameter and return-field meanings.
 
 ## Next Step on Failure
 - If reading fails, first verify whether the object ID exists and belongs to the current project.
@@ -33,5 +33,5 @@ te-cli te_audience +get_cluster_definition_schema --dry-run
 
 ## Recommended Chain
 - First read: [`./get-cluster-definition-schema.md`](./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 -> te_meta +list_events -> te_meta +list_properties -> +create_cluster
-- +get_cluster_definition_schema -> te_meta +list_events -> te_meta +list_properties -> +update_cluster
+- +get_cluster_definition_schema -> analysis_meta +list_events -> analysis_meta +list_properties -> +create_cluster
+- +get_cluster_definition_schema -> analysis_meta +list_events -> analysis_meta +list_properties -> +update_cluster

package/skills/te-audience/references/get-clusters-by-name.md

@@ -1,4 +1,4 @@
-# te_audience +get_clusters_by_name (Locate Clusters by Name)
+# analysis_audience +get_clusters_by_name (Locate Clusters by Name)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -9,8 +9,8 @@ Domain: **Cluster Management**
 
 ## Commands
 ```bash
-te-cli te_audience +get_clusters_by_name --project_id 1 --names '["demo"]'
-te-cli te_audience +get_clusters_by_name --dry-run
+ae-cli analysis_audience +get_clusters_by_name --project_id 1 --names '["demo"]'
+ae-cli analysis_audience +get_clusters_by_name --dry-run
 ```
 
 ## Parameters

package/skills/te-audience/references/get-tag-definition-schema.md

@@ -1,4 +1,4 @@
-# te_audience +get_tag_definition_schema (Get Tag Definition Schema)
+# analysis_audience +get_tag_definition_schema (Get Tag Definition Schema)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -12,8 +12,8 @@ Domain: **Schema Query**
 
 ## Commands
 ```bash
-te-cli te_audience +get_tag_definition_schema
-te-cli te_audience +get_tag_definition_schema --dry-run
+ae-cli analysis_audience +get_tag_definition_schema
+ae-cli analysis_audience +get_tag_definition_schema --dry-run
 ```
 
 ## Parameters

package/skills/te-audience/references/get-tags-by-name.md

@@ -1,4 +1,4 @@
-# te_audience +get_tags_by_name (Locate Tags by Name)
+# analysis_audience +get_tags_by_name (Locate Tags by Name)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -9,8 +9,8 @@ Domain: **Tag Management**
 
 ## Commands
 ```bash
-te-cli te_audience +get_tags_by_name --project_id 1 --names '["demo"]'
-te-cli te_audience +get_tags_by_name --dry-run
+ae-cli analysis_audience +get_tags_by_name --project_id 1 --names '["demo"]'
+ae-cli analysis_audience +get_tags_by_name --dry-run
 ```
 
 ## Parameters

package/skills/te-audience/references/list-cluster-members.md

@@ -1,4 +1,4 @@
-# te_audience +list_cluster_members (View Cluster Members)
+# analysis_audience +list_cluster_members (View Cluster Members)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -9,9 +9,9 @@ Domain: **Cluster Management**
 
 ## Commands
 ```bash
-te-cli te_audience +list_cluster_members --project_id 1 --cluster_name demo
-te-cli te_audience +list_cluster_members --project_id 1 --cluster_name demo --property_names '["#user_id","name"]' --use_cache false
-te-cli te_audience +list_cluster_members --dry-run
+ae-cli analysis_audience +list_cluster_members --project_id 1 --cluster_name demo
+ae-cli analysis_audience +list_cluster_members --project_id 1 --cluster_name demo --property_names '["#user_id","name"]' --use_cache false
+ae-cli analysis_audience +list_cluster_members --dry-run
 ```
 
 ## Parameters

package/skills/te-audience/references/list-clusters.md

@@ -1,4 +1,4 @@
-# te_audience +list_clusters (Cluster Search)
+# analysis_audience +list_clusters (Cluster Search)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -9,9 +9,9 @@ Domain: **Cluster Management**
 
 ## Commands
 ```bash
-te-cli te_audience +list_clusters --project_id 1
-te-cli te_audience +list_clusters --project_id 1 --query demo
-te-cli te_audience +list_clusters --dry-run
+ae-cli analysis_audience +list_clusters --project_id 1
+ae-cli analysis_audience +list_clusters --project_id 1 --query demo
+ae-cli analysis_audience +list_clusters --dry-run
 ```
 
 ## Parameters

package/skills/te-audience/references/list-tag-members.md

@@ -1,4 +1,4 @@
-# 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)
 
@@ -9,9 +9,9 @@ Domain: **Tag Management**
 
 ## 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 1 --tag_name demo
+ae-cli analysis_audience +list_tag_members --project_id 1 --tag_name demo --snapshot_date 2026-04-01 --property_names '["#user_id","name"]' --use_cache false
+ae-cli analysis_audience +list_tag_members --dry-run
 ```
 
 ## Parameters

package/skills/te-audience/references/list-tags.md

@@ -1,4 +1,4 @@
-# te_audience +list_tags (Tag Search)
+# analysis_audience +list_tags (Tag Search)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -9,9 +9,9 @@ Domain: **Tag Management**
 
 ## 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 1
+ae-cli analysis_audience +list_tags --project_id 1 --query demo
+ae-cli analysis_audience +list_tags --dry-run
 ```
 
 ## Parameters

package/skills/te-audience/references/refresh-cluster.md

@@ -1,4 +1,4 @@
-# te_audience +refresh_cluster (Trigger Cluster Recompute)
+# analysis_audience +refresh_cluster (Trigger Cluster Recompute)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -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 1 --cluster_name demo
+ae-cli analysis_audience +refresh_cluster --dry-run
 ```
 
 ## Parameters

package/skills/te-audience/references/refresh-tag.md

@@ -1,4 +1,4 @@
-# te_audience +refresh_tag (Trigger Tag Recompute)
+# analysis_audience +refresh_tag (Trigger Tag Recompute)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -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 1 --tag_name demo
+ae-cli analysis_audience +refresh_tag --dry-run
 ```
 
 ## Parameters

package/skills/te-audience/references/update-cluster.md

@@ -1,4 +1,4 @@
-# te_audience +update_cluster (Update Cluster)
+# analysis_audience +update_cluster (Update Cluster)
 
 > **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
@@ -17,16 +17,16 @@ Domain: **Cluster Management**
 
 ## Prerequisite Call Chain (run only when updating definition)
 1. First determine `--type` (condition / sql).
-2. Read `get-cluster-definition-schema.md`, then call `te-cli te_audience +get_cluster_definition_schema --cluster_type <condition|sql>` to obtain 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-cluster-definition-schema.md`, then call `ae-cli analysis_audience +get_cluster_definition_schema --cluster_type <condition|sql>` to obtain 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 the new `definition` based on the schema + metadata, then run `+update_cluster`.
 
 ## Commands
 ```bash
-te-cli te_audience +update_cluster --project_id 1 --cluster_name demo --display_name "Demo v2"
-te-cli te_audience +update_cluster --project_id 1 --cluster_name demo --type condition --definition '{}' --zone_offset 8
-te-cli te_audience +update_cluster --dry-run
+ae-cli analysis_audience +update_cluster --project_id 1 --cluster_name demo --display_name "Demo v2"
+ae-cli analysis_audience +update_cluster --project_id 1 --cluster_name demo --type condition --definition '{}' --zone_offset 8
+ae-cli analysis_audience +update_cluster --dry-run
 ```
 
 ## Parameters
@@ -37,7 +37,7 @@ te-cli te_audience +update_cluster --dry-run
 | `--display_name` | No | New cluster display name. Length: 1-80 |
 | `--remark` | No | New cluster remark |
 | `--type` | No | New cluster type. Supported values: condition and sql. It is recommended to provide this when updating the definition. |
-| `--definition` | No | New cluster definition JSON. If provided, MUST call `+get_cluster_definition_schema` first, then fill valid event/property names from `te_meta` metadata commands in the same `project_id`. |
+| `--definition` | No | New cluster definition JSON. If provided, MUST call `+get_cluster_definition_schema` first, then fill valid event/property names from `analysis_meta` metadata commands in the same `project_id`. |
 | `--zone_offset` | No | Optional time zone offset for cluster computation. Valid range: -12 to 14 (supports decimals like 5.5). |
 
 ## Decision Rules
@@ -55,5 +55,5 @@ te-cli te_audience +update_cluster --dry-run
 - If the result after writing is not as expected, immediately re-read the corresponding list/get interfaces and compare before and after.
 
 ## Recommended Chain
-- +get_cluster_definition_schema -> te_meta +list_events -> te_meta +list_properties -> +update_cluster
+- +get_cluster_definition_schema -> analysis_meta +list_events -> analysis_meta +list_properties -> +update_cluster
 - +list_clusters -> +get_clusters_by_name -> +update_cluster