@thinkingai/ae-cli 6.0.22 → 6.0.24

package/skills/ae-analysis/SKILL.md

@@ -10,6 +10,7 @@ description: "AE/TE/ThinkingEngine/ThinkingAI ae-cli manual for analysis-side ta
 > **CRITICAL - For all commands that require `project_id`, you MUST satisfy `PROJECT_ID_GATE` first (no guessing): verify the project by ID/name with `analysis_common +list_projects` only when there is no valid project context yet, when the user switches project/host/environment, or when the supplied project is ambiguous. Reuse a project already verified in the same continuous conversation and same host/environment.**
 > **CRITICAL - For write operations in this skill, you MUST complete the post-write link loop when applicable:** after success and extractable `resource_id`, call `analysis_common +get_resource_url` and return the main result + resource link (or explicit link-failure reason).
 > **CRITICAL - Before running any `+<tool_name>` command, you MUST first read the corresponding `references/<tool_name>.md`.** The reference filename always equals the command name without the leading `+`, for example `+query_adhoc` -> `references/query_adhoc.md`.
+> **CRITICAL - Before running any capability-gateway asset command such as `ae-cli analysis dashboard list`, `ae-cli analysis bi-panel get`, `ae-cli analysis project-space create`, or `ae-cli analysis public-link list`, read the matching `references/<resource>_<action>.md` file. Replace hyphens with underscores, for example `analysis dashboard list` -> `references/dashboard_list.md`, `analysis bi-panel get` -> `references/bi_panel_get.md`. Use [`references/analysis_gateway_assets.md`](references/analysis_gateway_assets.md) only as the overview matrix.**
 
 ## Global AE CLI Rules
 
@@ -21,7 +22,7 @@ Global parameters:
 | ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `--format <json\|table>` | Output format. Default is JSON.                                                                                                                       |
 | `--jq <expr>`            | jq filter expression for JSON output.                                                                                                                 |
-| `--host <url>`           | Override the active AE host. Available on every command and may be placed after the subcommand, e.g. `ae-cli analysis +list_dashboards --host <url>`. |
+| `--host <url>`           | Override the active AE host. Available on every command and may be placed after the subcommand, e.g. `ae-cli analysis dashboard list --host <url>`. |
 
 Output and errors:
 
