@thinkingai/ae-cli 6.0.33 → 6.0.35

package/skills/ae-engage/references/save-task.md

@@ -1,15 +1,15 @@
-# ae-engage `+save_task`
+# ae-cli `engage-task task save`
 
 Create or update a Hermes task draft.
 
-Mapped command: `ae-cli engage +save_task`
+Mapped command: `ae-cli engage-task task save`
 
 This command is the final write step. Do not use it as the first step in task construction.
 
 Recommended workflow:
 
-1. `ae-cli engage +channel_list --project_id <projectId>`
-2. `ae-cli engage +build_task_save_guide --project_id <projectId> --req '{...}'`
+1. `ae-cli engage-setting channel list --project-id <projectId>`
+2. `ae-cli engage-task task build-save-guide --project-id <projectId> --req '{...}'`
 3. If the guide indicates an audience or QP-derived fields are needed, create the audience directly and read it back:
 
 ```bash
@@ -18,7 +18,7 @@ ae-cli analysis user-cluster get --project-id <projectId> --cluster-names '["<co
 ```
 
 4. Build the final grouped `req`
-5. `ae-cli engage +save_task --project_id <projectId> --req '{...}'`
+5. `ae-cli engage-task task save --project-id <projectId> --req '{...}'`
 
 Audience creation is not a fixed preflight step. Use direct create/get only when the guide indicates that you must construct:
 
@@ -35,7 +35,7 @@ For the full guide contract, request format, return sections, and handoff usage,
 
 ## 1. General Principles
 
-`+save_task` accepts only the final grouped draft-save payload that Hermes can validate and persist.
+`engage-task task save` accepts only the final grouped draft-save payload that Hermes can validate and persist.
 
 The command supports two modes:
 
@@ -51,17 +51,23 @@ Regardless of mode, this tool only saves a draft:
 The CLI call shape is:
 
 ```bash
-ae-cli engage +save_task --project_id <projectId> --req '<req-json>'
+ae-cli engage-task task save --project-id <projectId> --req '<req-json>'
 ```
 
 Notes:
 
-- `projectId` is injected into top-level `req` by the CLI
-- if the caller also passes `req.projectId`, the outer `--project_id` wins
+- the outer Capability input uses `project_id` and `req`; fields inside `req` keep the native camelCase DTO shape shown below
+- Hermes assigns the outer `--project-id` to `req.projectId`; if `req.projectId` is also present, the outer value wins
 - the whole `req` must be a JSON object, not a stringified JSON string
 - for update mode, Hermes only allows modifying draft tasks
 - in update mode, omitted fields are backfilled from the existing draft before validation, so partial draft updates are allowed
 
+### Response shape
+
+The save result is under `data.result`, and any object keys inside it are recursively snake_case.
+A successful create/update commonly yields the task ID as `data.result`; validation failures use
+fields such as `data.result.operation_mode`, `data.result.errors`, and `data.result.warnings`.
+
 ---
 
 ## 2. Required Workflow
@@ -71,7 +77,7 @@ Notes:
 Run:
 
 ```bash
-ae-cli engage +channel_list --project_id <projectId>
+ae-cli engage-setting channel list --project-id <projectId>
 ```
 
 Purpose:
@@ -87,7 +93,7 @@ Never invent a `channelId`.
 Run:
 
 ```bash
-ae-cli engage +build_task_save_guide --project_id <projectId> --req '{...}'
+ae-cli engage-task task build-save-guide --project-id <projectId> --req '{...}'
 ```
 
 Use the guide to determine:
@@ -119,7 +125,7 @@ Do not create an audience by default for every task. It is conditional, not mand
 
 ### 2.4 Build Final `req` and Save
 
-Only after the above steps should you construct the final grouped `req` and submit it with `+save_task`.
+Only after the above steps should you construct the final grouped `req` and submit it with `engage-task task save`.
 
 ---
 
