@thinkingai/ae-cli 6.0.31 → 6.1.4

package/skills/ae-experiment/references/manage_experiment.md

@@ -0,0 +1,15 @@
+# +manage_experiment
+
+Manage experiment status.
+
+```bash
+ae-cli experiment +manage_experiment --project_id <id> --exp_id <expId> --target_status <status> [--remark <text>]
+```
+
+Flags:
+- `--project_id`, `-p`: Project ID.
+- `--exp_id`: Experiment ID.
+- `--target_status`: One of `draft`, `testing`, `pending`, `running`, `paused`, `ended`, `archive`.
+- `--remark`: Optional operation remark.
+
+When target status is `pending`, `testing`, or `running`, the MCP server performs a ready check first.

package/skills/ae-experiment/references/manage_feature_status.md

@@ -0,0 +1,11 @@
+# +manage_feature_status
+
+Update Feature status.
+
+```bash
+ae-cli experiment +manage_feature_status --project_id <id> --req '<json>'
+```
+
+Flags:
+- `--project_id`, `-p`: Project ID.
+- `--req`: Feature status request JSON object.

package/skills/ae-experiment/references/query_bucket_list.md

@@ -0,0 +1,10 @@
+# +query_bucket_list
+
+Query split buckets in a project.
+
+```bash
+ae-cli experiment +query_bucket_list --project_id <id>
+```
+
+Flags:
+- `--project_id`, `-p`: Project ID.

package/skills/ae-experiment/references/query_experiment_detail.md

@@ -0,0 +1,11 @@
+# +query_experiment_detail
+
+Query full experiment detail.
+
+```bash
+ae-cli experiment +query_experiment_detail --project_id <id> --exp_id <expId>
+```
+
+Flags:
+- `--project_id`, `-p`: Project ID.
+- `--exp_id`: Experiment ID.

package/skills/ae-experiment/references/query_experiment_list.md

@@ -0,0 +1,10 @@
+# +query_experiment_list
+
+Query experiments in a project.
+
+```bash
+ae-cli experiment +query_experiment_list --project_id <id>
+```
+
+Flags:
+- `--project_id`, `-p`: Project ID.

package/skills/ae-experiment/references/query_experiment_metric_trend.md

@@ -0,0 +1,16 @@
+# +query_experiment_metric_trend
+
+Query experiment metric trend report.
+
+```bash
+ae-cli experiment +query_experiment_metric_trend --project_id <id> --exp_id <expId> --metric_id <metricId> --start_time 2026-07-01 --end_time 2026-07-07 [--request_id <id>] [--force_refresh true]
+```
+
+Flags:
+- `--project_id`, `-p`: Project ID.
+- `--exp_id`: Experiment ID.
+- `--metric_id`: Metric ID.
+- `--start_time`: Start date, `yyyy-MM-dd`.
+- `--end_time`: End date, `yyyy-MM-dd`.
+- `--request_id`: Optional request ID for query tracking.
+- `--force_refresh`: Optional boolean for report refresh.

package/skills/ae-experiment/references/query_experiment_report_summary.md

@@ -0,0 +1,12 @@
+# +query_experiment_report_summary
+
+Query experiment report summary.
+
+```bash
+ae-cli experiment +query_experiment_report_summary --project_id <id> --exp_id <expId> [--force_refresh true]
+```
+
+Flags:
+- `--project_id`, `-p`: Project ID.
+- `--exp_id`: Experiment ID.
+- `--force_refresh`: Optional boolean for report refresh.

package/skills/ae-experiment/references/query_experiment_sample_size_report.md

