@thinkingai/ae-cli 1.0.1 → 1.0.3

package/skills/te-dataops/references/dataops-table.md

@@ -1,122 +1,122 @@
 ---
 name: dataops-table
 version: 1.0.0
-description: "数据表与视图管理：搜索表、查看表详情、创建物理表/视图、批量创建关联视图。触发关键词：建表、创建表、视图、数据字典、表详情、关联视图、linkview、datatable、DDL。"
+description: "Data table and view management: search tables, view table details, create physical tables/views, batch create linked views. Trigger keywords: create table, table creation, view, data dictionary, table details, linked view, linkview, datatable, DDL."
 metadata:
   requires:
-    bins: ["te-cli"]
+    bins: ["ae-cli"]
 ---
 
-# DataOps 数据表与视图管理
+# DataOps Data Table and View Management
 
-> **前置条件:** 阅读 [`te-dataops/SKILL.md`](../SKILL.md) 了解通用规则。
+> **Prerequisites:** Read [`te-dataops/SKILL.md`](../SKILL.md) for general rules.
 
-使用 `dataops_datatable` 子命令管理数据表。
+Use the `dataops_datatable` subcommand to manage data tables.
 
-**核心规则：**
-- 空间任务表的创建/修改/删除**必须用 dataops_datatable**，禁止用 dataops_ide
-- 创建前先确认同名表不存在
-- 创建视图或数据表时，按照 **Trino DDL 规范**生成 DDL
-- 任务表先创建 DEV 环境，再创建 PROD 环境（可同时创建）
+**Core Rules:**
+- Creating/modifying/deleting workspace task tables **must use dataops_datatable**, prohibited to use dataops_ide
+- Confirm no table with the same name exists before creation
+- When creating views or data tables, generate DDL according to **Trino DDL specifications**
+- Create task tables in DEV environment first, then PROD environment (can create simultaneously)
 
 ---
 
-## 工作流 A：搜索并查看表信息
+## Workflow A: Search and View Table Information
 
 ```bash
-# 在数据字典中搜索表（按表名/说明模糊匹配）
-te-cli dataops_datatable +dict_search_tables --spaceCode "${spaceCode}" --search "user" --maxResults 20
+# Search tables in data dictionary (fuzzy match by table name/description)
+ae-cli dataops_datatable +dict_search_tables --spaceCode "${spaceCode}" --search "user" --maxResults 20
 
-# 获取表的详细信息（字段、DDL、数据血缘）
-te-cli dataops_datatable +get_table_detail --spaceCode "${spaceCode}" --tableName "dwd_user_info"
+# Get detailed table information (fields, DDL, data lineage)
+ae-cli dataops_datatable +get_table_detail --spaceCode "${spaceCode}" --tableName "dwd_user_info"
 
-# 分页查询空间已注册的表列表
-te-cli dataops_datatable +list_tables_by_page --spaceCode "${spaceCode}" --search "user" --pageNum 1 --pageSize 20
+# Paginated query of registered tables in workspace
+ae-cli dataops_datatable +list_tables_by_page --spaceCode "${spaceCode}" --search "user" --pageNum 1 --pageSize 20
 
-# 按仓库维度获取表层级结构（repo→catalog→schema→tables）
-te-cli dataops_datatable +struct_by_repo --spaceCode "${spaceCode}"
+# Get table hierarchy by repository dimension (repo→catalog→schema→tables)
+ae-cli dataops_datatable +struct_by_repo --spaceCode "${spaceCode}"
 
-# 搜索系统表（事件表、用户表、维度表）
-te-cli dataops_datatable +list_system_tables --spaceCode "${spaceCode}" --projectName "my_project"
+# Search system tables (event tables, user tables, dimension tables)
+ae-cli dataops_datatable +list_system_tables --spaceCode "${spaceCode}" --projectName "my_project"
 ```
 
 ---
 
