@thinkingai/ae-cli 6.0.27 → 6.0.29

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

@@ -10,11 +10,11 @@ ae-cli analysis <resource> <action> [options]
 
 Flags use kebab-case. The gateway input JSON uses snake_case. Do not pass camelCase flags or payload keys unless a nested backend DTO explicitly requires them inside `--payload`.
 
-This file is an overview only. Before running one command, read the dedicated command reference named `references/<resource>_<action>.md` with hyphens converted to underscores, for example `dashboard_report_data_export.md`.
+This file is an overview only. Before running an L2 command, read the dedicated command reference named `references/<resource>_<action>.md` with hyphens converted to underscores, for example `dashboard_report_data_export.md`. L3 capabilities without a dedicated reference use dynamic discovery per [`ae-capability`](../../ae-capability/SKILL.md) and the L3 section below.
 
 ## When to use
 
-Use these commands for dashboard, BI panel, project-space, folder, favorite, public-link, dashboard-definition, dashboard-daily-report, and dashboard/BI page data workflows.
+Use these commands for dashboard, BI panel, BI panel version, project-space, folder, favorite, public-link, dashboard-definition, dashboard-daily-report, and dashboard/BI page data workflows.
 
 Prefer export commands for long-running or large data:
 
@@ -28,7 +28,7 @@ ae-cli analysis query cancel --run-id run_0123456789abcdef0123456789abcdef
 
 ## When not to use
 
-Do not use these commands for ad-hoc model analysis, report definition, report data, drilldown, schema helpers, alerts, audience clusters/tags, project lookup, metadata governance, dashboard locks, BI panel version/lock, dashboard filters, UI reorder/tree/move operations, daily report retry/download/get-config, or public-link logs/source-list/get. Use the existing `+<tool_name>` references for those.
+Do not use these commands for ad-hoc model analysis, report definition, report data, drilldown, schema helpers, alerts, audience clusters/tags, project lookup, metadata governance, dashboard locks, BI panel lock, dashboard filters, UI reorder/tree/move operations, daily report retry/download/get-config, or public-link logs/source-list/get. Use the existing `+<tool_name>` references for those.
 
 ## Output
 
@@ -82,7 +82,7 @@ Prefer the run/artifact commands over hand-written HTTP, Python, or curl. The de
 | `dashboard freeze` | `analysis.dashboard.freeze` | Freeze/unfreeze dashboards | `--dashboard-ids`, optional `--freeze false` | Freeze status |
 | `dashboard abnormal-get` | `analysis.dashboard.abnormal_get` | Inspect abnormal dependencies | `--dashboard-id` | Abnormal info |
 | `dashboard task-status` | `analysis.dashboard.task_status` | Inspect scheduled task status | `--dashboard-id` | Task status |
-| `dashboard-report-data run` | `analysis.dashboard_report_data.run` | Bounded inline dashboard report data | `--dashboard-id`, optional `--report-ids`, `--start-time`, `--end-time`, `--limit` | Inline data |
+| `dashboard-report-data run` | `analysis.dashboard_report_data.run` | Bounded inline dashboard report data; `--filters` is analysis Filter JSON from `+get_filter_schema` | `--dashboard-id`, optional `--report-ids`, `--filters`, `--start-time`, `--end-time`, `--limit` | Inline data |
 | `dashboard-report-data export` | `analysis.dashboard_report_data.export` | Large/long dashboard report data | same as run, plus optional `--artifact-format jsonl` | Async artifact descriptor |
 | `run inspect` | `analysis.run.inspect` | Poll async export status | `--run-id` | Run and artifact status |
 | `artifact download` | `analysis.artifact.download` | Download run-bound export artifact | `--run-id`, `--artifact-id`, `--output` | Local output file info |
