@thinkingai/ae-cli 6.0.30 → 6.0.32

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,7 +14,7 @@ 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.
+- 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.
@@ -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

@@ -1,12 +1,12 @@
 ---
 name: ae-metadata
 version: 1.0.0
-description: "AE/TE metadata capability-gateway CLI: metadata event/property detail, metadata data-table management, input-file upload, and property dimension-table binding. Use for ae-cli metadata commands backed by /api/cli/metadata/v1. Must read references before composing commands; command/flags use kebab-case while gateway input keeps snake_case. Never guess project_id, event/property names, input_file_id, or data_table_id."
+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."
 ---
 
 # ae-metadata
 
-Capability-gateway domain **`metadata`** — REST via `/api/cli/metadata/v1/...`, auth header **`cli-token`**.
+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.
 
@@ -17,7 +17,8 @@ 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> ...`. |
-| `--dry-run` | Validate input against gateway schema without executing. |
+| `--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`. |
 
 Output and errors:
 - Success: JSON envelope (default).
@@ -25,7 +26,7 @@ Output and errors:
 
 Safety:
 - Read-only commands can run directly after IDs/names are verified.
-- Write commands (`data-table *-write`, `*-delete`, `property-bindings-update`, dimension-table bind/create, `input-file upload`) require `--yes` for non-dry-run execution.
+- 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`).
 - 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`.
 
@@ -36,7 +37,7 @@ 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
-- Upload a local file to get `input_file_id`
+- 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.
@@ -48,20 +49,19 @@ ae-cli metadata <resource> <action> [options]
 ae-cli metadata property <dimension-table-action> [options]
 ```
 
-- Commands and flags use **kebab-case**: `data-table`, `input-file`, `dimension-table`, `--project-id`, `--data-table-id`.
+- Commands and flags use **kebab-case**: `data-table`, `dimension-table`, `--project-id`, `--data-table-id`.
 - Gateway `input` body fields remain **snake_case** (`project_id`, `event_name`, …); ae-cli maps flags automatically.
 
 ## 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`.
 
-## Commands (13)
+## Commands (12)
 
 | 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 input-file upload` | `POST /input-files` | [metadata_input_file_upload.md](references/metadata_input_file_upload.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) |
@@ -82,9 +82,10 @@ 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 +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_data_table_csv_delete.md

@@ -3,6 +3,7 @@
 > Capability id: `metadata.data_table.csv_delete` · Domain: `metadata`.
 
 ```bash
+# Summarize the target and impact, then wait for explicit user confirmation.
 ae-cli metadata data-table csv-delete --project-id <project_id> --data-table-id <id> --yes
 ae-cli metadata data-table csv-delete --project-id <project_id> --data-table-id <id> --dry-run
 ```

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

@@ -5,9 +5,9 @@
 ## Command
 
 ```bash
-ae-cli metadata data-table csv-write --project-id <project_id> --operation create --input-file-id <input_file_id> --data-table-name datatable_<project_id>_<name> --columns '<columns_json>' --yes
-ae-cli metadata data-table csv-write --project-id <project_id> --operation incremental_update --data-table-id <id> --input-file-id <input_file_id> --yes
-ae-cli metadata data-table csv-write --project-id <project_id> --operation replace_update --data-table-id <id> --input-file-id <input_file_id> --yes
+ae-cli metadata data-table csv-write --project-id <project_id> --operation create --input-file-id <input_file_id> --data-table-name datatable_<project_id>_<name> --columns '<columns_json>'
+ae-cli metadata data-table csv-write --project-id <project_id> --operation incremental_update --data-table-id <id> --input-file-id <input_file_id>
+ae-cli metadata data-table csv-write --project-id <project_id> --operation replace_update --data-table-id <id> --input-file-id <input_file_id>
 ```
 
 ## Parameters
@@ -16,7 +16,7 @@ ae-cli metadata data-table csv-write --project-id <project_id> --operation repla
 |---|---|---|
 | `--project-id` / `-p` | Yes | Numeric project ID. |
 | `--operation` | Yes | `create`, `incremental_update`, or `replace_update`. |
-| `--input-file-id` | Yes | ID returned by `metadata input-file upload`. |
+| `--input-file-id` | Yes | ID returned by `analysis input-file upload`. |
 | `--data-table-id` | For updates | Existing data table ID. |
 | `--data-table-name` | No | Optional technical data table name. If supplied, use `datatable_<project_id>_<name>`. |
 | `--display-name` | No | Human-readable table name. |
@@ -25,7 +25,7 @@ ae-cli metadata data-table csv-write --project-id <project_id> --operation repla
 
 ## Decision Rules
 
-- Upload the CSV first with `metadata input-file upload --purpose data_table.csv`.
+- Discover the purpose with `analysis input-file purpose list`, then upload the CSV with `analysis input-file upload --purpose data_table.csv`.
 - Do not invent `input_file_id` or `data_table_id`; use upload/list outputs.
 - If you provide `--data-table-name`, it must include the project segment, for example `datatable_2_orders`.
-- This is a write command; use `--dry-run` before non-dry-run and pass `--yes` when executing.
+- This is an ordinary `write` command and does not require CLI confirmation.

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

@@ -3,8 +3,8 @@
 > Capability id: `metadata.data_table.property_bindings_update` · Domain: `metadata`.
 
 ```bash
