@thinkingai/ae-cli 1.0.30 → 6.0.16-1

package/skills/ae-analysis/SKILL.md

@@ -1,11 +1,12 @@
 ---
 name: ae-analysis
-version: 3.0.0
+version: 3.1.0
 description: "AE/TE/ThinkingEngine/ThinkingAI ae-cli manual for analysis-side tasks in the AE system or analysis platform: reports, dashboards, alerts, ad hoc analysis, drilldown, audience clusters, tags, tag members, metrics and metric definitions, events, properties, virtual events, virtual properties, metadata, project configuration, tracking plans, event tracking, mark times, project lists, and resource links. Use when the user asks to query, create, update, refresh, inspect, troubleshoot, govern, or manage these AE analysis assets. Must use ae-cli, read the matching references/<tool_name>.md command manual before composing commands, and never guess command names, flags, JSON payloads, project_id, resource IDs, or parameter formats."
 ---
 
 # ae-analysis
 
+> **CRITICAL - This skill is self-contained.** Use the Global AE CLI Rules below; do not require a separate shared skill for analysis-side tasks.
 > **CRITICAL - For all commands that require `project_id`, you MUST satisfy `PROJECT_ID_GATE` first (no guessing): verify the project by ID/name with `analysis_common +list_projects` only when there is no valid project context yet, when the user switches project/host/environment, or when the supplied project is ambiguous. Reuse a project already verified in the same continuous conversation and same host/environment.**
 > **CRITICAL - For write operations in this skill, you MUST complete the post-write link loop when applicable:** after success and extractable `resource_id`, call `analysis_common +get_resource_url` and return the main result + resource link (or explicit link-failure reason).
 > **CRITICAL - Before running any `+<tool_name>` command, you MUST first read the corresponding `references/<tool_name>.md`.** The reference filename always equals the command name without the leading `+`, for example `+query_adhoc` -> `references/query_adhoc.md`.
@@ -195,9 +196,102 @@ Legacy query_adhoc chain:
 3. Build QP manually from the documented schema and verified project metadata.
 4. Call `+query_adhoc`.
 
-## Tool Groups (73)
+### F. ABSOLUTE_CONTRIBUTION_ATTRIBUTION
 
-### analysis (35)
+**When attributing a metric change to dimensions, you MUST use Absolute Contribution Decomposition. Never judge the primary driver based solely on relative change percentage.**
+
+#### Problem Definition
+
+Base rate fallacy causes inaccurate attribution:
+
+| Dimension | Baseline | Comparison | Absolute Δ | Relative Δ | Contribution |
+|-----------|----------|------------|-----------|-----------|-------------|
+| A         | 1        | 5          | +4        | +400%     | **40%**     |
+| B         | 50       | 55         | +5        | +10%      | **50%**     |
+| C         | 49       | 50         | +1        | +2%       | **10%**     |
+
+Wrong: "Dimension A grew 400%, it is the main driver."
+Correct: "Dimension B contributed 50% of the absolute increase (+5), making it the primary driver."
+
+#### Algorithm
+
+##### Scenario 1: Additive Metrics
+
+Use this for count-based metrics such as DAU, event counts, and payment amounts.
+
+```
+delta_total = V_total(comparison) - V_total(baseline)
+delta_dim_i = V_dim_i(comparison) - V_dim_i(baseline)
+contribution_pct_i = delta_dim_i / delta_total * 100%
+```
+
+- Sort by `|delta_dim_i|` in descending order.
+- Do not sort by `delta_dim_i / V_dim_i(baseline)`.
+
+##### Scenario 2: Ratio / Conversion Metrics
+
+Ratio changes come from two components:
+- **Composition effect**: changes in subgroup weight.
+- **Rate effect**: changes in each subgroup's own rate.
+
+Simplified mode is the default:
+
+```
+rate_change = R_total(comparison) - R_total(baseline)
+```
+
+Report subgroup rates hierarchically and call out structural impact in the conclusion.
+
+Precise decomposition is only required when the user explicitly requests structural breakdown:
+
+```
+contribution_rate_i   = w_i(baseline) * [R_i(comparison) - R_i(baseline)]
+contribution_weight_i = [w_i(comparison) - w_i(baseline)] * R_i(baseline)
+```
+
+Where `w_i` is the subgroup's share of total users.
+
+#### Execution Workflow
+
+1. Identify metric type: additive uses Scenario 1, ratio uses Scenario 2.
+2. Fetch baseline total and dimension values with `query_adhoc` and grouped dimensions.
+3. Fetch comparison total and dimension values with the same scope.
+4. Compute `delta_dim_i` for each dimension.
+5. Compute `contribution_pct_i = delta_dim_i / delta_total * 100%`.
+6. Sort by absolute contribution magnitude and preserve sign.
+7. Present the conclusion.
+
+If the builder supports comparison mode for both periods in one query, prefer it to avoid two `query_adhoc` calls.
+
+#### Output Format
+
+```
+Core conclusion: [Metric] from [baseline] to [comparison], changed by [±][absolute] ([±][percent])
+
+Dimension contribution ranking (by absolute contribution, descending):
+1. [dimension value] -> [±][absolute delta] (contributed [xx]%), relative change [±][percent]
+2. [dimension value] -> [±][absolute delta] (contributed [xx]%), relative change [±][percent]
+...
+
+Conclusion: "[Metric] [increase/decrease] was primarily driven by [top dimension] (contributed [xx]% of the change), followed by [second dimension] ([xx]%)"
+```
+
+If any dimension shows a cross-effect, such as positive contribution but negative relative change, call it out explicitly.
+
+#### Exceptions
+
+Skip absolute contribution decomposition when:
+- The user explicitly asks for growth-rate or percentage-change ranking only.
+- The user asks for a single dimension's trend without cross-dimension comparison.
+- A dimension baseline is zero; mark it as a new dimension separately.
+
+#### Self-Check
+
+After outputting attribution results, verify that dimension contributions sum to approximately 100%. If the sum deviates from 100% by more than 5 percentage points, flag that some dimensions may be missing or data scoping may be inconsistent.
+
+## Tool Groups (79)
+
+### analysis (40)
 
 Alerts (5):
 - `+get_alert_definition_schema` ([doc](references/get_alert_definition_schema.md))