@@ -0,0 +1,16 @@
+# +query_experiment_sample_size_report
+
+Query experiment sample-size report.
+
+```bash
+ae-cli experiment +query_experiment_sample_size_report --project_id <id> --exp_id <expId> --start_time 2026-07-01 --end_time 2026-07-07 [--request_id <id>] [--force_refresh true] [--by_hour true]
+```
+
+Flags:
+- `--project_id`, `-p`: Project ID.
+- `--exp_id`: Experiment ID.
+- `--start_time`: Start date, `yyyy-MM-dd`.
+- `--end_time`: End date, `yyyy-MM-dd`.
+- `--request_id`: Optional request ID for query tracking.
+- `--force_refresh`: Optional boolean for report refresh.
+- `--by_hour`: Optional boolean to show results by hour.

package/skills/ae-experiment/references/query_feature_detail.md

@@ -0,0 +1,12 @@
+# +query_feature_detail
+
+Query Feature detail by key and optional version.
+
+```bash
+ae-cli experiment +query_feature_detail --project_id <id> --feature_key <key> [--version <versionId>]
+```
+
+Flags:
+- `--project_id`, `-p`: Project ID.
+- `--feature_key`: Feature key.
+- `--version`: Optional Feature version ID.

package/skills/ae-experiment/references/query_feature_list.md

@@ -0,0 +1,10 @@
+# +query_feature_list
+
+Query Features in a project.
+
+```bash
+ae-cli experiment +query_feature_list --project_id <id>
+```
+
+Flags:
+- `--project_id`, `-p`: Project ID.

package/skills/ae-experiment/references/query_metric_detail.md

@@ -0,0 +1,11 @@
+# +query_metric_detail
+
+Query metric detail.
+
+```bash
+ae-cli experiment +query_metric_detail --project_id <id> --metric_id <metricId>
+```
+
+Flags:
+- `--project_id`, `-p`: Project ID.
+- `--metric_id`: Metric ID.

package/skills/ae-experiment/references/query_metric_list.md

@@ -0,0 +1,10 @@
+# +query_metric_list
+
+Query metrics in a project.
+
+```bash
+ae-cli experiment +query_metric_list --project_id <id>
+```
+
+Flags:
+- `--project_id`, `-p`: Project ID.

package/skills/ae-experiment/references/query_traffic_layer_detail.md

@@ -0,0 +1,11 @@
+# +query_traffic_layer_detail
+
+Query traffic layer detail.
+
+```bash
+ae-cli experiment +query_traffic_layer_detail --project_id <id> --layer_id <layerId>
+```
+
+Flags:
+- `--project_id`, `-p`: Project ID.
+- `--layer_id`: Traffic layer ID.

package/skills/ae-experiment/references/query_traffic_layer_list.md

@@ -0,0 +1,10 @@
+# +query_traffic_layer_list
+
+Query traffic layers in a project.
+
+```bash
+ae-cli experiment +query_traffic_layer_list --project_id <id>
+```
+
+Flags:
+- `--project_id`, `-p`: Project ID.

package/skills/ae-experiment/references/save_experiment.md

@@ -0,0 +1,17 @@
+# +save_experiment
+
+Create or update an experiment draft.
+
+```bash
+ae-cli experiment +save_experiment --project_id <id> --req '<json>'
+```
+
+Flags:
+- `--project_id`, `-p`: Project ID.
+- `--req`: Experiment save request JSON object.
+
+Notes:
+- Blank `req.expId` creates a draft and returns an experiment ID.
+- Non-blank `req.expId` patches the existing draft.
+- `req.projectId` is overwritten from `--project_id`.
+- Use `+check_experiment_ready` before moving to `pending`, `testing`, or `running`.

package/skills/ae-experiment/references/save_feature.md

@@ -0,0 +1,13 @@
+# +save_feature
+
+Create or update a Feature.
+
+```bash
+ae-cli experiment +save_feature --project_id <id> --req '<json>'
+```
+
+Flags:
+- `--project_id`, `-p`: Project ID.
+- `--req`: Feature save request JSON object.
+
+Create mode requires `featureKey`, `type`, and `targetPlatform`. Modify mode uses `id` or `update=true`.

package/skills/ae-experiment/references/save_metric.md