@@ -256,7 +262,7 @@ Only call that schema query when the guide explicitly shows that the field is ne
 
 ---
 
-## 5. Final Self-Check Before `+save_task`
+## 5. Final Self-Check Before `engage-task task save`
 
 Before submission, verify:
 
@@ -275,12 +281,12 @@ Before submission, verify:
 
 ## 6. Standard Example Flow
 
-Use this style of workflow, rather than jumping directly to `+save_task`:
+Use this style of workflow, rather than jumping directly to `engage-task task save`:
 
 ```bash
-ae-cli engage +channel_list --project_id 1
-ae-cli engage +build_task_save_guide --project_id 1 --req '{"context":{"triggerType":2,"channelId":"channel_123"}}'
-ae-cli engage +save_task --project_id 1 --req '{...final grouped req...}'
+ae-cli engage-setting channel list --project-id 1
+ae-cli engage-task task build-save-guide --project-id 1 --req '{"context":{"triggerType":2,"channelId":"channel_123"}}'
+ae-cli engage-task task save --project-id 1 --req '{...final grouped req...}'
 ```
 
 If the guide indicates an audience or QP-derived fields are needed, insert direct create/get:

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

@@ -1,12 +1,18 @@
 # engage-scene config-channel
 
-> Capability ids: `engage-scene.config-channel.{create,update,query-log}` · Domain: `engage`.
+> Capability ids: `engage-scene.config-channel.{list,get,create,update,update-status,delete,query-log}` · Domain: `engage`.
 
-场景管理 / 配置中心 - 配置通道管理与操作日志。
+Scene / config center — **config channel management** (Webhook / client config channels).
 
 ## Commands
 
 ```bash
+# List channels (optional type filter)
+ae-cli engage-scene config-channel list --project-id <project_id> [--channel-type 0|1]
+
+# Get channel detail (includes config JSON)
+ae-cli engage-scene config-channel get --project-id <project_id> --channel-id <channel_id>
+
 # Create a config channel and enable it
 ae-cli engage-scene config-channel create \
   --project-id <project_id> --channel-name <name> --channel-type <0|1> --config '<json string>'
@@ -15,19 +21,40 @@ ae-cli engage-scene config-channel create \
 ae-cli engage-scene config-channel update \
   --project-id <project_id> --channel-id <channel_id> --channel-name <name> [--config '<json string>']
 
-# Query a config channel's operation log
+# Enable / disable channel
+ae-cli engage-scene config-channel update-status \
+  --project-id <project_id> --channel-id <channel_id> --channel-status <1|2>
+
+# Delete a disabled channel (high-risk; requires --yes after confirm)
+ae-cli engage-scene config-channel delete --project-id <project_id> --channel-id <channel_id> --yes
+
+# Query operation log
 ae-cli engage-scene config-channel query-log --project-id <project_id> --channel-id <channel_id>
 ```
 
 ## Parameters
 
+### list
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+| `--channel-type` | No | Filter: **0 webhook**, **1 client**. Omit for all. |
+
+### get
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+| `--channel-id` | Yes | Channel ID. |
+
 ### create
 
 | Parameter | Required | Description |
 |---|---|---|
 | `--project-id` / `-p` | Yes | Numeric project ID. |
-| `--channel-name` | Yes | Channel name. |
-| `--channel-type` | Yes | Channel type: **0 webhook**, **1 client** (not the same as engage push `channelType`, where 1=webhook). |
+| `--channel-name` | Yes | Channel name (≤80). |
+| `--channel-type` | Yes | **0 webhook**, **1 client** (not the same as engage push `channelType`, where 1=webhook). |
 | `--config` | Yes | Channel-specific JSON config string. Webhook (`0`) requires `config.url`; client (`1`) must not include `url`. |
 
 ### update
