@thinkingai/ae-cli 6.0.33 → 6.0.34

package/skills/ae-engage/references/task-experiment-report.md

@@ -1,44 +1,11 @@
-# ae-engage +task_experiment_report
+# engage-task.task-data.experiment-report
 
+Query a task experiment report through the L3 Capability Gateway.
 
-Query the task experiment report.
+Mapped command: `ae-cli capability run engage-task.task-data.experiment-report --input '<json>'`
 
-Mapped command: `ae-cli engage +task_experiment_report`
-
-## Flags
-
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--task_id` | string | Yes | task ID |
-| `--report_type` | string | Yes | report type: `overview` or `detail` |
-| `--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 |
-
-## Enum Notes
-
-### `--report_type`
-
-- `overview`: experiment overview
-- `detail`: experiment detail
-
-### `--push_language_code`
-
-Common values include:
-
-- `default`
-- `en`
-- `zh-Hans`
-- `zh-Hant`
-- `ja`
-- `ko`
-
-## Examples
+Required input: `project_id`, `task_id`, `report_type`, `start_time`, `end_time`. `report_type` is `overview` or `detail`.
 
 ```bash
-ae-cli engage +task_experiment_report \
-  --project_id 1 --task_id task_123 \
-  --report_type overview --start_time 2026-04-01 --end_time 2026-04-07
+ae-cli capability run engage-task.task-data.experiment-report --input '{"project_id":1,"task_id":"task_123","report_type":"overview","start_time":"2026-04-01","end_time":"2026-04-07"}'
 ```

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

@@ -1,15 +1,15 @@
-# ae-engage +task_list
+# ae-cli engage-task task list
 
 
 Query the paginated task list.
 
-Mapped command: `ae-cli engage +task_list`
+Mapped command: `ae-cli engage-task task list`
 
 ## Flags
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
+| `--project-id` / `-p` | number | Yes | Project ID |
 | `--req` | json | Yes | query-condition JSON object |
 
 ## `--req` Object Fields
@@ -86,5 +86,5 @@ Common fields are listed below; provide them as needed:
 ## Examples
 
 ```bash
-ae-cli engage +task_list --project_id 1 --req '{"pageNum":1,"pageSize":20}'
+ae-cli engage-task task list --project-id 1 --req '{"pageNum":1,"pageSize":20}'
 ```

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

@@ -1,49 +1,11 @@
-# ae-engage +task_metric_detail
+# engage-task.task-data.metric-detail
 
+Query a task metric detail report through the L3 Capability Gateway.
 
-Query the metric-oriented detail report for a task.
+Mapped command: `ae-cli capability run engage-task.task-data.metric-detail --input '<json>'`
 
-Mapped command: `ae-cli engage +task_metric_detail`
-
-## Flags
-
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--task_id` | string | Yes | task ID |
-| `--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 |
-| `--metric_id_list` | json | No | metric ID JSON array |
-| `--group_type` | number | No | group type |
-| `--show_time_zone` | string | No | Display timezone offset |
-
-## Enum Notes
-
-### `--group_type`
-
-- `1`: group by batch
-- `2`: group by date
-- `3`: group by trigger
-- `4`: group by experiment result
-
-### `--push_language_code`
-
-Common values include:
-
-- `default`
-- `en`
-- `zh-Hans`
-- `zh-Hant`
-- `ja`
-- `ko`
-
-## Examples
+Required input: `project_id`, `task_id`, `start_time`, `end_time`. Optional input includes `request_id`, `push_language_code`, `metric_id_list`, `group_type`, and `show_time_zone`.
 
 ```bash
-ae-cli engage +task_metric_detail \
-  --project_id 1 --task_id task_123 \
-  --start_time 2026-04-01 --end_time 2026-04-07 \
-  --metric_id_list '["metric_1"]'
+ae-cli capability run engage-task.task-data.metric-detail --input '{"project_id":1,"task_id":"task_123","start_time":"2026-04-01","end_time":"2026-04-07"}'
 ```

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

