@thinkingai/ae-cli 1.0.3 → 1.0.15

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

@@ -1,6 +1,6 @@
 # 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,22 +11,22 @@ 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 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`.
+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 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 --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
 ```
 
@@ -39,7 +39,7 @@ ae-cli analysis +query_entity_details --dry-run
 | `--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                                                                                                                                                                                                     |
 

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

@@ -1,31 +1,31 @@
 # 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 `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.
+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
-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 --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
 ```
 
@@ -34,8 +34,8 @@ ae-cli 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 `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`. |

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

@@ -1,6 +1,6 @@
 # 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,23 +13,23 @@ 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 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`.
+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 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 --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
 ```
 

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

@@ -1,6 +1,6 @@
 # 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,7 +9,7 @@ Domain: **Cluster Management**
 
 ## Commands
 ```bash
-ae-cli analysis_audience +refresh_cluster --project_id 1 --cluster_name demo
+ae-cli analysis_audience +refresh_cluster --project_id <project_id> --cluster_name demo
 ae-cli analysis_audience +refresh_cluster --dry-run
 ```
 

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

@@ -1,6 +1,6 @@
 # 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,7 +9,7 @@ Domain: **Tag Management**
 
 ## Commands
 ```bash
-ae-cli analysis_audience +refresh_tag --project_id 1 --tag_name demo
+ae-cli analysis_audience +refresh_tag --project_id <project_id> --tag_name demo
 ae-cli analysis_audience +refresh_tag --dry-run
 ```
 

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

@@ -1,6 +1,6 @@
 # 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,7 +10,7 @@ Domain: **Project Configuration**
 
 ## Command
 ```bash
-ae-cli analysis_meta +save_track_items --project_id 1 --track_data '{}'
+ae-cli analysis_meta +save_track_items --project_id <project_id> --track_data '{}'
 ae-cli analysis_meta +save_track_items --dry-run
 ```
 

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

@@ -1,6 +1,6 @@
 # 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,17 +11,17 @@ 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`.
+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
-ae-cli analysis +update_alert --project_id 1 --alert_id 1 --definition '{}'
+ae-cli analysis +update_alert --project_id <project_id> --alert_id 1 --definition '{}'
 ae-cli analysis +update_alert --dry-run
 ```
 

package/skills/{te-audience/references/update-cluster.md → ae-analysis/references/update_cluster.md}

@@ -1,31 +1,32 @@
 # analysis_audience +update_cluster (Update Cluster)
 
-> **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**
 
 ## Use Cases
 - Prerequisite helper: first call `+get_cluster_definition_schema` to get the structure, then supplement it with the project's real metadata (events and properties).
+- When updating `definition`, metadata must be verified in the same session and `project_id`: first definition update in this session must call `analysis_meta +list_events` and `analysis_meta +list_properties`; later updates should reuse session-verified results first.
 - Update a user cluster definition. Supports updating the display name, remark, type, or definition. Updating only the display name or remark does not trigger recomputation.
 
 ## Required Prerequisites (MUST only when updating definition)
 - If this request includes `--definition`, you must first read and follow these reference docs:
-  - [`./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)
-- Do not submit a new `definition` until the above docs have been read and the prerequisite commands have been run.
+  - [`./get_cluster_definition_schema.md`](./get_cluster_definition_schema.md)
+  - [`./list_events.md`](./list_events.md)
+  - [`./list_properties.md`](./list_properties.md)
+- Do not submit a new `definition` until the above docs have been read and metadata has been verified: first definition update in this session for the same `project_id` must run metadata commands; if session-verified metadata already exists, reuse it first.
 
 ## Prerequisite Call Chain (run only when updating definition)
 1. First determine `--type` (condition / sql).