@@ -39,6 +66,21 @@ ae-cli engage-scene config-channel query-log --project-id <project_id> --channel
 | `--channel-name` | Yes | New channel name. |
 | `--config` | No | Channel-specific JSON config string. Omit to keep the current config (typical when renaming an enabled channel). Required when changing webhook URL, auth, or parameter definitions on a disabled channel. |
 
+### update-status
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+| `--channel-id` | Yes | Channel ID. |
+| `--channel-status` | Yes | **1 enable**, **2 disable**. |
+
+### delete
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+| `--channel-id` | Yes | Channel ID. Must already be **disabled** (`channel_status=2`). |
+
 ### query-log
 
 | Parameter | Required | Description |
@@ -46,13 +88,51 @@ ae-cli engage-scene config-channel query-log --project-id <project_id> --channel
 | `--project-id` / `-p` | Yes | Numeric project ID. |
 | `--channel-id` | Yes | Channel ID whose operation log to query. |
 
+## Webhook `config` JSON shape
+
+```json
+{
+  "url": "https://example.com/hook",
+  "testUrl": "https://example.com/hook-test",
+  "authConfig": {
+    "enable": true,
+    "secretKey": "<token>",
+    "secretType": 1
+  },
+  "customsParamList": [
+    {
+      "key": "user_id",
+      "columnName": "#account_id",
+      "defaultValue": "",
+      "systemIdParam": true
+    }
+  ],
+  "envParamList": []
+}
+```
+
+- `url` — production environment URL (required for webhook)
+- `testUrl` — optional test environment URL
+- `authConfig.enable` — channel auth switch; when true, `secretKey` is required; `secretType` **1 = basic**, **2 = advanced**
+- `customsParamList` — user params (field key / linked user property / default value / system-integration identity)
+- `envParamList` — environment params (from config tables)
+- At most one `systemIdParam=true` across user + env params
+
 ## Output
 
-- `create`: `data.channel_id` — the created channel ID.
-- `update`: `data.success`.
-- `query-log`: `data.items` + `data.total`.
+- `list`: `data.items` + `data.total` (snake_case fields: `channel_id` / `channel_name` / `channel_type` / `channel_status` / `creator` / `updater` / `create_time` / `update_time`)
+- `get`: `data.channel` (same as list item + `config`)
+- `create`: `data.channel_id`
+- `update` / `update-status` / `delete`: `data.success`
+- `query-log`: `data.items` + `data.total`
 
 ## Decision Rules
 
-- `create`/`update` are `write`; `query-log` is read.
-- Discover real `channel_id`s with `ae-cli engage +config_channel_list --project_id <project_id>` first.
+- Risk: `list` / `get` / `query-log` = read; `create` / `update` / `update-status` = write; `delete` = high-risk-write (user confirmation + `--yes`)
+- Discover `channel_id` with `list` first; never invent IDs
+- Enabled channel (`channel_status=1`): only limited fields such as name can change; disable first (`update-status --channel-status 2`) before changing URL, auth, or parameter definitions
+- Delete: disable first, then `delete --yes`
+- Copy: `get` → rename (often append `_copy`) → `create`
+- Filter by name: substring-match `channel_name` on `list` results
+
+Workflows: [`channel-mgmt.md`](channel-mgmt.md).

package/skills/ae-engage/references/scene-config-group.md

@@ -2,7 +2,7 @@
 
 > Capability ids: `engage-scene.config-group.{list,batch-add,update,batch-delete}` · Domain: `engage`.
 
-场景管理 / 配置中心 - 配置项分组管理。
+Scene management / config center — config item group management.
 
 ## Commands
 

package/skills/ae-engage/references/scene-config-item.md

@@ -1,8 +1,8 @@
 # engage-scene config-item
 
-> Capability ids: `engage-scene.config-item.{list,create,update}` · Domain: `engage`.
+> Capability ids: `engage-scene.config-item.{list,get,create,update,delete}` · Domain: `engage`.
 