@@ -1,20 +1,20 @@
-# ae-engage +task_stats
+# ae-cli engage-task task stats
 
 
 Query task status statistics.
 
-Mapped command: `ae-cli engage +task_stats`
+Mapped command: `ae-cli engage-task task stats`
 
 ## Flags
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
+| `--project-id` / `-p` | number | Yes | Project ID |
 | `--req` | json | Yes | statistics-condition JSON object |
 
 ## `--req` Object Fields
 
-The `--req` structure of `+task_stats` is broadly the same as `+task_list`, and common fields include:
+The `--req` structure of `engage-task task stats` is broadly the same as `engage-task task list`, and common fields include:
 
 | Field | Type | Required | Description |
 |------|------|------|------|
@@ -84,5 +84,5 @@ The `--req` structure of `+task_stats` is broadly the same as `+task_list`, and
 ## Examples
 
 ```bash
-ae-cli engage +task_stats --project_id 1 --req '{"pageNum":1,"pageSize":20}'
+ae-cli engage-task task stats --project-id 1 --req '{"pageNum":1,"pageSize":20}'
 ```

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

@@ -1,24 +1,24 @@
-# ae-engage +update_channel_status
+# ae-engage engage-setting channel update-status
 
 
 Update the status of an Engage channel.
 
-Mapped command: `ae-cli engage +update_channel_status`
+Mapped command: `ae-cli engage-setting channel update-status`
 
 ## 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 |
 | `--status` | number | Yes | channel status |
 
 ## Enum Notes
 
 ### `--status`
 
-- `0`: disabled
 - `1`: enabled
+- `2`: disabled
 
 ## Safety Constraints
 
@@ -27,5 +27,5 @@ This command is a **write operation** and Before executing, confirm that the use
 ## Examples
 
 ```bash
-ae-cli engage +update_channel_status --project_id 1 --channel_id <channel_id> --status 1
+ae-cli engage-setting channel update-status --project-id 1 --channel-id <channel_id> --status 1
 ```

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

@@ -1,30 +1,31 @@
-# ae-engage +validate_flow_node_config
+# ae-cli engage-flow node-config validate
 
 
 Validate and normalize a single node configuration before placing it into a `save_flow` request.
 
-Mapped command: `ae-cli engage +validate_flow_node_config`
+Mapped command: `ae-cli engage-flow node-config validate`
 
 ## 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 |
 | `--config` | string | Yes | Node config JSON object encoded as a string |
-| `--operation_mode` | string | Yes | Validation mode |
+| `--operation-mode` | string | Yes | Validation mode |
 
 ## When To Use
 
-Use this after `+flow_node_config_schema` and before passing a config into `+save_flow`.
+Use this after `engage-flow node-config schema` and before passing a config into `engage-flow flow save`.
 
 The command validates one node config only; it does not validate the full canvas topology. It returns:
 
 - `valid`: whether the candidate config passed validation
 - `normalizedConfigObject`: backend-normalized config with defaulted fields
-- `errors`: hard validation failures to fix before calling `+save_flow`
+- `errors`: hard validation failures to fix before calling `engage-flow flow save`
 - `warnings`: issues that depend on live channel/template/config data
 
-Use `--operation_mode save_flow` for the current exposed MCP protocol. Use `save_submit_flow` only when you intentionally want stricter submit-time checks.
+Use `--operation-mode save_flow` for the current exposed MCP protocol. Use `save_submit_flow` only when you intentionally want stricter submit-time checks.
 
 Important current rules:
 
@@ -38,7 +39,7 @@ Important current rules:
 
 ## Enum Notes
 
-### `--node_type`
+### `--node-type`
 
 Schema-backed node types include:
 
@@ -56,7 +57,7 @@ Schema-backed node types include:
 - `ab_split_flow`
 - `exit_flow`
 
-### `--operation_mode`
+### `--operation-mode`
 
 - `save_flow`
 - `save_submit_flow`