@@ -0,0 +1,13 @@
+# +save_metric
+
+Create or update a metric.
+
+```bash
+ae-cli experiment +save_metric --project_id <id> --req '<json>'
+```
+
+Flags:
+- `--project_id`, `-p`: Project ID.
+- `--req`: Metric save request JSON object.
+
+Create mode requires metric identifiers and metric configuration. Modify mode uses `update=true`.

package/skills/ae-experiment/references/save_submit_experiment.md

@@ -0,0 +1,13 @@
+# +save_submit_experiment
+
+Create or update a complete experiment and submit it in one call.
+
+```bash
+ae-cli experiment +save_submit_experiment --project_id <id> --req '<json>'
+```
+
+Flags:
+- `--project_id`, `-p`: Project ID.
+- `--req`: Save-and-submit request JSON object.
+
+Prefer `+save_experiment` for progressive draft construction.

package/skills/ae-experiment/references/save_traffic_layer.md

@@ -0,0 +1,13 @@
+# +save_traffic_layer
+
+Create or update a traffic layer.
+
+```bash
+ae-cli experiment +save_traffic_layer --project_id <id> --req '<json>'
+```
+
+Flags:
+- `--project_id`, `-p`: Project ID.
+- `--req`: Traffic layer save request JSON object.
+
+Create mode requires `bucketId`, `layerName`, and `layerType` in the request. Modify mode requires `layerId`.

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

@@ -9,7 +9,8 @@ description: "Interactive generation of an AE tracking plan and upload. Trigger
 > English input → English reply; Chinese input → Chinese reply; Japanese input → Japanese reply.
 > If uncertain, default to English.
 > This applies to all output: section titles, phase names, template prompts, example text, option lists, etc.
-> **⚠️ CRITICAL: Template localization is CLI-owned. Do NOT manually translate imported template content with the model. Use the `src/tracking` i18n pipeline by setting `AE_LANG=<user_lang>`, writing `draft.meta.lang`, and regenerating through `ae-cli tracking code import-template` / `ae-cli tracking plan draft`.**
+> **⚠️ CRITICAL: Template localization is CLI-owned. Do NOT manually translate imported template content with the model. Use the `src/tracking/i18n` module as the source of truth by setting `AE_LANG=<user_lang>`, writing `draft.meta.lang`, and regenerating through `ae-cli tracking code import-template` / `ae-cli tracking plan draft`.**
+> **Before changing any template-owned localized label, first look up the corresponding translation in `src/tracking/i18n` (for example `resources/xlsx/sheets.ts`, `resources/xlsx/headers.ts`, `resources/xlsx/types.ts`, and `resources/cli/*.json`). If no matching translation exists there, preserve the imported text and ask before rewriting business semantics.**
 > Do NOT copy Chinese text verbatim from this document into English/Japanese replies unless it is an identifier, template name needed for CLI import, or original source material quoted for traceability.
 
 ## Terminology Glossary
@@ -72,6 +73,7 @@ Phase 0 → 1 → 2 → 3 → 4, do not skip steps.
 > property `display_name`, property `desc`, etc.) should be generated in the **user's input language**.
 > For imported templates, do NOT translate those fields manually. Template sheet names, headers, property type display values,
 > CLI messages, and auto-track/i18n-owned labels must come from `src/tracking/i18n` via `AE_LANG=<user_lang>` and `draft.meta.lang`.
+> When a localized label is needed, inspect `src/tracking/i18n` and use the existing resource key/value; do not invent translations from the model.
 > If template business text needs localization and the CLI/i18n resources do not provide it, preserve the imported text and ask the user before rewriting business semantics.
 > Only identifier fields like `event_name`, `prop_name` remain in English snake_case (canonical format).
 > This skill only cares about command behavior, not internal implementation.
