@thinkingai/ae-cli 1.0.1

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

@@ -0,0 +1,31 @@
+# te_analysis +get_alert (view alert definition)
+
+> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+
+Domain: **Metadata Lookup**
+
+## Use Cases
+- Get detailed information about a specific alert by alertId.
+
+## Commands
+```bash
+te-cli te_analysis +get_alert --project_id 1 --alert_id 1
+te-cli te_analysis +get_alert --dry-run
+```
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project_id` / `-p` | Yes | Project ID |
+| `--alert_id` / `-a` | Yes | Alert ID |
+
+## Decision Rules
+- For the first run, it is recommended to pass only the required parameters (`--project_id`, `--alert_id`) and add optional parameters after confirming the chain works.
+- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
+
+## Next Step After Failure
+- If required parameters are missing, fall back to the smallest runnable command and fill them in (focus on `--project_id`, `--alert_id`).
+- If reading fails, first verify whether the object ID exists and belongs to the current project.
+
+## Recommended Chaining
+- +get_alert

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

@@ -0,0 +1,36 @@
+# te_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`.
+- 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
+- Helper tool positioning: this command provides structural definitions (schema) and should be used as a prerequisite step.
+- Recommended order: first use the current schema tool to get the structure, then call the specific business tool.
+- Typical follow-up tools: `+create_metric`, `+create_report`, `+drilldown_users`, `+get_cluster_definition_schema`, `+get_filter_schema`, `+get_groupby_schema`, `+get_tag_definition_schema`, `+query_adhoc`
+- Get the analysis query schema for the specified model type. Different model types use different query structures. This tool returns field definitions and examples. Supported model types: event, retention, funnel, distribution, sql, interval, path, attribution, prop_analysis, rank_list, heat_map.
+- Get the analysis query schema for the specified model type.
+
+## 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
+```
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--model_type` | Yes | Model type. Supported values: event, retention, funnel, distribution, sql, interval, path, attribution, prop_analysis, rank_list, heat_map |
+
+## Decision Rules
+- It is recommended to run `--dry-run` first to inspect the request body mapping before making the formal call.
+
+## Next Steps on Failure
+- If reading fails, first verify whether the object ID exists and belongs to the current project.
+- If the schema does not match expectations, confirm whether the correct schema interface was called (filter/groupby/query/tag/cluster).
+
+## Recommended chaining
+- +get_analysis_query_schema -> +get_filter_schema -> +get_groupby_schema

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

@@ -0,0 +1,33 @@
+# te_analysis +get_filter_schema (get filter schema)
+
+> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+
+Domain: **Schema Queries**
+
+## Use Cases
+- Helper tool positioning: this command provides structure definitions (schema) and should be used as a prerequisite step.
+- Recommended order: call the schema tool first to get the structure, then call the specific business tool.
+- Typical downstream tools: `+create_virtual_event`, `+get_analysis_query_schema`, `+get_cluster_definition_schema`, `+get_groupby_schema`, `+get_tag_definition_schema`, `+query_dashboard_report_data`, `+query_report_data`
+- Get the filter schema. Returns field definitions, operator enums, data type descriptions, and examples.
+- Get the filter schema.
+
+## Commands
+```bash
+te-cli te_analysis +get_filter_schema
+te-cli te_analysis +get_filter_schema --dry-run
+```
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| None | - | This command has no business parameters; call it directly. |
+
+## Decision Rules
+- It is recommended to run `--dry-run` first to observe the request-body mapping before making the formal call.
+
+## Next Step After Failure
+- If reading fails, first verify whether the object ID exists and belongs to the current project.
+- If the schema does not match expectations, confirm whether the correct schema interface was called (filter/groupby/query/tag/cluster).
+
+## Recommended Chaining
+- +get_analysis_query_schema -> +get_filter_schema -> +get_groupby_schema

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

@@ -0,0 +1,33 @@
+# te_analysis +get_groupby_schema (Get Group-By Schema)
+
+> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+
+Domain: **Schema queries**
+
+## Use Cases
+- Helper tool positioning: this command provides structural definitions (schema) and should be used as a prerequisite step.
+- Recommended order: first use the current schema tool to get the structure, then call the specific business tool.
+- Typical follow-up tools: `+get_analysis_query_schema`, `+get_cluster_definition_schema`, `+get_filter_schema`, `+get_tag_definition_schema`, `+query_report_data`
+- Get the group-by schema. Returns field definitions and examples for group-by configuration.
+- Get the group-by schema.
+
+## Command
+```bash
+te-cli te_analysis +get_groupby_schema
+te-cli te_analysis +get_groupby_schema --dry-run
+```
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| None | - | This command has no business parameters; call it directly. |
+
+## Decision Rules
+- It is recommended to run `--dry-run` first to inspect the request body mapping before making the formal call.
+
+## Next Steps on Failure
+- If reading fails, first verify whether the object ID exists and belongs to the current project.
+- If the schema does not match expectations, confirm whether the correct schema interface was called (filter/groupby/query/tag/cluster).
+
+## Recommended chaining
+- +get_analysis_query_schema -> +get_filter_schema -> +get_groupby_schema

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

