@thinkingai/ae-cli 6.0.27 → 6.0.29

package/skills/ae-analysis/references/event_delete.md

@@ -0,0 +1,24 @@
+# analysis-meta event delete
+
+Use when the user needs to batch delete events or virtual events.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta event delete --project-id <project_id> --event-names '{}'
+ae-cli analysis-meta event delete --dry-run
+```
+
+Capability id: `metadata.event.delete`.
+
+Input sends `project_id`, `event_names`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--event-names` | Yes | Event names JSON array, or a JSON string accepted by common-service. |

package/skills/ae-analysis/references/event_get.md

@@ -0,0 +1,24 @@
+# analysis-meta event get
+
+Use when the user needs to get one super event metadata detail.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta event get --project-id <project_id> --event-name <event_name>
+ae-cli analysis-meta event get --dry-run
+```
+
+Capability id: `metadata.event.get`.
+
+Input sends `project_id`, `event_name`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--event-name` | Yes | Event name. |

package/skills/ae-analysis/references/event_hide_update.md

@@ -0,0 +1,25 @@
+# analysis-meta event hide-update
+
+Use when the user needs to batch hide or show events.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta event hide-update --project-id <project_id> --event-names '{}' --is-hide true
+ae-cli analysis-meta event hide-update --dry-run
+```
+
+Capability id: `metadata.event.hide_update`.
+
+Input sends `project_id`, `event_names`, `is_hide`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--event-names` | Yes | Event names JSON array, or a JSON string accepted by common-service. |
+| `--is-hide` | Yes | Whether to hide the events. |

package/skills/ae-analysis/references/event_influence_list.md

@@ -0,0 +1,24 @@
+# analysis-meta event influence-list
+
+Use when the user needs to list assets affected by event delete, hide, or update.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta event influence-list --project-id <project_id> --event-name <event_name>
+ae-cli analysis-meta event influence-list --dry-run
+```
+
+Capability id: `metadata.event.influence_list`.
+
+Input sends `project_id`, `event_name`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--event-name` | Yes | Event name. |

package/skills/ae-analysis/references/event_list.md

@@ -0,0 +1,23 @@
+# analysis-meta event list
+
+Use when the user needs to list project super events.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta event list --project-id <project_id>
+ae-cli analysis-meta event list --dry-run
+```
+
+Capability id: `metadata.event.list`.
+
+Input sends `project_id`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |

package/skills/ae-analysis/references/event_relation_update.md

@@ -0,0 +1,24 @@
+# analysis-meta event relation-update
+
+Use when the user needs to update event-property connection or source relations.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta event relation-update --project-id <project_id> --payload '{}'
+ae-cli analysis-meta event relation-update --dry-run
+```
+
+Capability id: `metadata.event.relation_update`.
+
+Input sends `project_id`, `payload`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--payload` | Yes | Capability payload JSON. |

package/skills/ae-analysis/references/event_update.md

@@ -0,0 +1,26 @@
+# analysis-meta event update
+
+Use when the user needs to update event display names and remarks.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta event update --project-id <project_id> --event-name <event_name> --event-desc <event_desc> --remark <remark>
+ae-cli analysis-meta event update --dry-run
+```
+
+Capability id: `metadata.event.update`.
+
+Input sends `project_id`, `event_name`, `event_desc`, `remark`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--event-name` | Yes | Event name. |
+| `--event-desc` | No | Event display name. |
+| `--remark` | No | Event remark. |

package/skills/ae-analysis/references/exchange_config_update.md

@@ -0,0 +1,24 @@
+# analysis-meta exchange config-update
+
+Use when the user needs to update exchange-rate configuration switch or value.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta exchange config-update --project-id <project_id> --config-val <config_val>
+ae-cli analysis-meta exchange config-update --dry-run
+```
+
+Capability id: `metadata.exchange_config.update`.
+
+Input sends `project_id`, `config_val`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--config-val` | Yes | Exchange-rate configuration value. |

package/skills/ae-analysis/references/exchange_rate_refresh.md

@@ -0,0 +1,23 @@
+# analysis-meta exchange rate-refresh
+
+Use when the user needs to refresh exchange-rate data manually.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta exchange rate-refresh --project-id <project_id>
+ae-cli analysis-meta exchange rate-refresh --dry-run
+```
+
+Capability id: `metadata.exchange_rate.refresh`.
+
+Input sends `project_id`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |

package/skills/ae-analysis/references/exchange_rule_list.md