-场景管理 / 配置中心 - 配置项管理。
+Scene management / config center — config item management.
 
 ## Commands
 
@@ -10,6 +10,9 @@
 # List config items of a project
 ae-cli engage-scene config-item list --project-id <project_id>
 
+# Get config item detail
+ae-cli engage-scene config-item get --project-id <project_id> --config-id <config_id>
+
 # Create a config item (business type, group, optional avatar)
 ae-cli engage-scene config-item create \
   --project-id <project_id> --config-id <config_id> --config-name <name> \
@@ -22,6 +25,10 @@ ae-cli engage-scene config-item update \
   --project-id <project_id> --config-id <config_id> \
   [--config-name <name>] [--config-remark <remark>] [--business-type <type>] \
   [--group-id <group_id>] [--channel-id <channel_id>]
+
+# Delete a config item (high-risk)
+ae-cli engage-scene config-item delete \
+  --project-id <project_id> --config-id <config_id> --open-id <operator_open_id> --yes
 ```
 
 ## Parameters
@@ -46,6 +53,13 @@ ae-cli engage-scene config-item update \
 | `--file-name` | No | Avatar file name including extension. |
 | `--file-content` | No | Base64-encoded avatar file content. |
 
+### get
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+| `--config-id` | Yes | Config item ID. |
+
 ### update
 
 | Parameter | Required | Description |
@@ -58,11 +72,20 @@ ae-cli engage-scene config-item update \
 | `--group-id` | No | New group ID. |
 | `--channel-id` | No | Config channel ID to bind. |
 
+### delete
+
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` / `-p` | Yes | Numeric project ID. |
+| `--config-id` | Yes | Config item ID to delete. |
+| `--open-id` | Yes | Operator open ID retained by the original deletion workflow. |
+
 ## Output
 
 - `list`: `data.items` + `data.total`.
-- `create` / `update`: `data.success` — whether the operation succeeded.
+- `get`: `data.item`.
+- `create` / `update` / `delete`: `data.success` — whether the operation succeeded.
 
 ## Decision Rules
 
-- `create` / `update` are `write`; `list` is read. Use `config-item list` (or `engage +config_item_list`) to discover real `config_id`s and group IDs; never invent IDs.
+- `create` / `update` are `write`; `delete` is `high-risk-write` and requires `--yes`; `list` / `get` are read. Use `config-item list` to discover real `config_id`s and group IDs; never invent IDs.

package/skills/ae-engage/references/scene-config-metric.md

@@ -2,7 +2,7 @@
 
 > Capability ids: `engage-scene.config-metric.{list,get,batch-add,update-rule,batch-delete}` · Domain: `engage`.
 
-场景管理 / 配置中心 - 配置项关联指标管理。
+Scene management / config center — config item related-metric management.
 
 ## Commands
 

package/skills/ae-engage/references/scene-config-param.md

@@ -2,7 +2,7 @@
 
 > Capability ids: `engage-scene.config-param.{list,batch-add,update,batch-delete}` · Domain: `engage`.
 
-场景管理 / 配置中心 - 配置项参数管理。
+Scene management / config center — config item parameter management.
 
 ## Commands
 
@@ -13,7 +13,7 @@ ae-cli engage-scene config-param list --project-id <project_id> --config-id <con
 # Batch-add params to a config item
 ae-cli engage-scene config-param batch-add \
   --project-id <project_id> --config-id <config_id> \
-  --params '[{"param_name":"title","param_display_name":"标题","param_type":"STRING","param_sub_type":"SHORT_TEXT","is_required":1}]'
+  --params '[{"param_name":"title","param_display_name":"Title","param_type":"STRING","param_sub_type":"SHORT_TEXT","is_required":1}]'
 
 # Update a param
 ae-cli engage-scene config-param update \

package/skills/ae-engage/references/scene-preset-metric.md

@@ -2,7 +2,7 @@
 
 > Capability ids: `engage-scene.preset-metric.{get,set}` · Domain: `engage`.
 