-ae-cli metadata data-table property-bindings-update --project-id <project_id> --data-table-id <id> --bind-properties '<bind_json>' --yes
-ae-cli metadata data-table property-bindings-update --project-id <project_id> --data-table-id <id> --unbind-properties '<unbind_json>' --yes
+ae-cli metadata data-table property-bindings-update --project-id <project_id> --data-table-id <id> --bind-properties '<bind_json>'
+ae-cli metadata data-table property-bindings-update --project-id <project_id> --data-table-id <id> --unbind-properties '<unbind_json>'
 ```
 
 | Parameter | Required | Description |

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

@@ -3,6 +3,7 @@
 > Capability id: `metadata.data_table.sql_delete` · Domain: `metadata`.
 
 ```bash
+# Summarize the target and impact, then wait for explicit user confirmation.
 ae-cli metadata data-table sql-delete --project-id <project_id> --data-table-id <id> --yes
 ae-cli metadata data-table sql-delete --project-id <project_id> --data-table-id <id> --dry-run
 ```

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

@@ -5,8 +5,8 @@
 ## Command
 
 ```bash
-ae-cli metadata data-table sql-write --project-id <project_id> --operation create --table-name datatable_<project_id>_<name> --columns '<columns_json>' --qp '<qp_json>' --zone-offset 8 --yes
-ae-cli metadata data-table sql-write --project-id <project_id> --operation update --data-table-id <id> --columns '<columns_json>' --qp '<qp_json>' --strategy overwrite --update-cron '0 0 * * * ?' --yes
+ae-cli metadata data-table sql-write --project-id <project_id> --operation create --table-name datatable_<project_id>_<name> --columns '<columns_json>' --qp '<qp_json>' --zone-offset 8
+ae-cli metadata data-table sql-write --project-id <project_id> --operation update --data-table-id <id> --columns '<columns_json>' --qp '<qp_json>' --strategy overwrite --update-cron '0 0 * * * ?'
 ```
 
 ## Parameters
@@ -47,15 +47,26 @@ ae-cli metadata data-table sql-write --project-id <project_id> --operation updat
 | `taSqlView` | No | SQL view (`TaSqlView`). Use `{}` when no dynamic view params. |
 | `taSqlView.sqlViewParams` | No | View dynamic parameters. |
 
-Inspect the live schema:
+Inspect the live schema. For complex `qp` / `columns`, use **on-demand** pre-check (motto: validate = fix params; dry-run = confirm ready to run). Prefer **`--validate` only** while iterating — then execute. Do **not** stack `--validate` then `--dry-run` on the same final input by default (`dry-run` already validates params).
 
 ```bash
 ae-cli capability inspect metadata.data_table.sql_write