@@ -0,0 +1,33 @@
+# te_analysis +get_report_definition (read report definition)
+
+> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+
+Domain: **Report Management**
+
+## Use Cases
+- Get the definition details of a single report. Returns model type, event configuration, display configuration, and other definition data without executing a data query.
+- Get the definition details of a single report.
+- When interpreting report information, remember that for recent-day ranges, 1-N means the last N days (past N days), which is actually N+1 days ago through yesterday, while 0-N means the most recent N days, which is actually N days ago through today.
+
+## Commands
+```bash
+te-cli te_analysis +get_report_definition --project_id 1 --report_id 1
+te-cli te_analysis +get_report_definition --dry-run
+```
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project_id` / `-p` | Yes | Project ID |
+| `--report_id` / `-r` | Yes | Report ID |
+
+## Decision Rules
+- For the first run, it is recommended to pass only the required parameters (`--project_id`, `--report_id`) and add optional parameters after confirming the chain works.
+- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
+
+## Next Step After Failure
+- If required parameters are missing, fall back to the smallest runnable command and fill them in (focus on `--project_id`, `--report_id`).
+- If reading fails, first verify whether the object ID exists and belongs to the current project.
+
+## Recommended Chaining
+- +list_reports -> +get_report_definition -> +query_report_data

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

@@ -0,0 +1,38 @@
+# te_analysis +get_table_columns (Read Underlying Table Columns)
+
+> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+
+Domain: **Model analysis**
+
+## Use Cases
+- Query the field list of a project table. Returns all column names and types under the specified catalog, schema, and table so the table schema can be understood before SQL analysis.
+- Table guide:
+- default.public.ta_event_1: catalog is default, schema is public, table is ta_event_1
+- public.ta_event_1: catalog is hive(default value), schema is public, table is ta_event_1
+- ta_event_1: catalog is hive(default value), schema is ta(default value), table is ta_event_1
+- Query the field list of a project table.
+
+## 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
+```
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project_id` / `-p` | Yes | Project ID |
+| `--catalog` | Yes | Catalog name, default hive |
+| `--schema` | Yes | Schema name, default ta |
+| `--table` | Yes | Table name |
+
+## Decision Rules
+- On the first run, start with only the required parameters (`--project_id`,`--catalog`,`--schema`), and add optional parameters after confirming the path works.
+- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
+
+## Next Steps on Failure
+- If required parameters are missing, fall back to the smallest runnable command and fill them in first (focus on `--project_id`, `--catalog`, `--schema`).
+- If reading fails, first verify whether the object ID exists and belongs to the current project.
+
+## Recommended chaining
+- +get_table_columns

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

@@ -0,0 +1,33 @@
+# te_analysis +list_alerts (alert strategy search)
+
+> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+
+Domain: **Metadata Lookup**
+
+## Use Cases
+- List all alerts in the project. Supports keyword filtering by alert name. Returns a paginated list containing alerts array and pager result with total count.
+- List all alerts in the project.
+
+## 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
+```
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project_id` / `-p` | Yes | Project ID |
+| `--query` / `-q` | No | Optional keyword filter. Performs fuzzy matching against alert names; if omitted, all alerts are returned. |
+
+## Decision Rules
+- For the first run, it is recommended to pass only the required parameters (`--project_id`) and add optional parameters after confirming the chain works.
+- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
+
+## Next Step After Failure
+- If required parameters are missing, fall back to the smallest runnable command and fill them in (focus on `--project_id`).
+- If the result is empty, first confirm the project ID/keyword, then try broadening the filter conditions.
+
+## Recommended Chaining
+- +list_alerts

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

@@ -0,0 +1,33 @@
+# te_analysis +list_dashboards (List Dashboards)
+
+> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+
+Domain: **Dashboard management**
+
+## Use Cases
+- List dashboard metadata accessible to the current user in the project. Supports keyword filtering and returns dashboard IDs, names, descriptions, and related metadata, but not dashboard configuration or report data.
+- List dashboard metadata accessible to the current user in the project.
+
+## 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
+```
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project_id` / `-p` | Yes | Project ID |
+| `--query` / `-q` | No | Optional keyword filter. Performs fuzzy matching against dashboard names; if omitted, all accessible dashboards are returned. |
+
+## Decision Rules
+- On the first run, start with only the required parameters (`--project_id`), and add optional parameters after confirming the path works.
+- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
+
+## Next Steps on Failure
+- If required parameters are missing, fall back to the smallest runnable command and fill them in first (focus on `--project_id`).
+- If the result is empty, first confirm the project ID / keyword, then try loosening the filter conditions.
+
+## Recommended chaining
+- +list_dashboards -> +query_dashboard_detail -> +query_dashboard_report_data

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

@@ -0,0 +1,31 @@
+# te_analysis +list_public_access_links (public link search)
+
+> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+
+Domain: **Dashboard Management**
+
+## Use Cases
+- List public access links in the project. Returns link IDs, short codes, access targets, status, effective time, expiration time, and related metadata.
+- List public access links in the project.
+
+## Commands
+```bash
+te-cli te_analysis +list_public_access_links --project_id 1
+te-cli te_analysis +list_public_access_links --dry-run
+```
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project_id` / `-p` | Yes | Project ID |
+
+## Decision Rules
+- For the first run, it is recommended to pass only the required parameters (`--project_id`) and add optional parameters after confirming the chain works.
+- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
+
+## Next Step After Failure
+- If required parameters are missing, fall back to the smallest runnable command and fill them in (focus on `--project_id`).
+- If the result is empty, first confirm the project ID/keyword, then try broadening the filter conditions.
+
+## Recommended Chaining
+- +list_public_access_links -> +update_public_access_link

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