@@ -90,26 +90,20 @@ Prefer the run/artifact commands over hand-written HTTP, Python, or curl. The de
 | `dashboard-definition export` | `analysis.dashboard_definition.export` | Export dashboard definition JSON | `--dashboard-id`, `--dashboard-ids`, `--dashboard-folder-ids`, `--shared-spaces`, or `--payload` | Definition JSON |
 | `dashboard-definition import` | `analysis.dashboard_definition.import` | Validate/import dashboard definition | `--definition`, optional `--validate-only true` | Validation or import result |
 | `dashboard-daily-report update` | `analysis.dashboard_daily_report.update` | Update daily report config; defaults are sent when `--payload` is absent | `--dashboard-id`, optional config flags or `--payload` | Config result |
-| `dashboard-daily-report send` | `analysis.dashboard_daily_report.send` | Send daily report immediately; defaults are sent when `--payload` is absent | `--dashboard-id`, optional config flags or `--payload` | Async send result |
+| `dashboard-daily-report send` | `analysis.dashboard_daily_report.send` | Send daily report immediately; no config flags means use saved config, missing saved config fails | `--dashboard-id`, optional config flags or `--payload` | Async send result |
 | `bi-panel list` | `analysis.bi_panel.list` | Find accessible BI panels | `--project-id`, optional list filters | Paginated BI panel summaries |
-| `bi-panel get` | `analysis.bi_panel.get` | Inspect released BI panel page structure | `--panel-id`, optional `--fields` | Panel structure |
+| `bi-panel get` | `analysis.bi_panel.get` | Inspect released BI panel page structure only | `--panel-id`, optional `--fields` | Panel structure |
 | `bi-panel create` | `analysis.bi_panel.create` | Create a BI panel | optional `--panel-name`, `--payload` | Created panel |
 | `bi-panel update` | `analysis.bi_panel.update` | Update BI panel content/metadata | optional `--payload` | Update result |
 | `bi-panel delete` | `analysis.bi_panel.delete` | Delete BI panels | `--panel-ids '[...]'` | Delete result |
 | `bi-panel share` | `analysis.bi_panel.share` | Modify BI panel sharing | `--panel-id`, `--payload` | Share update result |
 | `bi-panel copy` | `analysis.bi_panel.copy` | Copy a BI panel | optional source/target flags and `--payload` | Copied panel |
+| `bi-panel-version get` | `analysis.bi_panel_version.get` | Inspect BI panel released or draft version | `--panel-id` or `--panel-uuid`, optional `--version-type release|draft` | Version detail |
+| `bi-panel-version publish` | `analysis.bi_panel_version.publish` | Publish current BI panel draft after source version matches | `--panel-id` or `--panel-uuid`, `--source-version` | Published version |
 | `bi-panel-page-data run` | `analysis.bi_panel_page_data.run` | Bounded inline BI page data | `--panel-id`, `--page-key`, `--result-type charts|summary` | Inline page data |
 | `bi-panel-page-data export` | `analysis.bi_panel_page_data.export` | Large/long BI page data | same as run, optional `--artifact-format jsonl` | Async artifact descriptor |
 | `project-space list` | `analysis.project_space.list` | Find accessible project spaces | `--project-id`, optional list filters | Paginated project spaces |
 | `project-space get` | `analysis.project_space.get` | Inspect one project space | `--project-id`, `--space-id` | Project space detail |