@@ -498,8 +500,9 @@ Priority from low to high: **template → codebase → prd → chat → autotrac
   - Import command: `AE_LANG=<user_lang> ae-cli tracking code import-template --template-name "<template name>" --out .ae-cli/draft.json`
   - ⚠️ **Must validate immediately after template import** (see Phase 1.6); template content may not be fully correct
   - ⚠️ **Do not manually translate template content after import**: Do NOT read draft.json and model-translate `display_name`, `event_desc`, `event_tag`, or property `display_name`/`desc`. Keep imported business content as produced by the CLI/template reader unless the user explicitly asks for semantic rewriting.
-  - ⚠️ **Use `src/tracking` i18n for localization owned by the CLI**: `AE_LANG=<user_lang>` + `draft.meta.lang` control CLI messages, xlsx sheet names, xlsx headers, property type display values, and auto-track/i18n-owned labels. If these are wrong, regenerate with the intended locale instead of editing labels by hand.
-  - ⚠️ **event_tag is not free-form model translation**: Do not manually map `业务事件`/`系统事件` to another language. Preserve template tags, or rely on `src/tracking` i18n/autotrack generation for system labels when the CLI owns them.
+  - ⚠️ **Use `src/tracking/i18n` for localization owned by the CLI**: `AE_LANG=<user_lang>` + `draft.meta.lang` control CLI messages, xlsx sheet names, xlsx headers, property type display values, and auto-track/i18n-owned labels. If these are wrong, inspect the existing translations under `src/tracking/i18n`, then regenerate with the intended locale instead of editing labels by hand.
+  - ⚠️ **No model-invented translations for template labels**: When replacing or explaining a localized template-owned label, use the exact value from `src/tracking/i18n` resources. If no corresponding resource exists, preserve the template text and ask the user before changing semantics.
+  - ⚠️ **event_tag is not free-form model translation**: Do not manually map `业务事件`/`系统事件` to another language. Preserve template tags, or rely on `src/tracking/i18n` and autotrack generation for system labels when the CLI owns them.
 - **codebase**: Scan project source directory, extract events/properties from business logic; **same-name events merge prop_names without overwriting existing fields**; new items `source: "codebase"`
 - **prd**: Read all user-provided product documents (md / pdf / docx / URL / images), extract events and properties from each file; **same-name events merge prop_names without overwriting existing fields**; image files analyzed via multimodal interpretation of UI elements and interaction flows; all new items `source: "prd"`
   - **prd path is a folder**: Recursively scan all files in the directory:
@@ -673,7 +676,7 @@ Run the following command to dynamically discover available templates:
 AE_LANG=<user_lang> ae-cli tracking plan list-templates --json
 ```
 
-**Language rules**: Template names and template business content must not be model-translated. Use localized names only when they are returned by the CLI / `src/tracking` i18n resources. If `list-templates --json` only returns the original template `name`, display that name as-is and keep it unchanged for import.
+**Language rules**: Template names and template business content must not be model-translated. Use localized names only when they are returned by the CLI or found in `src/tracking/i18n` resources. If `list-templates --json` only returns the original template `name`, display that name as-is and keep it unchanged for import. Before presenting or modifying any localized template-owned label, look it up in `src/tracking/i18n`; do not invent a translation.
 
 Built-in templates are resolved by ae-cli from the ae-cli package root. User templates are resolved from the ae-cli user template directory. Do **not** manually construct `./tracking-plan-template/...` paths from the user's current workspace.
 
@@ -1116,7 +1119,7 @@ AE_LANG=<user_lang> ae-cli tracking plan upload --project <projectId> --xlsx .ae
 - **With `--replace`**: Delete existing project plan first then upload (when user chooses "Replace", or severe conflict switches to replace)
 - **Without `--replace`**: AE merge-by-name merge (no conflicts, or advisory only with user confirmation to append)
 
-Upload language is controlled locally by `AE_LANG`, `--lang`, or `draft.meta.lang`. Do not call AE user language config APIs and do not use `--switch-lang`. If the xlsx language is wrong, regenerate the xlsx with the intended language before uploading:
+Upload commands MUST pass `--lang <user_lang>` explicitly. `--lang` must match the generated xlsx language and `draft.meta.lang`; `AE_LANG` is only used for CLI messages and xlsx regeneration context. Do not call AE user language config APIs and do not use `--switch-lang`. If the xlsx language is wrong, regenerate the xlsx with the intended language before uploading:
 ```bash
 AE_LANG=<user_lang> ae-cli tracking plan draft --in .ae-cli/draft.json --out .ae-cli/draft.xlsx
 AE_LANG=<user_lang> ae-cli tracking plan upload --project <projectId> --xlsx .ae-cli/draft.xlsx --draft .ae-cli/draft.json --lang <user_lang> [--replace]