-## 工作流 B：创建物理表
+## Workflow B: Create Physical Table
 
 ```bash
-# Step 1: 确认同名表不存在
-te-cli dataops_datatable +dict_search_tables --spaceCode "${spaceCode}" --search "dwd_user_info"
+# Step 1: Confirm no table with same name exists
+ae-cli dataops_datatable +dict_search_tables --spaceCode "${spaceCode}" --search "dwd_user_info"
 
-# Step 2: 创建 DEV 环境的物理表（DDL 需遵循 Trino 规范）
-te-cli dataops_datatable +create_table --spaceCode "${spaceCode}" \
+# Step 2: Create physical table in DEV environment (DDL must follow Trino specifications)
+ae-cli dataops_datatable +create_table --spaceCode "${spaceCode}" \
   --ddl "CREATE TABLE dwd_user_info (user_id VARCHAR, user_name VARCHAR, age INTEGER) WITH (format = 'ORC')" \
   --repoCode "te_etl" --catalog "hive" --schema "ws_default_dev" --confirmed true
 
-# Step 3: 创建 PROD 环境的物理表（同样 DDL，schema 改为 product 库）
-te-cli dataops_datatable +create_table --spaceCode "${spaceCode}" \
+# Step 3: Create physical table in PROD environment (same DDL, change schema to product database)
+ae-cli dataops_datatable +create_table --spaceCode "${spaceCode}" \
   --ddl "CREATE TABLE dwd_user_info (user_id VARCHAR, user_name VARCHAR, age INTEGER) WITH (format = 'ORC')" \
   --repoCode "te_etl" --catalog "hive" --schema "ws_default_product" --confirmed true
 ```
 
 ---
 
-## 工作流 C：创建视图
+## Workflow C: Create View
 
 ```bash
-# Step 1: 确认同名视图不存在
-te-cli dataops_datatable +dict_search_tables --spaceCode "${spaceCode}" --search "v_user_info"
+# Step 1: Confirm no view with same name exists
+ae-cli dataops_datatable +dict_search_tables --spaceCode "${spaceCode}" --search "v_user_info"
 
-# Step 2: 创建视图（未指定视图名时默认用 v_${来源表名}）
-te-cli dataops_datatable +create_view --spaceCode "${spaceCode}" \
+# Step 2: Create view (defaults to v_${source_table_name} if view name not specified)
+ae-cli dataops_datatable +create_view --spaceCode "${spaceCode}" \
   --ddl "CREATE VIEW v_user_info AS SELECT user_id, user_name FROM hive.ws_default_dev.dwd_user_info" \
   --repoCode "te_etl" --catalog "hive" --schema "ws_default_dev" --confirmed true
 ```
 
 ---
 
-## 工作流 D：批量创建直连视图
+## Workflow D: Batch Create Linked Views
 
 ```bash
-# Step 1: 列出可用于创建关联视图的源表
-te-cli dataops_datatable +linkview_list_source_tables --spaceCode "${spaceCode}" \
+# Step 1: List source tables available for creating linked views
+ae-cli dataops_datatable +linkview_list_source_tables --spaceCode "${spaceCode}" \
   --srcRepoCode "te_etl" --srcCatalog "hive" --srcSchema "ws_default_hidden"
 
-# Step 2: 批量创建直连视图（异步执行）
-te-cli dataops_datatable +batch_create --spaceCode "${spaceCode}" \
+# Step 2: Batch create linked views (async execution)
+ae-cli dataops_datatable +batch_create --spaceCode "${spaceCode}" \
   --srcRepoCode "te_etl" --srcCatalog "hive" --srcSchema "ws_default_hidden" \
   --processType 2 --batchCreationMode 1 --owner "${ownerOpenId}" \
   --viewInfos '[{"viewName":"v_orders","srcTableName":"ta_event_123","srcTableType":"TABLE"}]' \
   --confirmed true
 
-# Step 3: 轮询批量创建状态（建议 3-5 秒间隔）
+# Step 3: Poll batch creation status (recommend 3-5 second interval)
 # status: WAIT / RUNNING / SUCCESS / STOP
-te-cli dataops_datatable +linkview_get_batch_status --spaceCode "${spaceCode}" --batchId "${batchId}"
+ae-cli dataops_datatable +linkview_get_batch_status --spaceCode "${spaceCode}" --batchId "${batchId}"
 
-# 查看历史批量创建记录
-te-cli dataops_datatable +list_batches --spaceCode "${spaceCode}"
+# View historical batch creation records
+ae-cli dataops_datatable +list_batches --spaceCode "${spaceCode}"
 ```
 
 ---
 