+ae-cli metadata data-table sql-write \
+  --project-id 1 \
+  --operation create \
+  --table-name datatable_1_orders_dim \
+  --columns '[{"name":"id","type":"string"},{"name":"name","type":"string"}]' \
+  --qp '{"taSqlVo":{"sql":"select '\''1'\'' as id, '\''demo'\'' as name","sqlVoParams":[]},"taSqlView":{}}' \
+  --zone-offset 8 \
+  --validate
 ```
 
+`--validate` only checks/normalizes parameters (`valid` + `normalized_input`). It does not create the table. After `valid=true`, execute without `--yes`. Use `--dry-run` **instead of** `--validate` only when you need risk/output/cancel preview — not both.
+
 ## Create example
 
 ```bash
+# Typical complex-qp path: validate while fixing, then execute (no mandatory dry-run).
 ae-cli metadata data-table sql-write \
   --project-id 1 \
   --operation create \
@@ -64,7 +75,7 @@ ae-cli metadata data-table sql-write \
   --columns '[{"name":"id","type":"string","display_name":"id"},{"name":"name","type":"string","display_name":"name"}]' \
   --qp '{"taSqlVo":{"sql":"select '\''1'\'' as id, '\''demo'\'' as name","sqlVoParams":[]},"taSqlView":{}}' \
   --zone-offset 8 \
-  --dry-run
+  --validate
 
 ae-cli metadata data-table sql-write \
   --project-id 1 \
@@ -78,7 +89,10 @@ ae-cli metadata data-table sql-write \
 
 ## Decision Rules
 
-- This is a write command; use `--dry-run` before non-dry-run execution.
-- Keep `columns` and `qp` as valid JSON. `qp` must follow `SqlDatatableDef`; dry-run validates structure but does not execute SQL.
+- Write command. Motto: validate = fix params; dry-run = confirm ready to run. **Pick one pre-check on demand** — do not stack both on the same final input.
+- Complex `qp` / `columns`: use `--validate` while iterating until `valid=true`, then execute without CLI confirmation. Skip `--dry-run` unless you specifically need risk/output/cancel preview.
+- If you need that preview instead, use `--dry-run` **once** on the final input (it already validates params) — do not validate then dry-run as a habit.
+- Global `--validate` → `/validate`; `--dry-run` → `/dry-run`. Neither creates the table. Do not pass both flags together.
+- Keep `columns` and `qp` as valid JSON. `qp` must follow `SqlDatatableDef`; validate / dry-run check structure but do not execute SQL.
 - If you provide a table name, it must include the project segment, for example `datatable_2_orders_sql`.
-- If execute fails with `CAPABILITY_EXECUTION_FAILED`, fix qp structure first, then retry with a valid query before investigating backend SQL/Presto issues.
+- If execute fails with `CAPABILITY_EXECUTION_FAILED`, fix qp with `--validate`, then retry before investigating backend SQL/Presto issues.

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

@@ -5,8 +5,8 @@
 ## Command
 
 ```bash
-ae-cli metadata property bind-existing-dimension-table --project-id <project_id> --property-name <name> --property-scope user --data-table-id <id> --yes
-ae-cli metadata property bind-existing-dimension-table --project-id <project_id> --property-name <name> --property-scope event --data-table-id <id> --dict-columns '["display_name"]' --yes
+ae-cli metadata property bind-existing-dimension-table --project-id <project_id> --property-name <name> --property-scope user --data-table-id <id>
+ae-cli metadata property bind-existing-dimension-table --project-id <project_id> --property-name <name> --property-scope event --data-table-id <id> --dict-columns '["display_name"]'
 ```
 
 ## Parameters
@@ -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 a write command; use `--dry-run` before non-dry-run and pass `--yes` when executing.
+- This is an ordinary `write` command and does not require CLI confirmation.

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

@@ -5,7 +5,7 @@
 ## Command
 
 ```bash
-ae-cli metadata property create-and-bind-csv-dimension-table --project-id <project_id> --property-name <name> --property-scope user --input-file-id <input_file_id> --data-table-name datatable_<project_id>_<name> --columns '<columns_json>' --yes
+ae-cli metadata property create-and-bind-csv-dimension-table --project-id <project_id> --property-name <name> --property-scope user --input-file-id <input_file_id> --data-table-name datatable_<project_id>_<name> --columns '<columns_json>'
 ```
 
 ## Parameters
@@ -15,7 +15,7 @@ ae-cli metadata property create-and-bind-csv-dimension-table --project-id <proje
 | `--project-id` / `-p` | Yes | Numeric project ID. |
 | `--property-name` | Yes | Property technical name. |
 | `--property-scope` | Yes | Property owner table, for example `event` or `user`. |