-| `project-space create` | `analysis.project_space.create` | Create a project space; `avatar_type` defaults to 1 when omitted | `--space-name` or `--payload` | Created space |
-| `project-space delete` | `analysis.project_space.delete` | Delete project spaces | `--space-id` or `--space-ids` | Delete result |
-| `project-space share` | `analysis.project_space.share` | Modify project-space members | `--space-id`, `--payload` | Share update result |
-| `project-space members` | `analysis.project_space.members` | Read project-space members | `--space-id` | Members |
-| `folder create` | `analysis.folder.create` | Create personal/project-space folder | `--folder-name`, optional `--space-id`, `--parent-folder-id` | Created folder |
-| `folder delete` | `analysis.folder.delete` | Delete folders | `--folder-id` or `--folder-ids`, optional `--space-id` | Delete result |
-| `folder share` | `analysis.folder.share` | Modify folder members | `--folder-id`, `--payload` | Share update result |
-| `folder members` | `analysis.folder.members` | Read folder members | `--folder-id` | Members |
 | `favorite add` | `analysis.favorite.add` | Favorite dashboard/BI/folder | `--asset-id`, `--asset-type`, optional `--payload` | Favorite result |
 | `favorite remove` | `analysis.favorite.remove` | Remove favorite | same as add | Remove result |
 | `public-link create` | `analysis.public_link.create` | Generate public link | `--resource-type`, `--resource-id`, `--effective-at`, `--expires-at` | Link result |
@@ -118,6 +112,47 @@ Prefer the run/artifact commands over hand-written HTTP, Python, or curl. The de
 | `public-link offline` | `analysis.public_link.offline` | Take links offline | `--link-id` or `--link-ids` | Offline result |
 | `public-link delete` | `analysis.public_link.delete` | Delete public links | `--link-id` or `--link-ids` | Delete result |
 
+## L3 project-space and folder capabilities
+
+Per [`capability-command-admission` §10](../../../docs/capability-command-admission.md): new gateway capabilities default to **dynamic discovery** (`capability search` → `inspect` → `dry-run` → `run`); standalone skill references are **exceptions only** (L2 bar, confusion, high-risk delete, multi-step orchestration).
+
+For **create / delete / share**, read the linked reference before `capability inspect/dry-run/run`. For **`*.members` read**, use this matrix only — no separate `references/*.md` (pilot).
+
+| Capability ID | Use for | Reference / discovery |
+| --- | --- | --- |
+| `analysis.project_space.create` | Create a project space | [`project_space_create.md`](project_space_create.md) |
+| `analysis.project_space.delete` | Delete project spaces | [`project_space_delete.md`](project_space_delete.md) |
+| `analysis.project_space.share` | Modify project-space members | [`project_space_share.md`](project_space_share.md) |
+| `analysis.project_space.members` | Read project-space members | Matrix only (see below) |
+| `analysis.folder.create` | Create personal/project-space folder | [`folder_create.md`](folder_create.md) |
+| `analysis.folder.delete` | Delete folders | [`folder_delete.md`](folder_delete.md) |
+| `analysis.folder.share` | Modify folder members | [`folder_share.md`](folder_share.md) |
+| `analysis.folder.members` | Read folder members | Matrix only (see below) |
+
+### L3 members (matrix-only pilot)
+
+Read-only member lists; `risk=read`. Do not use to modify members — use the matching `*.share` capability.
+
+**When to use:** inspect who has access to a project space or folder.
+
+**When not to use:** modify members → `analysis.project_space.share` or `analysis.folder.share`.
+
+```bash
+ae-cli capability inspect analysis.project_space.members
+ae-cli capability run analysis.project_space.members --input '{"project_id":1,"space_id":10}'
+
+ae-cli capability inspect analysis.folder.members
+ae-cli capability run analysis.folder.members --input '{"project_id":1,"folder_id":1001}'
+```
+
+| field | type | required | capability |
+| --- | --- | --- | --- |
+| `project_id` | integer | yes | both |
+| `space_id` | integer | yes | `project_space.members` |
+| `folder_id` | integer | yes | `folder.members` |
+
+Output is the gateway envelope; `data` contains members.
+
 ## Examples
 
 ```bash

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

@@ -0,0 +1,27 @@
+# analysis-meta asset abnormal-get
+
+Use when the user needs to get abnormal reason for one asset.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta asset abnormal-get --project-id <project_id> --resource-type <resource_type> --resource-id <resource_id> --resource-name <resource_name> --table-type <table_type>
+ae-cli analysis-meta asset abnormal-get --dry-run
+```
+
+Capability id: `metadata.asset_abnormal.get`.
+
+Input sends `project_id`, `resource_type`, `resource_id`, `resource_name`, `table_type`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--resource-type` | Yes | Resource type. |
+| `--resource-id` | No | Resource ID. |
+| `--resource-name` | No | Resource name. |
+| `--table-type` | No | Property table type when the resource is a property. |

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

@@ -0,0 +1,24 @@
+# analysis-meta asset abnormal-list
+
+Use when the user needs to list abnormal assets by resource type.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta asset abnormal-list --project-id <project_id> --resource-types <resource_types>
+ae-cli analysis-meta asset abnormal-list --dry-run
+```
+
+Capability id: `metadata.asset_abnormal.list`.
+
+Input sends `project_id`, `resource_types`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--resource-types` | Yes | Resource types to query. |

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

@@ -0,0 +1,23 @@
+# analysis-meta asset authentication-list
+
+Use when the user needs to list authenticatable project assets and authentication status.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta asset authentication-list --project-id <project_id>
+ae-cli analysis-meta asset authentication-list --dry-run
+```
+
+Capability id: `metadata.asset_authentication.list`.
+
+Input sends `project_id`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |

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