-## 命令速查
-
-| 命令 | 用途 | 关键 Flags |
-|------|------|-----------|
-| `+dict_search_tables` | 数据字典搜索 | `--spaceCode` `--search` `--maxResults` |
-| `+get_table_detail` | 表详情 | `--spaceCode` `--tableName` |
-| `+list_tables_by_page` | 分页列表 | `--spaceCode` `--search` `--pageNum` `--pageSize` |
-| `+struct_by_repo` | 按仓库层级 | `--spaceCode` `--search` |
-| `+list_system_tables` | 系统表列表 | `--spaceCode` `--projectId`/`--projectName` `--pageNum` `--pageSize` |
-| `+create_table` | 创建物理表 | `--spaceCode` `--ddl` `--repoCode` `--catalog` `--schema` `--confirmed` |
-| `+create_view` | 创建视图 | `--spaceCode` `--ddl` `--repoCode` `--catalog` `--schema` `--confirmed` |
-| `+batch_create` | 批量创建视图 | `--spaceCode` `--srcRepoCode` `--srcCatalog` `--srcSchema` `--processType` `--batchCreationMode` `--owner` `--viewInfos` `--confirmed` |
-| `+linkview_get_batch_status` | 批量创建状态 | `--spaceCode` `--batchId` |
-| `+list_batches` | 历史批量记录 | `--spaceCode` `--status` |
-
-## 参数说明
-
-- **schema 命名**: DEV 环境用 `ws_${spaceCode}_dev`，PROD 环境用 `ws_${spaceCode}_product`
-- **processType**: `1`=仅 DEV | `2`=DEV+PROD
-- **batchCreationMode**: `1`=全量同步 | `2`=失败重试
-- **表名规则**: `^[a-z][0-9a-z_]{0,127}$`
+## Command Quick Reference
+
+| Command | Purpose | Key Flags |
+|---------|---------|-----------|
+| `+dict_search_tables` | Data dictionary search | `--spaceCode` `--search` `--maxResults` |
+| `+get_table_detail` | Table details | `--spaceCode` `--tableName` |
+| `+list_tables_by_page` | Paginated list | `--spaceCode` `--search` `--pageNum` `--pageSize` |
+| `+struct_by_repo` | By repository hierarchy | `--spaceCode` `--search` |
+| `+list_system_tables` | System table list | `--spaceCode` `--projectId`/`--projectName` `--pageNum` `--pageSize` |
+| `+create_table` | Create physical table | `--spaceCode` `--ddl` `--repoCode` `--catalog` `--schema` `--confirmed` |
+| `+create_view` | Create view | `--spaceCode` `--ddl` `--repoCode` `--catalog` `--schema` `--confirmed` |
+| `+batch_create` | Batch create views | `--spaceCode` `--srcRepoCode` `--srcCatalog` `--srcSchema` `--processType` `--batchCreationMode` `--owner` `--viewInfos` `--confirmed` |
+| `+linkview_get_batch_status` | Batch creation status | `--spaceCode` `--batchId` |
+| `+list_batches` | Historical batch records | `--spaceCode` `--status` |
+
+## Parameter Notes
+
+- **schema naming**: DEV environment uses `ws_${spaceCode}_dev`, PROD environment uses `ws_${spaceCode}_product`
+- **processType**: `1`=DEV only | `2`=DEV+PROD
+- **batchCreationMode**: `1`=full sync | `2`=retry failures
+- **Table name rule**: `^[a-z][0-9a-z_]{0,127}$`

package/skills/te-engage/SKILL.md

@@ -1,211 +1,211 @@
 ---
 name: te-engage
 version: 1.0.0
-description: "TE Engage MCP：配置项、流程、渠道设置、任务数据查询与管理"
+description: "TE Engage MCP: config items, flows, channel settings, task data query, and management"
 metadata:
   requires:
-    bins: ["te-cli"]
-  cliHelp: "te-cli te-engage --help"
+    bins: ["ae-cli"]
+  cliHelp: "ae-cli engage --help"
 ---
 
 # te-engage
 
-> **前置条件:** 阅读 [`../te-shared/SKILL.md`](../te-shared/SKILL.md) 了解认证、全局参数和安全约束。
+> **Prerequisite:** Read [`../te-shared/SKILL.md`](../te-shared/SKILL.md) for authentication, global parameters, and safety constraints.
 
-## 概述
+## Overview
 
-`te-engage` 域提供 Hermes Engage MCP 能力，覆盖配置项、流程、渠道设置和任务数据。命令通过 `te-cli te-engage <command>` 调用。
+The `te-engage` package provides Hermes Engage MCP capabilities across config items, flows, channel settings, and task data. Commands are invoked through `ae-cli engage <command>`.
 
-适合的场景包括：
+Typical use cases include:
 
-- 查询和管理渠道、配置通道、审批人、白名单
-- 查询任务列表、任务详情、实验报表、指标报表
-- 查询配置项与策略、复制模板、管理策略状态
-- 查询流程列表、节点 schema、流程报表，以及保存/管理流程
+- Querying and managing channels, config channels, approvers, and whitelists
+- Querying task lists, task details, experiment reports, and metric reports
+- Querying config items and strategies, copying templates, and managing strategy status
+- Querying flow lists, node schemas, and flow reports, and saving or managing flows
 
-## 参数约定
+## Parameter Conventions
 
-- 简单参数直接使用普通 flags，例如 `--project-id`、`--task-id`、`--flow-uuid`
-- 数组参数使用 JSON flags，例如 `--strategy-id-list '["id1","id2"]'`
-- 对象参数使用具名 JSON flags，例如 `--req '{...}'`、`--flow-list '[...]'`
-- 可选全局参数仍可与其他 domain 一样使用，例如 `--host`、`--mcp-url`、`--dry-run`
+- Use regular flags for simple parameters, for example `--project_id`, `--task_id`, and `--flow_uuid`
+- Use JSON flags for array parameters, for example `--strategy_id_list '["id1","id2"]'`
+- Use named JSON flags for object parameters, for example `--req '{...}'` and `--flow_list '[...]'`
+- Optional global parameters work the same way as in other domains, for example `--host`, `--mcp-url`, and `--dry-run`
 
-## JSON 参数格式
+## JSON Parameter Format
 
-常见 JSON flags 示例：
+Common JSON flag examples:
 
 ```bash
---provider-list '["webhook","fcm"]'
---strategy-id-list '["strategy_a","strategy_b"]'
---flow-id-list '["flow_1","flow_2"]'
+--provider_list '["webhook","fcm"]'
+--strategy_id_list '["strategy_a","strategy_b"]'
+--flow_id_list '["flow_1","flow_2"]'
 --req '{"pageNum":1,"pageSize":20}'
 ```
 