@@ -0,0 +1,33 @@
+# te_analysis +list_reports (List Reports)
+
+> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+
+Domain: **Report management**
+
+## Use Cases
+- List report metadata accessible to the current user in the project. Supports keyword filtering and returns report IDs, names, model types, update times, and related metadata, but not report definitions or analysis data.
+- List report metadata accessible to the current user in the project.
+
+## 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
+```
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project_id` / `-p` | Yes | Project ID |
+| `--query` / `-q` | No | Optional keyword filter. Performs fuzzy matching against report names and descriptions; if omitted, all accessible reports are returned. |
+
+## Decision Rules
+- On the first run, start with only the required parameters (`--project_id`), and add optional parameters after confirming the path works.
+- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
+
+## Next Steps on Failure
+- If required parameters are missing, fall back to the smallest runnable command and fill them in first (focus on `--project_id`).
+- If the result is empty, first confirm the project ID / keyword, then try loosening the filter conditions.
+
+## Recommended chaining
+- +list_reports -> +get_report_definition -> +query_report_data

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

@@ -0,0 +1,44 @@
+# te_analysis +load_filters (load filter candidate values)
+
+> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+
+Domain: **Model Analysis**
+
+## Use Cases
+- Load candidate values for a property. Queries the available enum values of the specified property (quot), which is useful when building filter conditions.
+- tableType values:
+- event: event property
+- user: user property
+- clusterDatePolicy is only used when tableType=user and user clusters are involved. Supported values: LATEST, AUTO, SPECIFIED.
+- Load candidate values for a property.
+
+## 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
+```
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project_id` / `-p` | Yes | Project ID |
+| `--quot` | Yes | Property identifier (field name). This is the property whose candidate values will be loaded. |
+| `--table_type` | Yes | Table type: event for event properties, user for user properties |
+| `--event_name` | No | Optional event name. When tableType=event, this can limit the query scope to a specific event. |
+| `--inputdata` | No | Optional input prefix used for fuzzy filtering of candidate values. If omitted, all candidate values are returned. |
+| `--zone_offset` | No | Time zone offset in hours. For example, UTC+8 is 8 |
+| `--cluster_date_policy` | No | Cluster date policy: LATEST, AUTO, or SPECIFIED |
+| `--specified_cluster_date` | No | Specified cluster date in yyyy-MM-dd format. Effective only when clusterDatePolicy=SPECIFIED. |
+| `--is_report` | No | Whether this is report mode. Default: false |
+
+## Decision Rules
+- For the first run, it is recommended to pass only the required parameters (`--project_id`, `--quot`, `--table_type`) and add optional parameters after confirming the chain works.
+- When dates/time ranges are involved, validate with a short range first and then expand gradually.
+- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
+
+## Next Step After Failure
+- If required parameters are missing, fall back to the smallest runnable command and fill them in (focus on `--project_id`, `--quot`, `--table_type`).
+
+## Recommended Chaining
+- +load_filters

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

