@thinkingai/ae-cli 6.0.30 → 6.0.32

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

@@ -1,52 +0,0 @@
-# analysis_meta +list_metrics (Metric Search)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Metadata Query**
-
-## Constraints
-
-**Fuzzy Search Fallback:** If `--query` returns no results, retry with broader keywords (max 3 attempts), then fall back to full list. See [SKILL.md § C. FUZZY_SEARCH_FALLBACK](../SKILL.md#c-fuzzy_search_fallback).
-
-**Not a builder pre-step:** Do not call `+list_metrics` before non-SQL ad-hoc analysis. The matching builder resolves referenced metrics internally; the event builder accepts a saved metric name in `metrics[].event`. If the builder fails, stop and ask for clarification instead of using this command as a fallback.
-
-## Use Cases
-- List metric metadata in the project. Supports keyword filtering and returns metric IDs, names, display names, model types, remarks, and related metadata, but not metric calculation results.
-- Supports pagination with fields/limit/offset for payload governance.
-- Query performs fuzzy matching on metricName, metricDesc, and metricRemark.
-- Use this command for metric metadata management, metric editing, auditing, or when the user explicitly asks to inspect/search metric metadata. Do not use it merely to prepare a builder-supported ad-hoc query.
-
-## Command
-```bash
-ae-cli analysis_meta +list_metrics --project_id <project_id>
-ae-cli analysis_meta +list_metrics --project_id <project_id> --query demo
-ae-cli analysis_meta +list_metrics --project_id <project_id> --query demo --fields '["metricId","metricName","metricDesc","metricRemark","metricMode"]' --limit 10 --offset 0
-ae-cli analysis_meta +list_metrics --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--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, authenticationStatus, openId, creator, creatorLoginName, updateOpenId, updateCreator, updateLoginName, createTime, updateTime. Default fields when omitted: metricId, metricName, metricDesc, metricRemark, metricMode, authenticationStatus. Invalid fields cause INVALID_FIELDS error. |
-| `--limit` | No | Optional limit. Default: 20, maximum: 50. |
-| `--offset` | No | Optional offset. Default: 0. |
-| `--authenticated_only` | No | When true, return only authenticated metrics. |
-
-## Decision Rules
-- Use `--authenticated_only true` only when the user explicitly asks for authenticated assets. `authenticationStatus` is `1` for authenticated and `0` for unauthenticated.
-- First run should only pass the required parameter (`--project_id`), and add optional parameters only after the path is confirmed to work.
-- For pagination, use `--limit` and `--offset` together. Default limit is 20.
-- Use `--fields` to select specific columns for lighter response payloads.
-- For builder-supported ad-hoc analysis, do not search metrics here first. Pass the user-provided metric name directly to the builder.
-- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
-
-## Next Steps After Failure
-- If the required parameter is missing, fall back to the smallest runnable command and fill it in (focus on `--project_id`).
-- If the result is empty, first confirm the project ID/keyword, then try loosening the filter conditions.
-- If INVALID_FIELDS error appears, check that all field names in `--fields` match the supported list.
-
-## Recommended Chaining
-- +list_metrics -> +create_metric -> +get_metric
-- For ad-hoc event metric query: +build_event_analysis_qp -> +query_adhoc

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

@@ -1,47 +0,0 @@
-# analysis_meta +list_properties (Property Metadata Discovery)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Metadata Query**
-
-## Constraints
-
-**Not a builder pre-step:** Do not call `+list_properties` before non-SQL ad-hoc analysis. The matching QP builder resolves property names internally. If the builder returns MCP failure, stop and ask for clarification instead of using this command as a fallback.
-
-## Use Cases
-- Read-only query for SYSTEM METADATA properties already effective in the project. Supports event/user scope. Do NOT use for tracking-plan metadata (bury/track program); that belongs to BuryProgramTool.
-- Read-only query for SYSTEM METADATA properties already effective in the project. Use when the user explicitly asks to inspect property metadata, not as a required preparation step for QP builder.
-
-## Commands
-```bash
-ae-cli analysis_meta +list_properties --project_id <project_id>
-ae-cli analysis_meta +list_properties --project_id <project_id> --scope event --event_name purchase --query demo
-ae-cli analysis_meta +list_properties --project_id <project_id> --query demo --fields '["propId", "propName", "propDesc", "remark", "selectType", "tableType"]' --limit 20 --offset 0
-ae-cli analysis_meta +list_properties --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--scope` | No | Optional property scope. event means event properties, user means user properties. If omitted, all scopes are queried. |
-| `--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 remark; if omitted, all matched properties are returned. |
-| `--fields` / `-f` | No | Optional fields to return (JSON array). Supported fields: `propId`, `propName`, `propDesc`, `remark`, `selectType`, `tableType`, `subTableType`, `authenticationStatus`. Default fields when omitted: `propId`, `propName`, `propDesc`, `remark`, `selectType`, `tableType`, `authenticationStatus`. |
-| `--limit` / `-l` | No | Optional page size. Default: 20, maximum: 50. |
-| `--offset` / `-o` | No | Optional page offset. Default: 0. |
-| `--authenticated_only` | No | When true, return only authenticated properties. |
-
-
-## Decision Rules
-- Use `--authenticated_only true` only when the user explicitly asks for authenticated assets. `authenticationStatus` is `1` for authenticated and `0` for unauthenticated.
-- For the first run, pass only the required parameter (`--project_id`) to confirm the path works, then add optional parameters.
-- For builder-supported ad-hoc analysis, pass the user's property wording to the builder instead of pre-querying property metadata.
-- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
-
-## Next Steps After 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_properties -> +create_virtual_property

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

@@ -1,41 +0,0 @@
-# analysis +list_public_access_links (public link search)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../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.
-- Supports pagination with fields/limit/offset for payload governance.
-- Query performs fuzzy matching on shorter and remarks.
-
-## Commands
-```bash
-ae-cli analysis +list_public_access_links --project_id <project_id>
-ae-cli analysis +list_public_access_links --project_id <project_id> --query demo
-ae-cli analysis +list_public_access_links --project_id <project_id> --query demo --fields '["id","shorter","accessStatus"]' --limit 10 --offset 0
-ae-cli analysis +list_public_access_links --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--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: 10000. |
-| `--offset` | No | Optional offset. Default: 0. |
-
-## 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 pagination, use `--limit` and `--offset` together. Default limit is 20.
-- Use `--fields` to select specific columns for lighter response payloads.
-- 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.
-- If INVALID_FIELDS error appears, check that all field names in `--fields` match the supported list.
-
-## Recommended Chaining
-- +list_public_access_links -> +update_public_access_link

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

@@ -1,43 +0,0 @@
-# analysis +list_reports (List Reports)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Report management**
-
-## Constraints
-
-**Fuzzy Search Fallback:** If `--query` returns no results, retry with broader keywords (max 3 attempts), then fall back to full list. See [SKILL.md § C. FUZZY_SEARCH_FALLBACK](../SKILL.md#c-fuzzy_search_fallback).
-
-**Builder failure is terminal:** For builder-supported ad-hoc analysis, this command may be used only in the initial `QUERY_EXISTING_FIRST` report search. Do not call `+list_reports` or `+get_report_definition` as a fallback after a QP builder returns non-generated status.
-
-## 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 analysis +list_reports --project_id <project_id>
-ae-cli analysis +list_reports --project_id <project_id> --query demo
-ae-cli analysis +list_reports --project_id <project_id> --fields '["reportId","reportName","reportDesc","remark","reportModel"]' --limit 20 --offset 0
-ae-cli 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 reportName, reportDesc, and remark; if omitted, all accessible reports are returned. |
-| `--fields` / `-f` | No | Optional fields to return (JSON array). Supported fields: `reportId`, `reportName`, `reportDesc`, `remark`, `reportModel`. Default fields when omitted: `reportId`, `reportName`, `reportDesc`, `remark`, `reportModel`. |
-| `--limit` / `-l` | No | Optional page size. Default: 20, maximum: 10000. |
-| `--offset` / `-o` | No | Optional page offset. Default: 0. |
-
-## 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/ae-analysis/references/list_spaces.md

@@ -1,27 +0,0 @@
-# analysis +list_spaces (List Spaces)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Dashboard Management**
-
-## Use Cases
-- List all spaces and folders accessible to the current user as a recursive tree.
-- Returns two parts: (1) project spaces with spaceId, name, spaceDesc, and children (folders/dashboards); (2) personal-space folders (My Space / Shared with me / Ungrouped) with their children.
-- Use to resolve `spaceId` for `+create_dashboard` / `+copy_dashboard`, and `toSpaceId` / `toFolderId` / `fromSpaceId` / `fromFolderId` for `+move_dashboard` and `+copy_dashboard`.
-
-## Commands
-```bash
-ae-cli analysis_audience +list_spaces --project_id <project_id>
-ae-cli analysis_audience +list_spaces --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-
-## Decision Rules
-- Call this before `+copy_dashboard` or `+move_dashboard` whenever the user specifies a target space or folder by name.
-
-## Recommended Chain
-- `+list_spaces` -> `+copy_dashboard` / `+move_dashboard` / `+create_dashboard`

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

@@ -1,46 +0,0 @@
-# analysis_audience +list_tag_members (View Tag Members)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Tag Management**
-
-## Use Cases
-- List members in the specified tag.
-- Supports payload governance parameters: `query`, `fields`, `limit`, `offset`.
-- Returns a paginated envelope (items + total + limit + offset + hasMore) for the selected snapshot date.
-
-## Commands
-```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 --request_id mcp_bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb --timeout_minutes 8
-ae-cli analysis_audience +list_tag_members --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--tag_name` | Yes | Tag name |
-| `--snapshot_date` | No | Optional tag snapshot date. Format: YYYY-MM-DD |
-| `--property_names` | No | Optional list of user property names (JSON array) |
-| `--use_cache` | No | Whether to use cache. Default: true |
-| `--query` | No | Optional keyword filter on `#user_id` and selected properties. |
-| `--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` | Yes | Required unique request ID used for tracking and cancellation. Generate it before starting the query. It must use `mcp_<32 lowercase hex UUID>`, for example `mcp_0123456789abcdef0123456789abcdef`. 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. `requestId` is not auto-generated for MCP query tools because the caller must know it before the response for proactive cleanup. If omitted or blank, the backend returns `REQUEST_ID_REQUIRED`; invalid format returns `INVALID_REQUEST_ID`. The response `metadata.requestId` echoes the supplied requestId and can also be passed to `cancel_query(requestId)` 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, include all required parameters (`--project_id`, `--tag_name`, `--request_id`) and add optional parameters after confirming the path works.
-- `--property_names` must be passed as a JSON array (e.g. `--property_names '["#user_id"]'`).
-- Generate and pass `--request_id` before starting any cancelable query; it is required. 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 value must use `mcp_<32 lowercase hex UUID>`, for example `mcp_0123456789abcdef0123456789abcdef`. Omitted or blank IDs return `REQUEST_ID_REQUIRED`; invalid format returns `INVALID_REQUEST_ID`.
-- When troubleshooting across projects, first confirm whether `--project_id` matches the current permissions and target environment.
-
-## Next Step on Failure
-- If required parameters are missing, fall back to the smallest runnable command and fill the gap (focus on `--project_id`, `--tag_name`, `--request_id`).
-- If the result is empty, first confirm the project ID/keyword, then try broadening the filter conditions.
-
-## Recommended Chain
-- +list_tags -> +get_tags_by_name -> +update_tag

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

@@ -1,44 +0,0 @@
-# analysis_audience +list_tags (Tag Search)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Tag Management**
-
-## Constraints
-
-**Fuzzy Search Fallback:** If `--query` returns no results, retry with broader keywords (max 3 attempts), then fall back to full list. See [SKILL.md § C. FUZZY_SEARCH_FALLBACK](../SKILL.md#c-fuzzy_search_fallback).
-
-## Use Cases
-- List tag metadata accessible to the current user in the project.
-- Supports payload governance parameters: `query`, `fields`, `limit`, `offset`.
-- Returns a paginated envelope (items + total + limit + offset + hasMore), not tag members.
-
-## Commands
-```bash
-ae-cli analysis_audience +list_tags --project_id <project_id>
-ae-cli analysis_audience +list_tags --project_id <project_id> --query demo
-ae-cli analysis_audience +list_tags --project_id <project_id> --fields '["id","clusterName","displayName","remarks","clusterType","subConditionTabType","progress","usersNum"]' --limit 20 --offset 0
-ae-cli analysis_audience +list_tags --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--query` / `-q` | No | Optional keyword filter. Performs fuzzy matching against tag names, display names, and remarks; if omitted, all tags are returned. |
-| `--fields` | No | Optional return field list (JSON array). Supported fields: `id`, `clusterName`, `displayName`, `clusterType`, `subConditionTabType`, `progress`, `usersNum`, `remarks`, `authenticationStatus`. Default fields when omitted: `id`, `clusterName`, `displayName`, `remarks`, `clusterType`, `subConditionTabType`, `progress`, `usersNum`, `authenticationStatus`. Invalid fields will fail with `INVALID_FIELDS`. |
-| `--limit` | No | Optional page size. Default: 20, max: 50. |
-| `--offset` | No | Optional page offset. Default: 0. |
-| `--authenticated_only` | No | When true, return only authenticated tags. |
-
-## Decision Rules
-- Use `--authenticated_only true` only when the user explicitly asks for authenticated assets. `authenticationStatus` is `1` for authenticated and `0` for unauthenticated.
-- For the first execution, it is recommended to pass only the required parameters (`--project_id`) and add optional parameters after confirming the path works.
-- When troubleshooting across projects, first confirm whether `--project_id` matches the current permissions and target environment.
-
-## Next Step on Failure
-- If required parameters are missing, fall back to the smallest runnable command and fill the gap (focus on `--project_id`).
-- If the result is empty, first confirm the project ID/keyword, then try broadening the filter conditions.
-
-## Recommended Chain
-- +list_tags -> +get_tags_by_name -> +update_tag

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

@@ -1,33 +0,0 @@
-# analysis +move_dashboard (Move Dashboard)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Dashboard Management**
-
-## Use Cases
-- Move a dashboard to a different space or folder.
-- Provide `--to_space_id` to move to a space root, or both `--to_space_id` and `--to_folder_id` to move into a folder within that space.
-- `--from_space_id` and `--from_folder_id` are optional; provide them when the dashboard exists in multiple spaces to disambiguate the source path.
-
-## Commands
-```bash
-ae-cli analysis_audience +move_dashboard --project_id <project_id> --dashboard_id <dashboard_id> --to_space_id <space_id>
-ae-cli analysis_audience +move_dashboard --project_id <project_id> --dashboard_id <dashboard_id> --to_space_id <space_id> --to_folder_id <folder_id>
-ae-cli analysis_audience +move_dashboard --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--dashboard_id` | Yes | Dashboard ID to move |
-| `--to_space_id` | Yes | Target space ID |
-| `--to_folder_id` | No | Target folder ID within the target space. Omit to place at the space root. |
-| `--from_space_id` | No | Source space ID. Omit if unknown. |
-| `--from_folder_id` | No | Source folder ID. Omit if unknown. |
-
-## Decision Rules
-- Call `+list_spaces` first to resolve `to_space_id` and `to_folder_id`.
-
-## Recommended Chain
-- `+list_spaces` -> `+move_dashboard`

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

@@ -1,141 +0,0 @@
-# analysis +query_adhoc (Ad Hoc Analysis Execution)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Model analysis**
-
-## Constraints
-
-**⚠️ QUERY_EXISTING_FIRST:** Before using ad-hoc query, you MUST first check for existing reports with `+list_reports` and dashboards with `analysis dashboard list`. Only use `query_adhoc` if no matching asset is used. See [SKILL.md § D. QUERY_EXISTING_FIRST](../SKILL.md#d-query_existing_first).
-
-**⚠️ QP_BUILDER_SUPPORTED_MODELS_ONLY:** QP builder supports all ten non-SQL ad-hoc model types: `event`, `retention`, `funnel`, `prop_analysis`, `attribution`, `distribution`, `heat_map`, `interval`, `path`, and `rank_list`.
-
-For these ten model types, call the matching builder before `query_adhoc`. Do not handcraft QP from `get_analysis_query_schema`, examples, or prior knowledge.
-
-Only `sql` has no builder. Use the schema/verified SQL-definition path for SQL.
-
-For builder-supported models, schema/metadata tools are not builder pre-steps. After report/dashboard lookup misses, do not call `get_analysis_query_schema`, `list_events`, `list_properties`, `list_metrics`, `get_metric`, or `get_report_definition` before the builder. The builder resolves event/property/metric metadata internally.
-
-**Hard stop rule:** If builder status is not `generated`, stop and ask the user to clarify or report the builder error. Do not call `query_adhoc`, `get_analysis_query_schema`, or manually assemble QP for any of the ten builder-supported models.
-
-Builder mapping:
-1. `event` -> `+build_event_analysis_qp`
-2. `retention` -> `+build_retention_analysis_qp`
-3. `funnel` -> `+build_funnel_analysis_qp`
-4. `prop_analysis` -> `+build_prop_analysis_qp`
-5. `attribution` -> `+build_attribution_analysis_qp`
-6. `distribution` -> `+build_distribution_analysis_qp`
-7. `heat_map` -> `+build_heat_map_analysis_qp`
-8. `interval` -> `+build_interval_analysis_qp`
-9. `path` -> `+build_path_analysis_qp`
-10. `rank_list` -> `+build_rank_list_analysis_qp`
-
-**Quick check workflow:**
-1. `list_reports --query <keyword>` - search matching reports
-2. `ae-cli analysis dashboard list --project-id <project_id> --query <keyword>` - search matching dashboards
-3. If found → use `+query_report_data` or `analysis dashboard-report-data run/export`
-4. If not found and model is non-SQL → read the matching builder reference, call the builder, then call `query_adhoc` with `model_type` + built `qp`; do not insert schema or metadata lookup before the builder
-5. If not found and model is `sql` → use the schema/verified SQL-definition path, then call `query_adhoc`
-
-## Use Cases
-- Execute a QP produced by the required chain for the target model.
-- Builder-supported models (all ten non-SQL models): execute the `qp` returned by builder tools.
-- SQL: execute QP from the schema/verified SQL-definition path.
-- 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:
-  - Builder-supported models: builder -> `query_adhoc`
-  - SQL: schema/verified definition -> `query_adhoc`
-
-## Builder-Supported Model Chain
-Use this chain for all ten non-SQL models.
-
-1. Read the matching builder reference:
-   - `event`: [`build_event_analysis_qp.md`](./build_event_analysis_qp.md)
-   - `retention`: [`build_retention_analysis_qp.md`](./build_retention_analysis_qp.md)
-   - `funnel`: [`build_funnel_analysis_qp.md`](./build_funnel_analysis_qp.md)
-   - `prop_analysis`: [`build_prop_analysis_qp.md`](./build_prop_analysis_qp.md)
-   - `attribution`: [`build_attribution_analysis_qp.md`](./build_attribution_analysis_qp.md)
-   - `distribution`: [`build_distribution_analysis_qp.md`](./build_distribution_analysis_qp.md)
-   - `heat_map`: [`build_heat_map_analysis_qp.md`](./build_heat_map_analysis_qp.md)
-   - `interval`: [`build_interval_analysis_qp.md`](./build_interval_analysis_qp.md)
-   - `path`: [`build_path_analysis_qp.md`](./build_path_analysis_qp.md)
-   - `rank_list`: [`build_rank_list_analysis_qp.md`](./build_rank_list_analysis_qp.md)
-2. Compose the builder JSON using the documented DTO keys. Nested JSON keys are camelCase, not snake_case.
-3. Run the builder with all required flags. `--dry-run` is allowed only with complete required builder inputs, not by itself.
-4. If builder returns `status=generated`, copy `data.qp` from the builder response and pass it as `--qp`.
-5. If the builder returns `need_clarification`, `invalid_argument`, `unsupported_feature`, or `validation_error`, stop and ask for clarification. Do not use the manual path as a fallback.
-
-## Legacy Query Chain
-Use this chain only for `sql`.
-
-1. Read this reference and the required schema/metadata references.
-2. Call `+get_analysis_query_schema` for the target model when the QP shape is not already verified.
-3. Discover real events/properties/metrics with analysis metadata commands as needed.
-4. Construct QP according to the documented schema and verified metadata.
-5. Call `+query_adhoc`.
-
-Timezone rule:
-- Builder commands do not accept `zone_offset`.
-- Apply timezone only on this execution command, for example `--zone_offset -11`.
-
-## 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 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
-```
-
-## 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. For every non-SQL model, pass QP returned by the matching builder tool. For SQL, use the schema/verified-definition path. |
-| `--request_id` | Yes | Required unique request ID used for tracking and cancellation. Generate it before starting the query. It must use `mcp_<32 lowercase hex UUID>`, for example `mcp_0123456789abcdef0123456789abcdef`. 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. `requestId` is not auto-generated for MCP query tools because the caller must know it before the response for proactive cleanup. If omitted or blank, the backend returns `REQUEST_ID_REQUIRED`; invalid format returns `INVALID_REQUEST_ID`. The response `metadata.requestId` echoes the supplied requestId and can also be passed to `cancel_query(requestId)` 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: 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, include all required parameters (`--project_id`,`--model_type`,`--qp`,`--request_id`). Generate `--request_id` before starting the query so cancellation can use the same value if the caller stops waiting.
-- Do not call this command with placeholder QP such as `{}`. For non-SQL models, wait for builder `status=generated`; for SQL, build QP from a verified schema/definition 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.
-- For `model_type=sql`, use exactly one row limit: either put `LIMIT` in the SQL, or use `--limit`. If both are present they must be equal — `query_adhoc` rejects mismatched values to avoid silently sampled or duplicated results. When the SQL already has a trailing `LIMIT`, you may omit `--limit` and the SQL governs.
-- Use `--fields` to select specific columns for lighter response payloads.
-- Non-SQL models must not manually craft QP with schema-first flow; call the matching builder and use its returned `qp`.
-- For SQL, `qp` must satisfy both schema structure and project metadata constraints.
-- Wrap JSON parameters in single quotes (for example `--qp '<real_qp_json>'`) to avoid shell escaping issues.
-- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
-- If the user supplied a timezone such as UTC-11, pass `--zone_offset -11` here, not to the builder.
-
-## Next Steps on Failure
-- 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, stop and ask the 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 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
-- +build_retention_analysis_qp -> +query_adhoc
-- +build_funnel_analysis_qp -> +query_adhoc
-- +build_prop_analysis_qp -> +query_adhoc
-- +build_attribution_analysis_qp / +build_distribution_analysis_qp / +build_heat_map_analysis_qp / +build_interval_analysis_qp / +build_path_analysis_qp / +build_rank_list_analysis_qp -> +query_adhoc
-- +get_analysis_query_schema -> +query_adhoc (SQL only)
-- +list_events -> +list_properties -> +query_adhoc -> +drilldown_users -> +drilldown_user_events

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

@@ -1,58 +0,0 @@
-# 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` | Yes | Required unique request ID used for tracking and cancellation. Generate it before starting the query. It must use `mcp_<32 lowercase hex UUID>`, for example `mcp_0123456789abcdef0123456789abcdef`. 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. `requestId` is not auto-generated for MCP query tools because the caller must know it before the response for proactive cleanup. If omitted or blank, the backend returns `REQUEST_ID_REQUIRED`; invalid format returns `INVALID_REQUEST_ID`. The response `metadata.requestId` echoes the supplied requestId and can also be passed to `cancel_query(requestId)` 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.
-- Generate and pass `--request_id` before starting any cancelable query; it is required. 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 value must use `mcp_<32 lowercase hex UUID>`, for example `mcp_0123456789abcdef0123456789abcdef`. Omitted or blank IDs return `REQUEST_ID_REQUIRED`; invalid format returns `INVALID_REQUEST_ID`.
-
-## Recommended Chaining
-- `+list_bi_panels` -> `+get_bi_panel_detail` -> `+query_bi_panel_data`

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

@@ -1,35 +0,0 @@
-# analysis +query_dashboard_detail (read dashboard structure)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../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
-ae-cli analysis +query_dashboard_detail --project_id <project_id> --dashboard_id 1
-ae-cli 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