@thinkingai/ae-cli 6.0.33 → 6.0.34

package/skills/ae-engage/references/channel-update-config.md

@@ -32,5 +32,5 @@ ae-cli engage-setting channel update-config \
 ## Decision Rules
 
 - Use this command when the user asks to edit/update an existing channel's name, config, push-id type, or reach-funnel settings.
-- `--config` is the channel-specific JSON config; discover the existing config with `ae-cli engage +channel_detail` first rather than inventing it.
+- `--config` is the channel-specific JSON config; discover the existing config with `ae-cli engage-setting channel get` first rather than inventing it.
 - Risk is `write`; ordinary update, no confirmation gate.

package/skills/ae-engage/references/channel_touch_limits_list.md

@@ -25,5 +25,5 @@ ae-cli engage-setting channel-touch-limits list --project-id <project_id> --dry-
 ## Decision Rules
 
 - Use this command when the user asks for project channel touch-limit, delivery-cap, or fatigue-control rules.
-- Use `+channel_list` to list channels and `+channel_detail` to inspect one channel; neither returns the project touch-limit rule list.
+- Use `engage-setting channel list` to list channels and `engage-setting channel get` to inspect one channel; neither returns the project touch-limit rule list.
 - If `items` is empty, do not invent rule IDs or channel IDs; report that no touch-limit rules were returned for the project.

package/skills/ae-engage/references/client-param.md

@@ -1,37 +1,53 @@
 # engage-setting client-param
 
-> Capability ids: `engage-setting.client-param.{update,delete,list}` · Domain: `engage`. (`create` temporarily disabled in CLI.)
+> Capability ids: `engage-setting.client-param.{create,update,delete,list}` · Domain: `engage`.
+
+Manage custom client params. `select_type` is derived server-side from `column_type`. `column_type` / `select_type` are immutable after create.
 
 ## Commands
 
 ```bash
-# Update a custom client param
+# Create a custom client param
+ae-cli engage-setting client-param create \
+  --project-id <project_id> --column-name <name> --column-type varchar \
+  [--column-desc <desc>] [--column-remark <remark>] [--alternative-val '["a","b"]']
+
+# Update display metadata (type is immutable)
 ae-cli engage-setting client-param update \
-  --project-id <project_id> --column-name <name> --column-type <type> --select-type <select> \
-  [--column-desc <desc>]
+  --project-id <project_id> --column-name <name> \
+  [--column-desc <desc>] [--column-remark <remark>] [--alternative-val '["a","b"]']
 
 # Delete a custom client param (high-risk)
 ae-cli engage-setting client-param delete --project-id <project_id> --column-name <name> --yes
 
-# List custom client params
+# List client params (custom + preset)
 ae-cli engage-setting client-param list --project-id <project_id>
 ```
 
 ## Parameters
 
+### create
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+| `--column-name` | Yes | Must match `^[A-Za-z][A-Za-z0-9_]*$`, max 80. |
+| `--column-type` | Yes | `varchar` \| `bigint` \| `double` \| `boolean`. `timestamp` is not supported. `select_type` is derived server-side (`varchar→string`, `bigint/double→number`, `boolean→bool`). |
+| `--column-desc` | No | Display name. Defaults to an empty string. |
+| `--column-remark` | No | Description/remark. |
+| `--alternative-val` | No | JSON array of alternative values. Only allowed when `--column-type` is `varchar`. |
+
 ### update
 
 | Parameter | Required | Description |
 |---|---|---|
 | `--project-id` / `-p` | Yes | Numeric project ID. |