@@ -206,11 +300,12 @@ Alerts (5):
 - `+create_alert` ([doc](references/create_alert.md))
 - `+update_alert` ([doc](references/update_alert.md))
 
-Reports and Dashboards (13):
+Reports and Dashboards (17):
 - `+create_report` ([doc](references/create_report.md))
 - `+get_report_definition` ([doc](references/get_report_definition.md))
 - `+list_reports` ([doc](references/list_reports.md))
 - `+query_report_data` ([doc](references/query_report_data.md))
+- `+create_space` ([doc](references/create_space.md))
 - `+create_dashboard` ([doc](references/create_dashboard.md))
 - `+list_dashboards` ([doc](references/list_dashboards.md))
 - `+query_dashboard_detail` ([doc](references/query_dashboard_detail.md))
@@ -220,13 +315,17 @@ Reports and Dashboards (13):
 - `+list_public_access_links` ([doc](references/list_public_access_links.md))
 - `+create_public_access_link` ([doc](references/create_public_access_link.md))
 - `+update_public_access_link` ([doc](references/update_public_access_link.md))
+- `+list_bi_panels` ([doc](references/list_bi_panels.md))
+- `+get_bi_panel_detail` ([doc](references/get_bi_panel_detail.md))
+- `+query_bi_panel_data` ([doc](references/query_bi_panel_data.md))
 
-Model Analysis (10):
+Model Analysis (11):
 - `+build_event_analysis_qp` ([doc](references/build_event_analysis_qp.md))
 - `+build_retention_analysis_qp` ([doc](references/build_retention_analysis_qp.md))
 - `+build_funnel_analysis_qp` ([doc](references/build_funnel_analysis_qp.md))
 - `+build_prop_analysis_qp` ([doc](references/build_prop_analysis_qp.md))
 - `+query_adhoc` ([doc](references/query_adhoc.md))
+- `+cancel_query` ([doc](references/cancel_query.md))
 - `+drilldown_users` ([doc](references/drilldown_users.md))
 - `+drilldown_user_events` ([doc](references/drilldown_user_events.md))
 - `+create_result_cluster` ([doc](references/create_result_cluster.md))
@@ -266,7 +365,7 @@ Schema Definitions (2):
 - `+get_cluster_definition_schema` ([doc](references/get_cluster_definition_schema.md))
 - `+get_tag_definition_schema` ([doc](references/get_tag_definition_schema.md))
 
-### analysis_meta (20)
+### analysis_meta (23)
 
 Metadata and Governance (10):
 - `+list_events` ([doc](references/list_events.md))
@@ -293,7 +392,8 @@ Project and Tracking (11):
 - `+list_project_mark_times` ([doc](references/list_project_mark_times.md))
 - `+delete_project_mark_times` ([doc](references/delete_project_mark_times.md))
 
-Entity Catalog (1):
+Entity Catalog (2):
+- `+create_entity` ([doc](references/create_entity.md))
 - `+list_entities` ([doc](references/list_entities.md))
 
 ### analysis_common (2)
@@ -316,4 +416,4 @@ npm run verify:analysis-common-tools
 
 ## Reference Docs
 
-See the unified `references/` directory (73 command docs total).
+See the unified `references/` directory (79 command docs total).

package/skills/ae-analysis/references/cancel_query.md

@@ -0,0 +1,39 @@
+# analysis +cancel_query (cancel MCP query)
+
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
+
+Domain: **Query lifecycle**
+
+## Use Cases
+- Cancel a running MCP query when the user asks to stop waiting.
+- Cancel a query when the caller or agent timed out before the query returned but it may still be running on the server.
+- Cancel a query by the same `requestId` that was supplied to or returned by a previous query command.
+- For proactive cancellation, pass `requestId` to the query tool before starting it, then call `cancel_query` with the same value if you stop waiting.
+- If a query returns `fetch failed`, hits an HTTP timeout, or the caller stops waiting, the backend query may still be running; call `+cancel_query --request_id <same value>` with the preset `requestId`.
+- auto-generated requestId is not available when the HTTP request fails before a response, so preset `requestId` before any query that may exceed the CLI/MCP HTTP timeout.
+
+## Command
+```bash
+ae-cli analysis +cancel_query --request_id mcp_0123456789abcdef0123456789abcdef --yes
+ae-cli analysis +cancel_query --request_id mcp_0123456789abcdef0123456789abcdef --reason "agent timeout" --yes
+ae-cli analysis +cancel_query --request_id mcp_0123456789abcdef0123456789abcdef --dry-run
+```
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--request_id` | Yes | Request ID returned by a query tool in `metadata.requestId`, or the requestId supplied before starting the query. It must use `mcp_<32 lowercase hex UUID>`, for example `mcp_0123456789abcdef0123456789abcdef`. |
+| `--reason` | No | Optional cancellation reason. Default: `MCP_CANCEL_QUERY_TOOL`. |
+
+## Decision Rules
+- This is a write operation. Use `--yes` only when the user clearly asked to cancel or stop a running query.
+- The request must belong to the current MCP user. Otherwise the service returns `REQUEST_NOT_FOUND_OR_NOT_OWNED`.
+- Do not invent a request ID. Use the ID from the query response or the ID explicitly supplied to the original query.
+- This command cancels by request ID only. It does not cancel by SQL text, report ID, dashboard ID, BI panel ID, run ID, or tool call ID.
+- For query commands that expose `--request_id`, prefer supplying a stable ID before execution using `mcp_<32 lowercase hex UUID>`, for example `mcp_0123456789abcdef0123456789abcdef`, so proactive cancellation does not depend on waiting for the response metadata.
+- For query commands that may exceed the CLI/MCP HTTP timeout, preset `--request_id`; if `fetch failed`, HTTP timeout, or caller timeout happens, immediately call `+cancel_query --request_id <same value> --yes`.
+- For commands that do not expose caller-supplied `request_id`, cancel only if the response includes a request ID.
+
+## Next Steps on Failure
+- If `REQUEST_NOT_FOUND_OR_NOT_OWNED` appears, verify the request ID, user identity, host, and whether the original query already finished.
+- If cancellation succeeds but the UI still shows stale data, refresh the query status/result surface rather than sending another cancel blindly.

package/skills/ae-analysis/references/drilldown_user_events.md

@@ -31,7 +31,7 @@ Domain: **Model analysis**
 ## Command
 ```bash
 ae-cli analysis +drilldown_user_events --project_id <project_id> --user_id u_123 --event_names '["login"]' --target_dates '["2026-04-08 00:00:00"]'