@@ -0,0 +1,23 @@
+# analysis-meta exchange rule-list
+
+Use when the user needs to list exchange-rate conversion rules.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta exchange rule-list --project-id <project_id>
+ae-cli analysis-meta exchange rule-list --dry-run
+```
+
+Capability id: `metadata.exchange_rule.list`.
+
+Input sends `project_id`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |

package/skills/ae-analysis/references/exchange_rule_update.md

@@ -0,0 +1,24 @@
+# analysis-meta exchange rule-update
+
+Use when the user needs to save currency field, amount field, and target currency rules.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta exchange rule-update --project-id <project_id> --payload '{}'
+ae-cli analysis-meta exchange rule-update --dry-run
+```
+
+Capability id: `metadata.exchange_rule.update`.
+
+Input sends `project_id`, `payload`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--payload` | Yes | Capability payload JSON. |

package/skills/ae-analysis/references/exchange_rule_validate.md

@@ -0,0 +1,24 @@
+# analysis-meta exchange rule-validate
+
+Use when the user needs to validate affected range before saving exchange-rate rules.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta exchange rule-validate --project-id <project_id> --payload '{}'
+ae-cli analysis-meta exchange rule-validate --dry-run
+```
+
+Capability id: `metadata.exchange_rule.validate`.
+
+Input sends `project_id`, `payload`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--payload` | Yes | Capability payload JSON. |

package/skills/ae-analysis/references/folder_create.md

@@ -1,15 +1,27 @@
-# analysis folder create
+# analysis folder create (L3)
 
-Use when the user explicitly wants to create a folder in personal space or a project space.
+Use when the user wants to create a folder in personal space or project space.
 
-Do not use to create a project space. Use `project-space create`.
+Do not use to create a project space. Use `analysis.project_space.create` via capability run.
 
-Command:
+This capability has no curated `ae-cli analysis` command. Read [`ae-capability`](../../ae-capability/SKILL.md), then:
 
 ```bash
-ae-cli analysis folder create --project-id <project_id> --folder-name <name> [--space-id <space_id>] [--parent-folder-id <folder_id>] [--payload '{...}'] --yes
+ae-cli capability inspect analysis.folder.create
+ae-cli capability dry-run analysis.folder.create --input '{"project_id":1,"folder_name":"Weekly","space_id":10}'
+ae-cli capability run analysis.folder.create --input '{"project_id":1,"folder_name":"Weekly","space_id":10}'
 ```
 
-Input sends `project_id`, `folder_name`, and optional `space_id`, `parent_folder_id`, `payload`.
+`risk=write` — no chat confirmation required after dry-run succeeds.
+
+Input uses snake_case JSON. Common fields:
+
+| field | type | required | description |
+| --- | --- | --- | --- |
+| `project_id` | integer | yes | Project ID. |
+| `folder_name` | string | no | Folder name. |
+| `space_id` | integer | no | Project space ID. Omit for personal-space folders. |
+| `parent_folder_id` | integer | no | Parent project-space folder ID. |
+| `payload` | object | no | Optional snake_case object for complex create payloads. |
 
 Output is the gateway envelope. `data` contains the created folder result.

package/skills/ae-analysis/references/folder_delete.md

@@ -1,15 +1,30 @@
-# analysis folder delete
+# analysis folder delete (L3)
 
-Use when the user explicitly wants to delete one or more folders.
+Use when the user wants to delete one or more folders.
 
-Do not use for deleting dashboards or BI panels inside a folder. Use the asset delete command.
+This capability has no curated `ae-cli analysis` command. Read [`ae-capability`](../../ae-capability/SKILL.md) High-Risk Confirmation Workflow, then:
 
-Command:
+**Phase 1 — preview:**
 
 ```bash
-ae-cli analysis folder delete --project-id <project_id> [--folder-id <folder_id>] [--folder-ids '[1,2]'] [--space-id <space_id>] --yes
+ae-cli capability inspect analysis.folder.delete
+ae-cli capability dry-run analysis.folder.delete --input '{"project_id":1,"folder_ids":[1001,1002]}'
 ```
 
-Input sends `project_id`, either `folder_id` or `folder_ids`, and optional `space_id`.
+Summarize capability ID, target folder IDs, and `risk=high-risk-write` in chat. Ask the user to confirm.
+
+**Phase 2 — execute (only after explicit user confirmation):**
+
+```bash
+ae-cli capability run analysis.folder.delete --input '{"project_id":1,"folder_ids":[1001,1002]}' --yes
+```
+
+Input uses snake_case JSON. Common fields:
+
+| field | type | required | description |
+| --- | --- | --- | --- |
+| `project_id` | integer | yes | Project ID. |
+| `folder_id` | integer | no | Single folder ID. |
+| `folder_ids` | integer[] | no | Batch folder IDs. |
 
 Output is the gateway envelope. `data` contains the delete result.

package/skills/ae-analysis/references/folder_share.md

@@ -1,15 +1,25 @@
-# analysis folder share
+# analysis folder share (L3)
 
-Use when the user wants to add, remove, or batch modify folder sharing members.
+Use when the user wants to modify folder sharing members.
 
-Do not use to inspect members only. Use `folder members`.
+Do not use to inspect members only. Use `analysis.folder.members` via `capability search/inspect/run`; see [`analysis_gateway_assets.md`](analysis_gateway_assets.md) L3 members section.
 
-Command:
+This capability has no curated `ae-cli analysis` command. Read [`ae-capability`](../../ae-capability/SKILL.md), then:
 
 ```bash