@@ -52,14 +53,55 @@ If user intent is Engage/DataOps/Community/metadata gateway detail, switch to `a
 - `ae-cli analysis_audience +<tool_name> [options]`
 - `ae-cli analysis_meta +<tool_name> [options]`
 - `ae-cli analysis_common +<tool_name> [options]`
+- `ae-cli analysis <resource> <action> [options]` for capability-gateway dashboard, BI panel, project-space, folder, favorite, public-link, dashboard-definition, dashboard-daily-report, and async asset data commands.
 
 Conventions:
 
-- CLI flags use underscores, e.g. `--project_id`.
+- MCP `+<tool_name>` command flags use underscores, e.g. `--project_id`.
+- Capability-gateway command flags use kebab-case, e.g. `--project-id`, `--dashboard-id`, `--request-id`. The CLI sends snake_case JSON to the gateway.
 - MCP params map automatically to camelCase.
 - JSON args pass as JSON string literals.
 - Write operations require confirmation unless `--yes`.
 
+## Capability Gateway Asset Commands
+
+Use these commands for dashboard, BI panel, project space, folder, favorite, public link, dashboard definition import/export, dashboard daily report, and dashboard/BI page data operations:
+
+```bash
+ae-cli analysis dashboard list --project-id <project_id>
+ae-cli analysis dashboard get --project-id <project_id> --dashboard-id <dashboard_id>
+ae-cli analysis dashboard update --project-id <project_id> --operation settings --dashboard-id <dashboard_id> --payload '{...}'
+ae-cli analysis dashboard-report-data export --project-id <project_id> --dashboard-id <dashboard_id>
+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 project-space list --project-id <project_id>
+ae-cli analysis query cancel --run-id <run_id>
+```
+
+Use capability-gateway asset commands when the user wants to manage or inspect:
+
+- Dashboards, dashboard basic detail including creator/create time, dashboard sharing, dashboard notes, dashboard copy/freeze/handover/delete, abnormal info, task status.
+- 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.
+- 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.
+- Internal-only or UI-only payloads unless the gateway command reference explicitly exposes them through `--payload`.
+
+Capability-gateway output:
+
+- Successful commands return the standard gateway envelope: `{ "ok": true, "data": ..., "meta": ... }`.
+- Failed commands return `{ "ok": false, "error": ... }` and exit non-zero.
+- Inline `run` data is bounded by `--limit` and `--timeout-seconds`.
+- Export commands return `run_id`, `artifact_id`, artifact status, inspect path, and download path. Use `--artifact-format jsonl` for the artifact format; `--format` is reserved for CLI output formatting. Cancel with `ae-cli analysis query cancel --run-id <run_id>`.
+- Unknown input fields and camelCase external fields are rejected by the gateway; use kebab-case CLI flags only.
+
+See [`references/analysis_gateway_assets.md`](references/analysis_gateway_assets.md) for the command matrix. Before running one command, read its dedicated reference file named as `<resource>_<action>.md`.
+
 ## Mandatory Constraints
 
 ### A. PROJECT_ID_GATE
@@ -78,7 +120,7 @@ For any command requiring `project_id`:
 
 When these writes succeed and `resource_id` is extractable, call `analysis_common +get_resource_url` and append link output:
 
-- `dashboard`: `+create_dashboard`, `+update_dashboard`
+- `dashboard`: `analysis dashboard create`, `analysis dashboard update`
 - `report`: `+create_report`
 - `metric`: `+create_metric`, `+update_metric`
 - `alert`: `+create_alert`, `+update_alert`
@@ -97,7 +139,7 @@ Closed-loop check (must be explicit in result):
 
 ### C. FUZZY_SEARCH_FALLBACK
 
-For list commands with `--query` parameter (list_reports, list_dashboards, list_events, list_clusters, list_tags, list_alerts, list_metrics):
+For list commands with `--query` parameter (`list_reports`, `analysis dashboard list`, `list_events`, `list_clusters`, `list_tags`, `list_alerts`, `list_metrics`):
 
 1. **First attempt**: Use `--query` with user-provided keyword for fuzzy search
 2. **If no results found**, retry up to 2 more times with:
@@ -123,8 +165,8 @@ Before executing ad-hoc queries (`query_adhoc`), MUST check for existing reports
 
 1. **Identify user intent** - Extract what metrics/dimensions/filters the user wants
 2. **Search existing reports** - Use `list_reports --query <keyword>` to find matching reports
-3. **Search existing dashboards** - Use `list_dashboards --query <keyword>` to find matching dashboards
-4. **If found** - Use `query_report_data` or `query_dashboard_report_data` to get data from existing assets
+3. **Search existing dashboards** - Use `analysis dashboard list --query <keyword>` to find matching dashboards
+4. **If found** - Use `query_report_data` or `analysis dashboard-report-data run/export` to get data from existing assets
 5. **If not found** - For QP builder-supported models (`event`, `retention`, `funnel`, `prop_analysis`), call the matching builder first and then call `query_adhoc` with builder `qp`; do not call schema or metadata tools between the report/dashboard miss and the builder. For all other `query_adhoc` models, use the legacy schema/metadata path.
 
 **Rationale:**
@@ -327,31 +369,15 @@ Alerts (6):
 - `+update_alert` ([doc](references/update_alert.md))
 - `+delete_alert` ([doc](references/delete_alert.md))
 
-Reports and Dashboards (24):
+Reports:
 - `+create_report` ([doc](references/create_report.md))
 - `+get_report_definition` ([doc](references/get_report_definition.md))
 - `+list_reports` ([doc](references/list_reports.md))
 - `+query_report_data` ([doc](references/query_report_data.md))
 - `+update_report` ([doc](references/update_report.md))
 - `+delete_report` ([doc](references/delete_report.md))
-- `+create_space` ([doc](references/create_space.md))
-- `+list_spaces` ([doc](references/list_spaces.md))
-- `+create_dashboard` ([doc](references/create_dashboard.md))
-- `+list_dashboards` ([doc](references/list_dashboards.md))
-- `+query_dashboard_detail` ([doc](references/query_dashboard_detail.md))
-- `+query_dashboard_report_data` ([doc](references/query_dashboard_report_data.md))
-- `+update_dashboard` ([doc](references/update_dashboard.md))
-- `+delete_dashboard` ([doc](references/delete_dashboard.md))
-- `+copy_dashboard` ([doc](references/copy_dashboard.md))
-- `+freeze_dashboards` ([doc](references/freeze_dashboards.md))
-- `+move_dashboard` ([doc](references/move_dashboard.md))
-- `+create_or_update_dashboard_note` ([doc](references/create_or_update_dashboard_note.md))
-- `+list_public_access_links` ([doc](references/list_public_access_links.md))
-- `+create_public_access_link` ([doc](references/create_public_access_link.md))
-- `+update_public_access_link` ([doc](references/update_public_access_link.md))
-- `+list_bi_panels` ([doc](references/list_bi_panels.md))
-- `+get_bi_panel_detail` ([doc](references/get_bi_panel_detail.md))
-- `+query_bi_panel_data` ([doc](references/query_bi_panel_data.md))
+
+Dashboard, BI panel, project-space, folder, favorite, public-link, dashboard-definition, dashboard-daily-report, and dashboard/BI data commands are capability-gateway commands. Use `ae-cli analysis <resource> <action>` after reading [`references/analysis_gateway_assets.md`](references/analysis_gateway_assets.md); do not use old `+` dashboard/space/BI/public-link command names.
 
 Model Analysis (17):
 - `+build_event_analysis_qp` ([doc](references/build_event_analysis_qp.md))

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

@@ -0,0 +1,114 @@
+# analysis capability-gateway asset commands
+
+> Prerequisite: follow [`../SKILL.md`](../SKILL.md), especially `PROJECT_ID_GATE`.
+
+These commands use the capability gateway instead of MCP tool names. The CLI command shape is:
+
+```bash
+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`.
+
+## 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.
+
+Prefer export commands for long-running or large data:
+
+```bash
+ae-cli analysis dashboard-report-data export --project-id 1 --dashboard-id 1001
+ae-cli analysis bi-panel-page-data export --project-id 1 --panel-id 2001 --page-key main --result-type charts
+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.
+
+## Output
+
+All commands return the gateway envelope:
+
+```json
+{
+  "ok": true,
+  "data": {},
+  "meta": {}
+}
+```
+
+Failures return:
+
+```json
+{
+  "ok": false,
+  "error": {
+    "code": "INVALID_QUERY_REQUEST",
+    "message": "..."
+  }
+}
+```
+
+Export commands return `run_id`, `artifact_id`, `status`, `artifact_status`, `inspect_path`, `download_path`, `expires_at`, and `expires_at_iso`. Download the artifact through the returned path; cancel by `run_id`.
+
+## Command matrix
+
+| Command | Capability ID | Use for | Key input | Output |
+| --- | --- | --- | --- | --- |
+| `dashboard list` | `analysis.dashboard.list` | Find accessible dashboards | `--project-id`, optional `--query`, `--fields`, `--limit`, `--offset` | Paginated dashboard summaries |
+| `dashboard create` | `analysis.dashboard.create` | Create a dashboard | `--project-id`, `--dashboard-name`, optional `--space-id`, `--folder-id` | Created dashboard |
+| `dashboard get` | `analysis.dashboard.get` | Inspect one dashboard definition/share/report structure, including creator and creation/update time | `--project-id`, `--dashboard-id` | Dashboard detail |
+| `dashboard update` | `analysis.dashboard.update` | Update settings or upsert a note | `--operation settings|note-upsert`, IDs, optional `--payload` | Update result |
+| `dashboard share-info` | `analysis.dashboard.share_info` | Read dashboard sharing info | `--project-id`, `--dashboard-id` | Share info |
+| `dashboard share` | `analysis.dashboard.share` | Modify dashboard sharing | `--project-id`, `--dashboard-id`, `--payload` or `--member-authorities` | Share update result |
+| `dashboard delete` | `analysis.dashboard.delete` | Delete dashboards | `--project-id`, `--dashboard-ids '[...]'` | Delete result |
+| `dashboard handover` | `analysis.dashboard.handover` | Transfer dashboards | `--dashboard-ids`, `--to-user-id` | Handover result |
+| `dashboard copy` | `analysis.dashboard.copy` | Copy a dashboard | `--dashboard-id`, `--dashboard-name`, optional target IDs | Copied dashboard |
+| `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 export` | `analysis.dashboard_report_data.export` | Large/long dashboard report data | same as run, plus optional `--artifact-format jsonl` | Async artifact descriptor |
+| `query cancel` | `analysis.query.cancel` | Cancel gateway run/export | `--run-id`, optional `--reason` | Cancellation result |
+| `dashboard-definition export` | `analysis.dashboard_definition.export` | Export dashboard definition JSON | `--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 | `--dashboard-id`, optional config flags or `--payload` | Config result |
+| `dashboard-daily-report send` | `analysis.dashboard_daily_report.send` | Send daily report immediately | `--dashboard-id`, optional `--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 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-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 | `--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 |
+| `public-link list` | `analysis.public_link.list` | List public links | `--project-id`, optional list filters | Paginated links |
+| `public-link update` | `analysis.public_link.update` | Edit public link | `--link-id`, `--effective-at`, `--expires-at` | Update result |
+| `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 |
+
+## Examples
+
+```bash
+ae-cli analysis dashboard list --project-id 1 --query retention --limit 20
+ae-cli analysis dashboard update --project-id 1 --operation note-upsert --dashboard-id 1001 --note-title "Summary" --description "Weekly note" --yes
+ae-cli analysis dashboard-definition import --project-id 1 --definition '{"dashboard_folders":[],"shared_spaces":[]}' --validate-only true
+ae-cli analysis public-link create --project-id 1 --resource-type dashboard --resource-id 1001 --effective-at "2026-07-08 00:00:00" --expires-at "2026-08-08 00:00:00" --yes
+```

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