-ae-cli analysis +drilldown_user_events --project_id <project_id> --user_id u_123 --event_names '["login"]' --target_dates '["2026-04-08 00:00:00"]' --zone_offset 8 --use_cache true --page_num 1 --page_size 20
+ae-cli analysis +drilldown_user_events --project_id <project_id> --user_id u_123 --event_names '["login"]' --target_dates '["2026-04-08 00:00:00"]' --zone_offset 8 --use_cache true --page_num 1 --page_size 20 --request_id mcp_bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
 ae-cli analysis +drilldown_user_events --dry-run
 ```
 
@@ -55,13 +55,15 @@ ae-cli analysis +drilldown_user_events --dry-run
 | `--entity_value` | No | Optional entity value for multi-entity scenarios |
 | `--use_cache` | No | Whether to use cache. Default: true |
 | `--page_num` | No | Start page number, default 1 |
-| `--page_size` | No | Page size. Default: 1000, maximum: 100000 |
+| `--page_size` | No | Page size. Default: 1000, maximum: 10000 |
+| `--request_id` | No | Optional unique request ID used for tracking and cancellation. If provided, it must use `mcp_<32 lowercase hex UUID>`, for example `mcp_0123456789abcdef0123456789abcdef`. For long-running or cancelable queries, provide this before starting the query so it can be cancelled later with `+cancel_query --request_id <same value>`, even if the caller stops waiting before the tool returns. If `fetch failed`, HTTP timeout, or caller timeout happens, the backend query may still be running. The auto-generated requestId is not available when the HTTP request fails before a response, so preset `requestId` is required for proactive cleanup. Generated automatically if omitted. The response `metadata.requestId` can also be passed to `cancel_query` when the query is no longer needed. |
 | `--timeout_minutes` | No | Query timeout in minutes |
 
 ## Decision Rules
 - `user_id` / `event_names` / `target_dates` must come from the previous step result and must not be constructed out of thin air.
 - On the first run, start with only the required parameters (`--project_id`,`--user_id`,`--event_names`,`--target_dates`), and add optional parameters after confirming the path works.
 - Wrap JSON parameters in single quotes (for example `--event_names '[]'`, `--target_dates '[]'`) to avoid shell escaping issues.
+- For long-running or cancelable drilldowns, supply your own `--request_id` before starting so `+cancel_query` can cancel by the same ID if the caller or user stops waiting. If `fetch failed`, HTTP timeout, or caller timeout happens, the backend query may still be running; call `+cancel_query --request_id <same value>` with the preset ID. The auto-generated requestId is not available when the HTTP request fails before a response. The value must use `mcp_<32 lowercase hex UUID>`, for example `mcp_0123456789abcdef0123456789abcdef`.
 - For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
 
 ## Next Steps on Failure

package/skills/ae-analysis/references/drilldown_users.md

@@ -30,7 +30,7 @@ Domain: **Model Analysis**
 ## Commands
 ```bash
 ae-cli analysis +drilldown_users --project_id <project_id> --model_type event --qp '{}'
