@thinkingai/ae-cli 6.0.33 → 6.0.35

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-generate-tracking-code/SKILL.md

@@ -34,7 +34,7 @@ description: "Interactive generation of AE tracking code, LogBus2 configuration,
 | LogBus2 配置 | LogBus2 Configuration | `daemon.json` for LogBus2 log sync tool |
 | LoggerConsumer | LoggerConsumer | Server SDK consumer that writes events to local log files |
 | BatchConsumer | BatchConsumer | Server SDK consumer that uploads events in batches |
-| 公共属性 | Super Property | Properties attached to all events automatically |
+| 公共属性 | Super Property | Properties attached to all events automatically. ⚠️ The correct Chinese AE term is "公共属性" or "公共事件属性". Never translate "Super Property" as "超级属性" — that is NOT a valid AE term. |
 | 预置属性 | Preset Property | System properties prefixed with `#` (e.g. `#device_id`, `#time`) |
 | 事件属性 | Event Property | Custom properties on specific events |
 | 用户属性 | User Property | Properties set on the user profile |
@@ -91,12 +91,12 @@ First, check if `.ae-cli/draft.json` exists and read existing configuration:
 **⚠️ Key: SERVER_URL and APP_ID are independent config items. Even if draft.json has project_id and host, you MUST resolve and confirm them. `project_id` ≠ `APP_ID`, `host` ≠ `SERVER_URL`.**
 
 1. **APP_ID** — Prefer automatic lookup before asking:
-   - If `meta.project_id` is known, run `ae-cli analysis_common +list_projects` once for the current host.
+   - If `meta.project_id` is known, run `ae-cli analysis project info list` once for the current host.
    - Find the project whose `projectId` matches `meta.project_id`.
    - If the matched project has `appId`, ask: **"I found APP_ID `<appId>` for project `<projectId>`. Use it? yes / enter new value"**
    - If the project is missing, ambiguous, or has no `appId`, ask the user to copy APP_ID from AE Admin → "Project Settings" → "Integration Config".
 2. **SERVER_URL** — Data ingestion endpoint (**different from web URL**; go to AE Admin → "Project Settings" → "Integration Config" → fill in "Public URL")
-   - If `meta.project_id` is known, you may try `ae-cli analysis_meta +get_project_config --project_id <project_id>` once.
+   - If `meta.project_id` is known, you may try `ae-cli analysis project info get --project-id <project_id>` once.
    - Use the returned value only if the response explicitly contains a receiver URL field such as `serverUrl`, `pushUrl`, `push_url`, `receiverUrl`, `publicUrl`, `publicReceiverAddress`, `privateReceiverAddress`, or equivalent ingestion endpoint field.
    - If both `publicReceiverAddress` and `privateReceiverAddress` are present, prefer `publicReceiverAddress` as `SERVER_URL` for generated snippets unless the user explicitly needs an internal/private-network receiver.
    - If a value is found, ask: **"I found SERVER_URL `<url>` for project `<projectId>`. Use it? yes / enter new value"**
@@ -646,6 +646,7 @@ Validation steps:
 - Including `platform === "server"` exclusive events in client code
 - Including `platform === "client"` exclusive events in server code (unless `platform === "both"`)
 - **Skipping SDK main doc read and guessing integration method** — each SDK has different integration approaches; must read wiki main doc's "Integrate SDK" section first, and choose the correct method based on project characteristics (with/without build tools)
+- **Translating "Super Property" as "超级属性" in any user-facing output (code comments, interaction prompts, markdown) — the correct AE Chinese term is "公共事件属性" or "公共属性"**
 - **Entering Phase 1 before Phase 0.5 is complete** — SDK integration must be confirmed before inserting code, otherwise generated track() calls won't work
 
 ---

package/skills/ae-generate-tracking-code/references/client-sdk-insert.md

@@ -1,6 +1,6 @@
 # Mode A — Client SDK Code Insertion
 
-> **Terminology**: 客户端 SDK = client SDK | 代码插入 = code insertion/injection | 前置检查 = pre-check | 集成方式 = integration method | 埋点 = tracking/event tracking | 业务触发点 = business trigger point | 公共属性 = super property | 用户属性 = user property | 自动采集事件 = auto-track event | 插入位置预览 = insertion site preview | 语言风格校验 = language style check
+> **Terminology**: 客户端 SDK = client SDK | 代码插入 = code insertion/injection | 前置检查 = pre-check | 集成方式 = integration method | 埋点 = tracking/event tracking | 业务触发点 = business trigger point | 公共属性 = super property (公共事件属性; never "超级属性") | 用户属性 = user property | 自动采集事件 = auto-track event | 插入位置预览 = insertion site preview | 语言风格校验 = language style check
 
 ## ⚠️ Mandatory Pre-checks (do not skip)
 