-| `--input-file-id` | Yes | ID returned by `metadata input-file upload`. |
+| `--input-file-id` | Yes | ID returned by `analysis input-file upload`. |
 | `--data-table-name` | No | Optional technical data table name. If supplied, use `datatable_<project_id>_<name>`. |
 | `--display-name` | No | Human-readable table name. |
 | `--description` | No | Table description. |
@@ -25,8 +25,8 @@ ae-cli metadata property create-and-bind-csv-dimension-table --project-id <proje
 
 ## Decision Rules
 
-- Upload the CSV first with `metadata input-file upload --purpose data_table.csv`.
+- Discover the purpose with `analysis input-file purpose list`, then upload the CSV with `analysis input-file upload --purpose data_table.csv`.
 - Do not invent `input_file_id`; use the value returned by upload.
 - If you provide `--data-table-name`, it must include the project segment, for example `datatable_2_user_dict`.
 - Use this one-step command when the user wants a new CSV dimension table bound to a property.
-- This is a write command; use `--dry-run` before non-dry-run and pass `--yes` when executing.
+- 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/skills/ae-team/SKILL.md

@@ -30,7 +30,7 @@ Output and errors:
 
 Safety constraints:
 - Read commands (`+list`, `+list-templates`, `+list-projects`, `+run-result`, `+run-artifacts`, `+ai-generate`) can execute directly once required IDs are known.
-- Write commands require explicit user intent and keep the confirmation prompt by default. Pass `--yes` only in fully automated pipelines.
+- Ordinary `write` commands require explicit user intent but no CLI confirmation. Only `high-risk-write` commands use the confirmation gate and may receive `--yes` after explicit user authorization.
 - Never invent team IDs, run IDs, `agentId` values, `mcpServerIds`, `skillIds`, `knowledgeBaseIds`, project IDs, or any resource identifiers. Discover them with list commands or accept them from the user.
 
 ## When to Use
@@ -105,7 +105,7 @@ ae-cli team +list
 ae-cli team +list-projects
 
 # 3. Start a run
-ae-cli team +run-start --team-id <team_id> --input "分析上周用户留存数据" --yes
+ae-cli team +run-start --team-id <team_id> --input "分析上周用户留存数据"
 
 # 4. Stream until done (blocks; no polling needed)
 ae-cli team +run-watch --id <run_id>
@@ -114,7 +114,7 @@ ae-cli team +run-watch --id <run_id>
 # exit 2 → waiting_user → go to step 4a
 
 # 4a. Handle waiting_user: read pendingQuestion from stdout, get user's answer, reply, re-watch
-ae-cli team +run-reply --id <run_id> --input "<user_answer>" --yes
+ae-cli team +run-reply --id <run_id> --input "<user_answer>"
 ae-cli team +run-watch --id <run_id>   # repeat until exit 0 or 1
 
 # 5. Retrieve artifacts
@@ -128,23 +128,23 @@ ae-cli team +run-artifacts --id <run_id> --include-content true
 ae-cli team +ai-generate --prompt "需要一个分析用户行为并自动生成留存报告的团队"
 
 # 2. Create the team (paste / adjust the returned config)
-ae-cli team +create --name "留存分析团队" --config '<config_json>' --yes
+ae-cli team +create --name "留存分析团队" --config '<config_json>'
 
 # 3. Start a run
-ae-cli team +run-start --team-id <new_team_id> --input "分析本月留存" --yes
+ae-cli team +run-start --team-id <new_team_id> --input "分析本月留存"
 ```
 
 ### Workflow C — Multi-turn chat
 
 ```bash
 # First turn
-ae-cli team +run-chat --team-id <team_id> --input "帮我分析DAU趋势" --yes
+ae-cli team +run-chat --team-id <team_id> --input "帮我分析DAU趋势"
 
 # If run status is waiting_user, reply:
-ae-cli team +run-reply --id <run_id> --input "请重点分析周末下降原因" --yes
+ae-cli team +run-reply --id <run_id> --input "请重点分析周末下降原因"
 
 # Continue same session