@@ -0,0 +1,71 @@
+# te_analysis +query_adhoc (Ad Hoc Analysis Execution)
+
+> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+
+Domain: **Model analysis**
+
+## Use Cases
+- Precondition helper: call `+get_analysis_query_schema` to get the structure before using this tool.
+- When constructing a real `qp`, you must supplement it with real project metadata; first call `te_meta +list_events` and `te_meta +list_properties`.
+- 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.
+- Distribution analysis: bucketed distribution analysis.
+- Attribution analysis: multi-touch attribution analysis (first touch, last touch, linear attribution).
+- Interval analysis: time interval analysis between events.
+- Path analysis: user behavior path analysis.
+- Property analysis: user property distribution analysis.
+- Heat map: visual heat map analysis of user interactions.
+- Rank list: ranking / leaderboard analysis.
+- SQL: custom SQL analysis.
+- Process: fetch events/properties and the schema first, then assemble the query JSON, and finally execute the analysis.
+
+## Mandatory prerequisites (MUST)
+- Before constructing `--qp`, you must first read and follow these reference documents:
+  - [`./get-analysis-query-schema.md`](./get-analysis-query-schema.md)
+  - [`../../te-meta/references/list-events.md`](../../te-meta/references/list-events.md)
+  - [`../../te-meta/references/list-properties.md`](../../te-meta/references/list-properties.md)
+- Do not generate the final `qp` until the documentation review and prerequisite command calls are complete.
+
+## Prerequisite call chain (required for constructing qp)
+1. First determine `--model_type`.
+2. Read `get-analysis-query-schema.md`, then call `te-cli te_analysis +get_analysis_query_schema --model_type <model_type>` to get the structure.
+3. Read `list-events.md`, then call `te-cli te_meta +list_events --project_id 1` to get the available events.
+4. Read `list-properties.md`, then call `te-cli te_meta +list_properties --project_id 1` to get the available properties.
+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
+```
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--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`. |
+| `--request_id` | No | Optional unique request ID used for tracking and deduplication. Generated automatically if omitted. |
+| `--use_cache` | No | Whether to use result cache. Default: true |
+| `--zone_offset` | No | Time zone offset in hours. For example, UTC+8 is 8 and UTC-5 is -5 |
+| `--is_sort_by_columns` | No | Whether to sort query results by columns. Default: false |
+| `--resolve_recent_day` | No | Whether to resolve relative time expressions such as "last 7 days". Default: false |
+| `--timeout_minutes` | No | Query timeout in minutes. If the query exceeds this time, it will be cancelled automatically. |
+
+## Decision Rules
+- On the first run, start with only the required parameters (`--project_id`,`--model_type`,`--qp`), and add optional parameters after confirming the path works.
+- `qp` cannot be written from experience alone: it must satisfy both the schema structure and the project metadata constraints.
+- Before calling `list_events` / `list_properties`, you must first study the corresponding reference documents.
+- Wrap JSON parameters in single quotes (for example `--qp '{}'`) to avoid shell escaping issues.
+- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
+
+## Next Steps on Failure
+- If required parameters are missing, fall back to the smallest runnable command and fill them in first (focus on `--project_id`, `--model_type`, `--qp`).
+- If `Invalid JSON` appears, first check the schema required fields, then verify whether the event/property names come from metadata query results for the same `project_id`.
+- 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
+- +list_events -> +list_properties -> +query_adhoc -> +drilldown_users -> +drilldown_user_events

package/skills/te-analysis/references/query-dashboard-detail.md

