@thinkingai/ae-cli 6.0.34 → 6.0.35

package/dist/te-meta-VHCN4Q62.js

@@ -1,363 +0,0 @@
-import {
-  callMcpTool,
-  parseMcpResult,
-  resolveMcpUrl
-} from "./chunk-3P3562ZX.js";
-import "./chunk-LCXU3AAT.js";
-import "./chunk-E7UXXHO3.js";
-import "./chunk-IR4ZLVPW.js";
-import "./chunk-V6FR6WTW.js";
-import "./chunk-24BAVOX3.js";
-import "./chunk-LYVNONC4.js";
-
-// src/commands/te-meta/shared.ts
-function createMcpCommand(config) {
-  const toolName = config.command.slice(1);
-  const mcpService = config.mcpService || "analysis";
-  return {
-    service: "analysis_meta",
-    command: config.command,
-    description: config.description,
-    flags: config.flags,
-    risk: config.risk,
-    dryRun: (ctx) => ({
-      method: "tools/call",
-      url: resolveMcpUrl(ctx.mcpUrl(), ctx.host(), mcpService),
-      body: {
-        name: toolName,
-        arguments: config.buildArgs(ctx)
-      }
-    }),
-    execute: async (ctx) => {
-      const url = resolveMcpUrl(ctx.mcpUrl(), ctx.host(), mcpService);
-      const result = await callMcpTool(url, toolName, config.buildArgs(ctx), ctx.host());
-      return parseMcpResult(result);
-    }
-  };
-}
-function optionalString(ctx, name) {
-  const value = ctx.str(name);
-  return value === "" ? void 0 : value;
-}
-function optionalNumber(ctx, name) {
-  const value = ctx.str(name);
-  return value === "" ? void 0 : Number(value);
-}
-function optionalJson(ctx, name) {
-  const value = ctx.str(name);
-  return value === "" ? void 0 : ctx.json(name);
-}
-function requiredJsonString(ctx, name) {
-  return JSON.stringify(ctx.json(name));
-}
-
-// src/commands/te-meta/meta/batch-edit-metadata.ts
-var batchEditMetadata = createMcpCommand({
-  command: "+batch_edit_metadata",
-  description: "Batch edit effective system metadata only",
-  flags: [
-    { name: "project_id", type: "number", required: true, alias: "p", desc: "Project ID" },
-    { name: "type", type: "string", required: true, desc: "Metadata type: event, event_property, or user_property" },
-    { name: "items", type: "json", required: true, desc: "Batch edit item list JSON array" }
-  ],
-  risk: "write",
-  mcpService: "te_analysis_extend",
-  buildArgs: (ctx) => ({
-    projectId: ctx.num("project_id"),
-    type: ctx.str("type"),
-    items: ctx.json("items")
-  })
-});
-
-// src/commands/te-meta/meta/batch-create-metadata.ts
-var batchCreateMetadata = createMcpCommand({
-  command: "+batch_create_metadata",
-  description: "Batch create effective system metadata only",
-  flags: [
-    { name: "project_id", type: "number", required: true, alias: "p", desc: "Project ID" },
-    { name: "events", type: "json", required: false, desc: "Event creation list JSON array" },
-    { name: "event_properties", type: "json", required: false, desc: "Event property creation list JSON array" },
-    { name: "user_properties", type: "json", required: false, desc: "User property creation list JSON array" }
-  ],
-  risk: "write",
-  mcpService: "te_analysis_extend",
-  buildArgs: (ctx) => ({
-    projectId: ctx.num("project_id"),
-    events: optionalJson(ctx, "events"),
-    eventProperties: optionalJson(ctx, "event_properties"),
-    userProperties: optionalJson(ctx, "user_properties")
-  })
-});
-
-// src/commands/te-meta/meta/index.ts
-var commands = [
-  batchEditMetadata,
-  batchCreateMetadata
-];
-var meta_default = commands;
-
-// src/commands/te-meta/project/get-project-config.ts
-var getProjectConfig = createMcpCommand({
-  command: "+get_project_config",
-  description: "Get project configuration details including timezone settings",
-  flags: [
-    { name: "project_id", type: "number", required: true, desc: "Project ID", alias: "p" }
-  ],
-  risk: "read",
-  buildArgs: (ctx) => ({
-    projectId: ctx.num("project_id")
-  })
-});
-
-// src/commands/te-meta/project/list-project-users.ts
-var listProjectUsers = createMcpCommand({
-  command: "+list_project_users",
-  description: "Get all project members",
-  flags: [
-    { name: "project_id", type: "number", required: true, desc: "Project ID", alias: "p" }
-  ],
-  risk: "read",
-  buildArgs: (ctx) => ({
-    projectId: ctx.num("project_id")
-  })
-});
-
-// src/commands/te-meta/project/get-track-program.ts
-var getTrackProgram = createMcpCommand({
-  command: "+get_track_program",
-  description: "Query tracking-plan metadata (bury program)",
-  flags: [
-    { name: "project_id", type: "number", required: true, alias: "p", desc: "Project ID" }
-  ],
-  risk: "read",
-  mcpService: "te_analysis_extend",
-  buildArgs: (ctx) => ({
-    projectId: ctx.num("project_id")
-  })
-});
-
-// src/commands/te-meta/project/save-track-items.ts
-var saveTrackItems = createMcpCommand({
-  command: "+save_track_items",
-  description: "Create or update tracking-plan metadata only",
-  flags: [
-    { name: "project_id", type: "number", required: true, alias: "p", desc: "Project ID" },
-    { name: "track_data", type: "json", required: true, desc: "Track program JSON object with events/eventProps/userProps/commonEventProps" }
-  ],
-  risk: "write",
-  mcpService: "te_analysis_extend",
-  buildArgs: (ctx) => ({
-    projectId: ctx.num("project_id"),
-    trackData: requiredJsonString(ctx, "track_data")
-  })
-});
-
-// src/commands/te-meta/project/delete-track-items.ts
-var deleteTrackItems = createMcpCommand({
-  command: "+delete_track_items",
-  description: "Delete tracking-plan metadata items only",
-  flags: [
-    { name: "project_id", type: "number", required: true, alias: "p", desc: "Project ID" },
-    { name: "delete_data", type: "json", required: true, desc: "Delete payload JSON object with events/eventPropNames/userPropNames/commonEventPropNames" }
-  ],
-  risk: "high-risk-write",
-  mcpService: "te_analysis_extend",
-  buildArgs: (ctx) => ({
-    projectId: ctx.num("project_id"),
-    deleteData: requiredJsonString(ctx, "delete_data")
-  })
-});
-
-// 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",
-  description: "Create a project date marker",
-  flags: [
-    { name: "project_id", type: "number", required: true, alias: "p", desc: "Project ID" },
-    { name: "marked_at", type: "string", required: true, desc: "Marked time yyyy-MM-dd HH:mm" },
-    { name: "zone_offset", type: "number", required: false, desc: "Marker time zone offset" },
-    { name: "content", type: "string", required: true, desc: "Marker content" },
-    { name: "is_visible", type: "number", required: false, desc: "Whether the marker is visible. Default: 1" }
-  ],
-  risk: "write",
-  mcpService: "te_analysis_extend",
-  buildArgs: (ctx) => ({
-    projectId: ctx.num("project_id"),
-    markedAt: ctx.str("marked_at"),
-    zoneOffset: optionalNumber(ctx, "zone_offset"),
-    content: ctx.str("content"),
-    isVisible: optionalNumber(ctx, "is_visible")
-  })
-});
-
-// src/commands/te-meta/project/update-project-mark-time.ts
-var updateProjectMarkTime = createMcpCommand({
-  command: "+update_project_mark_time",
-  description: "Update an existing project date marker",
-  flags: [
-    { name: "mark_time_id", type: "number", required: true, desc: "Mark time ID" },
-    { name: "project_id", type: "number", required: true, alias: "p", desc: "Project ID" },
-    { name: "marked_at", type: "string", required: true, desc: "Marked time yyyy-MM-dd HH:mm" },
-    { name: "zone_offset", type: "number", required: false, desc: "Marker time zone offset" },
-    { name: "content", type: "string", required: true, desc: "Marker content" },
-    { name: "is_visible", type: "number", required: false, desc: "Whether the marker is visible. Default: 1" }
-  ],
-  risk: "write",
-  mcpService: "te_analysis_extend",
-  buildArgs: (ctx) => ({
-    markTimeId: ctx.num("mark_time_id"),
-    projectId: ctx.num("project_id"),
-    markedAt: ctx.str("marked_at"),
-    zoneOffset: optionalNumber(ctx, "zone_offset"),
-    content: ctx.str("content"),
-    isVisible: optionalNumber(ctx, "is_visible")
-  })
-});
-
-// src/commands/te-meta/project/list-project-mark-times.ts
-var listProjectMarkTimes = createMcpCommand({
-  command: "+list_project_mark_times",
-  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: "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: 50, maximum: 200.", min: 1, max: 200 },
-    { 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"),
-    query: optionalString(ctx, "query"),
-    fields: optionalJson(ctx, "fields"),
-    limit: optionalNumber(ctx, "limit"),
-    offset: optionalNumber(ctx, "offset")
-  })
-});
-
-// src/commands/te-meta/project/delete-project-mark-times.ts
-var deleteProjectMarkTimes = createMcpCommand({
-  command: "+delete_project_mark_times",
-  description: "Delete one or more project date markers",
-  flags: [
-    { name: "project_id", type: "number", required: true, alias: "p", desc: "Project ID" },
-    { name: "mark_time_ids", type: "json", required: true, desc: "Marker ID list JSON array" }
-  ],
-  risk: "high-risk-write",
-  mcpService: "te_analysis_extend",
-  buildArgs: (ctx) => ({
-    projectId: ctx.num("project_id"),
-    markTimeIds: ctx.json("mark_time_ids")
-  })
-});
-
-// src/commands/te-meta/project/index.ts
-var commands2 = [
-  getProjectConfig,
-  listProjectUsers,
-  getTrackProgram,
-  saveTrackItems,
-  deleteTrackItems,
-  generateTrackProgram,
-  generateTrackSdkSample,
-  createProjectMarkTime,
-  updateProjectMarkTime,
-  listProjectMarkTimes,
-  deleteProjectMarkTimes
-];
-var project_default = commands2;
-
-// src/commands/te-meta/entity/list-entities.ts
-var listEntities = createMcpCommand({
-  command: "+list_entities",
-  description: "List entities in the project. Query performs fuzzy matching on entityName, columnName and columnDesc. Supports fields/limit/offset payload governance. Default returned fields: entityId, entityName, columnName, columnDesc, selectType. Entity metadata exposes columnDesc as the description field; no remark field is available in this list response.",
-  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: "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. Default fields when omitted: entityId, entityName, columnName, columnDesc, selectType.", alias: "f" },
-    { name: "limit", type: "number", required: false, desc: "Optional page size. Default: 50, maximum: 200.", alias: "l", min: 1, max: 200 },
-    { 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"),
-    query: optionalString(ctx, "query"),
-    fields: optionalJson(ctx, "fields"),
-    limit: optionalNumber(ctx, "limit"),
-    offset: optionalNumber(ctx, "offset")
-  })
-});
-
-// src/commands/te-meta/entity/create-entity.ts
-var createEntity = createMcpCommand({
-  command: "+create_entity",
-  description: "Create a new entity that links an event or user property as an analysis dimension.",
-  flags: [
-    { name: "project_id", type: "number", required: true, desc: "Project ID", alias: "p" },
-    { name: "entity_name", type: "string", required: true, desc: "Entity name" },
-    { name: "column_name", type: "string", required: true, desc: "Property column name to associate with the entity" },
-    { name: "table_type", type: "number", required: true, desc: "Table type: 0 = event property, 1 = user property" }
-  ],
-  risk: "write",
-  mcpService: "te_analysis_extend",
-  buildArgs: (ctx) => ({
-    projectId: ctx.num("project_id"),
-    entityName: ctx.str("entity_name"),
-    columnName: ctx.str("column_name"),
-    tableType: ctx.num("table_type")
-  })
-});
-
-// src/commands/te-meta/entity/index.ts
-var commands3 = [listEntities, createEntity];
-var entity_default = commands3;
-
-// src/commands/te-meta/index.ts
-var commands4 = [
-  ...meta_default,
-  ...project_default,
-  ...entity_default
-];
-var te_meta_default = commands4;
-export {
-  te_meta_default as default
-};

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