package/skills/ae-generate-tracking-code/references/server-sdk-insert.md

@@ -1,6 +1,6 @@
 # Server-side Code Insertion (LoggerConsumer + LogBus2)
 
-> **Terminology**: 服务端 SDK = server-side SDK | 代码插入 = code insertion/injection | LoggerConsumer = writes events to local log files (recommended for production) | LogBus2 = log sync tool that reads local logs and uploads to TE | 架构 = architecture | 异步上报 = async upload | 批量上传 = batch upload | 重试策略 = retry strategy | 公共属性 = super property | 用户属性 = user property | 依赖管理 = dependency management
+> **Terminology**: 服务端 SDK = server-side SDK | 代码插入 = code insertion/injection | LoggerConsumer = writes events to local log files (recommended for production) | LogBus2 = log sync tool that reads local logs and uploads to TE | 架构 = architecture | 异步上报 = async upload | 批量上传 = batch upload | 重试策略 = retry strategy | 公共属性 = super property (公共事件属性; never "超级属性") | 用户属性 = user property | 依赖管理 = dependency management
 
 ## Architecture
 

package/skills/ae-generate-tracking-code/references/snippet-delivery.md

@@ -1,6 +1,6 @@
 # Snippet Output Mode
 
-> **Terminology**: 片段/代码片段 = snippet/code snippet | 产物 = deliverable/output | markdown 响应 = markdown response | 初始化 = initialization | 公共属性 = super property | 用户属性 = user property | 事件组 = event group | 触发时机 = trigger timing | 验证步骤 = verification steps | 设备绑定 = device binding | 自动采集事件 = auto-track event | 占位值 = placeholder value | 属性类型 = property type
+> **Terminology**: 片段/代码片段 = snippet/code snippet | 产物 = deliverable/output | markdown 响应 = markdown response | 初始化 = initialization | 公共属性 = super property (公共事件属性; never "超级属性") | 用户属性 = user property | 事件组 = event group | 触发时机 = trigger timing | 验证步骤 = verification steps | 设备绑定 = device binding | 自动采集事件 = auto-track event | 占位值 = placeholder value | 属性类型 = property type
 
 ## Deliverables
 

package/skills/ae-generate-tracking-plan/SKILL.md

@@ -29,7 +29,7 @@ description: "Interactive generation of an AE tracking plan and upload. Trigger
 | 货币体系 | Currency System | Hard currency (diamonds), soft currency (gold), etc. |
 | 事件 | Event | Named user action or system occurrence (`event_name`) |
 | 事件属性 | Event Property | Data attached to an event (`prop_names`) |
-| 公共事件属性 | Common/Super Property | Property attached to every event automatically |
+| 公共事件属性 | Common/Super Property | Property attached to every event automatically. ⚠️ The correct Chinese AE term is "公共事件属性" or "公共属性". Never translate "Super Property" as "超级属性" — that is NOT a valid AE term. |
 | 用户属性 | User Property | Property on the user profile (persistent state) |
 | 预置属性 | Preset Property | System property prefixed with `#` (`#device_id`, `#time`, etc.) |
 | 自动采集事件 | Auto-track Event | SDK auto-collected events (`ta_app_start`, `ta_page_show`, etc.) |
@@ -700,7 +700,10 @@ Based on SDK integration mode collected in Phase 0, decide whether to inject aut
 3. Auto-track event `event_tag` set to `"System Event"`
 4. Auto-track events only carry preset properties (`prop_names` is empty or contains only preset property names)
 5. Preset properties prefixed with `#` are not added to `event_properties` pool (auto-collected by SDK)
-6. **Deduplication**: Templates may already contain same-name auto-track events (e.g. `ta_app_start` marked `source: "template"`); CLI deduplicates by event name globally and will not inject duplicates
+6. **Cleanup + Deduplication**: The CLI will:
+   - **Remove** auto-track events inherited from templates or existing plans that don't match the user's selected SDKs. For example: if a template built for Android/iOS contains `ta_app_install`, `ta_app_start`, `ta_app_end` but the user selects JavaScript SDK, those `ta_app_*` events will be automatically removed since JavaScript SDK does not support them.
+   - **Inject** the correct auto-track events for the user's selected SDKs.
+   - **Deduplicate** by event name globally — won't inject events that already exist in the draft (correct auto-track events inherited from templates are kept).
 
 **SDK type → Recommended events** (see `references/autotrack-events.md` for details):
 