-ae-cli analysis +drilldown_users --project_id <project_id> --model_type retention --qp '{}' --drilldown_date 2026-04-08 --drilldown_groups '[]' --event_index 8 --is_lost true --retention_days 8 --is_churned_user true --funnel_step 8 --interval demo --distribution_bucket 8 --compare_index 8 --include_total true --relation_val demo --limit 10 --offset 0
+ae-cli analysis +drilldown_users --project_id <project_id> --model_type retention --qp '{}' --drilldown_date 2026-04-08 --drilldown_groups '[]' --event_index 8 --is_lost true --retention_days 8 --is_churned_user true --funnel_step 8 --interval demo --distribution_bucket 8 --compare_index 8 --include_total true --relation_val demo --limit 10 --offset 0 --request_id mcp_cccccccccccccccccccccccccccccccc
 ae-cli analysis +drilldown_users --dry-run
 ```
 
@@ -55,14 +55,16 @@ ae-cli analysis +drilldown_users --dry-run
 | `--include_total` | No | Whether to query users from the total row. Default: false |
 | `--relation_val` | No | Relation value used in relation analysis scenarios |
 | `--use_cache` | No | Whether to use cache. Default: true |
-| `--limit` | No | Optional limit. Default: 1000, maximum: 100000. |
+| `--limit` | No | Optional limit. Default: 1000, maximum: 10000. |
 | `--offset` | No | Optional offset. Default: 0. |
+| `--request_id` | No | Optional unique request ID used for tracking and cancellation. If provided, it must use `mcp_<32 lowercase hex UUID>`, for example `mcp_0123456789abcdef0123456789abcdef`. For long-running or cancelable queries, provide this before starting the query so it can be cancelled later with `+cancel_query --request_id <same value>`, even if the caller stops waiting before the tool returns. If `fetch failed`, HTTP timeout, or caller timeout happens, the backend query may still be running. The auto-generated requestId is not available when the HTTP request fails before a response, so preset `requestId` is required for proactive cleanup. Generated automatically if omitted. The response `metadata.requestId` can also be passed to `cancel_query` when the query is no longer needed. |
 | `--timeout_minutes` | No | Query timeout in minutes. If the query exceeds this time, it will be cancelled automatically. |
 
 ## Decision Rules
 - Drilldown positioning parameters must come from upstream analysis results and must not be fabricated.
 - `qp` must not be rewritten or "simplified"; it should remain consistent with the source analysis.
 - For pagination, use `--limit` and `--offset` together. Default limit is 1000, maximum 100000.
+- For long-running or cancelable drilldowns, supply your own `--request_id` before starting so `+cancel_query` can cancel by the same ID if the caller or user stops waiting. If `fetch failed`, HTTP timeout, or caller timeout happens, the backend query may still be running; call `+cancel_query --request_id <same value>` with the preset ID. The auto-generated requestId is not available when the HTTP request fails before a response. The value must use `mcp_<32 lowercase hex UUID>`, for example `mcp_0123456789abcdef0123456789abcdef`.
 - For the first run, it is recommended to pass only the required parameters (`--project_id`, `--model_type`, `--qp`) and add optional parameters after confirming the chain works.
 - Wrap JSON parameters in single quotes (for example `--qp '{}'`, `--drilldown_groups '{}'`) to avoid shell escaping issues.
 - When dates/time ranges are involved, validate with a short range first and then expand gradually.

package/skills/ae-analysis/references/get_bi_panel_detail.md

@@ -0,0 +1,35 @@
+# analysis +get_bi_panel_detail (read BI panel structure)
+
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
+
+Domain: **BI panel management**
+
+## Use Cases
+- Read a BI panel's released structure without querying data.
+- Inspect pages, queryable charts, summary page metadata, dashboard-level parameter controls, dashboard-level permission controls, and page chart filter controls.
+- Get `pageKey`, `chartId`, `defaultColumns`, and control schemas needed by `+query_bi_panel_data`.
+
+## Command
+```bash
+ae-cli analysis +get_bi_panel_detail --project_id <project_id> --panel_id <panel_id>
+ae-cli analysis +get_bi_panel_detail --project_id <project_id> --panel_id <panel_id> --fields '["basic","pages","charts","parameterControls","permissionControls","chartFilterControls","summary"]'
+ae-cli analysis +get_bi_panel_detail --project_id <project_id> --panel_id <panel_id> --dry-run
+```
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project_id` / `-p` | Yes | Project ID |
+| `--panel_id` | Yes | BI panel ID returned by `+list_bi_panels` |
+| `--fields` / `-f` | No | Optional detail sections. Supported values: `basic`, `pages`, `charts`, `parameterControls`, `permissionControls`, `chartFilterControls`, `summary`. |
+
+## Decision Rules
+- This command reads the released BI panel version only. It does not expose version selection.
+- Use `charts` and the three control sections when preparing `+query_bi_panel_data`.
+- `parameterControls` are dashboard-level parameter controls and keep single-value semantics.
+- `permissionControls` are dashboard-level permission control values. Their `allowedValues` are hints, not an MCP-side whitelist.
+- `chartFilterControls` are page-level filter controls and apply only to their `boundChartIds`. Some filters are stored as `pageCharts` components and are returned as non-queryable filter controls.
+- Do not infer internal fields such as `paramList`, `permissionFilters`, `visualCfg`, `whereList`, `field`, `columnName`, `userId`, or `openId`.
+
+## Recommended Chaining
+- `+list_bi_panels` -> `+get_bi_panel_detail` -> `+query_bi_panel_data`

package/skills/ae-analysis/references/list_alerts.md

@@ -25,7 +25,7 @@ ae-cli analysis +list_alerts --dry-run
 |---|---|---|
 | `--project_id` / `-p` | Yes | Project ID |
 | `--query` / `-q` | No | Optional keyword filter. Performs fuzzy matching against alert names; if omitted, all alerts are returned. |
-| `--limit` / `-l` | No | Optional page size. Default: 20, maximum: 50. |
+| `--limit` / `-l` | No | Optional page size. Default: 20, maximum: 10000. |
 | `--offset` / `-o` | No | Optional page offset. Default: 0. |
 
 ## Decision Rules

package/skills/ae-analysis/references/list_bi_panels.md

@@ -0,0 +1,35 @@
+# analysis +list_bi_panels (list BI panels)
+
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
+
+Domain: **BI panel management**
+
+## Use Cases
+- Discover BI panels accessible to the current MCP user in a project.
+- Search BI panels by name before asking for structure or data.
+- Get lightweight panel metadata such as `panelId`, `name`, `pageCount`, and `hasSummary`.
+
+## Command
+```bash
+ae-cli analysis +list_bi_panels --project_id <project_id>
+ae-cli analysis +list_bi_panels --project_id <project_id> --query "history" --fields '["panelId","name","pageCount","hasSummary"]' --limit 20 --offset 0
+ae-cli analysis +list_bi_panels --project_id <project_id> --dry-run
+```
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project_id` / `-p` | Yes | Project ID |
+| `--query` / `-q` | No | Optional keyword filter. Fuzzy matches BI panel names. |
+| `--fields` / `-f` | No | Optional returned fields. Supported values: `panelId`, `name`, `spaceId`, `spaceName`, `ownerName`, `updatedAt`, `pageCount`, `hasSummary`. |
+| `--limit` / `-l` | No | Optional page size. Default: 20, maximum: 10000. |
+| `--offset` / `-o` | No | Optional page offset. Default: 0. |
+
+## Decision Rules
+- Use this before `+get_bi_panel_detail` unless the target `panel_id` is already verified in the same project and host.
+- Do not use this command to inspect pages, charts, controls, raw config, SQL, or permission rules.
+- Do not pass `userId` or `openId`; the service uses the current MCP user.
+- If no panel is found by keyword, broaden the keyword or list accessible panels and ask the user to choose.
+
+## Recommended Chaining
+- `+list_bi_panels` -> `+get_bi_panel_detail` -> `+query_bi_panel_data`

package/skills/ae-analysis/references/list_cluster_members.md

@@ -13,7 +13,7 @@ Domain: **Cluster Management**
 ```bash
 ae-cli analysis_audience +list_cluster_members --project_id <project_id> --cluster_name demo
 ae-cli analysis_audience +list_cluster_members --project_id <project_id> --cluster_name demo --property_names '["#user_id","name"]' --use_cache false