-场景管理 / 配置中心 - 配置项预置指标（曝光/点击/参与）QP 配置。
+Scene management / config center — config item preset metrics (impression / click / engagement) QP configuration.
 
 ## Commands
 

package/skills/ae-engage/references/scene-strategy.md

@@ -1,12 +1,18 @@
 # engage-scene strategy
 
-> Capability ids: `engage-scene.strategy.{create,update,log,batch-copy}` · Domain: `engage`.
+> Capability ids: `engage-scene.strategy.{list,get,create,update,log,batch-copy,manage}` · Domain: `engage`.
 
-场景管理 / 配置中心 - 配置项策略管理。create/update 使用 `--payload` 直传后端 DTO（原生 camelCase 结构），`project_id` 会注入 payload。
+Scene management / config center — config item strategy management. `create`/`update` pass backend DTOs via `--payload` (native camelCase structure); `project_id` is injected into the payload.
 
 ## Commands
 
 ```bash
+# List or get strategies
+ae-cli engage-scene strategy list --project-id <project_id> [--config-id <config_id>] \
+  [--strategy-uuid-list '["uuid-1"]']
+ae-cli engage-scene strategy get --project-id <project_id> --config-id <config_id> \
+  --strategy-uuid <uuid>
+
 # Create a config strategy (draft)
 ae-cli engage-scene strategy create --project-id <project_id> \
   --payload '{"configId":"cfg-1","templateId":"tpl-1","strategyName":"s1", ...}'
@@ -21,27 +27,37 @@ ae-cli engage-scene strategy log --project-id <project_id> --strategy-uuid <uuid
 # Batch-copy strategies
 ae-cli engage-scene strategy batch-copy --project-id <project_id> --config-id <config_id> \
   --strategy-ids '["s1","s2"]' [--op-mode batch]
+
+# Apply a strategy management action
+ae-cli engage-scene strategy manage --project-id <project_id> --config-id <config_id> \
+  --action online --strategy-uuid-list '["uuid-1"]'
 ```
 
 ## Parameters
 
 | Command | Required flags | Notes |
 |---|---|---|
+| list | `--project-id` | Optional `--config-id`, `--strategy-uuid-list`. |
+| get | `--project-id`, `--config-id`, `--strategy-uuid` | read. |
 | create | `--project-id`, `--payload` | payload = `ConfigStrategyAddDTO`. |
 | update | `--project-id`, `--payload` | payload = `ConfigStrategyModifyDTO` (`strategyUuid` + fields). |
 | log | `--project-id`, `--strategy-uuid` | read. |
 | batch-copy | `--project-id`, `--config-id`, `--strategy-ids` | `--op-mode` optional (default `batch`). |
+| manage | `--project-id`, `--config-id`, `--action` | Lifecycle actions require `--strategy-uuid-list`; review actions require `--strategy-list`; write. |
 
 ## Output
 
+- `list`: `data.items` + `data.total`; `get`: `data.item`.
 - `create`: `data.strategy_uuid`.
 - `update`: `data.success`.
 - `log`: `data.log`.
 - `batch-copy`: `data.result`.
+- `manage`: `data.item`.
 
 ## Decision Rules
 
 - Discover real strategy UUIDs / config IDs first; never invent IDs.
 - **`create` requires an enabled template** on the same config item. Enable workflow: `config-param batch-add` → `template create` → `template update` (non-empty `config[]` with real `paramId`) → `template update-status --status 1`. Otherwise `create` returns `TEMPLATE_ENABLE`.
 - `create` output field is `data.strategy_uuid` (not `strategy_id`).
-- Save-and-submit and strategy test-send are not exposed via `engage-scene` CLI; use legacy `engage +manage_strategy` or the product UI.
+- `manage` supports `online`, `offline`, `suspend`, `delete`, `approve`, `deny`, and `cancel`; it is a write operation.
+- Save-and-submit and strategy test-send are separate high-impact operations and remain unexposed; use the product UI.

