@thinkingai/ae-cli 6.1.6 → 6.1.7

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

@@ -1,36 +0,0 @@
-# analysis_meta +delete_project_mark_times (Delete Project Mark Times)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Project Configuration**
-
-## Use Cases
-- Delete one or more project date markers.
-- Do not use it to hide or edit a marker; use `+update_project_mark_time` when the marker should remain.
-
-## Commands
-```bash
-ae-cli analysis_meta +delete_project_mark_times --project_id <project_id> --mark_time_ids '[]' --dry-run
-# Summarize the target and impact, then wait for explicit user confirmation.
-ae-cli analysis_meta +delete_project_mark_times --project_id <project_id> --mark_time_ids '[]' --yes
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--mark_time_ids` | Yes | List of marker IDs |
-
-## Decision Rules
-- For the first run, pass only the required parameters (`--project_id` and `--mark_time_ids`) to confirm the path works, then add optional parameters.
-- Wrap JSON parameters in single quotes (for example `--mark_time_ids '{}'`) to avoid shell escaping issues.
-- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
-- This is `high-risk-write`: inspect the dry-run, summarize the target and impact, and wait for explicit user confirmation before the `--yes` execution.
-
-## 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` and `--mark_time_ids`).
-- If `Invalid JSON` appears, first validate with the smallest JSON structure (such as `{}` or `[]`), then add fields step by step.
-- If the result after writing does not match expectations, immediately reread the corresponding list/get interfaces for before-and-after comparison.
-
-## Recommended Chaining
-- +list_project_mark_times -> +delete_project_mark_times

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

@@ -1,36 +0,0 @@
-# analysis_meta +delete_track_items (Delete Track Program Items)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Project Configuration**
-
-## Use Cases
-- Delete TRACKING-PLAN metadata items only. Do not use for effective system metadata deletion/editing; those belong to MetaPowerTool/other system metadata flows.
-- Delete TRACKING-PLAN metadata items only.
-
-## Command
-```bash
-ae-cli analysis_meta +delete_track_items --project_id <project_id> --delete_data '{}' --dry-run
-# Summarize the target and impact, then wait for explicit user confirmation.
-ae-cli analysis_meta +delete_track_items --project_id <project_id> --delete_data '{}' --yes
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--delete_data` | Yes | Delete payload JSON object with events/eventPropNames/userPropNames/commonEventPropNames. At least one list must be provided. |
-
-## Decision Rules
-- First run should only pass required parameters (`--project_id`, `--delete_data`), and add optional parameters only after the path is confirmed to work.
-- Wrap JSON arguments in single quotes (for example `--delete_data '{}'`) to avoid shell escaping issues.
-- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
-- This is `high-risk-write`: inspect the dry-run, summarize the target and impact, and wait for explicit user confirmation before the `--yes` execution.
-
-## Next Steps After Failure
-- If required parameters are missing, fall back to the smallest runnable command and fill them in (focus on `--project_id` and `--delete_data`).
-- If `Invalid JSON` occurs, validate with the smallest JSON structure first (for example `{}` or `[]`), then add fields step by step.
-- 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
-- +get_track_program -> +delete_track_items -> +get_track_program

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