-ae-cli analysis_audience +list_cluster_members --project_id <project_id> --cluster_name demo --query user_001 --fields '["#user_id","name"]' --limit 20 --offset 0
+ae-cli analysis_audience +list_cluster_members --project_id <project_id> --cluster_name demo --query user_001 --fields '["#user_id","name"]' --limit 20 --offset 0 --request_id mcp_aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa --timeout_minutes 8
 ae-cli analysis_audience +list_cluster_members --dry-run
 ```
 
@@ -28,10 +28,13 @@ ae-cli analysis_audience +list_cluster_members --dry-run
 | `--fields` | No | Optional return field list (JSON array). Invalid fields will fail with `INVALID_FIELDS`. |
 | `--limit` | No | Optional page size. Default: 20, max: 50. |
 | `--offset` | No | Optional page offset. Default: 0. |
+| `--request_id` | No | Optional unique request ID used for tracking and cancellation. If provided, it must use `mcp_<32 lowercase hex UUID>`, for example `mcp_0123456789abcdef0123456789abcdef`. For long-running or cancelable queries, provide this before starting the query so it can be cancelled later with `+cancel_query --request_id <same value>`, even if the caller stops waiting before the tool returns. If `fetch failed`, HTTP timeout, or caller timeout happens, the backend query may still be running. The auto-generated requestId is not available when the HTTP request fails before a response, so preset `requestId` is required for proactive cleanup. Generated automatically if omitted. The response `metadata.requestId` can also be passed to `cancel_query` when the query is no longer needed. |
+| `--timeout_minutes` | No | Query timeout in minutes. If omitted, 30 minutes is used. |
 
 ## Decision Rules
 - 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.
 - `--property_names` must be passed as a JSON array (e.g. `--property_names '["#user_id"]'`).
+- For long-running or cancelable member queries, supply your own `--request_id` before starting so `analysis +cancel_query` can cancel by the same ID if the caller or user stops waiting. If `fetch failed`, HTTP timeout, or caller timeout happens, the backend query may still be running; call `+cancel_query --request_id <same value>` with the preset ID. The auto-generated requestId is not available when the HTTP request fails before a response. The value must use `mcp_<32 lowercase hex UUID>`, for example `mcp_0123456789abcdef0123456789abcdef`.
 - When troubleshooting across projects, first confirm whether `--project_id` matches the current permissions and target environment.
 
 ## Next Step on Failure

package/skills/ae-analysis/references/list_dashboards.md

@@ -28,7 +28,7 @@ ae-cli analysis +list_dashboards --dry-run
 | `--project_id` / `-p` | Yes | Project ID |
 | `--query` / `-q` | No | Optional keyword filter. Performs fuzzy matching against dashboard names and AI remarks; if omitted, all accessible dashboards are returned. |
 | `--fields` / `-f` | No | Optional fields to return (JSON array). Supported fields: `dashboardId`, `dashboardName`, `aiRemark`. |
-| `--limit` / `-l` | No | Optional page size. Default: 20, maximum: 50. |
+| `--limit` / `-l` | No | Optional page size. Default: 20, maximum: 10000. |
 | `--offset` / `-o` | No | Optional page offset. Default: 0. |
 
 ## Decision Rules

package/skills/ae-analysis/references/list_entities.md

@@ -24,7 +24,7 @@ ae-cli analysis_meta +list_entities --dry-run
 | `--event_name` | No | Optional event name filter |
 | `--query` / `-q` | No | Optional keyword filter. Fuzzy match is applied to entityName, columnName, and columnDesc; if omitted, all accessible dashboards are returned. |
 | `--fields` / `-f` | No | Optional fields to return (JSON array). Supported fields: `entityId`, `entityName`, `columnName`, `columnDesc`, `selectType`. |
-| `--limit` / `-l` | No | Optional page size. Default: 20, maximum: 50. |
+| `--limit` / `-l` | No | Optional page size. Default: 20, maximum: 10000. |
 | `--offset` / `-o` | No | Optional page offset. Default: 0. |
 
 

package/skills/ae-analysis/references/list_events.md

@@ -28,7 +28,7 @@ ae-cli analysis_meta +list_events --dry-run
 | `--project_id` / `-p` | Yes | Project ID |
 | `--query` / `-q` | No | Optional keyword filter. Performs fuzzy matching against eventName, eventDesc, and aiRemark; if omitted, all events are returned. |
 | `--fields` / `-f` | No | Optional fields to return (JSON array). Supported fields: `eventName`, `eventDesc`, `aiRemark`, `eventTag`, `remark`. |
-| `--limit` / `-l` | No | Optional page size. Default: 20, maximum: 50. |
+| `--limit` / `-l` | No | Optional page size. Default: 20, maximum: 10000. |
 | `--offset` / `-o` | No | Optional page offset. Default: 0. |
 ## Decision Rules
 - For the first run, pass only the required parameter (`--project_id`) to confirm the path works, then add optional parameters.

package/skills/ae-analysis/references/list_metrics.md

@@ -30,7 +30,7 @@ ae-cli analysis_meta +list_metrics --dry-run
 | `--project_id` / `-p` | Yes | Project ID |
 | `--query` / `-q` | No | Optional keyword filter. Fuzzy match on metricName, metricDesc, metricRemark. |
 | `--fields` | No | Optional fields to return. Supported: metricId, metricName, metricDesc, metricRemark, metricMode, openId, creator, creatorLoginName, updateOpenId, updateCreator, updateLoginName, createTime, updateTime. Invalid fields cause INVALID_FIELDS error. |
-| `--limit` | No | Optional limit. Default: 20, maximum: 50. |
+| `--limit` | No | Optional limit. Default: 20, maximum: 10000. |
 | `--offset` | No | Optional offset. Default: 0. |
 
 ## Decision Rules

package/skills/ae-analysis/references/list_project_mark_times.md

@@ -24,7 +24,7 @@ ae-cli analysis_meta +list_project_mark_times --dry-run
 | `--zone_offset` | No | Marker time zone offset |
 | `--query` / `-q` | No | Optional keyword filter. Fuzzy match on markContent. |
 | `--fields` | No | Optional fields to return. Supported: id, projectId, markTime, userZoneTime, zoneOffset, markContent, isShow, creatorName, creatorId, lastModifierName, lastModifierId, createTime, updateTime. Invalid fields cause INVALID_FIELDS error. |
-| `--limit` | No | Optional limit. Default: 20, maximum: 50. |
+| `--limit` | No | Optional limit. Default: 20, maximum: 10000. |
 | `--offset` | No | Optional offset. Default: 0. |
 
 ## Decision Rules

package/skills/ae-analysis/references/list_properties.md

@@ -28,7 +28,7 @@ ae-cli analysis_meta +list_properties --dry-run
 | `--event_name` | No | Optional event name. If provided, only event properties available for that event are returned. |
 | `--query` / `-q` | No | Optional keyword filter. Fuzzy match is applied to propName, propDesc, and aiRemark; if omitted, all matched properties are returned. |
 | `--fields` / `-f` | No | Optional fields to return (JSON array). Supported fields: `propName`, `propDesc`, `aiRemark`, `selectType`, `tableType`, `subTableType`. |
-| `--limit` / `-l` | No | Optional page size. Default: 20, maximum: 50. |
+| `--limit` / `-l` | No | Optional page size. Default: 20, maximum: 10000. |
 | `--offset` / `-o` | No | Optional page offset. Default: 0. |
 
 

package/skills/ae-analysis/references/list_public_access_links.md

@@ -23,7 +23,7 @@ ae-cli analysis +list_public_access_links --dry-run
 | `--project_id` / `-p` | Yes | Project ID |
 | `--query` / `-q` | No | Optional keyword filter. Fuzzy match on shorter and remarks. |
 | `--fields` | No | Optional fields to return. Supported: id, shorter, creator, projectIdAndName, source, accessId, target, options, remarks, accessStatus, effectTime, expireTime, createTime, updateTime. Invalid fields cause INVALID_FIELDS error. |
-| `--limit` | No | Optional limit. Default: 20, maximum: 50. |
+| `--limit` | No | Optional limit. Default: 20, maximum: 10000. |
 | `--offset` | No | Optional offset. Default: 0. |
 
 ## Decision Rules

package/skills/ae-analysis/references/list_reports.md

@@ -28,7 +28,7 @@ ae-cli analysis +list_reports --dry-run
 | `--project_id` / `-p` | Yes | Project ID |
 | `--query` / `-q` | No | Optional keyword filter. Performs fuzzy matching against report names, descriptions, and AI remarks; if omitted, all accessible reports are returned. |
 | `--fields` / `-f` | No | Optional fields to return (JSON array). Supported fields: `reportId`, `reportName`, `reportDesc`, `reportModel`, `aiRemark`. |
-| `--limit` / `-l` | No | Optional page size. Default: 20, maximum: 50. |
+| `--limit` / `-l` | No | Optional page size. Default: 20, maximum: 10000. |
 | `--offset` / `-o` | No | Optional page offset. Default: 0. |
 
 ## Decision Rules

package/skills/ae-analysis/references/list_tag_members.md

@@ -13,7 +13,7 @@ Domain: **Tag Management**
 ```bash
 ae-cli analysis_audience +list_tag_members --project_id <project_id> --tag_name demo
 ae-cli analysis_audience +list_tag_members --project_id <project_id> --tag_name demo --snapshot_date 2026-04-01 --property_names '["#user_id","name"]' --use_cache false