@@ -1,41 +0,0 @@
-# analysis_meta +batch_create_metadata (Batch Create Metadata)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Metadata Query**
-
-## Use Cases
-- Batch create SYSTEM METADATA in one atomic request (events/eventProperties/userProperties) and apply name-based associations. This tool is only for effective production metadata, not tracking-plan metadata. For bury plan draft/review/publish data, use BuryProgramTool only.
-- Do not use it to edit existing metadata; use `+batch_edit_metadata` after resolving the existing names.
-
-## Output
-The response reports the batch creation outcome. Treat any item-level validation error as a failed item; do not assume the whole requested batch was created from transport success alone.
-
-## Commands
-```bash
-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
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--events` | No | Event creation list. Each item: eventName(required), eventDesc(optional), remark(optional), superEventPropNames(optional List<String>). |
-| `--event_properties` | No | Event property creation list. Each item: propName(required), selectType(required canonical: number/string/date/bool/list; aliases like datetime/timestamp/time auto-normalize to date), propDesc(optional, defaults to propName when omitted), propRemark(optional), commonProp(optional boolean), superEventNames(optional List<String>). |
-| `--user_properties` | No | User property creation list. Each item: propName(required), selectType(required canonical: number/string/date/bool/list; aliases like datetime/timestamp/time auto-normalize to date), propDesc(optional, defaults to propName when omitted), propRemark(optional). |
-
-## Decision Rules
-- For the first run, pass only the required parameter (`--project_id`) to confirm the path works, then add optional parameters.
-- Wrap JSON parameters in single quotes (for example `--events '{}'` and `--event_properties '{}'`) to avoid shell escaping issues.
-- At least one non-empty list among `--events`, `--event_properties`, and `--user_properties` must be provided.
-- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
-- This is an ordinary `write` operation and does not require CLI confirmation.
-
-## Next Steps After Failure
-- If required parameters are missing, fall back to the smallest runnable command and fill them in first (focus on `--project_id`).
-- If `Invalid JSON` appears, first validate with the smallest JSON structure (such as `{}` or `[]`), then add fields step by step.
-
-## Recommended Chaining
-- +batch_create_metadata -> +batch_edit_metadata

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