-ae-cli analysis folder share --project-id <project_id> --folder-id <folder_id> [--payload '{...}'] --yes
+ae-cli capability inspect analysis.folder.share
+ae-cli capability dry-run analysis.folder.share --input '{"project_id":1,"folder_id":1001,"payload":{...}}'
+ae-cli capability run analysis.folder.share --input '{"project_id":1,"folder_id":1001,"payload":{...}}'
 ```
 
-Input sends `project_id`, `folder_id`, and backend-compatible snake_case `payload`.
+`risk=write` — no chat confirmation required after dry-run succeeds.
+
+Input uses snake_case JSON. Common fields:
+
+| field | type | required | description |
+| --- | --- | --- | --- |
+| `project_id` | integer | yes | Project ID. |
+| `folder_id` | integer | yes | Folder ID. |
+| `payload` | object | no | Optional snake_case share/member update payload. Inspect the capability schema before composing it. |
 
 Output is the gateway envelope. `data` contains the share update result.

package/skills/ae-analysis/references/get_analysis_query_schema.md

@@ -6,49 +6,48 @@ Domain: **Model schema queries**
 
 > **CRITICAL - Builder-supported ad hoc models**
 >
-> Do **not** use this tool for natural-language ad hoc requests whose target model is `event`, `retention`, `funnel`, or `prop_analysis`.
-> For those four models, use the matching QP builder first:
-> `+build_event_analysis_qp`, `+build_retention_analysis_qp`, `+build_funnel_analysis_qp`, or `+build_prop_analysis_qp`, then `+query_adhoc`.
+> Do **not** use this tool for natural-language non-SQL ad hoc requests.
+> All ten non-SQL models have matching QP builders; use the builder first, then `+query_adhoc`.
 >
 > If a builder returns `need_clarification`, `invalid_argument`, `unsupported_feature`, or `validation_error`, stop and ask the user or report the structured error. Do not fall back to this schema tool.
 
 > **CRITICAL - Step-by-Step Execution (BLOCKING)**
 >
-> This blocking sequence applies only to non-builder/manual model paths such as `distribution`, `attribution`, `heat_map`, `interval`, `path`, `rank_list`, or `sql`.
+> This blocking sequence applies only to the SQL manual path.
 > **You MUST execute these steps in order. Do NOT skip any step.**
 >
 > | Step | Command | When to proceed |
 > |------|---------|-----------------|
-> | **Step 1 (MANUAL PATH ONLY)** | `--model_type <type>` **without `--segments`** | Execute first only for non-builder/manual models. Review result. |
+> | **Step 1 (MANUAL PATH ONLY)** | `--model_type sql` **without `--segments`** | Execute first only for SQL. Review result. |
 > | **Step 2 (OPTIONAL)** | Add `--segments 'filter_group'` | Only if Step 1 result lacks filter/groupBy structures AND you need them |
 > | **Step 3 (OPTIONAL)** | Add `--segments 'examples'` | Only if Step 1+2 insufficient for multi-metric, time comparison, formulas |
 >
-> **WRONG:** `ae-cli analysis +get_analysis_query_schema --model_type distribution --segments 'examples'` ← **Never start here!**
-> **RIGHT:** `ae-cli analysis +get_analysis_query_schema --model_type distribution` → review → add segments if needed
+> **WRONG:** `ae-cli analysis +get_analysis_query_schema --model_type sql --segments 'examples'` ← **Never start here!**
+> **RIGHT:** `ae-cli analysis +get_analysis_query_schema --model_type sql` → review → add segments if needed
 
 ## Pre-call Checklist (Execute in Order)
 
-0. ✓ **Builder-supported model?** → If `event`/`retention`/`funnel`/`prop_analysis`, stop using this tool and use the matching builder.
+0. ✓ **Builder-supported model?** → If non-SQL, stop using this tool and use the matching builder.
 1. ✓ **Step 1 completed?** → Review core schema
 2. ✓ **Gap identified?** → Justify need (e.g., "need filter_group structure")
 3. ✓ **Justified?** → Call again with specific segment
 
-**Rule**: For non-builder/manual models, uncertain → execute Step 1 first. For `event`, `retention`, `funnel`, or `prop_analysis`, uncertain → read the matching builder reference first.
+**Rule**: For SQL, uncertain → execute Step 1 first. For non-SQL models, uncertain → read the matching builder reference first.
 
 ## Command (Execute in Order)
 
 ```bash