-## 常见场景
+## Common Scenarios
 
 ### 1. setting
 
 ```bash
-# 查询渠道列表
-te-cli te-engage +channel-list --project-id 1
+# Query the channel list
+ae-cli engage +channel_list --project_id 1
 
-# 过滤 provider
-te-cli te-engage +channel-list --project-id 1 --provider-list '["webhook","fcm"]'
+# Filter by provider
+ae-cli engage +channel_list --project_id 1 --provider_list '["webhook","fcm"]'
 
-# 查询 config channel
-te-cli te-engage +config-channel-list --project-id 1
+# Query config channels
+ae-cli engage +config_channel_list --project_id 1
 ```
 
 ### 2. task
 
 ```bash
-# 查询任务列表
-te-cli te-engage +task-list --project-id 1 --req '{"pageNum":1,"pageSize":20}'
+# Query the task list
+ae-cli engage +task_list --project_id 1 --req '{"pageNum":1,"pageSize":20}'
 
-# 查询任务详情
-te-cli te-engage +task-detail --project-id 1 --task-id task_123
+# Query task details
+ae-cli engage +task_detail --project_id 1 --task_id task_123
 
-# 查询任务概览
-te-cli te-engage +task-data-overview --project-id 1 --task-id task_123 --task-type normal
+# Query the task overview
+ae-cli engage +task_data_overview --project_id 1 --task_id task_123 --task_type normal
 ```
 
 ### 3. config
 
 ```bash
-# 查询配置项列表
-te-cli te-engage +config-item-list --project-id 1
+# Query the config item list
+ae-cli engage +config_item_list --project_id 1
 
-# 查询策略列表
-te-cli te-engage +strategy-list --project-id 1 --config-id cfg_123
+# Query the strategy list
+ae-cli engage +strategy_list --project_id 1 --config_id cfg_123
 
-# 查询配置项报表
-te-cli te-engage +config-item-trigger-report \
-  --project-id 1 --config-id cfg_123 \
-  --start-time 2026-04-01 --end-time 2026-04-07
+# Query a config item report
+ae-cli engage +config_item_trigger_report \
+  --project_id 1 --config_id cfg_123 \
+  --start_time 2026-04-01 --end_time 2026-04-07
 ```
 
 ### 4. flow
 
 ```bash
-# 查询流程列表
-te-cli te-engage +flow-list --project-id 1
+# Query the flow list
+ae-cli engage +flow_list --project_id 1
 
-# 查询流程详情
-te-cli te-engage +flow-detail --project-id 1 --flow-uuid flow_uuid_123
+# Query flow details
+ae-cli engage +flow_detail --project_id 1 --flow_uuid flow_uuid_123
 
-# 查询节点 schema
-te-cli te-engage +flow-node-config-schema --node-type message_push
+# Query the node schema
+ae-cli engage +flow_node_config_schema --node_type message_push
 ```
 
-## `+save-flow` 关键约束
+## `+save_flow` Critical Constraints
 
-当用户要“创建流程 / 生成流程画布 / 保存流程”时，不要把 `+save-flow` 当成普通单命令直接调用，必须按下面流程执行。
+When the user wants to "create a flow / generate a flow canvas / save a flow", do not treat `+save_flow` as a normal single command. You must follow the workflow below.
 
-### 必须遵守的工作流
+### Required Workflow
 
-1. 先确认用户意图已经足够明确，至少要有：
-   - 业务场景
-   - 目标用户
-   - 触达方式
-   - 是否分流，以及分流条件
-2. 不要从自然语言直接跳到 `--req`，必须先整理出稳定的中间意图结构，再映射成最终 `req`。
-3. 在构造条件相关节点前，必须先调用：
+1. First confirm that the user intent is specific enough. At minimum you need:
+   - The business scenario
+   - The target users
+   - The touchpoint or delivery method
+   - Whether branching is needed, and the branching conditions
+2. Do not jump directly from natural language to `--req`. You must first organize a stable intermediate intent structure, then map it to the final `req`.
+3. Before building any condition-related nodes, you must call:
 
 ```bash
-te-cli te_audience +get_cluster_definition_schema --cluster_type condition
+ae-cli analysis_audience +get_cluster_definition_schema --cluster_type condition
 ```
 
-4. 在构造 `message_push`、`wechat_push`、`webhook_push` 等触达节点前，必须先调用：
+4. Before building touchpoint nodes such as `message_push`, `wechat_push`, or `webhook_push`, you must call:
 
 ```bash
-te-cli te-engage +channel-list --project-id <projectId>
+ae-cli engage +channel_list --project_id <projectId>
 ```
 
-5. `+save-flow` 的最终 `--req` 必须是完整画布请求体，而不是意图描述。至少应包含：
+5. The final `--req` for `+save_flow` must be the complete canvas request payload, not an intent description. It must contain at least:
    - `flowName`
    - `flowDesc`
    - `nodeList`
    - `edgeList`