@@ -1,52 +0,0 @@
-# analysis_meta +generate_track_program (Generate Tracking Plan)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Project Configuration**
-
-## Use Cases
-- Generate a tracking plan from structured business context. This AI generation flow is different from save_track_items: save_track_items persists explicitly provided plan items, while this tool requests AI generation and saves the generated result asynchronously.
-- Users should check the in-site message center for final results.
-- Do not use it to persist a fully specified set of tracking items; use `+save_track_items` when the exact items are already known.
-
-## CRITICAL: Pre-execution Check
-**Before calling this command, you MUST:**
-1. Call `+get_track_program` first to check if a tracking plan already exists.
-2. If the tracking plan is empty/missing, proceed directly with `+generate_track_program`.
-3. If the tracking plan already exists, STOP and warn the user: "A tracking plan already exists. Generating a new one will trigger a merge operation. Do you want to continue?" Wait for user confirmation before proceeding.
-
-## Commands
-```bash
-ae-cli analysis_meta +generate_track_program --project_id <project_id> --language <language> --form_data '{}'
-ae-cli analysis_meta +generate_track_program --dry-run
-```
-
-## Parameters
-| Parameter             | Required | Description                                                                                                                                                                                                                                                                                                                                                                              |
-|-----------------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `--project_id` / `-p` | Yes      | Project ID                                                                                                                                                                                                                                                                                                                                                                               |
-| `--language` / `-l`   | Yes      | Language code. Supported values: `zh-CN`, `en-US`, `ja-JP`, `ko-KR`                                                                                                                                                                                                                                                                                                                      |
-| `--form_data`         | Yes      | Structured business context JSON object. Optional fields for example: account_system, revenue_model, core_gameplay, currency_system, main_entries, predefinedEvent (array of event names like install, start, close), developmentCarrier (array of platforms like Android, iOS, Unity, Cocos, Douyin Mini Game, WeChat Mini Game). All fields can be customized based on business needs. |
-
-## Decision Rules
-- **CRITICAL: Always call `+get_track_program` first to check existing tracking plan before generating.**
-- First run should only pass the required parameters (`--project_id`, `--language`, `--form_data`).
-- Wrap JSON arguments in single quotes (for example `--form_data '{}'`) to avoid shell escaping issues.
-- This is an asynchronous operation; check in-site message center for generation results.
-- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
-
-## Next Steps After Failure
-- If required parameters are missing, fall back to the smallest runnable command and fill them in (focus on `--project_id`, `--language`, and `--form_data`).
-- If `Invalid JSON` occurs, validate with the smallest JSON structure first.
-
-## Agent Response Flow
-**After successful command execution, the agent MUST inform the user in English:**
-1. The command has been submitted successfully
-2. It's running asynchronously in the background
-3. Check the TE page inbox/notifications for the generation results
-
-Example response: "Command submitted successfully. The tracking plan generation is running asynchronously. Please check your TE inbox for the results once it completes."
-
-## Recommended Chaining
-- **+get_track_program (check existing) -> +generate_track_program (if empty or user confirms) -> (check message center) -> +get_track_program (verify result)**
-- +get_project_config -> +get_track_program -> +generate_track_program

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

@@ -1,44 +0,0 @@
-# analysis_meta +generate_track_sdk_sample (Generate SDK Sample Files)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Project Configuration**
-
-## Use Cases
-- Generate SDK sample files based on the current tracking plan and requested SDK types. This flow is asynchronous and users should check in-site messages for final downloadable results.
-- Useful for developers who need SDK integration code samples based on the tracking plan.
-- Do not use it to create or change the tracking plan itself; generate samples only after `+get_track_program` confirms the plan content.
-
-## Commands
-```bash
-ae-cli analysis_meta +generate_track_sdk_sample --project_id <project_id> --sdk_type '["android-java","ios-swift"]'
-ae-cli analysis_meta +generate_track_sdk_sample --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--sdk_type` | Yes | SDK types as 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. |
-
-## Decision Rules
-- First run should only pass the required parameters (`--project_id`, `--sdk_type`).
-- Wrap JSON arguments in single quotes (for example `--sdk_type '["android-java"]'`) to avoid shell escaping issues.
-- This is an asynchronous operation; check in-site message center for downloadable SDK sample results.
-- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
-
-## Next Steps After Failure
-- If required parameters are missing, fall back to the smallest runnable command and fill them in (focus on `--project_id` and `--sdk_type`).
-- If `SDK_TYPE_INVALID` occurs, verify that all SDK types are from the allowed values list: 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.
-- If `Invalid JSON` occurs, validate with the smallest JSON array first (for example `["android-java"]`).
-
-## Agent Response Flow
-**After successful command execution, the agent MUST inform the user in English:**
-1. The command has been submitted successfully
-2. It's running asynchronously in the background
-3. Check the TE page inbox/notifications for the final downloadable results
-
-Example response: "Command submitted successfully. The SDK sample generation is running asynchronously. Please check your TE inbox for the download link once it completes."
-
-## Recommended Chaining
-- +get_track_program -> +generate_track_sdk_sample -> (check message center for download)

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