@@ -1300,6 +1303,7 @@ The tracking plan has been uploaded successfully. Would you like to generate tra
 - Asking all anchor questions at once
 - Skipping Phase 3 and uploading directly
 - Manually assembling xlsx bypassing `.ae-cli/draft.json`
+- Translating "Super Property" as "超级属性" in any user-facing output (interaction prompts, plan summaries, event/property descriptions) — the correct AE Chinese term is "公共事件属性" or "公共属性"
 - Calling `fetch` AE API directly within the skill — all AE communication must go through project scripts / CLI
 
 ---

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-metadata/SKILL.md

@@ -1,14 +1,14 @@
 ---
 name: ae-metadata
 version: 1.0.0
-description: "AE/TE metadata capability-gateway CLI: metadata event/property detail, data-table management, and property dimension-table binding. Metadata CLI routes through the analysis gateway. Input-file upload belongs to ae-analysis."
+description: "AE/TE metadata capability-gateway CLI: metadata data-table management and property dimension-table binding. Metadata CLI routes through the analysis gateway. Input-file upload and event/property detail belong to ae-analysis."
 ---
 
 # ae-metadata
 
 CLI domain **`metadata`** routes to the analysis capability gateway (`/api/cli/analysis/v1/...`), using auth header **`cli-token`**.
 
-Parallel to **`ae-analysis`** (MCP `analysis_meta` for metadata lists/governance). Use **this skill** for gateway-backed metadata detail and data-table/dimension-table operations; use **`ae-analysis`** for MCP metadata list/search, metrics, virtual create, and batch edit.
+Parallel to **`ae-analysis`**. Use **this skill** for gateway-backed metadata detail and data-table/dimension-table operations; use **`ae-analysis`** for metadata list/search, metrics, virtual create, and batch edit.
 
 ## Global AE CLI Rules
 