-| `--column-name` | Yes | Client param column name. |
-| `--column-type` | Yes | Column type (see ColumnTypeEnum). |
-| `--select-type` | Yes | Select type (see SelectTypeEnum). |
-| `--column-source` | No | Param source: preset or custom. |
-| `--column-desc` | No | Display name of the param. Defaults to an empty string. |
-| `--column-remark` | No | Description/remark for the param. |
-| `--alternative-val` | No | JSON array of alternative values. |
-| `--system-id-param` | No | Whether this is a system identifier param. |
+| `--column-name` | Yes | Existing custom client param name. |
+| `--column-desc` | No | Display name. Omit to keep existing. |
+| `--column-remark` | No | Description/remark. Omit to keep existing. |
+| `--alternative-val` | No | JSON array of alternative values. Only allowed when existing `column_type` is `varchar`. Omit to keep existing. |
+
+Do **not** pass `--column-type` / `--select-type` on update — they are rejected and cannot be changed.
 
 ### delete
 
@@ -48,11 +64,13 @@ ae-cli engage-setting client-param list --project-id <project_id>
 
 ## Output
 
-- `update`: `data.success` — whether the operation succeeded.
+- `create` / `update`: `data.success`.
 - `delete`: `data.success` and `data.task_list` (tasks still referencing the param, which block deletion; each item has `task_id`, `task_name`).
 - `list`: `data.items` (each with `column_name`, `column_type`, `select_type`, `column_source`, `column_desc`, `column_remark`, `alternative_val`, `system_id_param`) and `data.total`.
 
 ## Decision Rules
 
-- Use these commands when the user asks to manage custom client params (客户端参数).
-- `delete` is `high-risk-write` and requires `--yes` (or interactive confirmation). When `data.success` is false, `data.task_list` lists tasks that still reference the param — report them instead of forcing deletion.
+- Prefer `list` first to avoid duplicate `column_name` and to confirm existing type before update.
+- Use only the four allowed `column_type` values; never invent types like `string` / `single`.
+- After create, re-`list` to verify the stored row.
+- `delete` is `high-risk-write` and requires `--yes`. When `data.success` is false, report `data.task_list` instead of forcing deletion.

package/skills/ae-engage/references/common-metric.md

@@ -1,6 +1,7 @@
 # engage-setting common-metric
 
-> Capability ids: `engage-setting.common-metric.{list,get,update,delete}` · Domain: `engage`. (`create` temporarily disabled in CLI.)
+> Capability ids: `engage-setting.common-metric.{list,get,create,update,delete}` · Domain: `engage`.
+> Auth: read uses `opsViewSetting` (list also allows `opsViewOperationTask`); write/delete use `opsEditSetting`.
 
 ## Commands
 
@@ -11,10 +12,15 @@ ae-cli engage-setting common-metric list --project-id <project_id>
 # Get a common metric detail
 ae-cli engage-setting common-metric get --project-id <project_id> --metric-name <name>
 
+# Create a PRESET common metric (metric-type must be 1)
+ae-cli engage-setting common-metric create \
+  --project-id <project_id> --metric-type 1 --metric-name <name> --metric-qp '<qp_json>' \
+  --metric-window-num 1 --metric-window-time-unit day --display-name <display>
+
 # Update a common metric
 ae-cli engage-setting common-metric update \
-  --project-id <project_id> --metric-type <type> --metric-name <name> --metric-qp <qp> \
-  --metric-window-num <num> --metric-window-time-unit DAY --display-name <display>
+  --project-id <project_id> --metric-type 1 --metric-name <name> --metric-qp '<qp_json>' \
+  --metric-window-num <num> --metric-window-time-unit day --display-name <display>
 
 # Delete a common metric (high-risk)
 ae-cli engage-setting common-metric delete --project-id <project_id> --metric-name <name> --yes
@@ -35,27 +41,85 @@ ae-cli engage-setting common-metric delete --project-id <project_id> --metric-na
 | `--project-id` / `-p` | Yes | Numeric project ID. |
 | `--metric-name` | Yes | Metric name. |
 
-### update
+### create / update
 
 | Parameter | Required | Description |
 |---|---|---|
 | `--project-id` / `-p` | Yes | Numeric project ID. |