-6. `nodeList[].config` 和 `edgeList[].config` 必须是 JSON 字符串，不是 JSON 对象。
-7. `targetClusterQp` 如果出现在节点 `config` 中，其值通常也应是再次 `JSON.stringify` 后的字符串，而不是原始对象。
-8. 提交前必须自检：
-   - 只有一个入口节点
-   - 至少一个 `exit_flow`
-   - `edge.source` / `edge.target` 都引用有效节点
-   - 分支节点的 `sourceBranchId` 已在上游节点 `config` 中声明
-   - 整张图是 DAG，不能有环
+6. `nodeList[].config` and `edgeList[].config` must be JSON strings, not JSON objects.
+7. If `targetClusterQp` appears inside a node `config`, its value should usually also be a string produced by `JSON.stringify`, not a raw object.
+8. You must self-check before submitting:
+   - There is exactly one entry node
+   - There is at least one `exit_flow`
+   - `edge.source` and `edge.target` both reference valid nodes
+   - Any branch node `sourceBranchId` has already been declared in the upstream node `config`
+   - The whole graph is a DAG and contains no cycles
 
-### 明确禁止
+### Explicitly Forbidden
 
-- 不要凭空编造 `channelId`
-- 不要在用户信息不足时自行脑补分流逻辑
-- 不要把业务语义节点直接当成最终 `nodeList` 节点提交
-- 不要把 `config` 写成对象后直接塞进 `--req`
+- Do not invent a `channelId`
+- Do not fill in branching logic when the user has not provided enough information
+- Do not submit business-semantic nodes directly as final `nodeList` nodes
+- Do not put `config` into `--req` as an object
 
-### 推荐顺序
+### Recommended Order
 
 ```text
-用户需求
--> 整理意图
--> te_audience +get_cluster_definition_schema --cluster_type condition
--> +channel-list --project-id <projectId>
--> 构造 nodeList / edgeList
--> 自检
--> +save-flow
+User request
+-> Organize intent
+-> analysis_audience +get_cluster_definition_schema --cluster_type condition
+-> +channel_list --project_id <projectId>
+-> Build nodeList / edgeList
+-> Self-check
+-> +save_flow
 ```
 
-更细的生成规则优先参考：
+For more detailed generation rules, consult these references first:
 
 - `references/save-flow.md`
 - `references/flow-node-config-schema.md`
 - `references/validate-flow-node-config.md`
 
-## dry-run 调试
+## Dry-Run Debugging
 
 ```bash
-te-cli --dry-run te-engage +channel-list --project-id 1
-te-cli --dry-run te-engage +task-list --project-id 1 --req '{"pageNum":1,"pageSize":20}'
-te-cli --dry-run te-engage +flow-list --project-id 1
+ae-cli --dry-run engage +channel_list --project_id 1
+ae-cli --dry-run engage +task_list --project_id 1 --req '{"pageNum":1,"pageSize":20}'
+ae-cli --dry-run engage +flow_list --project_id 1
 ```
 
 ## References
 
-更细的单命令说明见按业务拆分的 `references/` 目录：
+More detailed single-command guidance is available in the business-oriented `references/` directory:
 
 - `references/channel-list.md`
 - `references/task-list.md`
 - `references/config-item-list.md`
 - `references/flow-list.md`
 
-这种拆包方式更适合后续继续扩展，因为对象入参较复杂的命令会集中在 `references/` 根目录维护。
+This split documentation structure is easier to extend later, because commands with more complex object inputs can stay centralized in the `references/` root directory.
 
-## 命令分组
+## Command Groups
 
 ### setting
 
-`+channel-list`, `+channel-detail`, `+update-channel-status`, `+delete-channel`, `+add-channel`, `+whitelist-list`, `+add-approver`, `+approver-list`, `+cancel-query-by-request-id`, `+config-channel-detail`, `+config-channel-list`, `+delete-config-channel`, `+update-config-channel-status`
+`+channel_list`, `+channel_detail`, `+update_channel_status`, `+delete_channel`, `+add_channel`, `+whitelist_list`, `+add_approver`, `+approver_list`, `+cancel_query_by_request_id`, `+config_channel_detail`, `+config_channel_list`, `+delete_config_channel`, `+update_config_channel_status`
 
 ### task
 