@@ -0,0 +1,15 @@
+# analysis bi-panel copy
+
+Use when the user wants to copy a BI panel, optionally targeting a project space or folder.
+
+Do not use to create a blank BI panel. Use `bi-panel create`.
+
+Command:
+
+```bash
+ae-cli analysis bi-panel copy --project-id <project_id> [--panel-name <name>] [--panel-uuid <source_uuid>] [--space-id <space_id>] [--folder-id <folder_id>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, optional source/target fields, and `payload`.
+
+Output is the gateway envelope. `data` contains the copied BI panel result.

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

@@ -0,0 +1,15 @@
+# analysis bi-panel create
+
+Use when the user explicitly wants to create a BI panel.
+
+Do not use to copy an existing BI panel. Use `bi-panel copy`.
+
+Command:
+
+```bash
+ae-cli analysis bi-panel create --project-id <project_id> [--panel-name <name>] [--panel-uuid <uuid>] [--space-id <space_id>] [--folder-id <folder_id>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id` plus optional BI panel identifiers, target IDs, and `payload`.
+
+Output is the gateway envelope. `data` contains the created BI panel result.

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

@@ -0,0 +1,15 @@
+# analysis bi-panel delete
+
+Use when the user explicitly wants to delete one or more BI panels.
+
+Do not use for dashboards. Use `dashboard delete`.
+
+Command:
+
+```bash
+ae-cli analysis bi-panel delete --project-id <project_id> --panel-ids '[2001,2002]' --yes
+```
+
+Input sends `project_id` and `panel_ids`.
+
+Output is the gateway envelope. `data` contains the delete result.

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

@@ -0,0 +1,18 @@
+# analysis bi-panel get
+
+Use when the user needs one BI panel's released page structure.
+
+Do not use to query chart data. Use `bi-panel-page-data run` or `bi-panel-page-data export`.
+
+Command:
+
+```bash
+ae-cli analysis bi-panel get --project-id <project_id> --panel-id <panel_id> [--fields '["pages"]']
+```
+
+Input sends `project_id`, `panel_id`, and optional `fields`.
+
+Supported fields are `basic`, `pages`, `charts`, `chartFilterControls`, `summary`,
+`parameterControls`, and `permissionControls`.
+
+Output is the gateway envelope. `data` contains the BI panel structure.

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

@@ -0,0 +1,15 @@
+# analysis bi-panel list
+
+Use when the user needs to find BI panels they can access.
+
+Do not use for dashboard assets. Use `dashboard list`.
+
+Command:
+
+```bash
+ae-cli analysis bi-panel list --project-id <project_id> [--query <keyword>] [--fields '["id","name"]'] [--limit 20] [--offset 0]
+```
+
+Input sends `project_id` and optional `query`, `fields`, `limit`, `offset`.
+
+Output is the gateway envelope. `data` contains BI panel summaries and paging metadata when returned.

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

@@ -0,0 +1,15 @@
+# analysis bi-panel-page-data export
+
+Use for BI panel page data that may be large or long-running.
+
+Do not use for tiny previews. Use `bi-panel-page-data run` with a small limit.
+
+Command:
+
+```bash
+ae-cli analysis bi-panel-page-data export --project-id <project_id> --panel-id <panel_id> --page-key <page_key> --result-type charts [--chart-ids '["chart1"]'] [--artifact-format jsonl]
+```
+
+Input sends `project_id`, `panel_id`, `page_key`, `result_type`, and optional control, paging, cache, request, timeout, and format fields. Use CLI flag `--artifact-format` for the gateway `format` input; `--format` is the CLI output formatter.
+
+Output is the gateway envelope. `data` contains an async export descriptor such as `run_id`, `artifact_id`, status fields, inspect path, and download path.

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

@@ -0,0 +1,15 @@
+# analysis bi-panel-page-data run
+
+Use for bounded inline BI panel page chart or summary data.
+
+Do not use for large or long-running page data. Use `bi-panel-page-data export`.
+
+Command:
+
+```bash
+ae-cli analysis bi-panel-page-data run --project-id <project_id> --panel-id <panel_id> --page-key <page_key> --result-type charts [--chart-ids '["chart1"]'] [--limit 100] [--timeout-seconds 60]
+```
+
+Input sends `project_id`, `panel_id`, `page_key`, `result_type`, and optional control, paging, cache, request, timeout, and limit fields.
+
+Output is the gateway envelope. `data` contains bounded inline page data.

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

@@ -0,0 +1,15 @@
+# analysis bi-panel share
+
+Use when the user wants to modify BI panel sharing members.
+
+Do not use to share dashboards or folders. Use the matching resource share command.
+
+Command:
+
+```bash
+ae-cli analysis bi-panel share --project-id <project_id> --panel-id <panel_id> [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, `panel_id`, and backend-compatible snake_case `payload`.
+
+Output is the gateway envelope. `data` contains the share update result.

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

@@ -0,0 +1,15 @@
+# analysis bi-panel update
+
+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.
+
+Command:
+
+```bash
+ae-cli analysis bi-panel update --project-id <project_id> [--panel-name <name>] [--panel-uuid <uuid>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, optional `panel_name`, `panel_uuid`, and `payload`.
+
+Output is the gateway envelope. `data` contains the update result.

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

@@ -0,0 +1,15 @@
+# analysis dashboard abnormal-get
+
+Use when the user needs abnormal dependency or import/export diagnostic information for one dashboard.
+
+Do not use for normal dashboard detail. Use `dashboard get`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard abnormal-get --project-id <project_id> --dashboard-id <dashboard_id>
+```
+
+Input sends `project_id` and `dashboard_id`.
+
+Output is the gateway envelope. `data` contains abnormal dependency information.

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

@@ -0,0 +1,15 @@
+# analysis dashboard copy
+
+Use when the user wants to copy a dashboard, optionally copying reports and targeting a project space or folder.
+
+Do not use to create a blank dashboard. Use `dashboard create`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard copy --project-id <project_id> --dashboard-id <source_dashboard_id> --dashboard-name <new_name> [--report-copy true] [--to-space-id <space_id>] [--to-folder-id <folder_id>] --yes
+```
+
+Input sends `project_id`, `dashboard_id`, `dashboard_name`, and optional `report_copy`, `to_space_id`, `to_folder_id`.
+
+Output is the gateway envelope. `data` contains the copied dashboard result.

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

@@ -0,0 +1,15 @@
+# analysis dashboard create
+
+Use when the user explicitly wants to create a dashboard in personal space, a project space, or a folder.
+
+Do not use to copy an existing dashboard. Use `dashboard copy` for copy workflows.
+
+Command:
+
+```bash
+ae-cli analysis dashboard create --project-id <project_id> --dashboard-name <name> [--space-id <space_id>] [--folder-id <folder_id>] [--initial-report-id <report_id>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, `dashboard_name`, and optional `space_id`, `folder_id`, `initial_report_id`, `payload`.
+
+Output is the gateway envelope. `data` contains the created dashboard identity or backend create result.

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

@@ -0,0 +1,15 @@
+# analysis dashboard-daily-report send
+
+Use when the user wants to send a dashboard daily report immediately.
+
+Do not use for configuration changes. Use `dashboard-daily-report update`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard-daily-report send --project-id <project_id> --dashboard-id <dashboard_id> [--need-csv 1] [--host-url <url>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, `dashboard_id`, and optional `need_csv`, `host_url`, `payload`.
+
+Output is the gateway envelope. `data` contains the immediate send result.

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

@@ -0,0 +1,15 @@
+# analysis dashboard-daily-report update
+
+Use when the user wants to update a dashboard daily report configuration.
+
+Do not use to send immediately. Use `dashboard-daily-report send`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard-daily-report update --project-id <project_id> --dashboard-id <dashboard_id> [--enable-send 1] [--send-time <time>] [--send-title <title>] [--send-content <content>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, `dashboard_id`, and optional daily report fields or `payload`.
+
+Output is the gateway envelope. `data` contains the daily report configuration update result.

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

@@ -0,0 +1,15 @@
+# analysis dashboard-definition export
+
+Use when the user wants to export dashboard definition JSON for selected dashboard folders or shared spaces.
+
+Do not use for dashboard report result data. Use `dashboard-report-data run` or `dashboard-report-data export`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard-definition export --project-id <project_id> [--dashboard-folder-ids '[...]'] [--shared-spaces '[...]'] [--export-file-name <name>] [--payload '{...}']
+```
+
+Input sends `project_id` and optional `dashboard_folder_ids`, `shared_spaces`, `export_file_name`, `payload`.
+
+Output is the gateway envelope. `data` contains exported definition data or an export descriptor.

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

@@ -0,0 +1,15 @@
+# analysis dashboard-definition import
+
+Use when the user wants to validate or import dashboard definition JSON. Use `--validate-only true` for pre-checks such as name conflict, reference relation, and importable state.
+
+Do not use a separate pre-check command; validation is part of this import command.
+
+Command:
+
+```bash
+ae-cli analysis dashboard-definition import --project-id <project_id> --definition '{...}' [--validate-only true] [--dashboard-name-conflict-policy <policy>] [--space-dashboard-policy <policy>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, `definition`, and optional validation/import policies and `payload`.
+
+Output is the gateway envelope. `data` contains validation findings or import result.

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

@@ -0,0 +1,15 @@
+# analysis dashboard delete
+
+Use when the user explicitly wants to delete one or more dashboards.
+
+Do not use for soft archival or hiding unless the gateway contract defines that behavior.
+
+Command:
+
+```bash
+ae-cli analysis dashboard delete --project-id <project_id> --dashboard-ids '[1001,1002]' --yes
+```
+
+Input sends `project_id` and `dashboard_ids`.
+
+Output is the gateway envelope. `data` contains the delete result.

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

@@ -0,0 +1,15 @@
+# analysis dashboard freeze
+
+Use when the user wants to freeze or unfreeze one or more dashboards.
+
+Do not use for dashboard lock/version operations; those are intentionally not CLI-enabled.
+
+Command:
+
+```bash
+ae-cli analysis dashboard freeze --project-id <project_id> --dashboard-ids '[1001,1002]' [--freeze true] --yes
+```
+
+Input sends `project_id`, `dashboard_ids`, and optional `freeze`.
+
+Output is the gateway envelope. `data` contains the freeze or unfreeze result.

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

@@ -0,0 +1,15 @@
+# analysis dashboard get
+
+Use when the user needs one dashboard detail, including basic metadata such as creator and create/update time, settings, reports, notes, and sharing information.
+
+Do not use to query report result data. Use `dashboard-report-data run` or `dashboard-report-data export`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard get --project-id <project_id> --dashboard-id <dashboard_id> [--use-cache true]
+```
+
+Input sends `project_id`, `dashboard_id`, and optional `use_cache`.
+
+Output is the gateway envelope. `data` contains the dashboard detail returned by the capability gateway.

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

@@ -0,0 +1,15 @@
+# analysis dashboard handover
+
+Use when the user explicitly wants to transfer one or more dashboards to another project user.
+
+Do not use to share dashboards without ownership transfer. Use `dashboard share`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard handover --project-id <project_id> --dashboard-ids '[1001,1002]' --to-user-id <user_id> --yes
+```
+
+Input sends `project_id`, `dashboard_ids`, and `to_user_id`.
+
+Output is the gateway envelope. `data` contains the handover result.

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

@@ -0,0 +1,15 @@
+# analysis dashboard list
+
+Use when the user needs to find dashboards they can access, with optional keyword, owner, permission, favorite, or projection filters supported by the gateway payload.
+
+Do not use for dashboard report data. Use `dashboard-report-data run` or `dashboard-report-data export` instead.
+
+Command:
+
+```bash
+ae-cli analysis dashboard list --project-id <project_id> [--query <keyword>] [--fields '["id","name"]'] [--limit 20] [--offset 0]
+```
+
+Input uses `project_id` plus optional `query`, `fields`, `limit`, `offset`. Use `--payload` only when the dedicated gateway contract requires extra snake_case filters.
+
+Output is the gateway envelope. `data` contains dashboard summaries and paging metadata when returned by the gateway.

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

@@ -0,0 +1,15 @@
+# analysis dashboard-report-data export
+
+Use for dashboard report data queries that may be large or long-running.
+
+Do not use when the user needs a tiny immediate preview. Use `dashboard-report-data run` with a small `--limit`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard-report-data export --project-id <project_id> --dashboard-id <dashboard_id> [--report-ids '[1,2]'] [--filters '{...}'] [--start-time <time>] [--end-time <time>] [--artifact-format jsonl]
+```
+
+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.
+
+Output is the gateway envelope. `data` contains an async export descriptor such as `run_id`, `artifact_id`, status fields, inspect path, and download path.

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

@@ -0,0 +1,15 @@
+# analysis dashboard-report-data run
+
+Use for bounded inline dashboard report data queries when the expected result is small enough for immediate JSON output.
+
+Do not use for large or long-running result sets. Use `dashboard-report-data export`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard-report-data run --project-id <project_id> --dashboard-id <dashboard_id> [--report-ids '[1,2]'] [--filters '{...}'] [--start-time <time>] [--end-time <time>] [--limit 100] [--timeout-seconds 60]
+```
+
+Input sends `project_id`, `dashboard_id`, and optional `report_ids`, `filters`, `start_time`, `end_time`, `use_cache`, `request_id`, `timeout_seconds`, `limit`.
+
+Output is the gateway envelope. `data` contains bounded inline report data.