@@ -16,7 +16,7 @@ Parallel to **`ae-analysis`** (MCP `analysis_meta` for metadata lists/governance
 |---|---|
 | `--format <json\|table>` | Output format. Default JSON. |
 | `--jq <expr>` | jq filter on JSON output. |
-| `--host <url>` | Override active AE host, e.g. `ae-cli metadata event get --host <url> ...`. |
+| `--host <url>` | Override active AE host, e.g. `ae-cli metadata data-table list --host <url> ...`. |
 | `--validate` | Optional: fix params only (`/validate`). Alone while iterating complex `qp` / payload — then run. Do not stack with `--dry-run`. |
 | `--dry-run` | Optional: confirm ready to run (`/dry-run`). Alone for risk/output preview. Do not stack with `--validate`. |
 
@@ -28,20 +28,18 @@ Output and errors:
 Safety:
 - Read-only commands can run directly after IDs/names are verified.
 - Ordinary writes (`data-table *-write`, `property-bindings-update`, dimension-table bind/create) execute without `--yes`. Delete commands are `high-risk-write`: dry-run first, summarize impact, wait for explicit confirmation, then execute with `--yes`.
-- **Before any command**, read the matching `references/<name>.md` (filename = command with spaces → underscores, e.g. `metadata event get` → `metadata_event_get.md`).
+- **Before any command**, read the matching `references/<name>.md` (filename = command with spaces → underscores, e.g. `metadata data-table list` → `metadata_data_table_list.md`).
 - Never invent `project_id`, event/property names, `input_file_id`, or `data_table_id`. Discover names via `ae-analysis` and data table IDs via `metadata data-table list`.
 
 ## When to Use
 
 Switch to **`ae-metadata`** when the user needs:
 
-- Full detail for **one** super-event (incl. virtual event `definition`)
-- Full detail for **one** super-property (incl. virtual property `definition`)
 - Metadata data-table list/get/create/update/delete/download
 - For local uploads, switch to `ae-analysis` and use `analysis input-file upload` with a discovered purpose.
 - Bind an existing data table to a property, or create a CSV dimension table and bind it
 
-Stay on **`ae-analysis`** for: metadata event/property/metric list/search, metric CRUD, batch metadata, virtual create, project config, tracking plans.
+Stay on **`ae-analysis`** for: metadata event/property detail, metadata event/property/metric list/search, metric CRUD, batch metadata, virtual create, project config, tracking plans.
 
 ## Command Format
 
@@ -55,14 +53,12 @@ ae-cli metadata property <dimension-table-action> [options]
 
 ## PROJECT_ID_GATE
 
-Same rules as `ae-analysis`: reuse verified project context in one conversation; otherwise `ae-cli analysis_common +list_projects` (or `ae-analysis` skill) to resolve `project_id`.
+Same rules as `ae-analysis`: reuse verified project context in one conversation; otherwise `ae-cli analysis project info list` (or `ae-analysis` skill) to resolve `project_id`.
 
-## Commands (12)
+## Commands (10)
 
 | User command | Capability id | Reference |
 |---|---|---|
-| `metadata event get` | `metadata.event.get` | [metadata_event_get.md](references/metadata_event_get.md) |
-| `metadata property get` | `metadata.property.get` | [metadata_property_get.md](references/metadata_property_get.md) |
 | `metadata data-table list` | `metadata.data_table.list` | [metadata_data_table_list.md](references/metadata_data_table_list.md) |
 | `metadata data-table get` | `metadata.data_table.get` | [metadata_data_table_get.md](references/metadata_data_table_get.md) |
 | `metadata data-table csv-write` | `metadata.data_table.csv_write` | [metadata_data_table_csv_write.md](references/metadata_data_table_csv_write.md) |
@@ -78,15 +74,12 @@ Same rules as `ae-analysis`: reuse verified project context in one conversation;
 
 ```bash
 ae-cli metadata --help
-ae-cli metadata event get --help
-ae-cli metadata property get --help
 ae-cli metadata data-table list --help
-ae-cli metadata event get --project-id 1 --event-name <name> --dry-run
 ae-cli metadata data-table list --project-id 1 --dry-run
 ae-cli analysis input-file purpose list --project-id 1
 ```
 
 ## Related Skills
 
-- **`ae-analysis`**: `analysis-meta event list` / `analysis-meta property list` to discover names before detail get.
+- **`ae-analysis`**: `analysis-meta event get` / `analysis-meta property get` for detail, and `analysis-meta event list` / `analysis-meta property list` to discover names.
 - **Dev workflow**: `.cursor/skills/te-cli-capability-gateway` — inspect gateway schema when adding new metadata capabilities.

package/skills/ae-metadata/references/metadata_property_dimension_table_bind_existing.md

@@ -22,6 +22,6 @@ ae-cli metadata property bind-existing-dimension-table --project-id <project_id>
 
 ## Decision Rules
 
-- Confirm the property with `metadata property get` or `analysis-meta property list`.
+- Confirm the property with `analysis-meta property get` or `analysis-meta property list`.
 - Confirm the data table with `metadata data-table get`.
 - This is an ordinary `write` command and does not require CLI confirmation.

package/dist/te-common-ST3QPSXJ.js

@@ -1,61 +0,0 @@
-import {
-  callMcpTool,
-  parseMcpResult,
-  resolveMcpUrl
-} from "./chunk-3P3562ZX.js";
-import "./chunk-LCXU3AAT.js";
-import "./chunk-E7UXXHO3.js";
-import "./chunk-IR4ZLVPW.js";
-import "./chunk-V6FR6WTW.js";
-import "./chunk-24BAVOX3.js";
-import "./chunk-LYVNONC4.js";
-
-// src/commands/te-common/shared.ts
-function createMcpCommand(config) {
-  const toolName = config.command.slice(1);
-  const mcpService = config.mcpService || "analysis";
-  return {
-    service: "analysis_common",
-    command: config.command,
-    description: config.description,
-    flags: config.flags,
-    risk: config.risk,
-    dryRun: (ctx) => ({
-      method: "tools/call",
-      url: resolveMcpUrl(ctx.mcpUrl(), ctx.host(), mcpService),
-      body: {
-        name: toolName,
-        arguments: config.buildArgs(ctx)
-      }
-    }),
-    execute: async (ctx) => {
-      const url = resolveMcpUrl(ctx.mcpUrl(), ctx.host(), mcpService);
-      const result = await callMcpTool(url, toolName, config.buildArgs(ctx), ctx.host());
-      return parseMcpResult(result);
-    }
-  };
-}
-
-// src/commands/te-common/project/list-projects.ts
-var listProjects = createMcpCommand({
-  command: "+list_projects",
-  description: "List all projects accessible to the current user. No parameters are required. Returns project IDs, names, company IDs, project types, remarks, app IDs, and the user's current role in each project.",
-  flags: [],
-  risk: "read",
-  buildArgs: () => ({})
-});
-
-// src/commands/te-common/project/index.ts
-var commands = [
-  listProjects
-];
-var project_default = commands;
-
-// src/commands/te-common/index.ts
-var commands2 = [
-  ...project_default
-];
-var te_common_default = commands2;
-export {
-  te_common_default as default
-};