-`+task-data-overview`, `+task-data-detail`, `+task-metric-detail`, `+task-experiment-report`, `+task-detail`, `+task-list`, `+task-stats`, `+manage-task`
+`+task_data_overview`, `+task_data_detail`, `+task_metric_detail`, `+task_experiment_report`, `+task_detail`, `+task_list`, `+task_stats`, `+manage_task`
 
 ### config
 
-`+config-item-trigger-report`, `+config-item-analysis-report`, `+config-item-strategy-comparison`, `+config-item-list`, `+config-item-detail`, `+delete-config-item`, `+copy-config-template`, `+strategy-list`, `+strategy-detail`, `+manage-strategy`
+`+config_item_trigger_report`, `+config_item_analysis_report`, `+config_item_strategy_comparison`, `+config_item_list`, `+config_item_detail`, `+delete_config_item`, `+copy_config_template`, `+strategy_list`, `+strategy_detail`, `+manage_strategy`
 
 ### flow
 
-`+save-flow`, `+flow-node-config-schema`, `+flow-detail`, `+flow-list`, `+flow-node-overview-report`, `+manage-flow`, `+flow-ab-split-node-report`, `+flow-process-report`, `+validate-flow-node-config`, `+flow-node-detail-report`, `+delete-flow`, `+modify-flow-base-info`
+`+save_flow`, `+flow_node_config_schema`, `+flow_detail`, `+flow_list`, `+flow_node_overview_report`, `+manage_flow`, `+flow_ab_split_node_report`, `+flow_process_report`, `+validate_flow_node_config`, `+flow_node_detail_report`, `+delete_flow`, `+modify_flow_base_info`
 
-## 日期格式
+## Date Format
 
-涉及日期参数的命令通常使用 `yyyy-MM-dd`，例如 `--start-time 2026-04-01`。
+Commands that accept date parameters usually use `yyyy-MM-dd`, for example `--start_time 2026-04-01`.
 
-## 写操作提醒
+## Write Operation Reminder
 
-以下命令属于写操作，执行前应确认用户明确意图：
+The following commands are write operations. Confirm that the user intent is explicit before executing them:
 
-- 渠道与配置通道：`+add-channel`, `+delete-channel`, `+update-channel-status`, `+delete-config-channel`, `+update-config-channel-status`
-- 策略与配置项：`+delete-config-item`, `+copy-config-template`, `+manage-strategy`
-- 流程：`+save-flow`, `+modify-flow-base-info`, `+manage-flow`, `+delete-flow`
-- 任务：`+manage-task`
+- Channels and config channels: `+add_channel`, `+delete_channel`, `+update_channel_status`, `+delete_config_channel`, `+update_config_channel_status`
+- Strategies and config items: `+delete_config_item`, `+copy_config_template`, `+manage_strategy`
+- Flows: `+save_flow`, `+modify_flow_base_info`, `+manage_flow`, `+delete_flow`
+- Tasks: `+manage_task`

package/skills/te-engage/references/add-approver.md

@@ -1,24 +1,24 @@
-# te-engage +add-approver
+# te-engage +add_approver
 
-> **前置条件:** 阅读 [`../../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Read [`../../te-shared/SKILL.md`](../../te-shared/SKILL.md)
 
-批量添加审批人。
+Batch add approvers.
 
-映射命令: `te-cli te-engage +add-approver`
+Mapped command: `ae-cli engage +add_approver`
 
 ## Flags
 
-| Flag | 类型 | 必填 | 说明 |
+| Flag | Type | Required | Description |
 |------|------|------|------|
-| `--project-id` / `-p` | number | 是 | 项目 ID |
-| `--approvers` | json | 是 | 审批人 open ID JSON 数组 |
+| `--project_id` / `-p` | number | Yes | Project ID |
+| `--approvers` | json | Yes | approver open ID JSON array |
 
-## 安全约束
+## Safety Constraints
 
-此命令为 **写操作**，会修改项目审批人配置。
+This command is a **write operation** and and modifies the project approver configuration.
 
-## 示例
+## Examples
 
 ```bash
-te-cli te-engage +add-approver --project-id 1 --approvers '["ou_xxx","ou_yyy"]'
+ae-cli engage +add_approver --project_id 1 --approvers '["ou_xxx","ou_yyy"]'
 ```