-ae-cli team +run-chat --team-id <team_id> --session-id <session_id> --input "给出优化建议" --yes
+ae-cli team +run-chat --team-id <team_id> --session-id <session_id> --input "给出优化建议"
 ```
 
 ### Workflow D — Use a template to create a team
@@ -154,7 +154,7 @@ ae-cli team +run-chat --team-id <team_id> --session-id <session_id> --input "给
 ae-cli team +list-templates --locale zh
 
 # 2. Create from a template's config
-ae-cli team +create --name "我的分析团队" --config '<template_config>' --yes
+ae-cli team +create --name "我的分析团队" --config '<template_config>'
 ```
 
 ## Quick Verification

package/skills/ae-team/references/create.md

@@ -13,7 +13,7 @@ Domain: **Team management / write**
 - `--name` must be 1–100 characters.
 - `--description` must be ≤2000 characters if provided.
 - `--scope` must be `personal` or `company` if provided; defaults to `personal` on the server.
-- Write operation: keep the confirmation prompt unless `--yes` is explicitly requested.
+- This is an ordinary `write` operation and does not require CLI confirmation.
 
 ## TeamConfig Structure
 
@@ -66,7 +66,7 @@ ae-cli team +create \
   --name "日报分析团队" \
   --config '{"version":1,"mode":"serial","steps":[{"id":"s1","name":"分析师","agentId":"xxx","prompt":"分析数据","role":"agent"}]}'
 
-ae-cli team +create --name "My Team" --config '...' --scope company --yes
+ae-cli team +create --name "My Team" --config '...' --scope company
 ae-cli team +create --dry-run --name "Test" --config '{}'
 ```
 

package/skills/ae-team/references/delete.md

@@ -15,9 +15,9 @@ Domain: **Team management / write**
 
 ## Command
 ```bash
-ae-cli team +delete --id <team_id>
+ae-cli team +delete --id <team_id> --dry-run
+# Summarize the target and impact, then wait for explicit user confirmation.
 ae-cli team +delete --id <team_id> --yes
-ae-cli team +delete --dry-run --id <team_id>
 ```
 
 ## Parameters
@@ -31,7 +31,7 @@ ae-cli team +delete --dry-run --id <team_id>
 - Do not retry delete until all active runs have reached a terminal status.
 
 ## Next Steps on Failure
-- `409 Conflict`: cancel active runs first (`+run-cancel --id <run_id> --yes`), then retry.
+- `409 Conflict`: cancel active runs first (`+run-cancel --id <run_id>`), then retry.
 - `404`: team already deleted or wrong ID — re-run `+list` to verify.
 
 ## Recommended Chaining

package/skills/ae-team/references/run-cancel.md

@@ -10,13 +10,13 @@ Domain: **TeamRun execution / write**
 
 ## Mandatory Rules (MUST)
 - `--id` is required. Obtain the real run ID from a previous `+run-start` or `+run-chat` response — do not guess.
-- Write operation: keep the confirmation prompt unless `--yes` is explicitly requested.
+- This is an ordinary `write` operation and does not require CLI confirmation.
 - Cancellation is irreversible. To re-run the same task, call `+run-start` again.
 
 ## Command
 ```bash
 ae-cli team +run-cancel --id <run_id>
-ae-cli team +run-cancel --id <run_id> --yes
+ae-cli team +run-cancel --id <run_id>
 ae-cli team +run-cancel --dry-run --id <run_id>
 ```
 
@@ -34,5 +34,5 @@ ae-cli team +run-cancel --dry-run --id <run_id>
 - Already terminal: the run has already completed, failed, or been cancelled — no action needed.
 
 ## Recommended Chaining
-- `+run-result` (verify status) → `+run-cancel --yes`
+- `+run-result` (verify status) → `+run-cancel`
 - `+run-cancel` (clear active runs) → `+delete` (team)

package/skills/ae-team/references/run-chat.md

@@ -13,16 +13,16 @@ Domain: **TeamRun execution / write**
 - `--team-id` is required. Obtain the real team ID via `+list` — do not guess.
 - `--input` is required. Pass the user's message verbatim.
 - To continue an existing session, pass `--session-id` with the `session.id` from the previous turn.
-- Write operation: keep the confirmation prompt unless `--yes` is explicitly requested.
+- This is an ordinary `write` operation and does not require CLI confirmation.
 - After each turn, capture `session.id` and `run.id` for subsequent turns or replies.
 
 ## Command
 ```bash
 # First turn (starts a new session)