@@ -64,6 +65,6 @@ Schema-backed node types include:
 ## Examples
 
 ```bash
-ae-cli engage +validate_flow_node_config \
-  --node_type message_push --operation_mode save_flow --config '{}'
+ae-cli engage-flow node-config validate \
+  --project-id 1 --node-type message_push --operation-mode save_flow --config '{}'
 ```

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

@@ -1,18 +1,18 @@
-# ae-engage +whitelist_list
+# ae-engage engage-setting whitelist list
 
 
 Query the whitelist list in a project.
 
-Mapped command: `ae-cli engage +whitelist_list`
+Mapped command: `ae-cli engage-setting whitelist list`
 
 ## Flags
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
+| `--project-id` / `-p` | number | Yes | Project ID |
 
 ## Examples
 
 ```bash
-ae-cli engage +whitelist_list --project_id 1
+ae-cli engage-setting whitelist list --project-id 1
 ```

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

@@ -68,5 +68,5 @@ ae-cli engage-setting whitelist verify \
 ## Decision Rules
 
 - Use these commands when the user asks to add / edit / delete / verify project whitelist entries.
-- Discover existing whitelist IDs with `ae-cli engage +whitelist_list --project_id <project_id>` first; never invent IDs.
+- Discover existing whitelist IDs with `ae-cli engage-setting whitelist list --project-id <project_id>` first; never invent IDs.
 - `delete` is `high-risk-write` and requires `--yes` (or interactive confirmation).

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

@@ -2,7 +2,7 @@
 
 > Capability ids: `engage-workbench.workbench.{list,add,update,delete}` · Domain: `engage`.
 
-工作台 - 工作台指标卡槽（workbench slot）管理。每个用户在每个项目下最多 4 个指标卡；卡槽按当前登录用户隔离，`update`/`delete` 只能操作本人卡槽。首次 `list` 会自动初始化 4 个默认卡槽。
+Workbench — workbench metric slot management. Each user may configure up to 4 metric cards per project; slots are scoped to the current login user, so `update`/`delete` only affect the caller's own slots. The first `list` auto-initialises 4 default slots.
 
 ## Commands
 

package/skills/ae-kb/SKILL.md

@@ -125,15 +125,17 @@ ae-cli kb +status --name engineering-handbook
 
 ### Query Knowledge
 
-Use `+query` with a natural-language question and a JSON array of source refs.
+Use `+query` with a natural-language question. Optionally scope to specific knowledge bases or tune result count and locale.
 
 ```bash
 ae-cli kb +query \
   --query "How do we release a dashboard?" \
-  --sources '[{"scope":"company","name":"engineering-handbook"}]'
+  --sources '[{"scope":"company","name":"engineering-handbook"}]' \
+  --top-k 10 \
+  --locale zh
 ```
 
-`--sources` entries require:
+When `--sources` is provided, each entry requires:
 
 - `scope`: knowledge base scope such as `personal` or `company`.
 - `name`: knowledge base name.
@@ -234,11 +236,13 @@ ae-cli kb +remove --name engineering-handbook
 ### `+query`
 
 ```bash
-ae-cli kb +query --query "<question>" --sources '[{"scope":"company","name":"kb-name"}]'
+ae-cli kb +query --query "<question>" [--sources '[{"scope":"company","name":"kb-name"}]'] [--top-k 10] [--locale zh|en|ja|ko]
 ```
 
 - `--query`, alias `-q`: required natural-language question.
-- `--sources`: required JSON array of knowledge base refs.
+- `--sources`: optional JSON array of knowledge base refs. Omit to search all accessible knowledge bases.
+- `--top-k`: optional max number of hits, 1-50, default 10.
+- `--locale`: optional locale: `zh`, `en`, `ja`, or `ko`.
 
 ### `+ask`
 

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