@@ -1,39 +0,0 @@
-# analysis_meta +batch_edit_metadata (Batch Edit Metadata)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Metadata Query**
-
-## Use Cases
-- Batch edit SYSTEM METADATA already effective in project (super events / event properties / user properties). Do NOT use for tracking-plan metadata (bury/track program); tracking plan operations must use BuryProgramTool. Routing rule: if target is planned/unpublished bury metadata, never call this tool.
-- Batch edit SYSTEM METADATA already effective in project (super events / event properties / user properties).
-
-## Output
-The response reports the batch update outcome. Review item-level failures before claiming that every requested metadata item changed.
-
-## Command
-```bash
-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
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--type` | Yes | Type of metadata to update: event, event_property, or user_property |
-| `--items` | Yes | Batch update list. For event: eventName (required), eventDesc (optional), remark (optional). For properties: propName (required), propDesc (optional), remark (optional). |
-
-## Decision Rules
-- First run should only pass required parameters (`--project_id`, `--type`, `--items`), and add optional parameters only after the path is confirmed to work.
-- Wrap JSON arguments in single quotes (for example `--items '{}'`) to avoid shell escaping issues.
-- `--type` only accepts `event`, `event_property`, and `user_property`.
-- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
-- This is an ordinary `write` operation and does not require CLI confirmation.
-
-## Next Steps After Failure
-- If required parameters are missing, fall back to the smallest runnable command and fill them in (focus on `--project_id`, `--type`, and `--items`).
-- If `Invalid JSON` occurs, validate with the smallest JSON structure first (for example `{}` or `[]`), then add fields step by step.
-
-## Recommended Chaining
-- +batch_edit_metadata -> +batch_create_metadata

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