package/skills/ae-generate-tracking-plan/references/te-api.md

@@ -99,7 +99,7 @@ Upload is a two-step capability-gateway flow:
 { "project_id": 1603, "input_file_id": "...", "lang": "zh" }
 ```
 
-- `lang` is optional for backward compatibility, but Agents should pass the generated xlsx language (`zh` / `en` / `ja` / `ko`) so the backend resolves localized sheet names and headers consistently.
+- Agents MUST pass `lang` with the generated xlsx language (`zh` / `en` / `ja` / `ko`) so the backend resolves localized sheet names and headers consistently.
 - Response: `{ return_code: 0, return_message: "success" }` on success.
 
 **合并语义**：对事件走 **merge-by-name**（同名不覆盖、新名新增）。若要完全替换，

package/skills/ae-kb/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: ae-kb
 version: 1.0.0
-description: "AE/TE knowledge base CLI manual for creating, querying, LLM-powered ask, deterministic index/grep/read retrieval, checking status, uploading, compiling, schema generation, URL sources, source deletion, and knowledge base deletion. Use when the user asks to manage TE/AE/ThinkingEngine knowledge bases, upload documents or URLs to a knowledge base, query knowledge, ask knowledge bases with an LLM, inspect knowledge base indexes, search knowledge base pages, read a specific knowledge base page, check knowledge base status, generate schemas, compile knowledge, remove sources, or delete a knowledge base. Must use ae-cli kb commands and must not guess knowledge base names, scopes, page paths, source display names, JSON payload shapes, or URL formats."
+description: "AE/TE knowledge base CLI manual for creating, querying, LLM-powered ask, listing accessible knowledge bases, deterministic index/grep/read retrieval, checking status, uploading, compiling, schema generation, URL sources, source deletion, and knowledge base deletion. Use when the user asks to manage TE/AE/ThinkingEngine knowledge bases, upload documents or URLs to a knowledge base, query knowledge, ask knowledge bases with an LLM, list accessible knowledge bases, inspect knowledge base indexes, search knowledge base pages, read a specific knowledge base page, check knowledge base status, generate schemas, compile knowledge, remove sources, or delete a knowledge base. Must use ae-cli kb commands and must not guess knowledge base names, scopes, page paths, source display names, JSON payload shapes, or URL formats."
 ---
 
 # ae-kb
@@ -14,8 +14,8 @@ ae-cli kb +<command> [options]
 
 ## Global Rules
 
-- Use this skill for TE/AE knowledge base tasks: create, query, ask with LLM, inspect indexes, grep pages, read pages, check status, upload sources, add URL sources, generate schema, compile, remove source files, and delete knowledge bases.
-- Read and ordinary `write` operations can run directly after required inputs and user intent are known. Only `high-risk-write` operations use the confirmation gate.
+- Use this skill for TE/AE knowledge base tasks: create, query, ask with LLM, list accessible knowledge bases, inspect indexes, grep pages, read pages, check status, upload sources, add URL sources, generate schema, compile, remove source files, and delete knowledge bases.
+- Read operations can run directly after required inputs are known. Write operations require explicit user intent and normally keep the confirmation prompt unless the user asks to bypass it.
 - Prefer `--dry-run` before destructive or broad writes when the user has not already validated the target.
 - Do not invent knowledge base names, scopes, source display names, or JSON payloads. Ask the user or query known context when values are missing.
 - JSON flags must be valid JSON strings, usually wrapped in single quotes in shell commands.
@@ -29,6 +29,7 @@ ae-cli kb +<command> [options]
 |---|---:|---|
 | `+query` | read | Query one or more knowledge bases with a natural-language question. |
 | `+ask` | read | LLM-powered Q&A over knowledge bases. Consumes platform tokens. |
+| `+list` | read | List accessible knowledge bases filtered by buildStatus (default: compiled). |
 | `+index` | read | List accessible knowledge bases and their `index.md` navigation maps. |
 | `+grep` | read | Keyword-search knowledge base pages and return matched lines with context. |
 | `+read` | read | Read a full knowledge base page or a line window. |
@@ -145,21 +146,35 @@ ae-cli kb +ask \
   --question "How do we troubleshoot payment alerts?" \
   --sources '[{"scope":"company","name":"engineering-handbook"}]' \
   --model-id claude-sonnet-4-6 \
-  --max-turns 10 \
+  --max-turns 50 \
   --locale zh
 ```
 
 - `--question`, alias `-q`: required natural-language question (1-2000 characters).
 - `--sources`: optional JSON array of knowledge base refs. Omit to search all accessible knowledge bases.
 - `--model-id`: optional LLM model ID. Omit to use the platform default.