@@ -0,0 +1,35 @@
+# te_analysis +query_dashboard_detail (read dashboard structure)
+
+> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+
+Domain: **Dashboard Management**
+
+## Use Cases
+- Get detailed information about a specific dashboard including:
+- Associated reports (IDs, names, types, and metadata)
+- Dashboard notes (IDs, titles, descriptions)
+- Share members (userId, userName, permissions)
+- Get detailed information about a specific dashboard including: - Associated reports (IDs, names, types, and metadata) - Dashboard notes (IDs, titles, descriptions) - Share members (userId, userName, permissions)
+
+## Commands
+```bash
+te-cli te_analysis +query_dashboard_detail --project_id 1 --dashboard_id 1
+te-cli te_analysis +query_dashboard_detail --dry-run
+```
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project_id` / `-p` | Yes | Project ID |
+| `--dashboard_id` / `-d` | Yes | Dashboard ID |
+
+## Decision Rules
+- For the first run, it is recommended to pass only the required parameters (`--project_id`, `--dashboard_id`) and add optional parameters after confirming the chain works.
+- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
+
+## Next Step After Failure
+- If required parameters are missing, fall back to the smallest runnable command and fill them in (focus on `--project_id`, `--dashboard_id`).
+- 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
+- +list_dashboards -> +query_dashboard_detail -> +query_dashboard_report_data

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

@@ -0,0 +1,60 @@
+# te_analysis +query_dashboard_report_data (Batch Query Dashboard Report Data)
+
+> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+
+Domain: **Dashboard management**
+
+## Use Cases
+- Precondition helper: call `+get_filter_schema` to get the structure before using this tool.
+- When constructing `filters`, you must supplement it with real event/property metadata from the project.
+- Query analysis data for one or more reports in a dashboard. Returns actual analysis results without the dashboard definition. Supports additional filters and time range overrides.
+- Query analysis data for one or more reports in a dashboard.
+
+## Mandatory prerequisites (MUST)
+- Before constructing `--filters`, you must first read and follow these reference documents:
+  - [`./get-filter-schema.md`](./get-filter-schema.md)
+  - [`../../te-meta/references/list-events.md`](../../te-meta/references/list-events.md)
+  - [`../../te-meta/references/list-properties.md`](../../te-meta/references/list-properties.md)
+- 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`.
+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
+```
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--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`. |
+| `--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. |
+| `--use_cache` | No | Whether to use cache. Default: true |
+| `--report_ids` | No | Optional list of report IDs. If omitted, all reports in the dashboard are queried. |
+
+## Decision Rules
+- `filters` cannot be written from experience alone: it must satisfy both the filter schema and the project metadata constraints.
+- Before calling `list_events` / `list_properties`, you must first study the corresponding reference documents.
+- On the first run, start with only the required parameters (`--project_id`, `--dashboard_id`) and add optional parameters after confirming the path works.
+- Wrap JSON parameters in single quotes (for example `--filters '{}'`, `--report_ids '[]'`) to avoid shell escaping issues.
+- When dates/time ranges are involved, first verify with a short range, then gradually expand the range.
+- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
+
+## Next Steps on Failure
+- If required parameters are missing, fall back to the smallest runnable command and fill them in first (focus on `--project_id`, `--dashboard_id`).
+- If `Invalid JSON` appears, first check the filter schema required fields, then verify whether the event/property names come from metadata query results for the same `project_id`.
+- 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
+- +list_dashboards -> +query_dashboard_detail -> +query_dashboard_report_data

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

@@ -0,0 +1,60 @@
+# te_analysis +query_entity_details (query entity details)
+
+> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+
+Domain: **Entity Detail Queries**
+
+## Use Cases
+- When building `definition`, first obtain the cluster schema and supplement it with the project's real event/property metadata.
+- Query entity detail data. Returns user detail results based on the entity ID and cluster definition, and supports display properties, sorting, and result limits.
+- Query entity detail data.
+
+## 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)
+- Do not generate final `definition` / `properties` until the above docs have been read and the prerequisite commands have been called.
+
+## Prerequisite Call Chain (required for building definition/properties)
+1. First confirm the cluster type (condition / sql).
+2. Read `get-cluster-definition-schema.md`, then call `ae-cli te_audience +get_cluster_definition_schema --cluster_type <condition|sql>` to get the structure.
+3. Read `list-events.md`, then call `ae-cli te_meta +list_events --project_id 1`.
+4. Read `list-properties.md`, then call `ae-cli te_meta +list_properties --project_id 1`.
+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
+```
+
+## Parameters
+| Parameter | Required | Description                                                                                                                                                                                                                                      |
+|---|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `--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`. |
+| `--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                                                                                                                                                                                    |
+| `--zone_offset` | No | Time zone offset. For example, UTC+8 is 8                                                                                                                                                                                               |
+| `--use_cache` | No | Whether to use cache. Default: true                                                                                                                                                                                                     |
+
+## Decision Rules
+- `definition` / `properties` cannot be written by hand based on experience alone: they must satisfy both the schema structure and the project's real metadata.
+- `list_events` / `list_properties` must be learned from the corresponding reference docs before calling them.
+- For the first run, it is recommended to pass only the required parameters (`--project_id`, `--definition`) and add optional parameters after confirming the chain works.
+- Wrap JSON parameters in single quotes (for example `--definition '{}'`, `--properties '{}'`) to avoid shell escaping issues.
+- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
+
+## Next Step After Failure
+- If required parameters are missing, fall back to the smallest runnable command and fill them in (focus on `--project_id`, `--definition`).
+- If `Invalid JSON` appears, first check the required schema fields, then verify that the event name/property name comes from metadata queried in the same `project_id`.
+- 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
+- +query_entity_details -> +query_event_details -> +build_event_details_sql