@@ -1,38 +0,0 @@
-# analysis +cancel_query (cancel MCP query)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Query lifecycle**
-
-## Use Cases
-- Cancel a running MCP query when the user asks to stop waiting.
-- Cancel a query when the caller or agent timed out before the query returned but it may still be running on the server.
-- Cancel a query by the same `requestId` that was supplied to or returned by a previous query command.
-- For proactive cancellation, pass `requestId` to the query tool before starting it, then call `cancel_query` with the same value if you stop waiting.
-- If a query returns `fetch failed`, hits an HTTP timeout, or the caller stops waiting, the backend query may still be running; call `+cancel_query --request_id <same value>` with the preset `requestId`.
-- MCP query tools require caller-supplied `requestId`; generate and pass it before starting any cancelable query, then reuse the same value if cleanup is needed.
-
-## Command
-```bash
-ae-cli analysis +cancel_query --request_id mcp_0123456789abcdef0123456789abcdef
-ae-cli analysis +cancel_query --request_id mcp_0123456789abcdef0123456789abcdef --reason "agent timeout"
-ae-cli analysis +cancel_query --request_id mcp_0123456789abcdef0123456789abcdef --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--request_id` | Yes | Request ID returned by a query tool in `metadata.requestId`, or the requestId supplied before starting the query. It must use `mcp_<32 lowercase hex UUID>`, for example `mcp_0123456789abcdef0123456789abcdef`. |
-| `--reason` | No | Optional cancellation reason. Default: `MCP_CANCEL_QUERY_TOOL`. |
-
-## Decision Rules
-- This is an ordinary `write` operation and does not require CLI confirmation.
-- The request must belong to the current MCP user. Otherwise the service returns `REQUEST_NOT_FOUND_OR_NOT_OWNED`.
-- Do not invent a request ID. Use the ID from the query response or the ID explicitly supplied to the original query.
-- This command cancels by request ID only. It does not cancel by SQL text, report ID, dashboard ID, BI panel ID, run ID, or tool call ID.
-- For query commands that expose `--request_id`, supplying a stable ID before execution is required. Use `mcp_<32 lowercase hex UUID>`, for example `mcp_0123456789abcdef0123456789abcdef`, so proactive cancellation does not depend on waiting for the response metadata.
-- For query commands that may exceed the CLI/MCP HTTP timeout, preset `--request_id`; if `fetch failed`, HTTP timeout, or caller timeout happens, immediately call `+cancel_query --request_id <same value>`.
-
-## Next Steps on Failure
-- If `REQUEST_NOT_FOUND_OR_NOT_OWNED` appears, verify the request ID, user identity, host, and whether the original query already finished.
-- If cancellation succeeds but the UI still shows stale data, refresh the query status/result surface rather than sending another cancel blindly.

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