@@ -1,31 +0,0 @@
-# ae-engage +config_channel_detail
-
-
-Query config channel details.
-
-Mapped command: `ae-cli engage +config_channel_detail`
-
-## Flags
-
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--channel_id` | string | Yes | config channel ID |
-
-## Common enums in the response
-
-### `channelType`
-
-- `0`: `WEBHOOK`
-- `1`: `CLIENT`
-
-### `channelStatus`
-
-- `1`: enabled
-- `2`: disabled
-
-## Examples
-
-```bash
-ae-cli engage +config_channel_detail --project_id 1 --channel_id <channel_id>
-```

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

@@ -1,26 +0,0 @@
-# ae-engage +config_channel_list
-
-
-Query the config channel list.
-
-Mapped command: `ae-cli engage +config_channel_list`
-
-## Flags
-
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--channel_type` | number | No | config channel type |
-
-## Enum Notes
-
-### `--channel_type`
-
-- `0`: `WEBHOOK`
-- `1`: `CLIENT`
-
-## Examples
-
-```bash
-ae-cli engage +config_channel_list --project_id 1
-```

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

@@ -1,29 +0,0 @@
-# ae-engage +config_item_detail
-
-
-Query config item details.
-
-Mapped command: `ae-cli engage +config_item_detail`
-
-## Flags
-
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--config_id` | string | Yes | config item ID |
-
-## Common enums in the response
-
-### `channelType`
-
-- `1`: `WEBHOOK`
-- `2`: `APP_PUSH`
-- `3`: `CLIENT_PUSH`
-- `4`: `WECHAT`
-- `5`: `DOU_YIN`
-
-## Examples
-
-```bash
-ae-cli engage +config_item_detail --project_id 1 --config_id cfg_123
-```

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

@@ -1,18 +0,0 @@
-# ae-engage +config_item_list
-
-
-Query the list of config items in a project.
-
-Mapped command: `ae-cli engage +config_item_list`
-
-## Flags
-
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-
-## Examples
-
-```bash
-ae-cli engage +config_item_list --project_id 1
-```

package/skills/ae-engage/references/copy-config-template.md

@@ -1,28 +0,0 @@
-# ae-engage +copy_config_template
-
-
-Copy a template from the source config item to the target config item.
-
-Mapped command: `ae-cli engage +copy_config_template`
-
-## Flags
-
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--source_project_id` | number | Yes | source Project ID |
-| `--source_config_id` | string | Yes | source config item ID |
-| `--source_template_id` | string | Yes | source template ID |
-| `--project_id` / `-p` | number | Yes | target Project ID |
-| `--config_id` | string | Yes | target config item ID |
-
-## Safety Constraints
-
-This command is a **write operation** and and copies the template and dependent resources.
-
-## Examples
-
-```bash
-ae-cli engage +copy_config_template \
-  --source_project_id 1 --source_config_id src_cfg --source_template_id tpl_1 \
-  --project_id 2 --config_id dst_cfg
-```

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

@@ -1,23 +0,0 @@
-# ae-engage +delete_config_channel
-
-
-Delete a config channel.
-
-Mapped command: `ae-cli engage +delete_config_channel`
-
-## Flags
-
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--channel_id` | string | Yes | config channel ID |
-
-## Safety Constraints
-
-This command is a **write operation** and and deletes a config channel.
-
-## Examples
-
-```bash
-ae-cli engage +delete_config_channel --project_id 1 --channel_id <channel_id>
-```

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

@@ -1,24 +0,0 @@
-# ae-engage +delete_config_item
-
-
-Delete a config item.
-
-Mapped command: `ae-cli engage +delete_config_item`
-
-## Flags
-
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--config_id` | string | Yes | config item ID |
-| `--open_id` | string | Yes | operator open ID |
-
-## Safety Constraints
-
-This command is a **write operation** and deletes a config item.
-
-## Examples
-
-```bash
-ae-cli engage +delete_config_item --project_id 1 --config_id cfg_123 --open_id ou_xxx
-```

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