-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`.
+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 progressively. Start with base mode; request `examples` only if base is insufficient; request `full` only for complex, ambiguous, or repeatedly failing definition updates.
+3. Read `list_events.md`. If this is the first definition update in the current session for this `project_id` (or metadata is not yet verified), call `ae-cli analysis_meta +list_events --project_id <project_id>`; otherwise, reuse the session-verified event metadata first.
+4. Read `list_properties.md`. If this is the first definition update in the current session for this `project_id` (or metadata is not yet verified), call `ae-cli analysis_meta +list_properties --project_id <project_id>`; otherwise, reuse the session-verified property metadata first.
 5. Build the new `definition` based on the schema + metadata, then run `+update_cluster`.
 
 ## Commands
 ```bash
-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 --project_id <project_id> --cluster_name demo --display_name "Demo v2"
+ae-cli analysis_audience +update_cluster --project_id <project_id> --cluster_name demo --type condition --definition '{}' --zone_offset 8
 ae-cli analysis_audience +update_cluster --dry-run
 ```
 
@@ -37,13 +38,14 @@ ae-cli analysis_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 `analysis_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 metadata verified in the same `project_id` (first definition update queries `analysis_meta` metadata commands; later updates in the same session should reuse verified results first). |
 | `--zone_offset` | No | Optional time zone offset for cluster computation. Valid range: -12 to 14 (supports decimals like 5.5). |
 
 ## Decision Rules
 - If you are not updating `definition` (only updating `display_name`/`remark`), you can skip the schema and metadata prerequisite chain.
 - When updating `definition`, it cannot be written from experience alone; it must satisfy both the schema structure and the project's real metadata.
-- Before calling `list_events` / `list_properties`, you must first read the corresponding reference docs.
+- Use progressive schema loading: base first, examples only when needed, full only as a last resort. Do not request full schema for simple cluster updates when the intent is clear.
+- Before calling `list_events` / `list_properties`, you must first read the corresponding reference docs. Query metadata on the first definition update in this session for the same `project_id`; after that, prefer reusing session-verified metadata.
 - For the first execution, it is recommended to pass only the required parameters (`--project_id`, `--cluster_name`) and add optional parameters after confirming the path works.
 - Wrap JSON parameters in single quotes (e.g. `--definition '{}'`) to avoid shell escaping issues.
 - When troubleshooting across projects, first confirm whether `--project_id` matches the current permissions and target environment.
@@ -55,5 +57,5 @@ ae-cli analysis_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 -> analysis_meta +list_events -> analysis_meta +list_properties -> +update_cluster
+- +get_cluster_definition_schema -> (first definition update or refresh) analysis_meta +list_events -> analysis_meta +list_properties -> +update_cluster
 - +list_clusters -> +get_clusters_by_name -> +update_cluster

package/skills/{te-analysis/references/update-dashboard.md → ae-analysis/references/update_dashboard.md}

@@ -1,6 +1,6 @@
 # analysis +update_dashboard (update dashboard)
 
-> **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**
 
@@ -16,8 +16,8 @@ Domain: **Dashboard Management**
 
 ## Commands
 ```bash
-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 --project_id <project_id> --dashboard_id 1
+ae-cli analysis +update_dashboard --project_id <project_id> --dashboard_id 1 --dashboard_name demo --report_ids '[1001]' --member_authorities '{"1001":"READ"}'
 ae-cli analysis +update_dashboard --dry-run
 ```
 

package/skills/{te-meta/references/update-metric.md → ae-analysis/references/update_metric.md}

@@ -1,6 +1,6 @@
 # analysis_meta +update_metric (Update Metric)
 
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
 
 Domain: **Metadata Query**
 
@@ -11,22 +11,22 @@ Domain: **Metadata Query**
 
 ## MUST Prerequisites
 - Before updating `--events` / `--params`, you must first read and follow these reference documents:
-  - [`../../te-analysis/references/get-analysis-query-schema.md`](../../te-analysis/references/get-analysis-query-schema.md)
-  - [`./list-events.md`](./list-events.md)
-  - [`./list-properties.md`](./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 submit new `events` / `params` until the document review and prerequisite command calls above are complete.
 
 ## Prerequisite Call Chain (Required for Updating events/params)
 1. Determine `--model_type` first (`event` / `retention`).
-2. Read `get-analysis-query-schema.md`, then call `ae-cli analysis +get_analysis_query_schema --model_type <event|retention>` to get the structure.
-3. Read `list-events.md`, then call `ae-cli analysis_meta +list_events --project_id 1`.
-4. Read `list-properties.md`, then call `ae-cli analysis_meta +list_properties --project_id 1`.
+2. Read `get_analysis_query_schema.md`, then call `ae-cli analysis +get_analysis_query_schema --model_type <event|retention>` to get the structure.
+3. Read `list_events.md`, then call `ae-cli analysis_meta +list_events --project_id <project_id>`.
+4. Read `list_properties.md`, then call `ae-cli analysis_meta +list_properties --project_id <project_id>`.
 5. Build the new `events` / `params` from the schema + metadata, then execute `+update_metric`.
 
 ## Commands
 ```bash
-ae-cli analysis_meta +update_metric --project_id 1 --metric_id 1 --name demo --display_name demo --model_type event --events '[]'
-ae-cli analysis_meta +update_metric --project_id 1 --metric_id 1 --name demo --display_name demo --remark demo --model_type event --events '[]' --params '{}'
+ae-cli analysis_meta +update_metric --project_id <project_id> --metric_id 1 --name demo --display_name demo --model_type event --events '[]'
+ae-cli analysis_meta +update_metric --project_id <project_id> --metric_id 1 --name demo --display_name demo --remark demo --model_type event --events '[]' --params '{}'
 ae-cli analysis_meta +update_metric --dry-run
 ```
 

package/skills/{te-meta/references/update-project-mark-time.md → ae-analysis/references/update_project_mark_time.md}

@@ -1,6 +1,6 @@
 # analysis_meta +update_project_mark_time (Update Project Date Marker)
 
-> **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
-ae-cli analysis_meta +update_project_mark_time --mark_time_id 1 --project_id 1 --marked_at '2026-04-09 10:00' --content demo
-ae-cli analysis_meta +update_project_mark_time --mark_time_id 1 --project_id 1 --marked_at '2026-04-09 10:00' --zone_offset 8 --content demo --is_visible 1
+ae-cli analysis_meta +update_project_mark_time --mark_time_id 1 --project_id <project_id> --marked_at '2026-04-09 10:00' --content demo
+ae-cli analysis_meta +update_project_mark_time --mark_time_id 1 --project_id <project_id> --marked_at '2026-04-09 10:00' --zone_offset 8 --content demo --is_visible 1
 ae-cli analysis_meta +update_project_mark_time --dry-run
 ```
 

package/skills/{te-analysis/references/update-public-access-link.md → ae-analysis/references/update_public_access_link.md}

@@ -1,6 +1,6 @@
 # analysis +update_public_access_link (Update Public Access Link)
 
-> **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**
 
@@ -10,8 +10,8 @@ Domain: **Dashboard management**
 
 ## Command
 ```bash
-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 --project_id <project_id> --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 <project_id> --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
 ```
 

package/skills/{te-audience/references/update-tag.md → ae-analysis/references/update_tag.md}

@@ -1,32 +1,32 @@
 # analysis_audience +update_tag (Update Tag)
 
-> **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
 - Prerequisite helper: first call `+get_tag_definition_schema` to get the structure, then call this tool.
-- When updating `definition`, you must first supplement it with real project metadata; at minimum, first call `analysis_meta +list_events` and `analysis_meta +list_properties`.
+- When updating `definition`, metadata must be verified in the same session and `project_id`: first definition update in this session must call `analysis_meta +list_events` and `analysis_meta +list_properties`; later updates should reuse session-verified results first.
 - Update a user tag definition. Supports updating the display name, remark, type, and tag definition. Updating only the display name or remark does not trigger recomputation.
 
 ## Required Prerequisites (MUST only when updating definition)
 - If this request includes `--definition`, you must first read and follow these reference docs:
-  - [`./get-tag-definition-schema.md`](./get-tag-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)
-- Do not submit a new `definition` until the above docs have been read and the prerequisite commands have been run.
+  - [`./get_tag_definition_schema.md`](./get_tag_definition_schema.md)
+  - [`./list_events.md`](./list_events.md)
+  - [`./list_properties.md`](./list_properties.md)
+- Do not submit a new `definition` until the above docs have been read and metadata has been verified: first definition update in this session for the same `project_id` must run metadata commands; if session-verified metadata already exists, reuse it first.
 
 ## Prerequisite Call Chain (run only when updating definition)
 1. First determine `--type` (condition / metric / first_last / sql).
-2. Read `get-tag-definition-schema.md`, then call `ae-cli analysis_audience +get_tag_definition_schema` 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`.
+2. Read `get_tag_definition_schema.md`, then call `ae-cli analysis_audience +get_tag_definition_schema --type <condition|metric|first_last|sql>` to obtain the structure progressively. Start with base mode; request `examples` only if base is insufficient; request `full` only for complex, ambiguous, or repeatedly failing definition updates.
+3. Read `list_events.md`. If this is the first definition update in the current session for this `project_id` (or metadata is not yet verified), call `ae-cli analysis_meta +list_events --project_id <project_id>`; otherwise, reuse the session-verified event metadata first.
+4. Read `list_properties.md`. If this is the first definition update in the current session for this `project_id` (or metadata is not yet verified), call `ae-cli analysis_meta +list_properties --project_id <project_id>`; otherwise, reuse the session-verified property metadata first.
 5. Build the new `definition` based on the schema + metadata, then run `+update_tag`.
 
 ## Commands
 ```bash
-ae-cli analysis_audience +update_tag --project_id 1 --tag_name demo --display_name "Demo v2"
-ae-cli analysis_audience +update_tag --project_id 1 --tag_name demo --type condition --definition '{}' --zone_offset 8
+ae-cli analysis_audience +update_tag --project_id <project_id> --tag_name demo --display_name "Demo v2"
+ae-cli analysis_audience +update_tag --project_id <project_id> --tag_name demo --type condition --definition '{}' --zone_offset 8
 ae-cli analysis_audience +update_tag --dry-run
 ```
 
@@ -38,13 +38,14 @@ ae-cli analysis_audience +update_tag --dry-run
 | `--display_name` | No | New tag display name. Length: 1-80 |
 | `--remark` | No | New tag remark |
 | `--type` | No | New tag type. Supported values: condition, metric, first_last, sql |
-| `--definition` | No | New tag definition JSON. If provided, MUST call `+get_tag_definition_schema` first, then fill valid event/property names from `analysis_meta` metadata commands in the same `project_id`. |
+| `--definition` | No | New tag definition JSON. If provided, MUST call `+get_tag_definition_schema` first, then fill valid event/property names from metadata verified in the same `project_id` (first definition update queries `analysis_meta` metadata commands; later updates in the same session should reuse verified results first). |
 | `--zone_offset` | No | Optional time zone offset for tag computation. Valid range: -12 to 14 (supports decimals like 5.5). |
 
 ## Decision Rules
 - If you are not updating `definition` (only updating `display_name`/`remark`), you can skip the schema and metadata prerequisite chain.
 - When updating `definition`, it cannot be written from experience alone; it must satisfy both the schema structure and the project's real metadata.
-- Before calling `list_events` / `list_properties`, you must first read the corresponding reference docs.
+- Use progressive schema loading: base first, examples only when needed, full only as a last resort. Do not request full schema for simple tag updates when the intent is clear.
+- Before calling `list_events` / `list_properties`, you must first read the corresponding reference docs. Query metadata on the first definition update in this session for the same `project_id`; after that, prefer reusing session-verified metadata.
 - 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.
 - Wrap JSON parameters in single quotes (e.g. `--definition '{}'`) to avoid shell escaping issues.
 - When troubleshooting across projects, first confirm whether `--project_id` matches the current permissions and target environment.
@@ -56,5 +57,5 @@ ae-cli analysis_audience +update_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 -> analysis_meta +list_events -> analysis_meta +list_properties -> +update_tag
+- +get_tag_definition_schema -> (first definition update or refresh) analysis_meta +list_events -> analysis_meta +list_properties -> +update_tag
 - +list_tags -> +get_tags_by_name -> +update_tag