-| `--metric-type` | Yes | Metric type (see MetricTypeEunm). |
-| `--metric-name` | Yes | Metric name. |
-| `--metric-qp` | Yes | Metric qp (event/property expression). |
-| `--metric-window-num` | Yes | Metric window number. |
-| `--metric-window-time-unit` | Yes | Metric window time unit (MINUTE/HOUR/DAY). |
-| `--display-name` | Yes | Display name of the metric. |
-| `--note` | No | Metric note/remark. |
-| `--order-id` | No | Sort order id. |
-| `--metric-setting-id` | No | Metric setting id (when binding to a setting). |
-| `--metric-params` | No | Metric params JSON string. |
+| `--metric-type` | Yes | `1` = PRESET (common metric). **create requires `1`**. Do not use `2` (CUSTOM / task-side). |
+| `--metric-name` | Yes | Technical name; prefer `^[a-z][0-9a-z_]{0,79}$`. |
+| `--metric-qp` | Yes | Complete metric QP **JSON object string** (`type=0` event or `type=1` formula). |
+| `--metric-window-num` | Yes | Window size (integer ≥ 1). |
+| `--metric-window-time-unit` | Yes | `minute` / `hour` / `day` (lowercase). |
+| `--display-name` | Yes | Display name. |
+| `--note` | No | Remark. |
+| `--order-id` | No | Sort order (usually omit on setting-page create). |
+| `--metric-setting-id` | No | Binding id (task/config metricMap; usually omit on setting-page create). |
+| `--metric-params` | No | Params JSON string; for formula metrics often `{"format":"float"}`. |
 
 ## Output
 
 - `list`: `data.items` (each with `project_id`, `metric_type`, `metric_name`, `metric_qp`, `metric_window_num`, `metric_window_time_unit`, `note`, `last_editer`, `last_update_time`, `order_id`, `display_name`, `metric_setting_id`, `metric_params`) and `data.total`.
 - `get`: `data.metric` — a single metric object with the same fields, or `null`.
-- `update` / `delete`: `data.success`.
+- `create` / `update` / `delete`: `data.success`.
+
+## Agent workflow (Pattern A: discover → match → assemble QP → write)
+
+Unlike the Engage console (user picks events in a picker), Agents must discover real project metadata first. Never invent `event_name` / property names / `--metric-qp` placeholders such as `event`.
+
+```bash
+# 1) Discover candidate events (keyword: payment / recharge / purchase / ...)
+ae-cli analysis-meta event list --project-id <project_id> --query <keyword> \
+  --fields '["event_name","event_desc","authentication_status"]' --limit 20
+
+# Optional soft hint: project recharge-success event name
+ae-cli engage-setting preset-event list --project-id <project_id>
+# → data.recharge_event_desc may contain eventName (not a ready metric_qp)
+
+# 2) If filters are needed, list properties for the matched event
+ae-cli analysis-meta property list --project-id <project_id> \
+  --scope event --event-name <matched_event_name>
+
+# 3) Assemble a type=0 metric QP object from the matched event, then create
+ae-cli engage-setting common-metric create --project-id <project_id> \
+  --metric-type 1 --metric-name <name> --metric-qp '<qp_json>' \
+  --metric-window-num 1 --metric-window-time-unit day --display-name <display>
+```
+
+If multiple events remain plausible after discovery, stop and ask the user which `event_name` to use.
+
+## `--metric-qp` example (type=0 event analysis)
+
+Pass as a single JSON **object string**. Minimal shape aligned with the Engage setting-page event metric:
+
+```json
+{
+  "type": 0,
+  "eventName": "purchase",
+  "eventDesc": "Purchase",
+  "eventType": "event",
+  "analysis": "A100",
+  "analysisDesc": "Total count",
+  "analysisParams": "",
+  "quota": "",
+  "quotaDesc": "",
+  "filts": [],
+  "relation": 1,
+  "customEvent": "",
+  "customFilters": [],
+  "eventNameDisplay": "Purchase total count",
+  "subTableType": "",
+  "taPropQuota": {
+    "analysis": "A100",
+    "analysisDesc": "Total count",
+    "analysisParams": "",
+    "quota": "",
+    "quotaDesc": ""
+  }
+}
+```
+
+CLI rejects non-JSON, non-object, and `{}` values before the request is sent.
 
 ## Preflight for config-metric batch-add
 