-ae-cli team +run-chat --team-id <team_id> --input "帮我分析最近的DAU趋势" --yes
+ae-cli team +run-chat --team-id <team_id> --input "帮我分析最近的DAU趋势"
 
 # Continue the same session
-ae-cli team +run-chat --team-id <team_id> --session-id <session_id> --input "继续上次的分析" --yes
+ae-cli team +run-chat --team-id <team_id> --session-id <session_id> --input "继续上次的分析"
 
 ae-cli team +run-chat --dry-run --team-id <team_id> --input "test"
 ```
@@ -43,7 +43,7 @@ ae-cli team +run-chat --dry-run --team-id <team_id> --input "test"
 ## Waiting User Flow
 ```
 +run-chat → run.status = waiting_user
-→ +run-reply --id <run_id> --input "..." --yes
+→ +run-reply --id <run_id> --input "..."
 → poll +run-result until terminal
 → optionally continue with +run-chat --session-id <session_id>
 ```

package/skills/ae-team/references/run-reply.md

@@ -11,13 +11,13 @@ Domain: **TeamRun execution / write**
 ## Mandatory Rules (MUST)
 - `--id` is required. The run **must be in `waiting_user` state** — sending a reply to a run in any other state will fail.
 - `--input` is required (1–50000 chars). Pass the user's reply verbatim.
-- Write operation: keep the confirmation prompt unless `--yes` is explicitly requested.
+- This is an ordinary `write` operation and does not require CLI confirmation.
 - After replying, poll `+run-result` until the run reaches a terminal status.
 
 ## Command
 ```bash
-ae-cli team +run-reply --id <run_id> --input "请继续，使用方案A" --yes
-ae-cli team +run-reply --id <run_id> --input "好的，请重点分析周末下降原因" --yes
+ae-cli team +run-reply --id <run_id> --input "请继续，使用方案A"
+ae-cli team +run-reply --id <run_id> --input "好的，请重点分析周末下降原因"
 ae-cli team +run-reply --dry-run --id <run_id> --input "test"
 ```
 

package/skills/ae-team/references/run-start.md

@@ -14,19 +14,18 @@ Domain: **TeamRun execution / write**
 - `--input` is required (1–50000 chars). Pass the user's task description verbatim; do not truncate.
 - JSON array flags (`--project-ids`, `--project-names`, `--space-ids`, etc.) must be valid JSON arrays, e.g. `'["id1","id2"]'`.
 - `--notification` must be valid JSON if provided, e.g. `'{"channels":["feishu"],"feishuChatId":"..."}'`.
-- Write operation: keep the confirmation prompt unless `--yes` is explicitly requested.
+- This is an ordinary `write` operation and does not require CLI confirmation.
 - After starting, capture the returned `id` (run ID) and use it to poll `+run-result`.
 
 ## Command
 ```bash
-ae-cli team +run-start --team-id <team_id> --input "分析上周用户留存情况，生成报告" --yes
+ae-cli team +run-start --team-id <team_id> --input "分析上周用户留存情况，生成报告"
 
 ae-cli team +run-start \
   --team-id <team_id> \
   --input "分析本月DAU趋势" \
   --notification '{"channels":["feishu"],"feishuChatId":"oc_xxx"}' \
-  --save-to-kb-id <kb_id> \
-  --yes
+  --save-to-kb-id <kb_id>
 
 ae-cli team +run-start --dry-run --team-id <team_id> --input "test"
 ```
@@ -59,7 +58,7 @@ ae-cli team +run-watch --id <run_id>
 # exit 0 → completed/partial_success
 # exit 1 → failed/cancelled/stale
 # exit 2 → waiting_user: read pendingQuestion from stdout, reply, re-watch
-ae-cli team +run-reply --id <run_id> --input "<user_answer>" --yes
+ae-cli team +run-reply --id <run_id> --input "<user_answer>"
 ae-cli team +run-watch --id <run_id>
 ```