package/skills/ae-engage/references/scene-template.md

@@ -1,8 +1,8 @@
 # engage-scene template
 
-> Capability ids: `engage-scene.template.{list,get,create,update,update-status,delete}` · Domain: `engage`.
+> Capability ids: `engage-scene.template.{list,get,copy,create,update,update-status,delete}` · Domain: `engage`.
 
-场景管理 / 配置中心 - 配置项模板管理。create/update 使用 `--payload` 直传后端 DTO（原生 camelCase 结构），`project_id` 会注入 payload。
+Scene management / config center — config item template management. `create`/`update` pass backend DTOs via `--payload` (native camelCase structure); `project_id` is injected into the payload.
 
 ## Commands
 
@@ -13,6 +13,11 @@ ae-cli engage-scene template list --project-id <project_id> --config-id <config_
 # Get a template's detail
 ae-cli engage-scene template get --project-id <project_id> --config-id <config_id> --template-id <template_id>
 
+# Copy a template to a target config item
+ae-cli engage-scene template copy \
+  --source-project-id <source_project_id> --source-config-id <source_config_id> \
+  --source-template-id <source_template_id> --project-id <target_project_id> --config-id <target_config_id>
+
 # Create a template
 ae-cli engage-scene template create --project-id <project_id> \
   --payload '{"configId":"cfg-1","templateId":"tpl-1","templateName":"t1","remark":""}'