@@ -0,0 +1,24 @@
+# analysis-meta asset authentication-update
+
+Use when the user needs to batch authenticate or unauthenticate assets.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta asset authentication-update --project-id <project_id> --payload '{}'
+ae-cli analysis-meta asset authentication-update --dry-run
+```
+
+Capability id: `metadata.asset_authentication.update`.
+
+Input sends `project_id`, `payload`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--payload` | Yes | Capability payload JSON. |

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

@@ -0,0 +1,24 @@
+# analysis-meta asset recent-list
+
+Use when the user needs to list recently visited assets for the current user.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta asset recent-list --project-id <project_id> --payload '{}'
+ae-cli analysis-meta asset recent-list --dry-run
+```
+
+Capability id: `metadata.asset.recent_list`.
+
+Input sends `project_id`, `payload`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--payload` | Yes | Capability payload JSON. |

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

@@ -0,0 +1,24 @@
+# analysis-meta asset search
+
+Use when the user needs to search project assets by keyword.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta asset search --project-id <project_id> --payload '{}'
+ae-cli analysis-meta asset search --dry-run
+```
+
+Capability id: `metadata.asset.search`.
+
+Input sends `project_id`, `payload`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--payload` | Yes | Capability payload JSON. |

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

@@ -2,6 +2,11 @@
 
 Use when the user needs one BI panel's released page structure.
 
+This command reads only the released/queryable structure. It can fail with
+`NOT_FOUND` for a newly created or draft-only panel. To inspect unpublished
+edits, use `bi-panel-version get --version-type draft`. To make draft edits
+queryable, publish them with `bi-panel-version publish`.
+
 Do not use to query chart data. Use `bi-panel-page-data run` or `bi-panel-page-data export`.
 
 Command:

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

