@thinkingai/ae-cli 6.0.27 → 6.0.28

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@thinkingai/ae-cli",
-  "version": "6.0.27",
+  "version": "6.0.28",
   "description": "CLI tool for ThinkingAI (AE) analytics platform",
   "type": "module",
   "bin": {

package/skills/ae-analysis/SKILL.md

@@ -75,6 +75,7 @@ ae-cli analysis dashboard-report-data export --project-id <project_id> --dashboa
 ae-cli analysis run inspect --run-id <run_id>
 ae-cli analysis artifact download --run-id <run_id> --artifact-id <artifact_id> --output <file>
 ae-cli analysis bi-panel-page-data run --project-id <project_id> --panel-id <panel_id> --page-key <page_key> --result-type charts
+ae-cli analysis bi-panel-version get --project-id <project_id> --panel-id <panel_id> --version-type draft
 ae-cli analysis project-space list --project-id <project_id>
 ae-cli analysis query cancel --run-id <run_id>
 ```
@@ -85,13 +86,13 @@ Use capability-gateway asset commands when the user wants to manage or inspect:
 - Dashboard report data that may be large or long-running. Prefer `dashboard-report-data export` for large results; use `run` only for bounded inline results.
 - Dashboard definition export/import. Use `dashboard-definition import --validate-only true` for import pre-checks; do not look for a separate import-check command.
 - Dashboard daily report update or immediate send.
-- BI panel list/detail/create/update/delete/share/copy and BI page data. Prefer `bi-panel-page-data export` for large results.
+- BI panel list/detail/create/update/delete/share/copy, BI panel release/draft version get/publish, and BI page data. Prefer `bi-panel-page-data export` for large results.
 - Project spaces, folders, favorites, and public links.
 
 Do **not** use these commands for:
 
 - Ad-hoc model analysis, report definition, report data, drilldown, entity/event details, metadata/schema helpers, alerts, audience clusters/tags, or project lookup. Use the existing `+<tool_name>` commands for those.
-- Dashboard locks, BI panel version/lock, dashboard filter module, UI reorder/move/tree operations, daily report retry/download/get-config, public-link logs/source-list/get, or other product-manager-red-marked abilities.
+- Dashboard locks, BI panel lock, dashboard filter module, UI reorder/move/tree operations, daily report retry/download/get-config, public-link logs/source-list/get, or other product-manager-red-marked abilities.
 - Internal-only or UI-only payloads unless the gateway command reference explicitly exposes them through `--payload`.
 
 Capability-gateway output:
@@ -361,7 +362,58 @@ After outputting attribution results, verify that dimension contributions sum to
 
 ## Tool Groups (100)
 
-### analysis (61)
+### analysis (108)
+
+
+Metadata Capabilities (47):
+
+- `asset abnormal-get` ([doc](references/asset_abnormal_get.md))
+- `asset abnormal-list` ([doc](references/asset_abnormal_list.md))
+- `asset authentication-list` ([doc](references/asset_authentication_list.md))
+- `asset authentication-update` ([doc](references/asset_authentication_update.md))
+- `asset recent-list` ([doc](references/asset_recent_list.md))
+- `asset search` ([doc](references/asset_search.md))
+- `datatable columns-get` ([doc](references/datatable_columns_get.md))
+- `datatable influence-list` ([doc](references/datatable_influence_list.md))
+- `datatable version-get` ([doc](references/datatable_version_get.md))
+- `datatable version-list` ([doc](references/datatable_version_list.md))
+- `event changelog-list` ([doc](references/event_changelog_list.md))
+- `event create` ([doc](references/event_create.md))
+- `event delete` ([doc](references/event_delete.md))
+- `event get` ([doc](references/event_get.md))
+- `event hide-update` ([doc](references/event_hide_update.md))
+- `event influence-list` ([doc](references/event_influence_list.md))
+- `event list` ([doc](references/event_list.md))
+- `event relation-update` ([doc](references/event_relation_update.md))
+- `event update` ([doc](references/event_update.md))
+- `exchange config-update` ([doc](references/exchange_config_update.md))
+- `exchange rate-refresh` ([doc](references/exchange_rate_refresh.md))
+- `exchange rule-list` ([doc](references/exchange_rule_list.md))
+- `exchange rule-update` ([doc](references/exchange_rule_update.md))
+- `exchange rule-validate` ([doc](references/exchange_rule_validate.md))
+- `metric create` ([doc](references/metric_create.md))
+- `metric delete` ([doc](references/metric_delete.md))
+- `metric get` ([doc](references/metric_get.md))
+- `metric list` ([doc](references/metric_list.md))
+- `metric update` ([doc](references/metric_update.md))
+- `property changelog-list` ([doc](references/property_changelog_list.md))
+- `property create` ([doc](references/property_create.md))
+- `property delete` ([doc](references/property_delete.md))
+- `property get` ([doc](references/property_get.md))
+- `property hide-update` ([doc](references/property_hide_update.md))
+- `property influence-list` ([doc](references/property_influence_list.md))
+- `property list` ([doc](references/property_list.md))
+- `property related-events` ([doc](references/property_related_events.md))
+- `property relation-update` ([doc](references/property_relation_update.md))
+- `property update` ([doc](references/property_update.md))
+- `super-metadata export` ([doc](references/super_metadata_export.md))
+- `super-metadata import` ([doc](references/super_metadata_import.md))
+- `virtual-event create` ([doc](references/virtual_event_create.md))
+- `virtual-event delete` ([doc](references/virtual_event_delete.md))
+- `virtual-event get` ([doc](references/virtual_event_get.md))
+- `virtual-property create` ([doc](references/virtual_property_create.md))
+- `virtual-property sql-rule-delete` ([doc](references/virtual_property_sql_rule_delete.md))
+- `virtual-property sql-rule-update` ([doc](references/virtual_property_sql_rule_update.md))
 
 Alerts (6):
 - `+get_alert_definition_schema` ([doc](references/get_alert_definition_schema.md))
@@ -498,4 +550,4 @@ npm run verify:analysis-common-tools
 
 ## Reference Docs
 
-See the unified `references/` directory (79 command docs total).
+See the unified `references/` directory (126 command docs total).

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

@@ -14,7 +14,7 @@ This file is an overview only. Before running one command, read the dedicated co
 
 ## 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,14 +90,16 @@ 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 |

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

@@ -0,0 +1,27 @@
+# analysis 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 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 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 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 asset abnormal-list --project-id <project_id> --resource-types <resource_types>
+ae-cli analysis 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 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 asset authentication-list --project-id <project_id>
+ae-cli analysis 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 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 asset authentication-update --project-id <project_id> --payload '{}'
+ae-cli analysis 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 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 asset recent-list --project-id <project_id> --payload '{}'
+ae-cli analysis 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 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 asset search --project-id <project_id> --payload '{}'
+ae-cli analysis 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/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 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 datatable columns-get --project-id <project_id> --table-ref <table_ref>
+ae-cli analysis 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 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 datatable influence-list --project-id <project_id> --datatable-id <datatable_id>
+ae-cli analysis 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 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 datatable version-get --project-id <project_id> --version-id <version_id>
+ae-cli analysis 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 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 datatable version-list --project-id <project_id> --datatable-id <datatable_id>
+ae-cli analysis 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/event_changelog_list.md

@@ -0,0 +1,24 @@
+# analysis 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 event changelog-list --project-id <project_id> --event-name <event_name>
+ae-cli analysis 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 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 event create --project-id <project_id> --payload '{}'
+ae-cli analysis 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. |

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

@@ -0,0 +1,24 @@
+# analysis event delete
+
+Use when the user needs to batch delete events or virtual events.
+
+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 event delete --project-id <project_id> --event-names '{}'
+ae-cli analysis event delete --dry-run
+```
+
+Capability id: `metadata.event.delete`.
+
+Input sends `project_id`, `event_names`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--event-names` | Yes | Event names JSON array, or a JSON string accepted by common-service. |

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

@@ -0,0 +1,24 @@
+# analysis event get
+
+Use when the user needs to get one super event metadata 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 event get --project-id <project_id> --event-name <event_name>
+ae-cli analysis event get --dry-run
+```
+
+Capability id: `metadata.event.get`.
+
+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. |