@thinkingai/ae-cli 6.0.30 → 6.0.32

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

@@ -1,69 +0,0 @@
-# analysis_audience +get_clusters_by_name (Locate Clusters by Name)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Cluster Management**
-
-## Use Cases
-- Get cluster definition details in batch by cluster name. Returns complete cluster information for matched clusters, including IDs, names, display names, types, status, user counts, and refresh status.
-
-## Commands
-```bash
-ae-cli analysis_audience +get_clusters_by_name --project_id <project_id> --names '["demo"]'
-ae-cli analysis_audience +get_clusters_by_name --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--names` | Yes | List of cluster names (JSON array). Exact-name matching is used; unmatched clusters are ignored automatically. |
-
-## Decision Rules
-- For the first execution, it is recommended to pass only the required parameters (`--project_id`, `--names`) and add optional parameters after confirming the path works.
-- `--names` must be passed as a JSON array (e.g. `--names '["cluster_a","cluster_b"]'`).
-- When troubleshooting across projects, first confirm whether `--project_id` matches the current permissions and target environment.
-
-## Enum Codebook (Asset Definition Interpretation Only)
-
-When interpreting cluster `definition` for users, if operator enum codes appear, use the following complete `calcuSymbol` mapping instead of outputting raw codes only.
-
-| Code | Meaning | Applicable Types |
-|---|---|---|
-| `C00` | equals | all |
-| `C000` | equals empty string | string |
-| `C01` | not equals | all |
-| `C010` | not equals empty string | string |
-| `C02` | less than | number |
-| `C020` | less than or equal | number |
-| `C03` | greater than | number |
-| `C030` | greater than or equal | number |
-| `C04` | has value | all |
-| `C05` | no value | all |
-| `C06` | range | number/date |
-| `C060` | date range | date |
-| `C07` | contains | string |
-| `C08` | does not contain | string |
-| `C09` | true | bool |
-| `C10` | false | bool |
-| `C11` | regex match | string |
-| `C12` | regex does not match | string |
-| `C13` | relative to current time | date/datetime |
-| `C14` | relative to event time | date/datetime |
-| `C15` | element exists | array |
-| `C16` | element does not exist | array |
-| `C17` | element position | array |
-| `C18` | no value | array |
-| `C19` | has value | array |
-| `C20` | belongs to cluster | cluster/tag (`tableType="2"`) |
-| `C21` | does not belong to cluster | cluster/tag (`tableType="2"`) |
-| `C22` | object exists that satisfies condition | array |
-| `C23` | no object satisfies condition | array |
-| `C24` | all objects satisfy condition | array |
-
-## Next Step on Failure
-- If required parameters are missing, fall back to the smallest runnable command and fill the gap (focus on `--project_id`, `--names`).
-- If reading fails, first verify whether the object ID exists and belongs to the current project.
-
-## Recommended Chain
-- +list_clusters -> +get_clusters_by_name -> +update_cluster

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

@@ -1,33 +0,0 @@
-# analysis +get_filter_schema (get filter schema)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../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
-ae-cli analysis +get_filter_schema
-ae-cli 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/ae-analysis/references/get_groupby_schema.md

@@ -1,33 +0,0 @@
-# analysis +get_groupby_schema (Get Group-By Schema)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../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
-ae-cli analysis +get_groupby_schema
-ae-cli 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/ae-analysis/references/get_metric.md