-# Step 1: start here only for non-builder/manual models (no segments)
-ae-cli analysis +get_analysis_query_schema --model_type distribution
+# Step 1: start here only for SQL (no segments)
+ae-cli analysis +get_analysis_query_schema --model_type sql
 
 # Step 2: Only after Step 1, if filter/groupBy needed
-ae-cli analysis +get_analysis_query_schema --model_type distribution --segments 'filter_group' --include_core false
+ae-cli analysis +get_analysis_query_schema --model_type sql --segments 'filter_group' --include_core false
 
 # Step 3: Only after Step 1/2, for complex scenarios
-ae-cli analysis +get_analysis_query_schema --model_type distribution --segments 'examples' --include_core false
+ae-cli analysis +get_analysis_query_schema --model_type sql --segments 'examples' --include_core false
 
 # Follow-up request (already have core from earlier step in same session)
-ae-cli analysis +get_analysis_query_schema --model_type distribution --segments 'examples' --include_core false
+ae-cli analysis +get_analysis_query_schema --model_type sql --segments 'examples' --include_core false
 ```
 
 ## Parameters
@@ -63,10 +62,10 @@ ae-cli analysis +get_analysis_query_schema --model_type distribution --segments
 
 | 场景 | 参数 | 执行顺序 |
 |---|---|---|
-| Builder 支持模型 | 不适用 | `event`/`retention`/`funnel`/`prop_analysis` 禁止用此工具作为 QP 准备步骤，改用 builder |
-| 简单 | 不传 `--segments` | **Step 1** - 非 builder/manual 模型 |
-| 中等 | `--segments 'filter_group'` | **Step 2** - 非 builder/manual 模型，有过滤或分组，需先完成 Step 1 |
-| 复杂 | `--segments 'examples'` | **Step 3** - 非 builder/manual 模型，需先完成 Step 1 |
+| Builder 支持模型 | 不适用 | 所有非 SQL 模型禁止用此工具作为 QP 准备步骤，改用 builder |
+| 简单 | 不传 `--segments` | **Step 1** - SQL manual path |
+| 中等 | `--segments 'filter_group'` | **Step 2** - SQL manual path，有过滤或分组，需先完成 Step 1 |
+| 复杂 | `--segments 'examples'` | **Step 3** - SQL manual path，需先完成 Step 1 |
 
 ## Next Steps on Failure
 - Verify model type and segment compatibility (e.g., aggregatetype not for funnel/path/interval/sql)

package/skills/ae-analysis/references/get_report_definition.md

@@ -6,7 +6,7 @@ Domain: **Report Management**
 
 ## Constraints
 
-**Not a builder fallback:** Do not call `+get_report_definition` to repair or replace a failed `+build_event_analysis_qp`, `+build_retention_analysis_qp`, `+build_funnel_analysis_qp`, or `+build_prop_analysis_qp` call. For builder-supported ad-hoc analysis, builder failure means stop and ask for clarification or report the structured error.
+**Not a builder fallback:** Do not call `+get_report_definition` to repair or replace a failed non-SQL QP builder call. Builder failure means stop and ask for clarification or report the structured error.
 
 ## Use Cases
 - Get the definition details of a single report. Returns model type, event configuration, display configuration, and other definition data without executing a data query.

package/skills/ae-analysis/references/list_events.md

@@ -8,7 +8,7 @@ Domain: **Metadata Query**
 
 **Fuzzy Search Fallback:** If `--query` returns no results, retry with broader keywords (max 3 attempts), then fall back to full list. See [SKILL.md § C. FUZZY_SEARCH_FALLBACK](../SKILL.md#c-fuzzy_search_fallback).
 
-**Not a builder pre-step:** Do not call `+list_events` before builder-supported ad-hoc analysis (`event`, `retention`, `funnel`, `prop_analysis`). The matching QP builder resolves event names internally. If the builder returns MCP failure, stop and ask for clarification instead of using this command as a fallback.
+**Not a builder pre-step:** Do not call `+list_events` before non-SQL ad-hoc analysis. The matching QP builder resolves event names internally. If the builder returns MCP failure, stop and ask for clarification instead of using this command as a fallback.
 
 ## Use Cases
 - Read-only query for SYSTEM METADATA already effective in the project. Use for super events in production metadata. Do NOT use for tracking-plan metadata (bury/track program); that belongs to BuryProgramTool.

package/skills/ae-analysis/references/list_metrics.md

@@ -8,7 +8,7 @@ Domain: **Metadata Query**
 
 **Fuzzy Search Fallback:** If `--query` returns no results, retry with broader keywords (max 3 attempts), then fall back to full list. See [SKILL.md § C. FUZZY_SEARCH_FALLBACK](../SKILL.md#c-fuzzy_search_fallback).
 
-**Not a builder pre-step:** Do not call `+list_metrics` before `+build_event_analysis_qp`, `+build_retention_analysis_qp`, `+build_funnel_analysis_qp`, or `+build_prop_analysis_qp` for normal ad-hoc analysis. Event builder resolves saved metric names internally when the metric name is passed in `metrics[].event`. If the builder fails, stop and ask for clarification instead of using this command as a fallback.
+**Not a builder pre-step:** Do not call `+list_metrics` before non-SQL ad-hoc analysis. The matching builder resolves referenced metrics internally; the event builder accepts a saved metric name in `metrics[].event`. If the builder fails, stop and ask for clarification instead of using this command as a fallback.
 
 ## Use Cases
 - List metric metadata in the project. Supports keyword filtering and returns metric IDs, names, display names, model types, remarks, and related metadata, but not metric calculation results.

package/skills/ae-analysis/references/list_properties.md

@@ -6,7 +6,7 @@ Domain: **Metadata Query**
 
 ## Constraints
 
-**Not a builder pre-step:** Do not call `+list_properties` before builder-supported ad-hoc analysis (`event`, `retention`, `funnel`, `prop_analysis`). The matching QP builder resolves property names internally. If the builder returns MCP failure, stop and ask for clarification instead of using this command as a fallback.
+**Not a builder pre-step:** Do not call `+list_properties` before non-SQL ad-hoc analysis. The matching QP builder resolves property names internally. If the builder returns MCP failure, stop and ask for clarification instead of using this command as a fallback.
 
 ## Use Cases
 - Read-only query for SYSTEM METADATA properties already effective in the project. Supports event/user scope. Do NOT use for tracking-plan metadata (bury/track program); that belongs to BuryProgramTool.

package/skills/ae-analysis/references/metric_create.md

@@ -0,0 +1,24 @@
+# analysis-meta metric create
+
+Use when the user needs to create a metric from event or retention analysis configuration.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta metric create --project-id <project_id> --payload '{}'
+ae-cli analysis-meta metric create --dry-run
+```
+
+Capability id: `metadata.metric.create`.
+
+Input sends `project_id`, `payload`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--payload` | Yes | Capability payload JSON. |

package/skills/ae-analysis/references/metric_delete.md

@@ -0,0 +1,24 @@
+# analysis-meta metric delete
+
+Use when the user needs to delete a metric.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta metric delete --project-id <project_id> --metric-id <metric_id>
+ae-cli analysis-meta metric delete --dry-run
+```
+
+Capability id: `metadata.metric.delete`.
+
+Input sends `project_id`, `metric_id`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--metric-id` | Yes | Metric ID. |

package/skills/ae-analysis/references/metric_get.md

@@ -0,0 +1,24 @@
+# analysis-meta metric get
+
+Use when the user needs to get metric definition, events, and params.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta metric get --project-id <project_id> --metric-id <metric_id>
+ae-cli analysis-meta metric get --dry-run
+```
+
+Capability id: `metadata.metric.get`.
+
+Input sends `project_id`, `metric_id`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--metric-id` | Yes | Metric ID. |

package/skills/ae-analysis/references/metric_list.md

@@ -0,0 +1,24 @@
+# analysis-meta metric list
+
+Use when the user needs to list project metrics.
+
+Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+
+Command:
+
+```bash
+ae-cli analysis-meta metric list --project-id <project_id> --ignore-authentication true
+ae-cli analysis-meta metric list --dry-run
+```
+
+Capability id: `metadata.metric.list`.
+
+Input sends `project_id`, `ignore_authentication`.
+
+Output is the gateway envelope. `data` contains the common-service capability result.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--ignore-authentication` | No | Whether to skip asset authentication status decoration. |