@@ -1,69 +0,0 @@
-# engage-scene config-item
-
-> Capability ids: `engage-scene.config-item.{list,create,update}` · Domain: `engage`.
-
-`config-item` 是配置中心（场景管理）里的配置项。create 走 multipart，可携带可选头像文件。
-
-## Commands
-
-```bash
-# List config items of a project
-ae-cli engage-scene config-item list --project-id <project_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> \
-  --business-type <config_file|params> \
-  [--config-remark <remark>] [--group-id <group_id>] \
-  [--avatar-word '["A","B"]'] [--file-name avatar.png] [--file-content "$(base64 -i avatar.png)"]
-
-# Update a config item's basic info and bound channel
-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>]
-```
-
-## Parameters
-
-### list
-
-| Parameter | Required | Description |
-|---|---|---|
-| `--project-id` / `-p` | Yes | Numeric project ID. |
-
-### create
-
-| Parameter | Required | Description |
-|---|---|---|
-| `--project-id` / `-p` | Yes | Numeric project ID. |
-| `--config-id` | Yes | Config item ID (unique within the project). |
-| `--config-name` | Yes | Config item display name (<=80 chars). |
-| `--business-type` | Yes | Business type: `config_file` or `params`. |
-| `--config-remark` | No | Remark (<=200 chars). |
-| `--group-id` | No | Group ID (0 = default group). |
-| `--avatar-word` | No | JSON array of avatar words for the icon. |
-| `--file-name` | No | Avatar file name incl. extension. |
-| `--file-content` | No | Base64-encoded avatar file content. |
-
-### update
-
-| Parameter | Required | Description |
-|---|---|---|
-| `--project-id` / `-p` | Yes | Numeric project ID. |
-| `--config-id` | Yes | Config item ID to update. |
-| `--config-name` | No | New display name. |
-| `--config-remark` | No | New remark. |
-| `--business-type` | No | New business type. |
-| `--group-id` | No | New group ID. |
-| `--channel-id` | No | Config channel ID to bind. |
-
-## Output
-
-- `list`: `data.items` + `data.total`.
-- `create` / `update`: `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 existing config items first; never invent IDs.

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

@@ -1,73 +0,0 @@
-# ae-engage +manage_strategy
-
-
-Batch manage strategy status or review actions.
-
-Mapped command: `ae-cli engage +manage_strategy`
-
-## Flags
-
-| Flag | Type | Required | Description |
-|------|------|------|------|
-| `--project_id` / `-p` | number | Yes | Project ID |
-| `--config_id` | string | Yes | config item ID |
-| `--action` | string | Yes | action type |
-| `--strategy_uuid_list` | json | No | Strategy UUID JSON array |
-| `--strategy_list` | json | No | Review-entry JSON array |
-| `--reason` | string | No | review reason |
-
-## Enum Notes
-
-### `--action`
-
-- `online`: publish strategy, requires `--strategy_uuid_list`
-- `offline`: take strategy offline, requires `--strategy_uuid_list`
-- `suspend`: suspend strategy, requires `--strategy_uuid_list`
-- `delete`: delete strategy, requires `--strategy_uuid_list`
-- `approve`: review approved, requires `--strategy_list`
-- `deny`: review denied, requires `--strategy_list`
-- `cancel`: cancel review, requires `--strategy_list`
-
-## JSON Parameter Notes
-
-### `--strategy_uuid_list`
-
-Used for actions such as `online`, `offline`, `suspend`, and `delete` that batch-process items directly by UUID.
-
-```json
-["uuid_1", "uuid_2"]
-```
-
-### `--strategy_list`
-
-Used for review actions such as `approve`, `deny`, and `cancel`. Each array item is an object:
-
-| Field | Type | Required | Description |
-|------|------|------|------|
-| `strategyUuid` | string | Yes | strategy UUID |
-| `reason` | string | No | review reason for that strategy |
-
-Examples: 
-
-```json
-[
-  { "strategyUuid": "uuid_1", "reason": "approve by ops" }
-]
-```
-
-## Safety Constraints
-
-This command is a **write operation** and changes the strategy status.
-
-Different `action` values require different parameters:
-
-- `online` / `offline` / `suspend` / `delete`: must include `--strategy_uuid_list`
-- `approve` / `deny` / `cancel`: must include `--strategy_list`
-
-## Examples
-
-```bash
-ae-cli engage +manage_strategy \
-  --project_id 1 --config_id cfg_123 --action online \
-  --strategy_uuid_list '["uuid_1"]'
-```