-- `--max-turns`: optional agent turn limit (1-20, server default 10).
+- `--max-turns`: optional agent turn limit (1-100, server default 50).
 - `--locale`: optional locale: `zh`, `en`, `ja`, or `ko`.
 
+### List Accessible Knowledge Bases
+
+Use `+list` when you only need accessible knowledge base metadata without loading `index.md` navigation maps. By default it returns knowledge bases with `buildStatus: compiled`:
+
+```bash
+ae-cli kb +list
+ae-cli kb +list --locale zh
+ae-cli kb +list --build-status compiled
+```
+
 ### Explore Knowledge Base Pages
 
 Use the deterministic retrieval primitives when an agent needs to explore knowledge base content like a code repository. These endpoints do not call an LLM on the server side.
 
-Start with `+index` to see accessible knowledge bases and navigation maps:
+Start with `+list` or `+index` to discover accessible knowledge bases. Use `+index` when you also need navigation maps:
+
+```bash
+ae-cli kb +list
+```
 
 ```bash
 ae-cli kb +index \
@@ -187,6 +202,7 @@ ae-cli kb +read \
 
 Retrieval rules:
 
+- `+list` accepts optional `--build-status` (default `compiled`) and `--locale`. Returns accessible knowledge base metadata including `buildStatus`, without `index.md` navigation maps.
 - `+index` accepts optional `--sources` and `--locale`; omit `--sources` to list all accessible knowledge bases.
 - `+grep` requires `--query` / `-q`; optional `--sources`, `--top-k` (1-50, default 10), and `--locale`.
 - `+read` requires `--source` pointing to exactly one knowledge base and `--path` relative to the knowledge base root; optional `--offset`, `--limit` (1-10000), and `--locale`.
@@ -226,16 +242,26 @@ ae-cli kb +query --query "<question>" --sources '[{"scope":"company","name":"kb-
 ### `+ask`
 
 ```bash
