@thinkingai/ae-cli 1.0.3 → 1.0.18

package/dist/{te-meta-FMM7KCVI.js → te-meta-MGO5BCMG.js}

@@ -2,9 +2,9 @@ import {
   callMcpTool,
   parseMcpResult,
   resolveMcpUrl
-} from "./chunk-53FNNCZW.js";
-import "./chunk-3CDLNXTD.js";
-import "./chunk-EBFUVWIZ.js";
+} from "./chunk-7QBNU44L.js";
+import "./chunk-4KQ7H7DY.js";
+import "./chunk-MR57UIKC.js";
 
 // src/commands/te-meta/shared.ts
 function createMcpCommand(config) {
@@ -58,34 +58,46 @@ function requiredJsonString(ctx, name) {
 // src/commands/te-meta/meta/list-events.ts
 var listEvents = createMcpCommand({
   command: "+list_events",
-  description: "Read-only query for effective system event metadata",
+  description: "List events in the project. Query performs fuzzy matching on eventName, eventDesc and aiRemark. Supports fields/limit/offset payload governance.",
   flags: [
     { name: "project_id", type: "number", required: true, desc: "Project ID", alias: "p" },
-    { name: "query", type: "string", required: false, desc: "Optional keyword filter", alias: "q" }
+    { name: "query", type: "string", required: false, desc: "Optional keyword filter. Fuzzy match is applied to eventName, eventDesc, and aiRemark; if omitted, all events are returned.", alias: "q" },
+    { name: "fields", type: "json", required: false, desc: "Optional fields to return. Supported fields: eventName, eventDesc, aiRemark, eventTag, remark.", alias: "f" },
+    { name: "limit", type: "number", required: false, desc: "Optional page size. Default: 20, maximum: 50.", alias: "l" },
+    { name: "offset", type: "number", required: false, desc: "Optional page offset. Default: 0.", alias: "o" }
   ],
   risk: "read",
   buildArgs: (ctx) => ({
     projectId: ctx.num("project_id"),
-    query: optionalString(ctx, "query")
+    query: optionalString(ctx, "query"),
+    fields: optionalJson(ctx, "fields"),
+    limit: optionalNumber(ctx, "limit"),
+    offset: optionalNumber(ctx, "offset")
   })
 });
 
 // src/commands/te-meta/meta/list-properties.ts
 var listProperties = createMcpCommand({
   command: "+list_properties",
-  description: "Read-only query for effective system property metadata",
+  description: "List properties in the project. Query performs fuzzy matching on propName, propDesc and aiRemark. Supports fields/limit/offset payload governance.",
   flags: [
     { name: "project_id", type: "number", required: true, desc: "Project ID", alias: "p" },
     { name: "scope", type: "string", required: false, desc: "Property scope: event or user" },
     { name: "event_name", type: "string", required: false, desc: "Optional event name filter" },
-    { name: "query", type: "string", required: false, desc: "Optional keyword filter", alias: "q" }
+    { name: "query", type: "string", required: false, desc: "Optional keyword filter. Fuzzy match is applied to propName, propDesc, and aiRemark; if omitted, all accessible properties are returned.", alias: "q" },
+    { name: "fields", type: "json", required: false, desc: "Optional fields to return. Supported fields: propName, propDesc, aiRemark, selectType, tableType, subTableType.", alias: "f" },
+    { name: "limit", type: "number", required: false, desc: "Optional page size. Default: 20, maximum: 50.", alias: "l" },
+    { name: "offset", type: "number", required: false, desc: "Optional page offset. Default: 0.", alias: "o" }
   ],
   risk: "read",
   buildArgs: (ctx) => ({
     projectId: ctx.num("project_id"),
     scope: optionalString(ctx, "scope"),
     eventName: optionalString(ctx, "event_name"),
-    query: optionalString(ctx, "query")
+    query: optionalString(ctx, "query"),
+    fields: optionalJson(ctx, "fields"),
+    limit: optionalNumber(ctx, "limit"),
+    offset: optionalNumber(ctx, "offset")
   })
 });
 
@@ -186,16 +198,22 @@ var createVirtualProperty = createMcpCommand({
 // src/commands/te-meta/meta/list-metrics.ts
 var listMetrics = createMcpCommand({
   command: "+list_metrics",
-  description: "List metric metadata in the project",
+  description: "List metric metadata in the project. Query performs fuzzy matching on metricName, metricDesc, and metricRemark. Supports fields/limit/offset pagination.",
   flags: [
     { name: "project_id", type: "number", required: true, alias: "p", desc: "Project ID" },
-    { name: "query", type: "string", required: false, alias: "q", desc: "Optional keyword filter" }
+    { name: "query", type: "string", required: false, alias: "q", desc: "Optional keyword filter. Fuzzy match on metricName, metricDesc, metricRemark." },
+    { name: "fields", type: "json", required: false, desc: "Optional fields to return. Supported: metricId, metricName, metricDesc, metricRemark, metricMode, openId, creator, creatorLoginName, updateOpenId, updateCreator, updateLoginName, createTime, updateTime." },
+    { name: "limit", type: "number", required: false, desc: "Optional limit. Default: 20, maximum: 50." },
+    { name: "offset", type: "number", required: false, desc: "Optional offset. Default: 0." }
   ],
   risk: "read",
   mcpService: "te_analysis_extend",
   buildArgs: (ctx) => ({
     projectId: ctx.num("project_id"),
-    query: optionalString(ctx, "query")
+    query: optionalString(ctx, "query"),
+    fields: optionalJson(ctx, "fields"),
+    limit: optionalNumber(ctx, "limit"),
+    offset: optionalNumber(ctx, "offset")
   })
 });
 
@@ -356,6 +374,40 @@ var deleteTrackItems = createMcpCommand({
   })
 });
 
+// src/commands/te-meta/project/generate-track-program.ts
+var generateTrackProgram = createMcpCommand({
+  command: "+generate_track_program",
+  description: "Generate a tracking plan from structured business context (async)",
+  flags: [
+    { name: "project_id", type: "number", required: true, alias: "p", desc: "Project ID" },
+    { name: "language", type: "string", required: true, alias: "l", desc: "Language code (zh-CN, en-US, ja-JP, ko-KR)" },
+    { name: "form_data", type: "json", required: true, desc: "Structured business context JSON object, optional fields for example: account_system, revenue_model, core_gameplay, currency_system, main_entries, predefinedEvent, developmentCarrier" }
+  ],
+  risk: "write",
+  mcpService: "te_analysis_extend",
+  buildArgs: (ctx) => ({
+    projectId: ctx.num("project_id"),
+    language: ctx.str("language"),
+    formData: ctx.json("form_data")
+  })
+});
+
+// src/commands/te-meta/project/generate-track-sdk-sample.ts
+var generateTrackSdkSample = createMcpCommand({
+  command: "+generate_track_sdk_sample",
+  description: "Generate SDK sample files based on tracking plan (async)",
+  flags: [
+    { name: "project_id", type: "number", required: true, alias: "p", desc: "Project ID" },
+    { name: "sdk_type", type: "json", required: true, desc: "SDK types JSON array. Allowed values: android-java, server-php, ios-swift, server-python, web-js, server-java, server-nodejs, wechat-miniapp, harmonyos-arkts, android-kotlin, unity-csharp, cocos-creator-ts, server-go, server-cpp, ios-objc" }
+  ],
+  risk: "write",
+  mcpService: "te_analysis_extend",
+  buildArgs: (ctx) => ({
+    projectId: ctx.num("project_id"),
+    sdkType: ctx.json("sdk_type")
+  })
+});
+
 // src/commands/te-meta/project/create-project-mark-time.ts
 var createProjectMarkTime = createMcpCommand({
   command: "+create_project_mark_time",
@@ -405,16 +457,24 @@ var updateProjectMarkTime = createMcpCommand({
 // src/commands/te-meta/project/list-project-mark-times.ts
 var listProjectMarkTimes = createMcpCommand({
   command: "+list_project_mark_times",
-  description: "List project date markers",
+  description: "List project date markers. Query performs fuzzy matching on markContent. Supports fields/limit/offset pagination.",
   flags: [
     { name: "project_id", type: "number", required: true, alias: "p", desc: "Project ID" },
-    { name: "zone_offset", type: "number", required: false, desc: "Marker time zone offset" }
+    { name: "zone_offset", type: "number", required: false, desc: "Marker time zone offset" },
+    { name: "query", type: "string", required: false, alias: "q", desc: "Optional keyword filter. Fuzzy match on markContent." },
+    { name: "fields", type: "json", required: false, desc: "Optional fields to return. Supported: id, projectId, markTime, userZoneTime, zoneOffset, markContent, isShow, creatorName, creatorId, lastModifierName, lastModifierId, createTime, updateTime." },
+    { name: "limit", type: "number", required: false, desc: "Optional limit. Default: 20, maximum: 50." },
+    { name: "offset", type: "number", required: false, desc: "Optional offset. Default: 0." }
   ],
   risk: "read",
   mcpService: "te_analysis_extend",
   buildArgs: (ctx) => ({
     projectId: ctx.num("project_id"),
-    zoneOffset: optionalNumber(ctx, "zone_offset")
+    zoneOffset: optionalNumber(ctx, "zone_offset"),
+    query: optionalString(ctx, "query"),
+    fields: optionalJson(ctx, "fields"),
+    limit: optionalNumber(ctx, "limit"),
+    offset: optionalNumber(ctx, "offset")
   })
 });
 
@@ -441,6 +501,8 @@ var commands2 = [
   getTrackProgram,
   saveTrackItems,
   deleteTrackItems,
+  generateTrackProgram,
+  generateTrackSdkSample,
   createProjectMarkTime,
   updateProjectMarkTime,
   listProjectMarkTimes,
@@ -451,15 +513,23 @@ var project_default = commands2;
 // src/commands/te-meta/entity/list-entities.ts
 var listEntities = createMcpCommand({
   command: "+list_entities",
-  description: "List entities in the project",
+  description: "List entities in the project. Query performs fuzzy matching on entityName, columnName and columnDesc. Supports fields/limit/offset payload governance.",
   flags: [
     { name: "project_id", type: "number", required: true, desc: "Project ID", alias: "p" },
-    { name: "event_name", type: "string", required: false, desc: "Optional event name filter" }
+    { name: "event_name", type: "string", required: false, desc: "Optional event name filter" },
+    { name: "query", type: "string", required: false, desc: "Optional keyword filter. Fuzzy match is applied to entityName, columnName, and columnDesc; if omitted, all entities are returned.", alias: "q" },
+    { name: "fields", type: "json", required: false, desc: "Optional fields to return. Supported fields: entityId, entityName, columnName, columnDesc, selectType, tableType, entityType.", alias: "f" },
+    { name: "limit", type: "number", required: false, desc: "Optional page size. Default: 20, maximum: 50.", alias: "l" },
+    { name: "offset", type: "number", required: false, desc: "Optional page offset. Default: 0.", alias: "o" }
   ],
   risk: "read",
   buildArgs: (ctx) => ({
     projectId: ctx.num("project_id"),
-    eventName: optionalString(ctx, "event_name")
+    eventName: optionalString(ctx, "event_name"),
+    query: optionalString(ctx, "query"),
+    fields: optionalJson(ctx, "fields"),
+    limit: optionalNumber(ctx, "limit"),
+    offset: optionalNumber(ctx, "offset")
   })
 });
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@thinkingai/ae-cli",
-  "version": "1.0.3",
-  "description": "CLI tool for ThinkingAI AgenticEngine (AE) analytics platform",
+  "version": "1.0.18",
+  "description": "CLI tool for ThinkingAI (AE) analytics platform",
   "type": "module",
   "bin": {
     "ae-cli": "bin/ae-cli.js"
@@ -33,7 +33,7 @@
     "analytics",
     "cli"
   ],
-  "author": "ThinkingAI",
+  "author": "ThinkingData",
   "license": "MIT",
   "engines": {
     "node": ">=18.0.0"

package/skills/ae-analysis/SKILL.md

@@ -0,0 +1,287 @@
+---
+name: ae-analysis
+version: 3.0.0
+description: "AE/TE/ThinkingEngine/ThinkingAI ae-cli manual for analysis-side tasks in the AE system or analysis platform: reports, dashboards, alerts, ad hoc analysis, drilldown, audience clusters, tags, tag members, metrics and metric definitions, events, properties, virtual events, virtual properties, metadata, project configuration, tracking plans, event tracking, mark times, project lists, and resource links. Use when the user asks to query, create, update, refresh, inspect, troubleshoot, govern, or manage these AE analysis assets. Must use ae-cli, read the matching references/<tool_name>.md command manual before composing commands, and never guess command names, flags, JSON payloads, project_id, resource IDs, or parameter formats."
+metadata:
+  requires:
+    bins: ["ae-cli"]
+  cliHelp: "ae-cli --help"
+---
+
+# ae-analysis
+
+> **CRITICAL - This skill is self-contained.** Use the Global AE CLI Rules below; do not require a separate shared skill for analysis-side tasks.
+> **CRITICAL - For all commands that require `project_id`, you MUST satisfy `PROJECT_ID_GATE` first (no guessing): verify the project by ID/name with `analysis_common +list_projects` only when there is no valid project context yet, when the user switches project/host/environment, or when the supplied project is ambiguous. Reuse a project already verified in the same continuous conversation and same host/environment.**
+> **CRITICAL - For write operations in this skill, you MUST complete the post-write link loop when applicable:** after success and extractable `resource_id`, call `analysis_common +get_resource_url` and return the main result + resource link (or explicit link-failure reason).
+> **CRITICAL - Before running any `+<tool_name>` command, you MUST first read the corresponding `references/<tool_name>.md`.** The reference filename always equals the command name without the leading `+`, for example `+query_adhoc` -> `references/query_adhoc.md`.
+
+## Global AE CLI Rules
+
+AE CLI (`ae-cli`) is the command-line tool for the AE / TE / ThinkingEngine analysis platform. For AE analysis-side requests, prefer `ae-cli` and this skill's reference docs over model memory.
+
+Authentication priority:
+1. `TE_TOKEN` environment variable.
+2. Cached token in `~/.ae-cli/tokens.json`, usually valid for 20 hours.
+3. macOS Chrome token extraction via `ae-cli auth login`.
+
+Useful authentication commands:
+
+```bash
+ae-cli auth login
+ae-cli auth status
+ae-cli auth logout
+```
+
+Global parameters:
+
+| Parameter | Description |
+|---|---|
+| `--host <host>` | Target AE host. Use when the environment is not the default host. |
+| `--format <json|table>` | Output format. Default is JSON. |
+| `--jq <expr>` | jq filter expression for JSON output. |
+| `--dry-run` | Preview the request without executing it. |
+| `--yes` | Skip confirmation for write operations. Use only when the user intent is explicit or automation requires it. |
+
+Output and errors:
+- Successful commands return machine-readable JSON by default.
+- Failed commands return `{ "ok": false, "error": { "type": "...", "message": "...", "hint": "..." } }` and exit non-zero.
+- On auth/config errors, check `ae-cli auth status`, host configuration, and the target environment before retrying.
+
+Safety constraints:
+- Read commands can execute directly after required IDs and references are verified.
+- Write commands require explicit user intent and normally keep the confirmation prompt.
+- Use `--dry-run` before risky or complex writes.
+- Never invent command names, flags, JSON payloads, `project_id`, resource IDs, field names, event names, property names, metric definitions, or date formats. Read the matching command reference and discover real project metadata first.
+- **NEVER fabricate or guess resource names** (reports, dashboards, events, properties, metrics, clusters, tags, alerts). Always use list commands to discover real resources first. If a resource is not found after fuzzy search and full list fallback, explicitly tell the user "resource not found" and stop - do not proceed with fabricated names.
+
+Language consistency:
+- **Input-output language matching**: Always respond in the same language as the user's input.
+  - User asks in Chinese → Respond in Chinese, including result interpretation and error messages
+  - User asks in English → Respond in English
+- **CLI output handling**: CLI returns JSON in English, but your interpretation and summary MUST match user's language
+- **Resource names**: Keep original resource names as-is (don't translate), but descriptions and explanations should match user's language
+- **Error messages**: Translate CLI error messages to user's language when presenting results
+
+## When to Use
+
+Use `ae-analysis` for all AE analysis-side work below:
+
+- Domain `analysis`: alerts, reports/dashboards, ad-hoc model analysis, drilldown, entity/event details, schema helpers.
+- Domain `analysis_audience`: clusters/tags and definition schemas.
+- Domain `analysis_meta`: metadata governance, metrics, virtual metadata, project config, tracking plans, mark times, entity catalog.
+- Domain `analysis_common`: project listing and post-write resource links.
+
+If user intent is Engage/DataOps/Community, switch to `ae-engage` / `ae-dataops` / `ae-community`.
+
+## Command Format
+
+- `ae-cli analysis +<tool_name> [options]`
+- `ae-cli analysis_audience +<tool_name> [options]`
+- `ae-cli analysis_meta +<tool_name> [options]`
+- `ae-cli analysis_common +<tool_name> [options]`
+
+Conventions:
+- CLI flags use underscores, e.g. `--project_id`.
+- MCP params map automatically to camelCase.
+- JSON args pass as JSON string literals.
+- Write operations require confirmation unless `--yes`.
+
+## Mandatory Constraints
+
+### A. PROJECT_ID_GATE
+
+For any command requiring `project_id`:
+1. If the same continuous conversation already has a verified project context (`project_id`, project name when known, and host/environment), reuse it directly for follow-up commands.
+2. Call `analysis_common +list_projects` only when no verified project context exists, the user provides a new project ID/name, the user switches host/environment, the user asks to list projects, or the current project is ambiguous.
+3. Verify any new user-provided ID or name against returned projects before using it.
+4. If the user supplied an exact `project_id` and it uniquely matches one returned project in the intended host/environment, continue with that ID.
+5. If the project is missing, the name is ambiguous, the host/environment is unclear, or the supplied ID/name does not uniquely match, show candidate projects and stop for user choice.
+6. Do not use sample project IDs from reference docs as real IDs.
+7. When reusing verified project context, mention the reused `project_id` briefly if it helps the user understand why `+list_projects` was not called again.
+
+### B. Write-operation Post-link Completion
+
+When these writes succeed and `resource_id` is extractable, call `analysis_common +get_resource_url` and append link output:
+- `dashboard`: `+create_dashboard`, `+update_dashboard`
+- `report`: `+create_report`
+- `metric`: `+create_metric`, `+update_metric`
+- `alert`: `+create_alert`, `+update_alert`
+- `tag`: `+create_tag`, `+update_tag`
+- `cluster`: `+create_cluster`, `+create_result_cluster`, `+update_cluster`
+- `virtual_event`: `+create_virtual_event`
+- `event_virtual_prop` / `user_virtual_prop`: `+create_virtual_property`
+- `super_event` / `super_prop_event` / `super_prop_user`: `+batch_create_metadata`, `+batch_edit_metadata`
+
+Closed-loop check (must be explicit in result):
+- Write result
+- `resource_id` checked
+- `+get_resource_url` called or skipped (no ID)
+- Link completion status
+
+### C. FUZZY_SEARCH_FALLBACK
+
+For list commands with `--query` parameter (list_reports, list_dashboards, list_events, list_clusters, list_tags, list_alerts, list_metrics):
+
+1. **First attempt**: Use `--query` with user-provided keyword for fuzzy search
+2. **If no results found**, retry up to 2 more times with:
+   - Broader keywords (remove modifiers, use root words)
+   - Alternative terms or synonyms
+3. **After 3 failed fuzzy attempts**, fall back to full list (omit `--query`)
+4. **Present full list** to user and ask them to identify the target resource
+5. **Never proceed** with operations on non-existent resources
+
+**Example workflow:**
+- User asks: "Find active user report"
+- Attempt 1: `--query "active user"` → no results
+- Attempt 2: `--query "active"` → no results
+- Attempt 3: `--query "user"` → no results
+- Fallback: list all reports, show to user, ask for selection
+
+### D. QUERY_EXISTING_FIRST
+
+Before executing ad-hoc queries (`query_adhoc`), MUST check for existing reports/dashboards first:
+
+**Mandatory workflow for data queries:**
+
+1. **Identify user intent** - Extract what metrics/dimensions/filters the user wants
+2. **Search existing reports** - Use `list_reports --query <keyword>` to find matching reports
+3. **Search existing dashboards** - Use `list_dashboards --query <keyword>` to find matching dashboards
+4. **If found** - Use `query_report_data` or `query_dashboard_report_data` to get data from existing assets
+5. **If not found** - Only then use `query_adhoc` for ad-hoc analysis
+
+**Rationale:**
+- **Performance**: Existing reports are pre-computed and faster
+- **Consistency**: Reports have business-defined metrics and calibrated logic
+- **Resource efficiency**: Avoid redundant computation
+- **Permissions**: Users may have report access but not ad-hoc query permissions
+
+**Example:**
+- User: "Query active users in last 7 days"
+- Step 1: `list_reports --query "active user"` → found "DAU Active Users Report"
+- Step 2: `query_report_data --report_id <id>` → return data
+- ❌ WRONG: Directly use `query_adhoc` without checking existing reports
+
+**Exceptions (when ad-hoc is acceptable):**
+- User explicitly requests "ad-hoc query" or "ad-hoc analysis"
+- User wants custom filters/groupings not available in existing reports
+- User is exploring data for new insights (exploratory analysis)
+- No matching reports found after search + fallback
+
+## Tool Groups (69)
+
+### analysis (31)
+
+Alerts (5):
+- `+get_alert_definition_schema` ([doc](references/get_alert_definition_schema.md))
+- `+list_alerts` ([doc](references/list_alerts.md))
+- `+get_alert` ([doc](references/get_alert.md))
+- `+create_alert` ([doc](references/create_alert.md))
+- `+update_alert` ([doc](references/update_alert.md))
+
+Reports and Dashboards (13):
+- `+create_report` ([doc](references/create_report.md))
+- `+get_report_definition` ([doc](references/get_report_definition.md))
+- `+list_reports` ([doc](references/list_reports.md))
+- `+query_report_data` ([doc](references/query_report_data.md))
+- `+create_dashboard` ([doc](references/create_dashboard.md))
+- `+list_dashboards` ([doc](references/list_dashboards.md))
+- `+query_dashboard_detail` ([doc](references/query_dashboard_detail.md))
+- `+query_dashboard_report_data` ([doc](references/query_dashboard_report_data.md))
+- `+update_dashboard` ([doc](references/update_dashboard.md))
+- `+create_or_update_dashboard_note` ([doc](references/create_or_update_dashboard_note.md))
+- `+list_public_access_links` ([doc](references/list_public_access_links.md))
+- `+create_public_access_link` ([doc](references/create_public_access_link.md))
+- `+update_public_access_link` ([doc](references/update_public_access_link.md))
+
+Model Analysis (6):
+- `+query_adhoc` ([doc](references/query_adhoc.md))
+- `+drilldown_users` ([doc](references/drilldown_users.md))
+- `+drilldown_user_events` ([doc](references/drilldown_user_events.md))
+- `+create_result_cluster` ([doc](references/create_result_cluster.md))
+- `+load_filters` ([doc](references/load_filters.md))
+- `+get_table_columns` ([doc](references/get_table_columns.md))
+
+Entity/Event Details (4):
+- `+query_entity_details` ([doc](references/query_entity_details.md))
+- `+query_event_details` ([doc](references/query_event_details.md))
+- `+build_entity_details_sql` ([doc](references/build_entity_details_sql.md))
+- `+build_event_details_sql` ([doc](references/build_event_details_sql.md))
+
+Schema (3):
+- `+get_analysis_query_schema` ([doc](references/get_analysis_query_schema.md))
+- `+get_filter_schema` ([doc](references/get_filter_schema.md))
+- `+get_groupby_schema` ([doc](references/get_groupby_schema.md))
+
+### analysis_audience (14)
+
+Clusters (6):
+- `+create_cluster` ([doc](references/create_cluster.md))
+- `+get_clusters_by_name` ([doc](references/get_clusters_by_name.md))
+- `+list_cluster_members` ([doc](references/list_cluster_members.md))
+- `+list_clusters` ([doc](references/list_clusters.md))
+- `+update_cluster` ([doc](references/update_cluster.md))
+- `+refresh_cluster` ([doc](references/refresh_cluster.md))
+
+Tags (6):
+- `+create_tag` ([doc](references/create_tag.md))
+- `+get_tags_by_name` ([doc](references/get_tags_by_name.md))
+- `+list_tag_members` ([doc](references/list_tag_members.md))
+- `+list_tags` ([doc](references/list_tags.md))
+- `+update_tag` ([doc](references/update_tag.md))
+- `+refresh_tag` ([doc](references/refresh_tag.md))
+
+Schema Definitions (2):
+- `+get_cluster_definition_schema` ([doc](references/get_cluster_definition_schema.md))
+- `+get_tag_definition_schema` ([doc](references/get_tag_definition_schema.md))
+
+### analysis_meta (20)
+
+Metadata and Governance (10):
+- `+list_events` ([doc](references/list_events.md))
+- `+list_properties` ([doc](references/list_properties.md))
+- `+list_metrics` ([doc](references/list_metrics.md))
+- `+get_metric` ([doc](references/get_metric.md))
+- `+create_metric` ([doc](references/create_metric.md))
+- `+update_metric` ([doc](references/update_metric.md))
+- `+batch_edit_metadata` ([doc](references/batch_edit_metadata.md))
+- `+batch_create_metadata` ([doc](references/batch_create_metadata.md))
+- `+create_virtual_event` ([doc](references/create_virtual_event.md))
+- `+create_virtual_property` ([doc](references/create_virtual_property.md))
+
+Project and Tracking (11):
+- `+get_project_config` ([doc](references/get_project_config.md))
+- `+list_project_users` ([doc](references/list_project_users.md))
+- `+get_track_program` ([doc](references/get_track_program.md))
+- `+save_track_items` ([doc](references/save_track_items.md))
+- `+delete_track_items` ([doc](references/delete_track_items.md))
+- `+generate_track_program` ([doc](references/generate_track_program.md))
+- `+generate_track_sdk_sample` ([doc](references/generate_track_sdk_sample.md))
+- `+create_project_mark_time` ([doc](references/create_project_mark_time.md))
+- `+update_project_mark_time` ([doc](references/update_project_mark_time.md))
+- `+list_project_mark_times` ([doc](references/list_project_mark_times.md))
+- `+delete_project_mark_times` ([doc](references/delete_project_mark_times.md))
+
+Entity Catalog (1):
+- `+list_entities` ([doc](references/list_entities.md))
+
+### analysis_common (2)
+
+- `+list_projects` ([doc](references/list_projects.md))
+- `+get_resource_url` ([doc](references/get_resource_url.md))
+
+## Quick Verification
+
+```bash
+ae-cli analysis --help
+ae-cli analysis_audience --help
+ae-cli analysis_meta --help
+ae-cli analysis_common --help
+npm run verify:analysis-tools
+npm run verify:analysis-audience-tools
+npm run verify:analysis-meta-tools
+npm run verify:analysis-common-tools
+```
+
+## Reference Docs
+
+See the unified `references/` directory (69 command docs total).

package/skills/{te-meta/references/batch-create-metadata.md → ae-analysis/references/batch_create_metadata.md}

@@ -1,6 +1,6 @@
 # analysis_meta +batch_create_metadata (Batch Create Metadata)
 
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
 
 Domain: **Metadata Query**
 
@@ -9,8 +9,8 @@ Domain: **Metadata Query**
 
 ## Commands
 ```bash
-ae-cli analysis_meta +batch_create_metadata --project_id 1
-ae-cli analysis_meta +batch_create_metadata --project_id 1 --events '[{"eventName":"purchase"}]' --event_properties '[{"propName":"price","selectType":"number"}]' --user_properties '[{"propName":"vip_level","selectType":"string"}]'
+ae-cli analysis_meta +batch_create_metadata --project_id <project_id>
+ae-cli analysis_meta +batch_create_metadata --project_id <project_id> --events '[{"eventName":"purchase"}]' --event_properties '[{"propName":"price","selectType":"number"}]' --user_properties '[{"propName":"vip_level","selectType":"string"}]'
 ae-cli analysis_meta +batch_create_metadata --dry-run
 ```
 

package/skills/{te-meta/references/batch-edit-metadata.md → ae-analysis/references/batch_edit_metadata.md}

@@ -1,6 +1,6 @@
 # analysis_meta +batch_edit_metadata (Batch Edit Metadata)
 
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
 
 Domain: **Metadata Query**
 
@@ -10,7 +10,7 @@ Domain: **Metadata Query**
 
 ## Command
 ```bash
-ae-cli analysis_meta +batch_edit_metadata --project_id 1 --type event --items '[{"eventName":"purchase","eventDesc":"Purchase"}]'
+ae-cli analysis_meta +batch_edit_metadata --project_id <project_id> --type event --items '[{"eventName":"purchase","eventDesc":"Purchase"}]'
 ae-cli analysis_meta +batch_edit_metadata --dry-run
 ```
 

package/skills/{te-analysis/references/build-entity-details-sql.md → ae-analysis/references/build_entity_details_sql.md}

@@ -1,6 +1,6 @@
 # analysis +build_entity_details_sql (Generate Entity Details SQL)
 
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
 
 Domain: **Entity details SQL queries**
 
@@ -11,22 +11,22 @@ Domain: **Entity details SQL queries**
 
 ## Mandatory prerequisites (MUST)
 - Before constructing `--definition` / `--properties`, you must first read and follow these reference documents:
-  - [`../../te-audience/references/get-cluster-definition-schema.md`](../../te-audience/references/get-cluster-definition-schema.md)
-  - [`../../te-meta/references/list-events.md`](../../te-meta/references/list-events.md)
-  - [`../../te-meta/references/list-properties.md`](../../te-meta/references/list-properties.md)
+  - [`./get_cluster_definition_schema.md`](./get_cluster_definition_schema.md)
+  - [`./list_events.md`](./list_events.md)
+  - [`./list_properties.md`](./list_properties.md)
 - Do not generate the final `definition` / `properties` until the documentation review and prerequisite command calls are complete.
 
 ## Prerequisite call chain (required for constructing definition/properties)
 1. First confirm the cluster type (condition / sql).
-2. Read `get-cluster-definition-schema.md`, then call `ae-cli analysis_audience +get_cluster_definition_schema --cluster_type <condition|sql>` to get the structure.
-3. Read `list-events.md`, then call `ae-cli analysis_meta +list_events --project_id 1`.
-4. Read `list-properties.md`, then call `ae-cli analysis_meta +list_properties --project_id 1`.
+2. Read `get_cluster_definition_schema.md`, then call `ae-cli analysis_audience +get_cluster_definition_schema --cluster_type <condition|sql>` to get the structure.
+3. Read `list_events.md`, then call `ae-cli analysis_meta +list_events --project_id <project_id>`.
+4. Read `list_properties.md`, then call `ae-cli analysis_meta +list_properties --project_id <project_id>`.
 5. Build `definition` (and optional `properties`) from the schema + metadata, then call `+build_entity_details_sql`.
 
 ## Command
 ```bash
-ae-cli analysis +build_entity_details_sql --project_id 1 --definition '{}'
-ae-cli analysis +build_entity_details_sql --project_id 1 --entity_id 1001 --definition '{}' --properties '{}' --sort_by time --sort_order desc --limit 100 --zone_offset 8
+ae-cli analysis +build_entity_details_sql --project_id <project_id> --definition '{}'
+ae-cli analysis +build_entity_details_sql --project_id <project_id> --entity_id 1001 --definition '{}' --properties '{}' --sort_by time --sort_order desc --limit 100 --zone_offset 8
 ae-cli analysis +build_entity_details_sql --dry-run
 ```
 

package/skills/{te-analysis/references/build-event-details-sql.md → ae-analysis/references/build_event_details_sql.md}

@@ -1,6 +1,6 @@
 # analysis +build_event_details_sql (generate event detail SQL)
 
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
 
 Domain: **Event Detail SQL Queries**
 
@@ -11,21 +11,21 @@ Domain: **Event Detail SQL Queries**
 
 ## Mandatory Prerequisites (MUST)
 - Before building `--filters` / `--properties`, you must first read and follow the following reference docs:
-  - [`./get-filter-schema.md`](./get-filter-schema.md)
-  - [`../../te-meta/references/list-events.md`](../../te-meta/references/list-events.md)
-  - [`../../te-meta/references/list-properties.md`](../../te-meta/references/list-properties.md)
+  - [`./get_filter_schema.md`](./get_filter_schema.md)
+  - [`./list_events.md`](./list_events.md)
+  - [`./list_properties.md`](./list_properties.md)
 - Do not generate final `filters` / `properties` until the above docs have been read and the prerequisite commands have been called.
 
 ## Prerequisite Call Chain (required for filters/properties)
-1. Read `get-filter-schema.md`, then call `ae-cli analysis +get_filter_schema` to get the filter structure.
-2. Read `list-events.md`, then call `ae-cli analysis_meta +list_events --project_id 1` to confirm available event names.
-3. Read `list-properties.md`, then call `ae-cli analysis_meta +list_properties --project_id 1` to get available properties.
+1. Read `get_filter_schema.md`, then call `ae-cli analysis +get_filter_schema` to get the filter structure.
+2. Read `list_events.md`, then call `ae-cli analysis_meta +list_events --project_id <project_id>` to confirm available event names.
+3. Read `list_properties.md`, then call `ae-cli analysis_meta +list_properties --project_id <project_id>` to get available properties.
 4. Build `filters` / `properties` based on the schema and metadata, then call `+build_event_details_sql`.
 
 ## Commands
 ```bash
-ae-cli analysis +build_event_details_sql --project_id 1 --event_name login --start_time '2026-04-08 00:00:00' --end_time '2026-04-08 23:59:59'
-ae-cli analysis +build_event_details_sql --project_id 1 --event_name login --relative_date_range 0-7 --filters '{}' --properties '{}' --sort_by time --sort_order desc --limit 100 --zone_offset 8
+ae-cli analysis +build_event_details_sql --project_id <project_id> --event_name login --start_time '2026-04-08 00:00:00' --end_time '2026-04-08 23:59:59'
+ae-cli analysis +build_event_details_sql --project_id <project_id> --event_name login --relative_date_range 0-7 --filters '{}' --properties '{}' --sort_by time --sort_order desc --limit 100 --zone_offset 8
 ae-cli analysis +build_event_details_sql --dry-run
 ```
 

package/skills/{te-analysis/references/create-alert.md → ae-analysis/references/create_alert.md}

@@ -1,6 +1,6 @@
 # analysis +create_alert (Create Alert)
 
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
 
 Domain: **Metadata queries**
 
@@ -11,17 +11,17 @@ Domain: **Metadata queries**
 
 ## Mandatory prerequisites (MUST)
 - Before constructing `--definition`, you must first read and follow:
-  - [`./get-alert-definition-schema.md`](./get-alert-definition-schema.md)
+  - [`./get_alert_definition_schema.md`](./get_alert_definition_schema.md)
 - Do not generate the final `definition` until the documentation review and schema call are complete.
 
 ## Prerequisite call chain (required for constructing definition)
-1. Read `get-alert-definition-schema.md` to understand the return structure of `+get_alert_definition_schema`.
+1. Read `get_alert_definition_schema.md` to understand the return structure of `+get_alert_definition_schema`.
 2. Call `ae-cli analysis +get_alert_definition_schema` to get the schema.
 3. Build `definition` from the schema, then call `+create_alert`.
 
 ## Command
 ```bash
-ae-cli analysis +create_alert --project_id 1 --definition '{}'
+ae-cli analysis +create_alert --project_id <project_id> --definition '{}'
 ae-cli analysis +create_alert --dry-run
 ```