@@ -1,47 +0,0 @@
-# analysis +create_alert (Create Alert)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Metadata queries**
-
-## Use Cases
-- Precondition helper: call `+get_alert_definition_schema` to get the structure before using this tool.
-- Create a new alert. After creation, use list_alerts or get_alert to retrieve the created alert. See get_alert_definition_schema for the parameter structure.
-- Create a new alert.
-
-## Mandatory prerequisites (MUST)
-- Before constructing `--definition`, you must first read and follow:
-  - [`./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`.
-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 <project_id> --definition '{}'
-ae-cli analysis +create_alert --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--definition` | Yes | Alert definition JSON. MUST call `+get_alert_definition_schema` first and strictly follow the returned structure. |
-
-## Decision Rules
-- `definition` cannot be written from experience alone: it must satisfy the alert schema structure constraints.
-- On the first run, start with only the required parameters (`--project_id`, `--definition`) and add optional parameters after confirming the path works.
-- Wrap JSON parameters in single quotes (for example `--definition '{}'`) to avoid shell escaping issues.
-- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
-- This is an ordinary `write` operation and does not require CLI confirmation.
-
-## Next Steps on Failure
-- If required parameters are missing, fall back to the smallest runnable command and fill them in first (focus on `--project_id` and `--definition`).
-- If `Invalid JSON` appears, first check the schema required fields and enumeration values, then add fields incrementally.
-- If the result after writing does not match expectations, immediately read back the corresponding list/get interface to compare before and after.
-
-## Recommended chaining
-- +get_alert_definition_schema -> +create_alert

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

@@ -1,39 +0,0 @@
-# analysis_meta +create_entity (Create Entity)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Entity Management**
-
-## Use Cases
-- Create a new entity that links an event property or user property as an analysis dimension.
-- Use `+list_entities` first to confirm the entity does not already exist.
-
-## Commands
-```bash
-ae-cli analysis_meta +create_entity --project_id <project_id> --entity_name "User Entity" --column_name user_id --table_type 1
-ae-cli analysis_meta +create_entity --project_id <project_id> --entity_name "Event Entity" --column_name event_col --table_type 0
-ae-cli analysis_meta +create_entity --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--entity_name` | Yes | Entity name |
-| `--column_name` | Yes | Property column name to associate with the entity |
-| `--table_type` | Yes | Table type: `0` = event property, `1` = user property |
-
-## Decision Rules
-- `--table_type` must be `0` (event property) or `1` (user property); no other values are accepted.
-- Before using `--column_name`, call `analysis-meta property list` to verify it exists. If the same column name appears in **both** event properties and user properties, **stop and ask the user which table type to use** — do not guess `--table_type`. Ask every time this condition is met; never carry over the answer from a previous request.
-- For the first run, pass only the required parameters and confirm before adding others.
-- This is an ordinary `write` operation and does not require CLI confirmation.
-
-## Next Steps After Failure
-- If `PROJECT_ID_REQUIRED` or `ENTITY_NAME_REQUIRED` appears, check that all required parameters are provided.
-- If `INVALID_TABLE_TYPE` appears, verify `--table_type` is exactly `0` or `1`.
-- If the result after writing is not as expected, use `analysis_meta +list_entities` to compare before and after.
-
-## Recommended Chaining
-- `analysis_meta +list_entities` → `+create_entity`
-- `analysis-meta property list` → `+create_entity`

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

@@ -1,39 +0,0 @@
-# analysis_meta +create_project_mark_time (Create Project Date Marker)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Project Configuration**
-
-## Use Cases
-- Create a project date marker. Returns the new marker ID, timestamp, content, and visibility status.
-- Create a project date marker.
-- Do not use it to modify an existing marker; use `+update_project_mark_time` with the verified marker ID.
-
-## Command
-```bash
-ae-cli analysis_meta +create_project_mark_time --project_id <project_id> --marked_at '2026-04-09 10:00' --content demo
-ae-cli analysis_meta +create_project_mark_time --project_id <project_id> --marked_at '2026-04-09 10:00' --zone_offset 8 --content demo --is_visible 1
-ae-cli analysis_meta +create_project_mark_time --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--marked_at` | Yes | Marker timestamp. Format: yyyy-MM-dd HH:mm |
-| `--zone_offset` | No | Marker time zone offset |
-| `--content` | Yes | Marker content |
-| `--is_visible` | No | Whether the marker is visible. Default: 1 |
-
-## Decision Rules
-- First run should only pass required parameters (`--project_id`, `--marked_at`, `--content`), and add optional parameters only after the path is confirmed to work.
-- For date/time ranges, first validate with a short range, then expand the range step by step.
-- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
-- This is an ordinary `write` operation and does not require CLI confirmation.
-
-## Next Steps After Failure
-- If required parameters are missing, fall back to the smallest runnable command and fill them in (focus on `--project_id`, `--marked_at`, and `--content`).
-- If the result after writing is not as expected, immediately read back the corresponding list/get interface for a before-and-after comparison.
-
-## Recommended Chaining
-- +create_project_mark_time -> +list_project_mark_times

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

@@ -1,32 +0,0 @@
-# analysis +delete_alert (Delete Alert)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Alert Management**
-
-## Use Cases
-- Permanently delete an alert by its ID.
-- Do not use this command to disable or edit an alert; use `+update_alert` when the alert must remain.
-
-## Output
-Success confirms that the specified alert was deleted. The command does not return alert data; use `+list_alerts` to verify it is absent.
-
-## Commands
-```bash
-ae-cli analysis +delete_alert --project_id <project_id> --alert_id <alert_id> --dry-run
-# Summarize the target and impact, then wait for explicit user confirmation.
-ae-cli analysis +delete_alert --project_id <project_id> --alert_id <alert_id> --yes
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--alert_id` | Yes | Alert ID to delete |
-
-## Decision Rules
-- Use `+list_alerts` first to confirm the alert ID before deleting.
-- This is `high-risk-write`: inspect the dry-run, summarize the target and impact, and wait for explicit user confirmation before the `--yes` execution.
-
-## Recommended Chain
-- `+list_alerts` -> `+delete_alert`