@@ -65,11 +129,14 @@ ae-cli engage-setting common-metric delete --project-id <project_id> --metric-na
 ae-cli engage-setting common-metric list --project-id <project_id>
 ```
 
-If `items` is empty, common metrics must be created in the Engage console before binding them to a config item, or treat the case as environment-blocked.
+If `items` is empty, create PRESET metrics with `common-metric create` (Pattern A above) or treat the case as environment-blocked.
 
 ## Decision Rules
 
-- Use these commands when the user asks to manage common metrics (常用指标) for the analysis workbench.
+- Use these commands when the user asks to manage common metrics for the analysis workbench.
 - Discover existing metric names with `common-metric list` first; never invent names for `get`/`update`/`delete`.
-- `--metric-qp` must be a complete metric QP expression; do not pass `{}` as a placeholder.
+- For create/update, discover events/properties via `ae-analysis` (`analysis-meta event list` / `property list`) before assembling `--metric-qp`.
+- `--metric-type` for setting-page common metrics is always `1` (PRESET). create rejects any other value.
+- `--metric-window-time-unit` must be lowercase `minute` / `hour` / `day` (not `DAY`).
+- `--metric-qp` must be a complete metric QP JSON object; do not pass `{}` or placeholder strings.
 - `delete` is `high-risk-write` and requires `--yes` (or interactive confirmation).

package/skills/ae-engage/references/config-item-analysis-report.md

@@ -1,33 +1,14 @@
-# ae-engage +config_item_analysis_report
+# engage-scene.report.config-item-analysis
 
+Query config item analysis results through the L3 Capability Gateway.
 
-Query the config item analysis report.
+Mapped command: `ae-cli capability run engage-scene.report.config-item-analysis --input '<json>'`
 
-Mapped command: `ae-cli engage +config_item_analysis_report`
-
-## Flags
-
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--config_id` | string | Yes | config item ID |
-| `--start_time` | string | Yes | Start date |
-| `--end_time` | string | Yes | End date |
-| `--request_id` | string | No | Query requestId |
-| `--template_id_list` | json | No | template ID JSON array |
-| `--strategy_id_list` | json | No | strategy ID JSON array |
-| `--show_time_zone` | number | No | display timezone offset |
-
-## Parameter Constraints
-
-- `--template_id_list` and `--strategy_id_list` cannot be used together.
-- If neither is provided, query config-item-level data.
-- `--start_time`、`--end_time` use `yyyy-MM-dd`.
-
-## Examples
+Required input: `project_id`, `config_id`, `start_time`, `end_time`. Optional input: `request_id`,
+`template_id_list`, `strategy_id_list`, `show_time_zone`. `template_id_list` and `strategy_id_list`
+are mutually exclusive.
 
 ```bash
-ae-cli engage +config_item_analysis_report \
-  --project_id 1 --config_id cfg_123 \
-  --start_time 2026-04-01 --end_time 2026-04-07
+ae-cli capability run engage-scene.report.config-item-analysis \
+  --input '{"project_id":1,"config_id":"cfg_123","start_time":"2026-04-01","end_time":"2026-04-07"}'
 ```

package/skills/ae-engage/references/config-item-strategy-comparison.md

@@ -1,24 +1,13 @@
-# ae-engage +config_item_strategy_comparison
+# engage-scene.report.strategy-comparison
 
+Compare config strategy results through the L3 Capability Gateway.
 
-Compare multiple strategies under the same config item.
+Mapped command: `ae-cli capability run engage-scene.report.strategy-comparison --input '<json>'`
 