@@ -1,38 +0,0 @@
-# analysis_meta +get_metric (View Metric Details)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Metadata Query**
-
-## Constraints
-
-**Not a builder pre-step:** Do not call `+get_metric` before `+build_event_analysis_qp` for normal ad-hoc analysis. If the user asks to query a saved metric, pass the metric display/name/remark directly as `metrics:[{"event":"<metric name>"}]` to `+build_event_analysis_qp`. The builder resolves saved metrics internally. If it cannot resolve the metric, stop on the builder's structured error and ask for clarification.
-
-## Use Cases
-- Get the definition details of a single metric. Returns the metric name, display name, remark, model type, linked events, and parameter definition without executing metric calculation.
-- Use this command for metric metadata inspection, metric editing, auditing, or when the user explicitly asks for metric definition details. Do not use it merely to expand a saved metric before a builder-supported ad-hoc query.
-
-## Commands
-```bash
-ae-cli analysis_meta +get_metric --project_id <project_id> --metric_id 1
-ae-cli analysis_meta +get_metric --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--metric_id` / `-m` | Yes | Metric ID |
-
-## Decision Rules
-- For the first run, pass only the required parameters (`--project_id` and `--metric_id`) to confirm the path works, then add optional parameters.
-- For builder-supported ad-hoc analysis, do not read metric details first. Call the matching builder with the user's metric/event/property wording.
-- 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` and `--metric_id`).
-- If reading fails, first verify that the object ID exists and belongs to the current project.
-
-## Recommended Chaining
-- +get_metric -> +update_metric
-- For ad-hoc saved metric query: +build_event_analysis_qp -> +query_adhoc

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

@@ -1,37 +0,0 @@
-# analysis +get_report_definition (read report definition)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Report Management**
-
-## Constraints
-
-**Not a builder fallback:** Do not call `+get_report_definition` to repair or replace a failed non-SQL QP builder call. Builder failure means stop and ask for clarification or report the structured error.
-
-## 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
-ae-cli analysis +get_report_definition --project_id <project_id> --report_id 1
-ae-cli 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/ae-analysis/references/get_resource_url.md

@@ -1,32 +0,0 @@
-# Resource link completion (call analysis_common +get_resource_url)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **cross-module post-write constraint**
-
-## Use Cases
-- After a `create_*` or `update_*` write operation succeeds in this unified skill, complete the clickable asset link.
-- Supported resource types (resourceType): `dashboard`, `report`, `metric`, `alert`, `tag`, `cluster`, `data_table`, `super_event`, `super_prop_user`, `super_prop_event`, `virtual_event`, `user_virtual_prop`, `event_virtual_prop`.
-- Key return fields: `markdown_link`, `raw_url`.
-
-## Mandatory Rules (MUST)
-- As long as `project_id + resource_type + resource_id` can be determined, this command must be called.
-- The final response must output `markdown_link` directly (do not place it in a code block) so the user can click through.
-- If resource link generation fails, keep the main write-operation success conclusion and add the failure reason.
-
-## Command
-```bash
-ae-cli analysis_common +get_resource_url --project_id <project_id> --resource_type dashboard --resource_id 1
-ae-cli analysis_common +get_resource_url --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--resource_type` | Yes | Resource type: dashboard/report/metric/alert/tag/cluster/data_table/super_event/super_prop_user/super_prop_event/virtual_event/user_virtual_prop/event_virtual_prop |
-| `--resource_id` | Yes | Numeric resource ID |
-
-## Recommended Chaining
-- `+create_*` -> `analysis_common +get_resource_url`
-- `+update_*` -> `analysis_common +get_resource_url`

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

@@ -1,37 +0,0 @@
-# analysis +get_table_columns (Read Underlying Table Columns)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Model analysis**
-
-## Use Cases
-- Query the field list of a project table. Returns all column names and types for `tableRef` so the table schema can be understood before SQL analysis.
-- Table guide:
-- `hive.ta_dim.datatable_1`: catalog is hive, schema is ta_dim, table is datatable_1.
-- `ta_dim.datatable_1`: catalog defaults to hive, schema is ta_dim, table is datatable_1.
-- `ta_event_1`: table only; resolved against project available tables and fails if ambiguous.
-- The only common catalog is `hive`. Common hive schemas are `ta` (default analysis tables), `ta_dim` (dimension/datatable/exchange tables), `temp` (SQL temporary tables), and `ta_ext` (external datatable/API tables). Do not replace an explicit schema such as `ta_dim` with default `ta`.
-
-## Command
-```bash
-ae-cli analysis +get_table_columns --project_id <project_id> --table_ref hive.ta_dim.datatable_1
-ae-cli analysis +get_table_columns --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--table_ref` | Yes | Table reference. Supports `hive.schema.table`, `schema.table`, or `table`. If only `table` is provided, the backend resolves it against project available tables and fails on ambiguity. |
-
-## Decision Rules
-- Prefer a fully qualified `--table_ref` when the schema is known, especially for `ta_dim`, `temp`, or `ta_ext` tables.
-- Use table-only `--table_ref <table>` only when you expect the table name to be unique in the project; if the backend returns ambiguity, retry with one of the returned fully qualified `tableRef` values.
-- 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, fill in `--project_id` and `--table_ref` first.
-- If reading fails, first verify whether the `tableRef` exists, is unambiguous, and belongs to the current project permissions.
-
-## Recommended chaining
-- +get_table_columns

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

@@ -1,49 +0,0 @@
-# analysis_audience +get_tag_definition_schema (Get Tag Definition Schema)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Schema Query**
-
-## Use Cases
-- Support tool positioning: the current command provides the structure definition (schema) and should be used as a prerequisite step.
-- Recommended sequence: first call this schema tool to get the structure, then call specific business tools.
-- Typical downstream tools: `+create_tag`, `+update_tag`
-- Get the tag definition schema. Supports tag type + response mode + condition subtype.
-
-## Commands
-```bash
-ae-cli analysis_audience +get_tag_definition_schema --type condition
-ae-cli analysis_audience +get_tag_definition_schema --type metric
-ae-cli analysis_audience +get_tag_definition_schema --type condition --response_mode examples --condition_subtype behavior_seq
-ae-cli analysis_audience +get_tag_definition_schema --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--type` | Yes | Tag type. Supported values: `condition`, `metric`, `first_last`, `sql`. |
-| `--response_mode` | No | Schema response mode. Supported values: `base`, `examples`, `full`. Default: `base`. |
-| `--condition_subtype` | No | Only effective when `--type condition`. Supported values: `core`, `behavior_seq`, `all`. Default: `core`. |
-
-## Progressive Loading Strategy
-- Use the smallest response that can solve the current task. Large schemas consume context and can make the follow-up definition construction less reliable.
-- Start with `--response_mode base` or omit `--response_mode` for simple `condition`, `metric`, and `sql` tags.
-- Request `--response_mode examples` only when the base schema is not enough to build or validate the target `definition`.
-- `first_last` tags have a more specialized structure; use base first when the requested shape is simple, and escalate to `examples` when the field mapping or event/property role is unclear.
-- Request `--response_mode full` only for complex, ambiguous, or repeatedly failing definition construction. Do not use `full` by default.
-- For normal condition tags, use the default `--condition_subtype core`.
-- Use `--condition_subtype behavior_seq` only when the user specifically needs behavior sequence conditions.
-- Use `--condition_subtype all` only when comparing condition subtypes or when the exact subtype cannot be determined after reading the user request. Avoid `all` for simple creation/update tasks.
-
-## Decision Rules
-- `--type` is required and must match the target tag type.
-- It is recommended to run `--dry-run` first to inspect the request mapping before making the actual call.
-- Prefer `--response_mode base` first; request `examples` only when needed; request `full` only as a last resort.
-
-## Next Step 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 used (filter/groupby/query/tag/cluster).
-
-## Recommended Chain
-- +get_tag_definition_schema -> (first build/update in session or refresh) analysis_meta +list_events -> analysis_meta +list_properties -> +create_tag
-- +get_tag_definition_schema -> (first build/update in session or refresh) analysis_meta +list_events -> analysis_meta +list_properties -> +update_tag

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

@@ -1,69 +0,0 @@
-# analysis_audience +get_tags_by_name (Locate Tags by Name)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Tag Management**
-
-## Use Cases
-- Get tag definition details in batch by tag name. Returns complete tag information for matched tags, including IDs, names, display names, types, status, user counts, and tag definitions.
-
-## Commands
-```bash
-ae-cli analysis_audience +get_tags_by_name --project_id <project_id> --names '["demo"]'
-ae-cli analysis_audience +get_tags_by_name --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--names` | Yes | List of tag names (JSON array). Exact-name matching is used; unmatched tags are ignored automatically. |
-
-## Decision Rules
-- For the first execution, it is recommended to pass only the required parameters (`--project_id`, `--names`) and add optional parameters after confirming the path works.
-- `--names` must be passed as a JSON array (e.g. `--names '["tag_a","tag_b"]'`).
-- When troubleshooting across projects, first confirm whether `--project_id` matches the current permissions and target environment.
-
-## Enum Codebook (Asset Definition Interpretation Only)
-
-When interpreting tag `definition` for users, if operator enum codes appear, use the following complete `calcuSymbol` mapping instead of outputting raw codes only.
-
-| Code | Meaning | Applicable Types |
-|---|---|---|
-| `C00` | equals | all |
-| `C000` | equals empty string | string |
-| `C01` | not equals | all |
-| `C010` | not equals empty string | string |
-| `C02` | less than | number |
-| `C020` | less than or equal | number |
-| `C03` | greater than | number |
-| `C030` | greater than or equal | number |
-| `C04` | has value | all |
-| `C05` | no value | all |
-| `C06` | range | number/date |
-| `C060` | date range | date |
-| `C07` | contains | string |
-| `C08` | does not contain | string |
-| `C09` | true | bool |
-| `C10` | false | bool |
-| `C11` | regex match | string |
-| `C12` | regex does not match | string |
-| `C13` | relative to current time | date/datetime |
-| `C14` | relative to event time | date/datetime |
-| `C15` | element exists | array |
-| `C16` | element does not exist | array |
-| `C17` | element position | array |
-| `C18` | no value | array |
-| `C19` | has value | array |
-| `C20` | belongs to cluster | cluster/tag (`tableType="2"`) |
-| `C21` | does not belong to cluster | cluster/tag (`tableType="2"`) |
-| `C22` | object exists that satisfies condition | array |
-| `C23` | no object satisfies condition | array |
-| `C24` | all objects satisfy condition | array |
-
-## Next Step on Failure
-- If required parameters are missing, fall back to the smallest runnable command and fill the gap (focus on `--project_id`, `--names`).
-- If reading fails, first verify whether the object ID exists and belongs to the current project.
-
-## Recommended Chain
-- +list_tags -> +get_tags_by_name -> +update_tag

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

@@ -1,35 +0,0 @@
-# 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

@@ -1,45 +0,0 @@
-# analysis_audience +list_cluster_members (View Cluster Members)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Cluster Management**
-
-## Use Cases
-- List members in the specified cluster.
-- Supports payload governance parameters: `query`, `fields`, `limit`, `offset`.
-- Returns a paginated envelope (items + total + limit + offset + hasMore).
-
-## Commands
-```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 --request_id mcp_aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa --timeout_minutes 8
-ae-cli analysis_audience +list_cluster_members --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--cluster_name` | Yes | Cluster name |
-| `--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`, `--cluster_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`, `--cluster_name`, `--request_id`).
-- If the result is empty, first confirm the project ID/keyword, then try broadening the filter conditions.
-
-## Recommended Chain
-- +list_clusters -> +get_clusters_by_name -> +update_cluster

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

@@ -1,46 +0,0 @@
-# analysis_audience +list_clusters (Audience/User Segment Cluster Search)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Cluster 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).
-
-**Term boundary:** This command lists audience/user segment clusters only. It is not a server, region, or deployment inventory tool.
-
-## Use Cases
-- List audience/user segment cluster 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 cluster members.
-
-## Commands
-```bash
-ae-cli analysis_audience +list_clusters --project_id <project_id>
-ae-cli analysis_audience +list_clusters --project_id <project_id> --query demo
-ae-cli analysis_audience +list_clusters --project_id <project_id> --fields '["id","clusterName","displayName","remarks","clusterType","progress","usersNum"]' --limit 20 --offset 0
-ae-cli analysis_audience +list_clusters --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--query` / `-q` | No | Optional keyword filter. Performs fuzzy matching against clusterName, displayName, and remarks; if omitted, all clusters are returned. |
-| `--fields` | No | Optional return field list (JSON array). Supported fields: `id`, `clusterName`, `displayName`, `clusterType`, `progress`, `usersNum`, `refreshStatus`, `remarks`, `authenticationStatus`. Default fields when omitted: `id`, `clusterName`, `displayName`, `remarks`, `clusterType`, `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 clusters. |
-
-## 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_clusters -> +get_clusters_by_name -> +update_cluster

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