@@ -1,35 +0,0 @@
-# analysis +get_alert (view alert definition)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Metadata Lookup**
-
-## Use Cases
-- Get detailed information about a specific alert by alertId.
-- Do not use it to discover an unknown alert ID; call `+list_alerts` first.
-
-## Output
-Returns the alert identity and saved definition. Use that returned definition as the baseline before an update; do not reconstruct it from memory.
-
-## Commands
-```bash
-ae-cli analysis +get_alert --project_id <project_id> --alert_id 1
-ae-cli analysis +get_alert --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--alert_id` / `-a` | Yes | Alert ID |
-
-## Decision Rules
-- For the first run, it is recommended to pass only the required parameters (`--project_id`, `--alert_id`) and add optional parameters after confirming the chain works.
-- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
-
-## Next Step After Failure
-- If required parameters are missing, fall back to the smallest runnable command and fill them in (focus on `--project_id`, `--alert_id`).
-- If reading fails, first verify whether the object ID exists and belongs to the current project.
-
-## Recommended Chaining
-- +get_alert

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

@@ -1,33 +0,0 @@
-# analysis +get_alert_definition_schema (Get Alert Definition Schema)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Metadata queries**
-
-## Use Cases
-- Helper tool positioning: this command provides structural definitions (schema) and should be used as a prerequisite step.
-- Recommended order: first use the current schema tool to get the structure, then call the specific business tool.
-- Typical follow-up tools: `+create_alert`, `+update_alert`
-- Get the alert definition schema. Returns field definitions, enum descriptions, and examples for creating or updating alerts.
-- Use this to understand the alert definition structure before calling create_alert or update_alert.
-- Do not use the schema response as an alert instance or query result; it only describes valid definition fields.
-
-## Command
-```bash
-ae-cli analysis +get_alert_definition_schema
-ae-cli analysis +get_alert_definition_schema --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| None | - | This command has no business parameters; call it directly. |
-
-## Decision Rules
-- It is recommended to run `--dry-run` first to inspect the request body mapping before making the formal call.
-
-## Next Steps on Failure
-- If reading fails, first verify whether the object ID exists and belongs to the current project.
-
-## Recommended chaining
-- +get_alert_definition_schema

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

@@ -1,33 +0,0 @@
-# analysis_meta +get_project_config (Read Project Analysis Configuration)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Project Configuration**
-
-## Use Cases
-- Get project configuration details. Returns: projectId, projectName, companyId, defaultTimeZoneOffset (project default time zone offset), remark, timeZoneEnabled (whether multiple time zones are supported), timeZoneOffsetColumn (time zone column name in event data), and availableTimeZones (array of time zone offsets used in this project). Call this tool when you need project basic info or time zone configuration.
-- Get project configuration details.
-- Do not use it for project discovery or membership lookup; use `analysis_common +list_projects` or `+list_project_users` respectively.
-
-## Command
-```bash
-ae-cli analysis_meta +get_project_config --project_id <project_id>
-ae-cli analysis_meta +get_project_config --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-
-## Decision Rules
-- First run should only pass the required parameter (`--project_id`), and add optional parameters only after the path is confirmed to work.
-- `timeZoneEnabled` and `availableTimeZones` are often used to determine whether `zone_offset` can be passed to `create/update_cluster` and `create/update_tag`.
-- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
-
-## Next Steps After Failure
-- If the required parameter is missing, fall back to the smallest runnable command and fill it in (focus on `--project_id`).
-- If reading fails, first verify whether the object ID exists and belongs to the current project.
-
-## Recommended Chaining
-- +get_project_config -> +create_project_mark_time / +update_project_mark_time

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