-ae-cli analysis_audience +list_tag_members --project_id <project_id> --tag_name demo --query user_001 --fields '["#user_id","name"]' --limit 20 --offset 0
+ae-cli analysis_audience +list_tag_members --project_id <project_id> --tag_name demo --query user_001 --fields '["#user_id","name"]' --limit 20 --offset 0 --request_id mcp_bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb --timeout_minutes 8
 ae-cli analysis_audience +list_tag_members --dry-run
 ```
 
@@ -29,10 +29,13 @@ ae-cli analysis_audience +list_tag_members --dry-run
 | `--fields` | No | Optional return field list (JSON array). Invalid fields will fail with `INVALID_FIELDS`. |
 | `--limit` | No | Optional page size. Default: 20, max: 50. |
 | `--offset` | No | Optional page offset. Default: 0. |
+| `--request_id` | No | Optional unique request ID used for tracking and cancellation. If provided, it must use `mcp_<32 lowercase hex UUID>`, for example `mcp_0123456789abcdef0123456789abcdef`. For long-running or cancelable queries, provide this before starting the query so it can be cancelled later with `+cancel_query --request_id <same value>`, even if the caller stops waiting before the tool returns. If `fetch failed`, HTTP timeout, or caller timeout happens, the backend query may still be running. The auto-generated requestId is not available when the HTTP request fails before a response, so preset `requestId` is required for proactive cleanup. Generated automatically if omitted. The response `metadata.requestId` can also be passed to `cancel_query` when the query is no longer needed. |
+| `--timeout_minutes` | No | Query timeout in minutes. If omitted, 30 minutes is used. |
 
 ## Decision Rules
 - For the first execution, it is recommended to pass only the required parameters (`--project_id`, `--tag_name`) and add optional parameters after confirming the path works.
 - `--property_names` must be passed as a JSON array (e.g. `--property_names '["#user_id"]'`).
+- For long-running or cancelable member queries, supply your own `--request_id` before starting so `analysis +cancel_query` can cancel by the same ID if the caller or user stops waiting. If `fetch failed`, HTTP timeout, or caller timeout happens, the backend query may still be running; call `+cancel_query --request_id <same value>` with the preset ID. The auto-generated requestId is not available when the HTTP request fails before a response. The value must use `mcp_<32 lowercase hex UUID>`, for example `mcp_0123456789abcdef0123456789abcdef`.
 - When troubleshooting across projects, first confirm whether `--project_id` matches the current permissions and target environment.
 
 ## Next Step on Failure

package/skills/ae-analysis/references/query_adhoc.md

@@ -79,7 +79,7 @@ Timezone rule:
 ## Command Syntax
 ```bash
 ae-cli analysis +query_adhoc --project_id <project_id> --model_type <model_type> --qp '<qp_json_from_builder_or_legacy_chain>'