-ae-cli kb +ask --question "<question>" [--sources '[{"scope":"company","name":"kb-name"}]'] [--model-id claude-sonnet-4-6] [--max-turns 10] [--locale zh|en|ja|ko]
+ae-cli kb +ask --question "<question>" [--sources '[{"scope":"company","name":"kb-name"}]'] [--model-id claude-sonnet-4-6] [--max-turns 50] [--locale zh|en|ja|ko]
 ```
 
 - `--question`, alias `-q`: required natural-language question (1-2000 characters).
 - `--sources`: optional JSON array of knowledge base refs. Omit to search all accessible knowledge bases.
 - `--model-id`: optional LLM model ID. Omit to use the platform default.
-- `--max-turns`: optional agent turn limit, 1-20, server default 10.
+- `--max-turns`: optional agent turn limit (1-100, server default 50).
 - `--locale`: optional locale: `zh`, `en`, `ja`, or `ko`.
 - **Token cost**: this command invokes an LLM on the server and consumes platform tokens. Prefer `+index` -> `+grep` -> `+read` for token-free deterministic retrieval.
 
+### `+list`
+
+```bash
+ae-cli kb +list [--build-status compiled] [--locale zh|en|ja|ko]
+```
+
+- `--build-status`: optional build status filter (default: `compiled`).
+- `--locale`: optional locale: `zh`, `en`, `ja`, or `ko`.
+- Response items include `buildStatus`.
+
 ### `+index`
 
 ```bash

package/skills/ae-metadata/SKILL.md

@@ -87,5 +87,5 @@ ae-cli analysis input-file purpose list --project-id 1
 
 ## Related Skills
 
-- **`ae-analysis`**: `analysis_meta +list_events` / `+list_properties` to discover names before detail get.
+- **`ae-analysis`**: `analysis-meta event list` / `analysis-meta property list` to discover names before detail get.
 - **Dev workflow**: `.cursor/skills/te-cli-capability-gateway` — inspect gateway schema when adding new metadata capabilities.

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

@@ -35,18 +35,18 @@ Gateway request body uses snake_case `input`:
 
 ## Decision Rules
 
-- Prefer **`metadata event get`** over `analysis_meta +list_events` when you need **full detail + virtual definition**, not browsing or fuzzy search.
-- Use `ae-analysis` → `analysis_meta +list_events` first when the event name is unknown or you need keyword search / pagination.
+- Prefer **`metadata event get`** over `analysis-meta event list` when you need **full detail + virtual definition**, not browsing or fuzzy search.
+- Use `ae-analysis` → `analysis-meta event list` first when the event name is unknown or you need keyword search / pagination.
 - If the gateway returns `EVENT_NOT_FOUND`, verify `event_name` spelling and `project_id`; do not invent names.
 - Auth: `cli-token` header (ae-cli injects automatically in sandbox; local CLI uses `getCliToken()`).
 
 ## Recommended Chaining
 
-- `ae-analysis`: `analysis_meta +list_events` (discover name) → `metadata event get` (detail)
+- `ae-analysis`: `analysis-meta event list` (discover name) → `metadata event get` (detail)
 - `metadata event get` → `metadata property get` (inspect properties listed in response)
 
 ## Next Steps After Failure
 
-- Empty or not found: confirm project id and exact `event_name` from `+list_events`.
+- Empty or not found: confirm project id and exact `event_name` from `analysis-meta event list`.
 - Permission error: confirm metadata view permission in the project.
 - Gateway unavailable: confirm nginx routes `/api/cli/metadata/` and backend capability catalog is deployed.

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 +list_properties`.
+- Confirm the property with `metadata 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/skills/ae-metadata/references/metadata_property_get.md

@@ -37,18 +37,18 @@ Gateway request body uses snake_case `input`:
 
 ## Decision Rules
 
-- Prefer **`metadata property get`** over `analysis_meta +list_properties` when you need **full detail + virtual definition**, not browsing or fuzzy search.
-- Use `ae-analysis` → `analysis_meta +list_properties` first when the property name is unknown or you need keyword search / pagination.
+- Prefer **`metadata property get`** over `analysis-meta property list` when you need **full detail + virtual definition**, not browsing or fuzzy search.
+- Use `ae-analysis` → `analysis-meta property list` first when the property name is unknown or you need keyword search / pagination.
 - `property_scope` must be exactly `event` or `user` (backend accepts case-insensitive).
 - Virtual / dict / exchange-rate properties are addressed by `property-name` only; do not pass legacy `prop_name`.
 - Event-scoped names like `#account_id` must be passed literally (quote in shell when `#` is present).
 
 ## Recommended Chaining
 