@@ -26,7 +31,7 @@ ae-cli engage-scene template update --project-id <project_id> \
     "config":[{
       "paramId":48,
       "paramName":"title",
-      "paramDisplayName":"标题",
+      "paramDisplayName":"Title",
       "paramType":"STRING",
       "paramSubType":"SHORT_TEXT",
       "isRequired":1,
@@ -48,6 +53,7 @@ ae-cli engage-scene template delete --project-id <project_id> --config-id <confi
 |---|---|---|
 | list | `--project-id`, `--config-id` | read. |
 | get | `--project-id`, `--config-id`, `--template-id` | read. |
+| copy | `--source-project-id`, `--source-config-id`, `--source-template-id`, `--project-id`, `--config-id` | write. |
 | create | `--project-id`, `--payload` | payload = `ConfigTemplateAddDTO`. |
 | update | `--project-id`, `--payload` | payload = `ConfigTemplateModifyDTO`. |
 | update-status | `--project-id`, `--config-id`, `--template-id`, `--status` | status 1 enable / 0 disable. |
@@ -59,7 +65,7 @@ ae-cli engage-scene template delete --project-id <project_id> --config-id <confi
 
 - `list`: `data.items` + `data.total`.
 - `get`: `data.template`.
-- `create` / `update` / `update-status` / `delete`: `data.success`.
+- `copy` / `create` / `update` / `update-status` / `delete`: `data.success`.
 
 ## Decision Rules
 

package/skills/ae-engage/references/task-data-detail.md

@@ -1,73 +1,11 @@
-# ae-engage +task_data_detail
+# engage-task.task-data.detail
 
+Query a task detail report through the L3 Capability Gateway.
 
-Query the task detailed data report.
+Mapped command: `ae-cli capability run engage-task.task-data.detail --input '<json>'`
 
-Mapped command: `ae-cli engage +task_data_detail`
-
-## Flags
-
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--task_id` | string | Yes | task ID |
-| `--detail_type` | string | Yes | detail type |
-| `--start_time` | string | Yes | Start date |
-| `--end_time` | string | Yes | End date |
-| `--request_id` | string | No | Query requestId |
-| `--push_language_code` | string | No | push language code |
-| `--task_instance_id` | string | No | task instance ID |
-| `--data_dim_type` | string | No | data dimension type |
-| `--retention_type` | string | No | retention type |
-| `--data_view_type` | number | No | Trigger task view type |
-| `--show_time_zone` | string | No | display timezone offset |
-
-## Enum Notes
-
-### `--detail_type`
-
-- `time`: view by time
-- `instance`: view by instance
-- `instance_daily`: view day-by-day details for a single instance
-
-### `--data_dim_type`
-
-- `uv`: count by unique users
-- `pv`: count by events/occurrences
-
-### `--retention_type`
-
-- `retention`: retention analysis
-- `lost`: churn analysis
-
-### `--data_view_type`
-
-Only valid when `--task_type` is `trigger` and `--detail_type` is `time`:
-
-- `2`: date view
-- `3`: trigger view
-
-### `--push_language_code`
-
-Common values include:
-
-- `default`
-- `en`
-- `zh-Hans`
-- `zh-Hant`
-- `ja`
-- `ko`
-
-## Parameter Constraints
-
-- When `--detail_type` is `instance_daily`, you must include `--task_instance_id`.
-- `--start_time`、`--end_time` use `yyyy-MM-dd`.
-
-## Examples
+Required input: `project_id`, `task_id`, `detail_type`, `start_time`, `end_time`. `detail_type` is `time`, `instance`, or `instance_daily`; the last form also requires `task_instance_id`.
 
 ```bash
-ae-cli engage +task_data_detail \
-  --project_id 1 --task_id task_123 \
-  --detail_type time \
-  --start_time 2026-04-01 --end_time 2026-04-07
+ae-cli capability run engage-task.task-data.detail --input '{"project_id":1,"task_id":"task_123","detail_type":"time","start_time":"2026-04-01","end_time":"2026-04-07"}'
 ```

package/skills/ae-engage/references/task-data-overview.md

@@ -1,41 +1,11 @@
-# ae-engage +task_data_overview
+# engage-task.task-data.overview
 
+Query a task performance overview through the L3 Capability Gateway.
 
-Query the funnel-style task data overview.
+Mapped command: `ae-cli capability run engage-task.task-data.overview --input '<json>'`
 
-Mapped command: `ae-cli engage +task_data_overview`
-
-## Flags
-
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--task_id` | string | Yes | task ID |
-| `--request_id` | string | No | Query requestId |
-| `--push_language_code` | string | No | push language code |
-| `--data_dim_type` | string | No | data dimension type |
-| `--show_time_zone` | string | No | display timezone offset |
-
-## Enum Notes
-
-### `--data_dim_type`
-
-- `uv`: count by unique users
-- `pv`: count by events/occurrences
-
-### `--push_language_code`
-
-Common values include:
-
-- `default`
-- `en`
-- `zh-Hans`
-- `zh-Hant`
-- `ja`
-- `ko`
-
-## Examples
+Required input: `project_id`, `task_id`. Optional input: `request_id`, `push_language_code`, `data_dim_type`, `show_time_zone`.
 
 ```bash
-ae-cli engage +task_data_overview --project_id 1 --task_id task_123
+ae-cli capability run engage-task.task-data.overview --input '{"project_id":1,"task_id":"task_123"}'
 ```

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

@@ -1,16 +1,16 @@
-# ae-engage +task_detail
+# ae-cli engage-task task get
 
 
 Query the details of a single task.
 
-Mapped command: `ae-cli engage +task_detail`
+Mapped command: `ae-cli engage-task task get`
 
 ## Flags
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--task_id` | string | Yes | task ID |
+| `--project-id` / `-p` | number | Yes | Project ID |
+| `--task-id` | string | Yes | task ID |
 
 ## Common enums in the response
 
@@ -56,5 +56,5 @@ Mapped command: `ae-cli engage +task_detail`
 ## Examples
 
 ```bash
-ae-cli engage +task_detail --project_id 1 --task_id task_123
+ae-cli engage-task task get --project-id 1 --task-id task_123
 ```