-Mapped command: `ae-cli engage +config_item_strategy_comparison`
-
-## Flags
-
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--config_id` | string | Yes | config item ID |
-| `--strategy_id_list` | json | Yes | strategy ID JSON array with at least two entries |
-| `--request_id` | string | No | query requestId |
-| `--show_time_zone` | number | No | display timezone offset |
-
-## Examples
+Required input: `project_id`, `config_id`, `strategy_id_list` with at least two IDs. Optional input:
+`request_id`, `show_time_zone`.
 
 ```bash
-ae-cli engage +config_item_strategy_comparison \
-  --project_id 1 --config_id cfg_123 \
-  --strategy_id_list '["strategy_a","strategy_b"]'
+ae-cli capability run engage-scene.report.strategy-comparison \
+  --input '{"project_id":1,"config_id":"cfg_123","strategy_id_list":["strategy_a","strategy_b"]}'
 ```

package/skills/ae-engage/references/config-item-trigger-report.md

@@ -1,41 +1,14 @@
-# ae-engage +config_item_trigger_report
+# engage-scene.report.config-item-trigger
 
+Query config item publish and trigger trends through the L3 Capability Gateway.
 
-Query the publish and trigger trend report for a config item.
+Mapped command: `ae-cli capability run engage-scene.report.config-item-trigger --input '<json>'`
 
-Mapped command: `ae-cli engage +config_item_trigger_report`
-
-## Flags
-
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--config_id` | string | Yes | config item ID |
-| `--start_time` | string | Yes | Start date |
-| `--end_time` | string | Yes | End date |
-| `--request_id` | string | No | query requestId |
-| `--template_id_list` | json | No | template ID JSON array |
-| `--strategy_id_list` | json | No | strategy ID JSON array |
-| `--show_time_zone` | number | No | display timezone offset |
-| `--analyze_report_internal_query` | boolean | No | internal analysis switch |
-
-## Enum Notes
-
-### `--analyze_report_internal_query`
-
-- `true`: use the internal analysis-report query path
-- `false`: use the default query path
-
-## Parameter Constraints
-
-- `--template_id_list` and `--strategy_id_list` cannot be used together.
-- If neither is provided, query config-item-level data.
-- `--start_time`、`--end_time` use `yyyy-MM-dd`.
-
-## Examples
+Required input: `project_id`, `config_id`, `start_time`, `end_time`. Optional input: `request_id`,
+`template_id_list`, `strategy_id_list`, `show_time_zone`, `analyze_report_internal_query`.
+`template_id_list` and `strategy_id_list` are mutually exclusive.
 
 ```bash
-ae-cli engage +config_item_trigger_report \
-  --project_id 1 --config_id cfg_123 \
-  --start_time 2026-04-01 --end_time 2026-04-07
+ae-cli capability run engage-scene.report.config-item-trigger \
+  --input '{"project_id":1,"config_id":"cfg_123","start_time":"2026-04-01","end_time":"2026-04-07"}'
 ```

package/skills/ae-engage/references/delete-channel.md

@@ -1,16 +1,16 @@
-# ae-engage +delete_channel
+# ae-engage engage-setting channel delete
 
 
 Delete an Engage channel.
 
-Mapped command: `ae-cli engage +delete_channel`
+Mapped command: `ae-cli engage-setting channel delete`
 
 ## Flags
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--channel_id` | string | Yes | channel ID |
+| `--project-id` / `-p` | number | Yes | Project ID |
+| `--channel-id` | string | Yes | channel ID |
 
 ## Safety Constraints
 
@@ -19,5 +19,5 @@ This command is a **write operation** and Before executing, confirm that this ch
 ## Examples
 
 ```bash