@@ -1,34 +0,0 @@
-# analysis_meta +get_track_program (Read Tracking Plan Baseline)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Project Configuration**
-
-## Use Cases
-- Query TRACKING-PLAN metadata (bury program), including planned events/properties/common properties. This is NOT system metadata. Do NOT use MetaTool/MetaPowerTool for these plan objects.
-- Query TRACKING-PLAN metadata (bury program), including planned events/properties/common properties.
-
-## Output
-Returns the current plan content. An empty plan permits first-time generation; a non-empty result must be reviewed before any merge-generating operation.
-
-## Commands
-```bash
-ae-cli analysis_meta +get_track_program --project_id <project_id>
-ae-cli analysis_meta +get_track_program --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-
-## Decision Rules
-- For the first run, pass only the required parameter (`--project_id`) to confirm the path works, then add optional parameters.
-- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
-
-## 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 reading fails, first verify that the object ID exists and belongs to the current project.
-
-## Recommended Chaining
-- +get_project_config -> +get_track_program

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

@@ -1,41 +0,0 @@
-# analysis +list_alerts (alert strategy search)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Metadata Lookup**
-
-## Constraints
-
-**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).
-
-## Use Cases
-- List all alerts in the project. Supports keyword filtering by alert name. Returns a paginated list containing alerts array and pager result with total count.
-- List all alerts in the project.
-- Do not use it for alert result data or one known alert's complete definition; use `+get_alert` after resolving the ID.
-
-## Commands
-```bash
-ae-cli analysis +list_alerts --project_id <project_id>
-ae-cli analysis +list_alerts --project_id <project_id> --query demo
-ae-cli analysis +list_alerts --project_id <project_id> --limit 50 --offset 0
-ae-cli analysis +list_alerts --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--query` / `-q` | No | Optional keyword filter. Performs fuzzy matching against alert names; if omitted, all alerts are returned. |
-| `--limit` / `-l` | No | Optional page size. Default: 50, maximum: 200. |
-| `--offset` / `-o` | No | Optional page offset. Default: 0. |
-
-## Decision Rules
-- For the first run, it is recommended to pass only the required parameters (`--project_id`) and add optional parameters after confirming the chain works.
-- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
-
-## Next Step After Failure
-- If required parameters are missing, fall back to the smallest runnable command and fill them in (focus on `--project_id`).
-- If the result is empty, first confirm the project ID/keyword, then try broadening the filter conditions.
-
-## Recommended Chaining
-- +list_alerts

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

@@ -1,42 +0,0 @@
-# analysis_meta +list_entities (Entity Search)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Entity Query**
-
-## Use Cases
-- List entities in the project. Returns entity details such as entity ID, name, column name, column description, and type. Can be filtered by event name.
-- List entities in the project.
-- Do not use it to list user members or event rows; it returns entity metadata only.
-
-## Command
-```bash
-ae-cli analysis_meta +list_entities --project_id <project_id>
-ae-cli analysis_meta +list_entities --project_id <project_id> --query demo
-ae-cli analysis_meta +list_entities --project_id <project_id> --event_name demo
-ae-cli analysis_meta +list_entities --project_id <project_id> --fields '["entityId", "entityName", "columnName", "columnDesc", "selectType"]' --limit 50 --offset 0
-ae-cli analysis_meta +list_entities --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--event_name` | No | Optional event name filter |
-| `--query` / `-q` | No | Optional keyword filter. Fuzzy match is applied to entityName, columnName, and columnDesc; if omitted, all accessible dashboards are returned. |
-| `--fields` / `-f` | No | Optional fields to return (JSON array). Supported fields: `entityId`, `entityName`, `columnName`, `columnDesc`, `selectType`, `tableType`, `entityType`. Default fields when omitted: `entityId`, `entityName`, `columnName`, `columnDesc`, `selectType`. Entity metadata exposes `columnDesc` as the description field; no remark field is available in this list response. |
-| `--limit` / `-l` | No | Optional page size. Default: 50, maximum: 200. |
-| `--offset` / `-o` | No | Optional page offset. Default: 0. |
-
-
-## Decision Rules
-- First run should only pass the required parameter (`--project_id`), and add optional parameters only after the path is confirmed to work.
-- `--event_name` is used to filter entities by event name, not for keyword search.
-- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
-
-## Next Steps After Failure
-- If the required parameter is missing, fall back to the smallest runnable command and fill it in (focus on `--project_id`).
-- If the result is empty, first confirm the project ID/keyword, then try loosening the filter conditions.
-
-## Recommended Chaining
-- +list_entities -> analysis-meta virtual-property create / analysis-meta virtual-event create

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

@@ -1,43 +0,0 @@
-# analysis_meta +list_project_mark_times (List Project Mark Times)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Project Configuration**
-
-## Use Cases
-- List project date markers. Returns marker IDs, timestamps, content, and visibility status.
-- Supports pagination with fields/limit/offset for payload governance.
-- Query performs fuzzy matching on markContent.
-- Do not use it for report time ranges or event timestamps; this command only lists project date markers.
-
-## Commands
-```bash
-ae-cli analysis_meta +list_project_mark_times --project_id <project_id>
-ae-cli analysis_meta +list_project_mark_times --project_id <project_id> --zone_offset 8
-ae-cli analysis_meta +list_project_mark_times --project_id <project_id> --query demo --fields '["id","markTime","markContent"]' --limit 10 --offset 0
-ae-cli analysis_meta +list_project_mark_times --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--zone_offset` | No | Marker time zone offset |
-| `--query` / `-q` | No | Optional keyword filter. Fuzzy match on markContent. |
-| `--fields` | No | Optional fields to return. Supported: id, projectId, markTime, userZoneTime, zoneOffset, markContent, isShow, creatorName, creatorId, lastModifierName, lastModifierId, createTime, updateTime. Invalid fields cause INVALID_FIELDS error. |
-| `--limit` | No | Optional limit. Default: 50, maximum: 200. |
-| `--offset` | No | Optional offset. Default: 0. |
-
-## Decision Rules
-- For the first run, pass only the required parameter (`--project_id`) to confirm the path works, then add optional parameters.
-- For pagination, use `--limit` and `--offset` together. Default limit is 20.
-- Use `--fields` to select specific columns for lighter response payloads.
-- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
-
-## 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 the result is empty, first confirm the project ID/keyword, then try loosening the filter conditions.
-- If INVALID_FIELDS error appears, check that all field names in `--fields` match the supported list.
-
-## Recommended Chaining
-- +get_project_config -> +list_project_mark_times

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

@@ -1,33 +0,0 @@
-# analysis_meta +list_project_users (Read Project Member List)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Project Configuration**
-
-## Use Cases
-- Get all project members. Returns userId, loginName, and userName for each member. Use this to resolve userId when managing dashboard share members.
-- Get all project members.
-- Do not use it as an organization-wide people search or as proof of resource-level authority; it lists project membership only.
-
-## Command
-```bash
-ae-cli analysis_meta +list_project_users --project_id <project_id>
-ae-cli analysis_meta +list_project_users --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-
-## Decision Rules
-- First run should only pass the required parameter (`--project_id`), and add optional parameters only after the path is confirmed to work.
-- The result can be used for dashboard member configuration, permission mapping, and similar scenarios.
-- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
-
-## Next Steps After Failure
-- If the required parameter is missing, fall back to the smallest runnable command and fill it in (focus on `--project_id`).
-- If the result is empty, first confirm the project ID/keyword, then try loosening the filter conditions.
-
-## Recommended Chaining
-- +get_project_config -> +list_project_users

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