-- `ae-analysis`: `analysis_meta +list_properties` (discover name + scope) → `metadata property get` (detail)
+- `ae-analysis`: `analysis-meta property list` (discover name + scope) → `metadata property get` (detail)
 - `metadata event get` → `metadata property get` (follow properties from event detail)
 
 ## Next Steps After Failure
 
-- Not found: confirm scope (`event` vs `user`) and exact name from `+list_properties`.
+- Not found: confirm scope (`event` vs `user`) and exact name from `analysis-meta property list`.
 - Permission error: confirm metadata view permission in the project.

package/dist/te-common-5NJLF3XG.js

@@ -1,130 +0,0 @@
-import {
-  callMcpTool,
-  parseMcpResult,
-  resolveMcpUrl
-} from "./chunk-6LEYLOV3.js";
-import "./chunk-KGJQCYVC.js";
-import "./chunk-NOO24N7W.js";
-import "./chunk-2NDGFQHW.js";
-import "./chunk-AJTH7LT3.js";
-import "./chunk-YCLVYFK7.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/resource/get-resource-url.ts
-function normalizeResourceUrlFields(node, host) {
-  if (!node || typeof node !== "object") return;
-  const obj = node;
-  for (const [key, value] of Object.entries(obj)) {
-    if (typeof value === "string") {
-      if (/url|link/i.test(key) || value.includes("/#/")) {
-        obj[key] = absolutizeRelativeUrls(value, host);
-      }
-    } else if (value && typeof value === "object") {
-      normalizeResourceUrlFields(value, host);
-    }
-  }
-}
-function absolutizeRelativeUrls(s, host) {
-  const base = host.replace(/\/+$/, "");
-  s = s.replace(/\]\((\/(?!\/)[^)]*)\)/g, `](${base}$1)`);
-  if (/^\/(?!\/)/.test(s)) s = base + s;
-  return s;
-}
-var getResourceUrl = {
-  service: "analysis_common",
-  command: "+get_resource_url",
-  description: "Generate a clickable Markdown link for a resource by ID and type (absolute URL)",
-  flags: [
-    { name: "project_id", type: "number", required: true, desc: "Project ID", alias: "p" },
-    { name: "resource_type", type: "string", required: true, desc: "Resource type: dashboard/report/metric/alert/tag/cluster/data_table/super_event/super_prop_user/super_prop_event/virtual_event/user_virtual_prop/event_virtual_prop" },
-    { name: "resource_id", type: "number", required: true, desc: "Numeric resource ID" }
-  ],
-  risk: "read",
-  dryRun: (ctx) => ({
-    method: "tools/call",
-    url: resolveMcpUrl(ctx.mcpUrl(), ctx.host(), "analysis"),
-    body: {
-      name: "get_resource_url",
-      arguments: {
-        projectId: ctx.num("project_id"),
-        resourceType: ctx.str("resource_type"),
-        resourceId: ctx.num("resource_id")
-      }
-    }
-  }),
-  execute: async (ctx) => {
-    const url = resolveMcpUrl(ctx.mcpUrl(), ctx.host(), "analysis");
-    const result = await callMcpTool(
-      url,
-      "get_resource_url",
-      {
-        projectId: ctx.num("project_id"),
-        resourceType: ctx.str("resource_type"),
-        resourceId: ctx.num("resource_id")
-      },
-      ctx.host()
-    );
-    const parsed = parseMcpResult(result);
-    if (typeof parsed !== "object" || parsed === null) {
-      return parsed;
-    }
-    normalizeResourceUrlFields(parsed, ctx.host());
-    return parsed;
-  }
-};
-
-// src/commands/te-common/resource/index.ts
-var commands2 = [
-  getResourceUrl
-];
-var resource_default = commands2;
-
-// src/commands/te-common/index.ts
-var commands3 = [
-  ...project_default,
-  ...resource_default
-];
-var te_common_default = commands3;
-export {
-  te_common_default as default
-};