-ae-cli analysis +query_adhoc --project_id <project_id> --model_type <model_type> --qp '<qp_json_from_builder_or_legacy_chain>' --fields '["date","event"]' --limit 10 --offset 0 --zone_offset 8 --request_id demo --use_cache true --is_sort_by_columns true --resolve_recent_day true --timeout_minutes 8
+ae-cli analysis +query_adhoc --project_id <project_id> --model_type <model_type> --qp '<qp_json_from_builder_or_legacy_chain>' --fields '["date","event"]' --limit 10 --offset 0 --zone_offset 8 --request_id mcp_aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa --use_cache true --is_sort_by_columns true --resolve_recent_day true --timeout_minutes 8
 ae-cli analysis +query_adhoc --project_id <project_id> --model_type <model_type> --qp '<qp_json_from_builder_or_legacy_chain>' --dry-run
 ```
 
@@ -89,18 +89,18 @@ ae-cli analysis +query_adhoc --project_id <project_id> --model_type <model_type>
 | `--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. For `event`/`retention`/`funnel`/`prop_analysis`, pass QP returned by the matching builder tool. For non-builder models, construct QP through the legacy schema/metadata path. |
-| `--request_id` | No | Optional unique request ID used for tracking and deduplication. Generated automatically if omitted. |
+| `--request_id` | No | Optional unique request ID used for tracking and cancellation. If provided, it must use `mcp_<32 lowercase hex UUID>`, for example `mcp_0123456789abcdef0123456789abcdef`. For long-running or cancelable queries, provide this before starting the query so it can be cancelled later with `+cancel_query --request_id <same value>`, even if the caller stops waiting before the tool returns. If `fetch failed`, HTTP timeout, or caller timeout happens, the backend query may still be running. The auto-generated requestId is not available when the HTTP request fails before a response, so preset `requestId` is required for proactive cleanup. Generated automatically if omitted. The response `metadata.requestId` can also be passed to `cancel_query` when the query is no longer needed. |
 | `--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". If omitted, service auto-resolves when `qp.eventView.recentDay` exists and `startTime`/`endTime` is incomplete; otherwise defaults to false. |
 | `--fields` | No | Optional fields to return. Must match column names in result. Invalid fields cause INVALID_FIELDS error. |
-| `--limit` | No | Optional limit. Default: 1000, maximum: 100000. |
+| `--limit` | No | Optional limit. Default: 1000, maximum: 10000. |
 | `--offset` | No | Optional offset. Default: 0. |
 | `--timeout_minutes` | No | Query timeout in minutes. If the query exceeds this time, it will be cancelled automatically. |
 
 ## Decision Rules
-- On the first run, start with only the required parameters (`--project_id`,`--model_type`,`--qp`), and add optional parameters after confirming the path works.
+- On the first run, start with only the required parameters (`--project_id`,`--model_type`,`--qp`) only when the query is clearly small. For any query that may exceed the CLI/MCP HTTP timeout, include a preset `--request_id` from the first run.
 - Do not call this command with placeholder QP such as `{}`. For builder-supported models, wait for builder `status=generated`; for non-builder models, build QP from verified schema/metadata first.
 - For builder-supported models, do not run metadata/schema lookup to "help" the builder. The builder is the metadata resolver.
 - For pagination, use `--limit` and `--offset` together. Default limit is 1000, maximum 100000.
@@ -116,7 +116,8 @@ ae-cli analysis +query_adhoc --project_id <project_id> --model_type <model_type>
 - If required parameters are missing, resolve `project_id`, `model_type`, and a real `qp` first. Do not run placeholder calls except explicit `--dry-run` validation.
 - If a builder returns non-`generated` status for `event`, `retention`, `funnel`, or `prop_analysis`, stop and ask user to clarify before calling `query_adhoc`.
 - If `Invalid JSON` appears on legacy manual QP paths, first check schema required fields, then verify whether 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.
+- If the query returns `fetch failed`, hits an HTTP timeout, or the caller stops waiting after you preset `--request_id`, immediately call `+cancel_query --request_id <same value> --yes`; the backend query may still be running.
+- If the query times out inside the service and returns `QUERY_TIMEOUT`, use the returned `metadata.requestId` for cancellation if further cleanup is needed, then narrow the time range / grouping dimensions and split subqueries to locate the issue.
 
 ## Recommended chaining
 - +build_event_analysis_qp -> +query_adhoc

package/skills/ae-analysis/references/query_bi_panel_data.md

@@ -0,0 +1,58 @@
+# analysis +query_bi_panel_data (query BI panel data)
+
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
+
+Domain: **BI panel management**
+
+## Use Cases
+- Query released BI panel chart data as one-dimensional `columns` + `rows`.
+- Query BI panel summary content as `markdown` + paged `blocks`.
+- Apply dashboard-level parameter controls, dashboard-level permission controls, and page chart filter controls using the schema returned by `+get_bi_panel_detail`.
+
+## Mandatory Prerequisite
+Call `+get_bi_panel_detail` first unless you already have verified `pageKey`, queryable `chartIds`, returned columns, and control schemas for the same `project_id`, `panel_id`, host, and released version.
+
+## Command
+```bash
+ae-cli analysis +query_bi_panel_data --project_id <project_id> --panel_id <panel_id> --page_key <page_key> --result_type charts
+ae-cli analysis +query_bi_panel_data --project_id <project_id> --panel_id <panel_id> --page_key <page_key> --result_type charts --chart_ids '["chart_city"]' --columns '["city","height"]' --row_limit 50 --row_offset 0
+ae-cli analysis +query_bi_panel_data --project_id <project_id> --panel_id <panel_id> --page_key summary --result_type summary --block_limit 20 --block_offset 0
+ae-cli analysis +query_bi_panel_data --project_id <project_id> --panel_id <panel_id> --page_key <page_key> --result_type charts --request_id mcp_1234567890abcdef1234567890abcdef --chart_filter_controls '[{"controlId":"chart_filter_city","value":["上海市","北京市"]}]'
+ae-cli analysis +query_bi_panel_data --project_id <project_id> --panel_id <panel_id> --page_key <page_key> --result_type charts --dry-run
+```
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project_id` / `-p` | Yes | Project ID |
+| `--panel_id` | Yes | BI panel ID returned by `+list_bi_panels` |
+| `--page_key` | Yes | Page key returned by `+get_bi_panel_detail` |
+| `--result_type` | Yes | `charts` or `summary` |
+| `--request_id` | No | Optional unique request ID used for tracking and cancellation. If provided, it must use `mcp_<32 lowercase hex UUID>`, for example `mcp_0123456789abcdef0123456789abcdef`. For long-running or cancelable queries, provide this before starting the query so it can be cancelled later with `+cancel_query --request_id <same value>`, even if the caller stops waiting before the tool returns. If `fetch failed`, HTTP timeout, or caller timeout happens, the backend query may still be running. The auto-generated requestId is not available when the HTTP request fails before a response, so preset `requestId` is required for proactive cleanup. Generated automatically if omitted. The response `metadata.requestId` can also be passed to `cancel_query` when the query is no longer needed. |
+| `--chart_ids` | No | JSON array of chart IDs when `result_type=charts`. If omitted, all queryable charts on the page are queried. |
+| `--parameter_controls` | No | JSON array of dashboard-level parameter control overrides. Each item has `controlId` and one scalar `value`. |
+| `--permission_controls` | No | JSON array of dashboard-level permission control values. Each item has `controlId` and `value`; `value` may be one scalar or an array. |
+| `--chart_filter_controls` | No | JSON array of page chart filter control values. Each item has `controlId` and `value`; `value` may be one scalar or an array and applies only to bound charts. |
+| `--columns` | No | Optional returned columns for chart data. Must match columns returned by `+get_bi_panel_detail`. |
+| `--row_limit` | No | Chart row limit. Default: 50, maximum: 10000. |
+| `--row_offset` | No | Chart row offset. Default: 0. |
+| `--block_limit` | No | Summary block limit. Default: 20, maximum: 10000. |
+| `--block_offset` | No | Summary block offset. Default: 0. |
+| `--use_cache` | No | Whether to use cache. Default: true. |
+| `--timeout_minutes` | No | Query timeout in minutes. Default: 3, minimum: 1, maximum: 10. |
+
+## Control Rules
+- `parameter_controls` accept one scalar value only. Arrays are invalid.
+- `permission_controls` accept one scalar value or an array. `allowedValues` from detail are hints only; real data permission is enforced by the BI query path.
+- `chart_filter_controls` accept one scalar value or an array regardless of UI single/multi-select setting. They apply only to `boundChartIds`.
+- PageCharts filter components that have no passed value and no default do not add a filter.
+- Do not pass internal fields such as `paramList`, `permissionFilters`, `visualCfg`, `whereList`, `whereValues`, `field`, `columnName`, `userId`, or `openId`.
+
+## Decision Rules
+- For charts, omit `--chart_ids` on the first run to query all queryable charts on the page.
+- Explicitly querying a non-queryable filter component returns a chart-level unsupported result.
+- Use `--columns`, `--row_limit`, and `--row_offset` to reduce response size.
+- For long-running or cancelable queries, supply your own `--request_id` before starting so `+cancel_query` can cancel by the same ID if the caller or user stops waiting. If `fetch failed`, HTTP timeout, or caller timeout happens, the backend query may still be running; call `+cancel_query --request_id <same value>` with the preset ID. The auto-generated requestId is not available when the HTTP request fails before a response. The value must use `mcp_<32 lowercase hex UUID>`, for example `mcp_0123456789abcdef0123456789abcdef`.
+
+## Recommended Chaining
+- `+list_bi_panels` -> `+get_bi_panel_detail` -> `+query_bi_panel_data`