@@ -1,43 +0,0 @@
-# analysis +list_dashboards (List Dashboards)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Dashboard 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` dashboard search. Do not call dashboard/report detail tools as a fallback after a QP builder returns non-generated status.
-
-## 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 analysis +list_dashboards --project_id <project_id>
-ae-cli analysis +list_dashboards --project_id <project_id> --query demo
-ae-cli analysis +list_dashboards --project_id <project_id> --fields '["dashboardId","dashboardName","remark"]' --limit 20 --offset 0
-ae-cli 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 and remarks; if omitted, all accessible dashboards are returned. |
-| `--fields` / `-f` | No | Optional fields to return (JSON array). Supported fields: `dashboardId`, `dashboardName`, `remark`. Default fields when omitted: `dashboardId`, `dashboardName`, `remark`. Dashboard metadata exposes `remark` but no separate desc field. |
-| `--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_dashboards -> +query_dashboard_detail -> +query_dashboard_report_data

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

@@ -1,46 +0,0 @@
-# analysis_meta +list_events (Event Metadata Discovery)
-
-> **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_events` before non-SQL ad-hoc analysis. The matching QP builder resolves event 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 already effective in the project. Use for super events in production metadata. Do NOT use for tracking-plan metadata (bury/track program); that belongs to BuryProgramTool.
-- Read-only query for SYSTEM METADATA already effective in the project. Use when the user explicitly asks to inspect event metadata, not as a required preparation step for QP builder.
-
-## Commands
-```bash
-ae-cli analysis_meta +list_events --project_id <project_id>
-ae-cli analysis_meta +list_events --project_id <project_id> --query demo
-ae-cli analysis_meta +list_events --project_id <project_id> --query demo --fields '["eventId", "eventName", "eventDesc", "remark"]' --limit 20 --offset 0
-ae-cli analysis_meta +list_events --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--query` / `-q` | No | Optional keyword filter. Performs fuzzy matching against eventName, eventDesc, and remark; if omitted, all events are returned. |
-| `--fields` / `-f` | No | Optional fields to return (JSON array). Supported fields: `eventId`, `eventName`, `eventDesc`, `remark`, `eventTag`, `authenticationStatus`. Default fields when omitted: `eventId`, `eventName`, `eventDesc`, `remark`, `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 events. |
-
-## 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 event wording to the builder instead of pre-querying event 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_events -> +create_virtual_event