@@ -12,4 +12,10 @@ ae-cli analysis bi-panel share --project-id <project_id> --panel-id <panel_id> [
 
 Input sends `project_id`, `panel_id`, and backend-compatible snake_case `payload`.
 
+Supported payload fields include:
+
+- `all_auth_user_authority`: project-wide BI panel authority. Use `READ`, `JUNIOR`, `SENIOR`, or `MAINTAIN`; `VIEWER` is accepted as `READ`.
+- `auth_users`: user authority list.
+- `auth_user_groups`: user-group authority list.
+
 Output is the gateway envelope. `data` contains the share update result.

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

@@ -2,7 +2,10 @@
 
 Use when the user wants to update BI panel content or metadata.
 
-Do not use for BI panel version or lock workflows; those are intentionally not CLI-enabled.
+Do not use this command to verify draft content or publish a draft. `bi-panel get`
+reads only the released/queryable version. Use `bi-panel-version get` to inspect
+`release` or `draft`, and `bi-panel-version publish` to publish a matching draft
+`source_version`.
 
 Command:
 

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

@@ -0,0 +1,23 @@
+# analysis bi-panel-version get
+
+Use when the user needs a BI panel's released version or unpublished draft version.
+
+Do not use `bi-panel get` for draft verification; `bi-panel get` reads only the
+released/queryable structure.
+
+Command:
+
+```bash
+ae-cli analysis bi-panel-version get --project-id <project_id> --panel-id <panel_id> --version-type draft
+ae-cli analysis bi-panel-version get --project-id <project_id> --panel-uuid <panel_uuid> --version-type release
+```
+
+Input sends `project_id`, one of `panel_id` or `panel_uuid`, optional
+`version_type` (`release` by default), and optional `fields`.
+
+Output is the gateway envelope. `data` contains `panel_id`, `panel_uuid`,
+`requested_version_type`, `version_type`, `version`, `page_content`,
+`panel_config`, and `worksheet_map`.
+
+When the result is used before publishing, save `data.version` and pass it as
+`--source-version` to `bi-panel-version publish`.

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

@@ -0,0 +1,20 @@
+# analysis bi-panel-version publish
+
+Use when the user wants to publish the current BI panel draft so `bi-panel get`
+and BI page-data queries can read it as a released/queryable version.
+
+Do not use this command blindly after `bi-panel update`. First inspect the draft with
+`bi-panel-version get --version-type draft` and use the returned `data.version`
+as `--source-version`. The gateway rejects stale `source_version` values.
+
+Command:
+
+```bash
+ae-cli analysis bi-panel-version publish --project-id <project_id> --panel-id <panel_id> --source-version <draft_version> --yes
+```
+
+Input sends `project_id`, one of `panel_id` or `panel_uuid`, and required
+`source_version`.
+
+Output is the gateway envelope. `data` contains `panel_id`, `panel_uuid`,
+`source_version_type`, `source_version`, and `published_version`.

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

@@ -8,7 +8,7 @@ Domain: **Model Analysis**
 - Build a validated event-analysis QP from structured intent.
 - Use in the mandatory builder flow before `+query_adhoc --model_type event`.
 - This command builds QP only and does not execute the analysis query.
-- This is one of exactly four QP builders: `event`, `retention`, `funnel`, `prop_analysis`.
+- This is the `event` builder in the ten-model guided QP builder set.
 - Use this builder for event-analysis ad hoc requests; do not manually build event QP through `+get_analysis_query_schema`.
 
 ## JSON Rules

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

@@ -8,7 +8,7 @@ Domain: **Model Analysis**
 - Build a validated funnel-analysis QP from structured intent.
 - Use in the mandatory builder flow before `+query_adhoc --model_type funnel`.
 - This command builds QP only and does not execute the analysis query.
-- This is one of exactly four QP builders: `event`, `retention`, `funnel`, `prop_analysis`.
+- This is the `funnel` builder in the ten-model guided QP builder set.
 - Use this builder for funnel ad hoc requests; do not manually build funnel QP through `+get_analysis_query_schema`.
 
 ## JSON Rules

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

@@ -8,7 +8,7 @@ Domain: **Model Analysis**
 - Build a validated `prop_analysis` QP from structured intent.
 - Use in the mandatory builder flow before `+query_adhoc --model_type prop_analysis`.
 - This command builds QP only and does not execute the analysis query.
-- This is one of exactly four QP builders: `event`, `retention`, `funnel`, `prop_analysis`.
+- This is the `prop_analysis` builder in the ten-model guided QP builder set.
 - Use this builder for property-analysis ad hoc requests; do not manually build prop_analysis QP through `+get_analysis_query_schema`.
 
 ## JSON Rules

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

@@ -8,7 +8,7 @@ Domain: **Model Analysis**
 - Build a validated retention-analysis QP from structured intent.
 - Use in the mandatory builder flow before `+query_adhoc --model_type retention`.
 - This command builds QP only and does not execute the analysis query.
-- This is one of exactly four QP builders: `event`, `retention`, `funnel`, `prop_analysis`.
+- This is the `retention` builder in the ten-model guided QP builder set.
 - Use this builder for retention ad hoc requests; do not manually build retention QP through `+get_analysis_query_schema`.
 
 ## JSON Rules

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

@@ -26,7 +26,7 @@ ae-cli analysis +cancel_query --request_id 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.
+- This is a write operation (`risk: write`). 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.

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

@@ -12,6 +12,11 @@ ae-cli analysis dashboard-daily-report send --project-id <project_id> --dashboar
 
 Input sends `project_id`, `dashboard_id`, and optional daily report fields or `payload`.
 
-When `--payload` is absent, the command sends safe defaults expected by the gateway: `need_csv=false`, empty `host_url`, all channel switches false, `send_date=1,2,3,4,5,6,7`, `send_time=09:00`, `lang=zh-CN`, `screen_type=normal`, and `zone_offset=0`. When `--payload` is present, payload values remain authoritative; pass top-level flags only for fields you intentionally want to override.
+Behavior:
+
+- If no daily report config flags and no `--payload` are provided, the gateway uses the dashboard's saved daily report config.
+- If the dashboard has no saved daily report config, the command fails with a stable business error instead of creating a misleading task.
+- If any config flag or `--payload` is provided, the request config is used for this immediate send. Provide at least one valid channel, for example `--enable-dd true --dd-url '["https://..."]'`, or email fields such as `--enable-email true --email-login-users user@example.com`.
+- Use `dashboard-daily-report update` to save or change scheduled daily report config.
 
 Output is the gateway envelope. `data` contains the immediate send result.

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

@@ -12,6 +12,12 @@ ae-cli analysis dashboard-report-data export --project-id <project_id> --dashboa
 
 Input sends `project_id`, `dashboard_id`, and optional `report_ids`, `filters`, `start_time`, `end_time`, `use_cache`, `request_id`, `timeout_seconds`, `format`. Use CLI flag `--artifact-format` for the gateway `format` input; `--format` is the CLI output formatter.
 
+`--filters` is an analysis Filter JSON injected as `commonFilter.aiFilter` for each queried report. It is not a dashboard UI control dump. Use `ae-cli analysis +get_filter_schema` for the exact schema. Minimal shape:
+
+```json
+{"relation":"and","filts":[{"field":{"type":"event_property","propertyName":"#event_name"},"operator":"equal","values":["login"]}]}
+```
+
 Output is the gateway envelope. `data` contains an async export descriptor with `run_id`, `artifact_id`, status fields, and expiration fields. It does not expose inspect/download API paths; use the CLI commands below.
 
 Follow-up workflow:

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

@@ -12,4 +12,10 @@ ae-cli analysis dashboard-report-data run --project-id <project_id> --dashboard-
 
 Input sends `project_id`, `dashboard_id`, and optional `report_ids`, `filters`, `start_time`, `end_time`, `use_cache`, `request_id`, `timeout_seconds`, `limit`.
 
+`--filters` is an analysis Filter JSON injected as `commonFilter.aiFilter` for each queried report. It is not a dashboard UI control dump. Use `ae-cli analysis +get_filter_schema` for the exact schema. Minimal shape:
+
+```json
+{"relation":"and","filts":[{"field":{"type":"event_property","propertyName":"#event_name"},"operator":"equal","values":["login"]}]}
+```
+
 Output is the gateway envelope. `data` contains bounded inline report data.

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

@@ -0,0 +1,24 @@
+# analysis-meta datatable columns-get
+
+Use when the user needs to get columns for a project table reference.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta datatable columns-get --project-id <project_id> --table-ref <table_ref>
+ae-cli analysis-meta datatable columns-get --dry-run
+```
+
+Capability id: `metadata.data_table.columns_get`.
+
+Input sends `project_id`, `table_ref`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--table-ref` | Yes | Project table reference. |

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

@@ -0,0 +1,24 @@
+# analysis-meta datatable influence-list
+
+Use when the user needs to list metadata and assets affected by data table deletion or column changes.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta datatable influence-list --project-id <project_id> --datatable-id <datatable_id>
+ae-cli analysis-meta datatable influence-list --dry-run
+```
+
+Capability id: `metadata.data_table.influence_list`.
+
+Input sends `project_id`, `datatable_id`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--datatable-id` | Yes | Data table ID. |

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

@@ -0,0 +1,24 @@
+# analysis-meta datatable version-get
+
+Use when the user needs to get data table version detail.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta datatable version-get --project-id <project_id> --version-id <version_id>
+ae-cli analysis-meta datatable version-get --dry-run
+```
+
+Capability id: `metadata.data_table_version.get`.
+
+Input sends `project_id`, `version_id`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--version-id` | Yes | Data table version ID. |

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

@@ -0,0 +1,24 @@
+# analysis-meta datatable version-list
+
+Use when the user needs to list data table historical versions.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta datatable version-list --project-id <project_id> --datatable-id <datatable_id>
+ae-cli analysis-meta datatable version-list --dry-run
+```
+
+Capability id: `metadata.data_table_version.list`.
+
+Input sends `project_id`, `datatable_id`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--datatable-id` | Yes | Data table ID. |

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

@@ -8,7 +8,7 @@ Domain: **Model analysis**
 - Drill down to detailed event sequences for a specific user on specific dates.
 - This tool is typically used after drilldown_users.
 - Common parameters (focus on these): projectId, userId, eventNames, targetDates.
-- Advanced parameters (for special scenarios): zoneOffset, properties, timeGranularity, firstDayOfWeek, sortOrder, eventNameFilter, timeFilter, timeFilterBeforeNums, timeFilterAfterNums, entityId, entityValue, useCache, pageNum, pageSize.
+- Advanced parameters (for special scenarios): zoneOffset, properties, timeGranularity, firstDayOfWeek, sortOrder, eventNameFilter, timeFilter, timeFilterBeforeNums, timeFilterAfterNums, entityId, entityValue, useCache, limit, offset.
 - The userId must come from drilldown_users and must not be guessed.
 - targetDates is a list of discrete dates, not a date range.
 - Constraint: drilldown positioning parameters must come from the previous query result and must not be guessed.
@@ -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 --request_id mcp_bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
+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 --limit 20 --offset 0 --request_id mcp_bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
 ae-cli analysis +drilldown_user_events --dry-run
 ```
 
@@ -54,8 +54,8 @@ ae-cli analysis +drilldown_user_events --dry-run
 | `--entity_id` | No | Optional entity ID for multi-entity scenarios |
 | `--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: 10000 |
+| `--limit` | No | Maximum rows. Default: 1000, maximum: 10000 |
+| `--offset` | No | Row 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 |
 

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

@@ -0,0 +1,24 @@
+# analysis-meta event changelog-list
+
+Use when the user needs to list event metadata change logs.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta event changelog-list --project-id <project_id> --event-name <event_name>
+ae-cli analysis-meta event changelog-list --dry-run
+```
+
+Capability id: `metadata.event.changelog_list`.
+
+Input sends `project_id`, `event_name`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--event-name` | Yes | Event name. |

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

@@ -0,0 +1,24 @@
+# analysis-meta event create
+
+Use when the user needs to create super events and optionally associate event properties.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta event create --project-id <project_id> --payload '{}'
+ae-cli analysis-meta event create --dry-run
+```
+
+Capability id: `metadata.event.create`.
+
+Input sends `project_id`, `payload`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--payload` | Yes | Capability payload JSON. |