-ae-cli engage +delete_channel --project_id 1 --channel_id <channel_id>
+ae-cli engage-setting channel delete --project-id 1 --channel-id <channel_id>
 ```

package/skills/ae-engage/references/delete-flow.md

@@ -1,16 +1,16 @@
-# ae-engage +delete_flow
+# ae-cli engage-flow flow delete
 
 
 Batch delete flows.
 
-Mapped command: `ae-cli engage +delete_flow`
+Mapped command: `ae-cli engage-flow flow delete`
 
 ## Flags
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--flow_uuid_list` | json | Yes | Flow UUID JSON array |
+| `--project-id` / `-p` | number | Yes | Project ID |
+| `--flow-uuid-list` | json | Yes | Flow UUID JSON array |
 
 ## Safety Constraints
 
@@ -19,5 +19,5 @@ This command is a **write operation** and and deletes flows.
 ## Examples
 
 ```bash
-ae-cli engage +delete_flow --project_id 1 --flow_uuid_list '["flow_uuid_1"]'
+ae-cli engage-flow flow delete --project-id 1 --flow-uuid-list '["flow_uuid_1"]'
 ```

package/skills/ae-engage/references/flow-ab-split-node-report.md

@@ -1,53 +1,19 @@
-# ae-engage +flow_ab_split_node_report
+# engage-flow.report.ab-split-node
 
+Query an AB split node report through the L3 Capability Gateway.
 
-Query the AB split node report.
+Mapped command: `ae-cli capability run engage-flow.report.ab-split-node --input '<json>'`
 
-Mapped command: `ae-cli engage +flow_ab_split_node_report`
+## Input
 
-## Flags
+- Required: `project_id`, `report_type`, `node_uuid`, `start_time`, `end_time`.
+- Provide at least one of `flow_id` or `flow_uuid`.
+- `report_type` is `overview` or `detail`.
+- Optional: `request_id`, `push_language_code`, `indicators_uuid`, `show_time_zone`.
 
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--report_type` | string | Yes | report type: `overview` or `detail` |
-| `--node_uuid` | string | Yes | AB node UUID |
-| `--start_time` | string | Yes | Start date |
-| `--end_time` | string | Yes | End date |
-| `--flow_id` | string | No | Flow ID |
-| `--flow_uuid` | string | No | Flow UUID |
-| `--request_id` | string | No | Query requestId |
-| `--push_language_code` | string | No | push language code |
-| `--indicators_uuid` | string | No | indicator UUID |
-| `--show_time_zone` | string | No | display timezone offset |
-
-## Enum Notes
-
-### `--report_type`
-
-- `overview`: AB split node overview report
-- `detail`: AB split node detail report
-
-### `--push_language_code`
-
-Common values include:
-
-- `default`
-- `en`
-- `zh-Hans`
-- `zh-Hant`
-- `ja`
-- `ko`
-
-## Parameter Constraints
-
-- `--flow_id` At least one of `--flow_id` and `--flow_uuid` must be provided.
-- `--start_time`、`--end_time` use `yyyy-MM-dd`.
-
-## Examples
+## Example
 
 ```bash
-ae-cli engage +flow_ab_split_node_report \
-  --project_id 1 --flow_uuid flow_uuid_123 --node_uuid node_123 \
-  --report_type overview --start_time 2026-04-01 --end_time 2026-04-07
+ae-cli capability run engage-flow.report.ab-split-node --input \
+  '{"project_id":1,"flow_uuid":"flow_uuid_123","node_uuid":"node_123","report_type":"overview","start_time":"2026-04-01","end_time":"2026-04-07"}'
 ```

package/skills/ae-engage/references/flow-detail.md

@@ -1,20 +1,25 @@
-# ae-engage +flow_detail
+# ae-cli engage-flow flow get
 
 
 Query flow details.
 
-Mapped command: `ae-cli engage +flow_detail`
+Mapped command: `ae-cli engage-flow flow get`
+
+## Response shape
+
+The flow detail is under `data.flow`. Every response key is snake_case, for example
+`data.flow.mapping_status`, `data.flow.version_type`, and `data.flow.node_list[].type`.
 
 ## Flags
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--flow_uuid` | string | Yes | Flow UUID |
+| `--project-id` / `-p` | number | Yes | Project ID |
+| `--flow-uuid` | string | Yes | Flow UUID |
 
 ## Common enums in the response
 