@@ -1,39 +0,0 @@
-# analysis_common +list_projects (view projects accessible to the current user)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **project discovery / cross-module pre-query**
-
-## Use Cases
-- List all projects accessible to the current user. No parameters are required.
-- Returns a list of project summaries; key fields include: `projectId`, `projectName`, `companyId`, `projectType`, `remark`, `appId`, `roleName`.
-
-## Mandatory Rules (MUST)
-- This command does not accept any business parameters; do not invent `project_id`, keywords, or pagination parameters.
-- If a later target command requires `project_id`, `+list_projects` is used for first-time project discovery, new project verification, project switching, or ambiguity resolution. Do not call it repeatedly when the same continuous conversation already has a verified project context for the same host/environment.
-- In the final response, prioritize the returned `projectId`, `projectName`, and `roleName` to help the user confirm the project.
-
-## Command
-```bash
-ae-cli analysis_common +list_projects
-ae-cli analysis_common +list_projects --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| None | - | No business parameters required |
-
-## Decision Rules
-- When the user says "let me see what projects I have", "list the available projects first", or "I don't know project_id", call this command first.
-- When a later command depends on `project_id` and there is no verified project context, show candidate projects first, then ask the user to explicitly confirm the target `projectId`.
-- When the same continuous conversation already has a verified `project_id` for the same host/environment, reuse it directly and do not call `+list_projects` again unless the user switches projects, switches host/environment, asks to list projects, or the current project context becomes ambiguous.
-- If there are many projects returned, prioritize summarizing by `projectName`, `projectId`, and `roleName` to avoid expanding all low-value fields at once.
-
-## Next Step on Failure
-- If the result is empty, first confirm whether the current account, environment, and permissions are correct.
-- If the call fails, first check the authentication status, the target environment host, and the current login identity.
-
-## Recommended Chaining
-- First use: `+list_projects` -> user confirms `project_id` -> any command that requires `project_id`
-- Follow-up use in the same verified context: reuse confirmed `project_id` -> target command

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

@@ -1,47 +0,0 @@
-# analysis +load_filters (load filter candidate values)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Model Analysis**
-
-## Use Cases
-- Load candidate values for a property. Queries the available enum values of the specified property (quot), which is useful when building filter conditions.
-- tableType values:
-- event: event property
-- user: user property
-- clusterDatePolicy is only used when tableType=user and user clusters are involved. Supported values: LATEST, AUTO, SPECIFIED.
-- Load candidate values for a property.
-
-## Output
-Returns candidate values for the requested property and scope. Treat the list as selectable values, not as aggregated counts or analysis results.
-
-## Commands
-```bash
-ae-cli analysis +load_filters --project_id <project_id> --quot demo --table_type event
-ae-cli analysis +load_filters --project_id <project_id> --quot demo --table_type event --event_name demo --inputdata demo --zone_offset 8 --cluster_date_policy SPECIFIED --specified_cluster_date 2026-04-08 --is_report true
-ae-cli analysis +load_filters --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--quot` | Yes | Property identifier (field name). This is the property whose candidate values will be loaded. |
-| `--table_type` | Yes | Table type: event for event properties, user for user properties |
-| `--event_name` | No | Optional event name. When tableType=event, this can limit the query scope to a specific event. |
-| `--inputdata` | No | Optional input prefix used for fuzzy filtering of candidate values. If omitted, all candidate values are returned. |
-| `--zone_offset` | No | Time zone offset in hours. For example, UTC+8 is 8 |
-| `--cluster_date_policy` | No | Cluster date policy: LATEST, AUTO, or SPECIFIED |
-| `--specified_cluster_date` | No | Specified cluster date in yyyy-MM-dd format. Effective only when clusterDatePolicy=SPECIFIED. |
-| `--is_report` | No | Whether this is report mode. Default: false |
-
-## Decision Rules
-- For the first run, it is recommended to pass only the required parameters (`--project_id`, `--quot`, `--table_type`) and add optional parameters after confirming the chain works.
-- When dates/time ranges are involved, validate with a short range first and then expand gradually.
-- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
-
-## Next Step After Failure
-- If required parameters are missing, fall back to the smallest runnable command and fill them in (focus on `--project_id`, `--quot`, `--table_type`).
-
-## Recommended Chaining
-- +load_filters

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

@@ -1,37 +0,0 @@
-# analysis_meta +save_track_items (Save Track Program Items)
-
-> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
-
-Domain: **Project Configuration**
-
-## Use Cases
-- Create/update TRACKING-PLAN metadata only (planned bury items). Do not use this tool to create or edit effective system metadata. If the user intent is production metadata changes, route to MetaPowerTool instead.
-- Create/update TRACKING-PLAN metadata only (planned bury items).
-
-## Output
-The response reports persistence of the submitted tracking-plan items. Read the plan back with `+get_track_program` before claiming the saved structure is effective.
-
-## Command
-```bash
-ae-cli analysis_meta +save_track_items --project_id <project_id> --track_data '{}'
-ae-cli analysis_meta +save_track_items --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--track_data` | Yes | Track program JSON object. Example: {"events":[{"eventName":"purchase","displayName":"Purchase","eventDesc":"User purchases a product","eventTag":"eCommerce","dataOrigin":"APP","props":["item_id","price"]}],"eventProps":[{"name":"price","displayName":"Price","type":"number","desc":"Product price"}],"userProps":[{"name":"vip_level","displayName":"Membership Level","type":"string","updateType":"user_set","propTag":"Membership","desc":"User membership level"}],"commonEventProps":[{"name":"platform","displayName":"Platform","type":"string","desc":"Application platform"}]}. Required fields: eventName/name and type. type values: string, number, datetime, bool, array_string, row, array_row. updateType values: user_setOnce, user_set, user_add, user_append. Constraints: eventName/name max 64 chars (letters, digits, underscore), displayName max 60 chars, desc/eventDesc max 200 chars. |
-
-## Decision Rules
-- First run should only pass the required parameters (`--project_id`, `--track_data`), and add optional parameters only after the path is confirmed to work.
-- Wrap JSON arguments in single quotes (for example `--track_data '{}'`) 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 After Failure
-- If required parameters are missing, fall back to the smallest runnable command and fill them in (focus on `--project_id` and `--track_data`).
-- If `Invalid JSON` occurs, validate with the smallest JSON structure first (for example `{}` or `[]`), then add fields step by step.
-
-## Recommended Chaining
-- +get_track_program -> +save_track_items -> +get_track_program