-### `status`
+### `data.flow.status`
 
 - `0`: `DRAFT`
 - `1`: `WAITING`
@@ -22,7 +27,7 @@ Mapped command: `ae-cli engage +flow_detail`
 - `3`: `PENDING`
 - `4`: `COMPLETE`
 
-### `mappingStatus`
+### `data.flow.mapping_status`
 
 - `0`: `DRAFT`
 - `1`: `APPROVE`
@@ -34,7 +39,7 @@ Mapped command: `ae-cli engage +flow_detail`
 - `7`: `PENDING`
 - `8`: `COMPLETE`
 
-### `versionType`
+### `data.flow.version_type`
 
 - `0`: history version
 - `1`: current version
@@ -42,13 +47,13 @@ Mapped command: `ae-cli engage +flow_detail`
 - `3`: new version
 - `4`: test version
 
-### `entryTriggerType`
+### `data.flow.entry_trigger_type`
 
 - `0`: scheduled single trigger
 - `1`: scheduled recurring trigger
 - `2`: event trigger
 
-### `nodeList[].type`
+### `data.flow.node_list[].type`
 
 Common node types include:
 
@@ -74,5 +79,5 @@ Common node types include:
 ## Examples
 
 ```bash
-ae-cli engage +flow_detail --project_id 1 --flow_uuid flow_uuid_123
+ae-cli engage-flow flow get --project-id 1 --flow-uuid flow_uuid_123
 ```

package/skills/ae-engage/references/flow-list.md

@@ -1,18 +1,23 @@
-# ae-engage +flow_list
+# ae-cli engage-flow flow list
 
 
 Query the flow list.
 
-Mapped command: `ae-cli engage +flow_list`
+Mapped command: `ae-cli engage-flow flow list`
+
+## Response shape
+
+The result is `{ data: { items, total } }`. Each item recursively uses snake_case fields,
+for example `data.items[].flow_id`, `data.items[].flow_uuid`, and `data.items[].mapping_status`.
 
 ## Flags
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
+| `--project-id` / `-p` | number | Yes | Project ID |
 
 ## Examples
 
 ```bash
-ae-cli engage +flow_list --project_id 1
+ae-cli engage-flow flow list --project-id 1
 ```

package/skills/ae-engage/references/flow-node-config-schema.md

@@ -1,15 +1,16 @@
-# ae-engage +flow_node_config_schema
+# ae-cli engage-flow node-config schema
 
 
 Query the configuration schema for one flow node type before constructing a `save_flow` node config.
 
-Mapped command: `ae-cli engage +flow_node_config_schema`
+Mapped command: `ae-cli engage-flow node-config schema`
 
 ## Flags
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--node_type` | string | Yes | Flow node type |
+| `--project-id` / `-p` | number | Yes | Project ID |
+| `--node-type` | string | Yes | Flow node type |
 
 ## When To Use
 
@@ -34,7 +35,7 @@ Do not use this command to build an old full `FlowSaveReqDTO`, `nodeList`, or `e
 
 ## Enum Notes
 
-### `--node_type`
+### `--node-type`
 
 Schema-backed node types include:
 
@@ -55,13 +56,13 @@ Schema-backed node types include:
 ## Examples
 
 ```bash
-ae-cli engage +flow_node_config_schema --node_type message_push
+ae-cli engage-flow node-config schema --project-id 1 --node-type message_push
 ```
 
 Typical flow:
 
 ```bash
-ae-cli engage +flow_node_config_schema --node_type event_trigger
-ae-cli engage +validate_flow_node_config \
-  --node_type event_trigger --operation_mode save_flow --config '<config-json-string>'
+ae-cli engage-flow node-config schema --project-id 1 --node-type event_trigger
+ae-cli engage-flow node-config validate \
+  --project-id 1 --node-type event_trigger --operation-mode save_flow --config '<config-json-string>'
 ```