@thinkingai/ae-cli 1.0.3 → 1.0.15

package/skills/te-audience/SKILL.md

@@ -1,63 +0,0 @@
----
-name: te-audience
-version: 1.0.0
-description: "TE audience operations and targeting: create, update, query, recompute, and inspect member details for clusters and tags, plus cluster/tag definition schemas. Triggered when the user mentions audience building/targeting, audience packages, tag systems, tag assignment, tag member lookup, updating cluster rules, or recomputing clusters or tags."
-metadata:
-  requires:
-    bins: ["ae-cli"]
-  cliHelp: "ae-cli analysis_audience --help"
----
-
-# te-audience
-
-> **CRITICAL - Before starting, MUST first read [`../te-shared/SKILL.md`](../te-shared/SKILL.md)**: authentication, host configuration, global parameters, and write-operation confirmation rules are defined there.
-> **CRITICAL - Before performing write operations, MUST first read [`../te-common/SKILL.md`](../te-common/SKILL.md)**: shared post-action constraints (append resource links after create/update) are defined in that module.
-> **CRITICAL - For every command that requires `project_id`, MUST follow `te-common`'s `PROJECT_ID_GATE` (if missing, stop and confirm with the user).**
-> **CRITICAL - Before running any `+<tool_name>` command, MUST first read the corresponding reference document `./references/<tool-name>.md`** For example: before running `+create_cluster`, you must read [`./references/create-cluster.md`](./references/create-cluster.md)
-
-## When to Use
-
-Use `te-audience` when the user needs cluster and tag capabilities:
-
-- Clusters: create, update, query, member inspection, recomputation
-- Tags: create, update, query, member inspection, recomputation
-- Cluster/tag definition schema: for frontend configurators or command argument construction
-
-## Command Format
-
-`ae-cli analysis_audience +<tool_name> [options]`
-
-## Tool Groups (14)
-
-### Clusters (6)
-- `+create_cluster` ([Docs](./references/create-cluster.md))
-- `+get_clusters_by_name` ([Docs](./references/get-clusters-by-name.md))
-- `+list_cluster_members` ([Docs](./references/list-cluster-members.md))
-- `+list_clusters` ([Docs](./references/list-clusters.md))
-- `+update_cluster` ([Docs](./references/update-cluster.md))
-- `+refresh_cluster` ([Docs](./references/refresh-cluster.md))
-
-### Tags (6)
-- `+create_tag` ([Docs](./references/create-tag.md))
-- `+get_tags_by_name` ([Docs](./references/get-tags-by-name.md))
-- `+list_tag_members` ([Docs](./references/list-tag-members.md))
-- `+list_tags` ([Docs](./references/list-tags.md))
-- `+update_tag` ([Docs](./references/update-tag.md))
-- `+refresh_tag` ([Docs](./references/refresh-tag.md))
-
-### Schema Definitions (2)
-- `+get_cluster_definition_schema` ([Docs](./references/get-cluster-definition-schema.md))
-- `+get_tag_definition_schema` ([Docs](./references/get-tag-definition-schema.md))
-
-## Quick Validation
-
-```bash
-ae-cli analysis_audience --help
-npm run verify:analysis-audience-tools
-# Example: preview the request with dry-run (replace project_id with your actual project ID)
-ae-cli analysis_audience +list_clusters --project_id <YOUR_PROJECT_ID> --dry-run
-```
-
-## Reference Docs
-
-See the `references/` directory (14 per-command documents total).

package/skills/te-audience/references/get-cluster-definition-schema.md

@@ -1,37 +0,0 @@
-# analysis_audience +get_cluster_definition_schema (Get Cluster Definition Schema)
-
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
-
-Domain: **Schema Query**
-
-## Use Cases
-- Support tool positioning: the current command provides the structure definition (schema) and should be used as a prerequisite step.
-- Recommended sequence: first call this schema tool to get the structure, then call `analysis_meta +list_events` / `analysis_meta +list_properties` to obtain real metadata, and finally create or update clusters.
-- Get the cluster definition schema. Supports the condition and sql cluster types and returns field definitions, enum descriptions, and examples.
-
-## Commands
-```bash
-ae-cli analysis_audience +get_cluster_definition_schema --cluster_type condition
-ae-cli analysis_audience +get_cluster_definition_schema --cluster_type sql
-ae-cli analysis_audience +get_cluster_definition_schema --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--cluster_type` | Yes | Cluster type. Supported values: condition and sql |
-
-## Decision Rules
-- `--cluster_type` must be explicitly set to `condition` or `sql`.
-- It is recommended to run `--dry-run` first to inspect the request mapping before making the actual call.
-- The current command returns only structure constraints; it does not guarantee that the field values are available in the target project. Event names and property names must be confirmed again with `analysis_meta` metadata interfaces.
-- Before calling `analysis_meta +list_events` / `analysis_meta +list_properties`, first read their reference docs to confirm the parameter and return-field meanings.
-
-## Next Step on Failure
-- If reading fails, first verify whether the object ID exists and belongs to the current project.
-- If the schema does not match expectations, confirm whether the correct schema interface was used (filter/groupby/query/tag/cluster).
-
-## Recommended Chain
-- First read: [`./get-cluster-definition-schema.md`](./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 -> analysis_meta +list_events -> analysis_meta +list_properties -> +create_cluster
-- +get_cluster_definition_schema -> analysis_meta +list_events -> analysis_meta +list_properties -> +update_cluster

package/skills/te-audience/references/get-clusters-by-name.md

@@ -1,32 +0,0 @@
-# analysis_audience +get_clusters_by_name (Locate Clusters by Name)
-
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
-
-Domain: **Cluster Management**
-
-## Use Cases
-- Get cluster definition details in batch by cluster name. Returns complete cluster information for matched clusters, including IDs, names, display names, types, status, user counts, and refresh status.
-
-## Commands
-```bash
-ae-cli analysis_audience +get_clusters_by_name --project_id 1 --names '["demo"]'
-ae-cli analysis_audience +get_clusters_by_name --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--names` | Yes | List of cluster names (JSON array). Exact-name matching is used; unmatched clusters are ignored automatically. |
-
-## Decision Rules
-- For the first execution, it is recommended to pass only the required parameters (`--project_id`, `--names`) and add optional parameters after confirming the path works.
-- `--names` must be passed as a JSON array (e.g. `--names '["cluster_a","cluster_b"]'`).
-- When troubleshooting across projects, first confirm whether `--project_id` matches the current permissions and target environment.
-
-## Next Step on Failure
-- If required parameters are missing, fall back to the smallest runnable command and fill the gap (focus on `--project_id`, `--names`).
-- If reading fails, first verify whether the object ID exists and belongs to the current project.
-
-## Recommended Chain
-- +list_clusters -> +get_clusters_by_name -> +update_cluster

package/skills/te-audience/references/get-tag-definition-schema.md

@@ -1,32 +0,0 @@
-# analysis_audience +get_tag_definition_schema (Get Tag Definition Schema)
-
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
-
-Domain: **Schema Query**
-
-## Use Cases
-- Support tool positioning: the current command provides the structure definition (schema) and should be used as a prerequisite step.
-- Recommended sequence: first call this schema tool to get the structure, then call specific business tools.
-- Typical downstream tools: `+create_tag`, `+update_tag`
-- Get the tag definition schema. Supports the condition, metric, first_last, and sql tag types and returns field definitions, enum descriptions, and examples.
-
-## Commands
-```bash
-ae-cli analysis_audience +get_tag_definition_schema
-ae-cli analysis_audience +get_tag_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 mapping before making the actual call.
-
-## Next Step on Failure
-- If reading fails, first verify whether the object ID exists and belongs to the current project.
-- If the schema does not match expectations, confirm whether the correct schema interface was used (filter/groupby/query/tag/cluster).
-
-## Recommended Chain
-- +get_analysis_query_schema -> +get_filter_schema -> +get_groupby_schema

package/skills/te-audience/references/get-tags-by-name.md

@@ -1,32 +0,0 @@
-# analysis_audience +get_tags_by_name (Locate Tags by Name)
-
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
-
-Domain: **Tag Management**
-
-## Use Cases
-- Get tag definition details in batch by tag name. Returns complete tag information for matched tags, including IDs, names, display names, types, status, user counts, and tag definitions.
-
-## Commands
-```bash
-ae-cli analysis_audience +get_tags_by_name --project_id 1 --names '["demo"]'
-ae-cli analysis_audience +get_tags_by_name --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--names` | Yes | List of tag names (JSON array). Exact-name matching is used; unmatched tags are ignored automatically. |
-
-## Decision Rules
-- For the first execution, it is recommended to pass only the required parameters (`--project_id`, `--names`) and add optional parameters after confirming the path works.
-- `--names` must be passed as a JSON array (e.g. `--names '["tag_a","tag_b"]'`).
-- When troubleshooting across projects, first confirm whether `--project_id` matches the current permissions and target environment.
-
-## Next Step on Failure
-- If required parameters are missing, fall back to the smallest runnable command and fill the gap (focus on `--project_id`, `--names`).
-- If reading fails, first verify whether the object ID exists and belongs to the current project.
-
-## Recommended Chain
-- +list_tags -> +get_tags_by_name -> +update_tag

package/skills/te-common/SKILL.md

@@ -1,135 +0,0 @@
----
-name: te-common
-version: 1.0.0
-description: "TE cross-module common constraints: define the post-write flow after create/update operations (resource link completion, output conventions, failure fallback). Triggered when requirements involve shared rules across te-analysis/te-meta/te-audience."
-metadata:
-  requires:
-    bins: ["ae-cli"]
----
-
-# te-common
-
-> **CRITICAL - Before starting, MUST first read [`../te-shared/SKILL.md`](../te-shared/SKILL.md)**: authentication, host configuration, global parameters, and write-operation confirmation rules are all in there.
-> **CRITICAL - Before executing any `+<tool_name>` command, MUST first read the corresponding reference document `./references/<tool-name>.md`** For example: before executing `+get_resource_url`, you must first read [`./references/get-resource-url.md`](./references/get-resource-url.md)
-
-## When to Use
-
-When the requirement belongs to the unified execution constraints across `te-analysis` / `te-meta` / `te-audience`, you must use `te-common` first:
-
-- Post-write actions, such as resource link completion
-- Unified output conventions and fallback policies
-- Future cross-module common constraints
-
-## Execution Sequence (AI Agent Must Follow)
-
-```
-[Start] → [Read command reference document] → [Execute write operation] → [Succeeded?]
-                                          ↓ Yes
-                              [Pause immediately, review the "write-operation post-link completion" section of this document]
-                                          ↓
-                              [Call +get_resource_url]
-                                          ↓
-                              [Output complete result + link]
-                                          ↓
-                                      [End]
-```
-
-**Key point**: after a write operation succeeds → immediately go back to te-common, do not skip it.
-
----
-
-## Current Mandatory Constraints (MUST)
-
-### A. PROJECT_ID_GATE (preflight gate, no guessing)
-
-- For any command about to be executed, you must first confirm whether that command requires `project_id` (per the corresponding `references/<tool-name>.md` document).
-- **Regardless of whether the user provided a project name or project_id, you must first call `+list_projects` to retrieve the project list for verification.**
-- Verification rules:
-  - If the user provided a number, you must find the matching project_id in the list
-  - If the user provided a name, you must find the matching project name in the list and obtain the corresponding project_id
-  - If no match is found, you must tell the user and show the available project list so they can choose again
-- Before verification passes and the correct `project_id` is confirmed, do not call the target command.
-
-Recommended interaction flow:
-
-**Scenario 1: The user did not provide project information**
-```text
-This step requires project_id.
-I will first list the available projects for you to choose from:
-
-[Call +list_projects to display the project list]
-
-Please choose one from the projects above (for example, reply with the project ID or the project name).
-I will not execute the target command before you confirm.
-```
-
-**Scenario 2: The user provided a project name or ID**
-```text
-The project you mentioned is "xxx".
-I will first verify whether this project exists:
-
-[Call +list_projects to get the project list]
-
-Verification result:
-- ✅ Project "xxx" exists, project_id = 123
-- Or ❌ Project "xxx" was not found, available projects are listed below: [display list]
-
-Please confirm whether to use this project (project_id = 123) for the next operation.
-```
-
-### B. Write-operation post-link completion (mandatory closed loop)
-
-**Trigger condition**: When any of the following commands succeeds, MUST enter the link completion flow:
-
-| resource_type | Create command | Update command |
-|---|---|---|
-| `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` | `+create_virtual_property` (`--table_type event`) | - |
-| `user_virtual_prop` | `+create_virtual_property` (`--table_type user`) | - |
-| `super_event` | `+batch_create_metadata` (creating events) | `+batch_edit_metadata --type event` |
-| `super_prop_event` | `+batch_create_metadata` (creating event_properties) | `+batch_edit_metadata --type event_property` |
-| `super_prop_user` | `+batch_create_metadata` (creating user_properties) | `+batch_edit_metadata --type user_property` |
-
-**Closed loop execution (must be completed)**:
-1. ✅ Write operation succeeded → immediately check whether the return value contains `resource_id`
-2. ✅ Has `resource_id` → call `+get_resource_url` (using the verified `project_id`)
-3. ✅ Link generated successfully → output the complete response including the clickable link
-4. ⚠️ Link generation failed → output the main result + explicitly state "link completion failed: [reason]"
-
-**Multi-resource result handling (for batch metadata only)**:
-- `+batch_create_metadata` / `+batch_edit_metadata` may return multiple resources at once (events/properties).
-- For each resource from which `resource_id` can be extracted, you must call `+get_resource_url` separately.
-- The final output must provide links for each resource one by one; if some fail, mark the failed items and the reasons, while the successful items are returned normally.
-
-**Prohibited behaviors**:
-- ❌ End the response immediately after a write operation succeeds (you must complete link completion or explain the failure)
-- ❌ Treat a write operation as failed because link completion failed (the write result is independently valid)
-
-**Closed-loop check template** (must explicitly confirm each step):
-```
-[Write operation result]
-→ Check resource_id: [yes/no]
-→ Call get_resource_url: [called / skipped (no ID)]
-→ Link completion status: [successful link / failure reason / skipped]
-→ Closed loop complete ✅
-```
-
-If the ID cannot be extracted or link generation fails, you must explain the failure reason, but you cannot roll back or judge the main write operation as failed.
-
-## Execution Template
-
-1. Execute the main write-operation command.
-2. Extract `project_id`, `resource_type`, `resource_id` from the input or return value.
-3. Call `ae-cli analysis_common +get_resource_url --project_id <id> --resource_type <type> --resource_id <id>`.
-4. Output the main result + `markdown_link` (clickable) / `raw_url`.
-
-## Unified Command Entry
-
-- `+list_projects` ([documentation](./references/list-projects.md))
-- `+get_resource_url` ([documentation](./references/get-resource-url.md))

package/skills/te-community/SKILL.md

@@ -1,125 +0,0 @@
----
-name: te-community
-version: 1.0.0
-description: "TE community analysis: post search, comment sentiment, topic trends, risky content, livestream data"
-metadata:
-  requires:
-    bins: ["ae-cli"]
-  cliHelp: "ae-cli community --help"
----
-
-# te-community
-
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../te-shared/SKILL.md) to learn about authentication, global parameters and security constraints.
-
-## Overview
-
-The `te-community` domain provides community social media data analysis capabilities, including post search, comment sentiment analysis, topic trends, risk content monitoring and livestream data.
-
-Commands are invoked via `ae-cli community <command>`. **This document is mainly for navigation**: For specific usage, examples and Flags, see **`references/`** and each composite analysis reference below.
-
-## Common parameters
-
-| Parameters | Description |
-|------|------|
-| `--space-id` | Community space ID |
-| `--game-id` | Game/space identification |
-
-## Channel ID prerequisite: `get_channel_info`
-
-A large number of subcommands rely on **`--channel-id`** or **`--channel-id-list`** (e.g. post details, comment summaries, live session lists, and channel-filtered search). If you only have `space-id` / `game-id` and do not yet know channel IDs, call `ae-cli community get_channel_info` first to retrieve channel IDs and names, then run follow-up commands. See [get_channel_info](references/get_channel_info.md) for details.
-
-## Array parameter format
-
-Multi-valued parameters are separated by commas:
-```
---channel-id-list 1,2,3
---keywords tag1,tag2
---sentiment-types 0,1
-```
-
-## Date format
-
-All date parameters use `yyyy-MM-dd` format, such as `--start-time 2024-01-01`.
-
-## Reference documentation (subcommand navigation)
-
-Open the corresponding file as needed to view instructions and examples (one page per command):
-
-- Search posts or videos by keyword/time period: [search_posts](references/search_posts.md)
-- Got the `post-id`, view the details of a single piece of content: [get_post_detail](references/get_post_detail.md)
-- Query the list of available analysis tags: [get_corpus_tags](references/get_corpus_tags.md)
-- Quickly view the overall sentiment and summary of the comment area: [get_comments_summary](references/get_comments_summary.md)
-- Analyze the distribution and proportion of comment tags: [get_comment_tag_analysis](references/get_comment_tag_analysis.md)
-- View sentiment trends (by time period): [get_sentiment_overview](references/get_sentiment_overview.md)
-- View the community overview (posts, interactions, etc.): [get_overview_metrics](references/get_overview_metrics.md)
-- Identify current hot topics: [get_hot_topics](references/get_hot_topics.md)
-- Drill down to view the details of a topic: [get_topic_detail](references/get_topic_detail.md)
-- Observe trends for specific tags: [get_tag_trends](references/get_tag_trends.md)
-- Generate/view single-day community summary (daily): [get_daily_summary](references/get_daily_summary.md)
-- Troubleshoot risk content and security compliance issues: [get_risk_content](references/get_risk_content.md)
-- Get the list of livestream rooms and determine the room range: [get_livestream_rooms](references/get_livestream_rooms.md)
-- View the live session history list: [get_livestream_list](references/get_livestream_list.md)
-- Check the details of a livestream session: [get_livestream_detail](references/get_livestream_detail.md)
-- Livestream session AI analysis report (highlight slices and emotional views): [get_livestream_analysis](references/get_livestream_analysis.md)
-- Check the overall performance of the livestream module within the time period: [get_livestream_overview](references/get_livestream_overview.md)
-- View the annual metrics of a single livestream room: [get_livestream_room_metrics](references/get_livestream_room_metrics.md)
-- Get the channel list and basic channel information: [get_channel_info](references/get_channel_info.md)
-
-## Advanced analysis skills
-
-The following skills are called based on the MCP tool chain combination and are used to generate structured in-depth analysis.
-
-### community-activity-analysis (activity-specific operation insight analysis)
-
-In-depth evaluation of in-game activities or marketing events, including exposure impact, community sentiment, UGC ecosystem response, and long-tail effects.
-
-For details, see: [`references/community-activity-analysis.md`](references/community-activity-analysis.md)
-
----
-
-### community-daily-report (Daily Express)
-
-Generate a concise "User Operations Daily Brief" covering single-day macro trends, breaking sentiment signals, and safety/compliance risks, with day-over-day comparison (T-1 vs T-2).
-
-For details, see: [`references/community-daily-report.md`](references/community-daily-report.md)
-
----
-
-### community-character-analysis (character-specific in-depth analysis)
-
-In-depth analysis of specific game character ecology, players' emotional motivations and core needs, focusing on root causes rather than superficial phenomena.
-
-For details, see: [`references/community-character-analysis.md`](references/community-character-analysis.md)
-
----
-
-### community-hottopic-insight (topic analysis)
-
-Build a "time -> event -> sentiment" evolution chain around a single topic and output an executive summary, key discussion clusters, sentiment slices, channel insights, and action recommendations.
-
-For details, see: [`references/community-hottopic-insight.md`](references/community-hottopic-insight.md)
-
----
-
-### community-weekly-report (weekly summary of community operations)
-
-Summarize the data for the week, focus on connecting the core escalating discussion events of the week based on the "Daily Summary", and output a "Community Operations Weekly Summary Report."
-
-For details, see: [`references/community-weekly-report.md`](references/community-weekly-report.md)
-
----
-
-### community-analyzing-official-content (official content analysis)
-
-Analyze recently published official content for a specified game in the community module, then classify and summarize it using the predefined categories.
-
-For details, see: [`references/community-analyzing-official-content.md`](references/community-analyzing-official-content.md)
-
----
-
-### community-analyzing-theme-comment (in-depth analysis of the theme comment area)
-
-Conduct in-depth analysis of comments on specified posts or videos, then produce a report covering trend shifts, viewpoint distribution, and key takeaways.
-
-For details, see: [`references/community-analyzing-theme-comment.md`](references/community-analyzing-theme-comment.md)

package/skills/te-meta/SKILL.md

@@ -1,71 +0,0 @@
----
-name: te-meta
-version: 1.0.0
-description: "TE metadata and tracking-plan governance: event/property management, metric creation and updates, batch metadata editing, virtual events/properties, project configuration and members, tracking plans (track program), milestones/date markers (mark time), and entity catalog. Triggered when users mention editing tracking, tracking dictionaries, event/property governance, building metrics, checking project config, maintaining track programs, or managing mark time."
-metadata:
-  requires:
-    bins: ["ae-cli"]
-  cliHelp: "ae-cli analysis_meta --help"
----
-
-# te-meta
-
-> **CRITICAL - Before starting, MUST first read [`../te-shared/SKILL.md`](../te-shared/SKILL.md)**: authentication, host configuration, global parameters, and write-operation confirmation rules are all there.
-> **CRITICAL - Before performing write operations, MUST first read [`../te-common/SKILL.md`](../te-common/SKILL.md)**: the unified post-operation constraints (resource-link completion after create/update) are defined there.
-> **CRITICAL - For all commands that require `project_id`, MUST follow `te-common`'s `PROJECT_ID_GATE` (if missing, stop and confirm with the user).**
-> **CRITICAL - Before running any `+<tool_name>` command, MUST first read the corresponding reference doc `./references/<tool-name>.md`**. For example: before running `+create_metric`, you must first read [`./references/create-metric.md`](./references/create-metric.md)
-
-## When to Use
-
-When the user needs "metadata governance and project configuration" capabilities, use `te-meta`:
-
-- Event/property metadata queries: `+list_events`, `+list_properties`
-- Metric and virtual metadata governance: metric / batch metadata / virtual event/property
-- Project configuration: `+get_project_config`, `+list_project_users`
-- Tracking plans and date markers: track program / mark time
-- Entity catalog: `+list_entities`
-
-## Command Format
-
-`ae-cli analysis_meta +<tool_name> [options]`
-
-## Tool Groups (20)
-
-### Metadata and Governance (10)
-- `+list_events` ([documentation](./references/list-events.md))
-- `+list_properties` ([documentation](./references/list-properties.md))
-- `+list_metrics` ([documentation](./references/list-metrics.md))
-- `+get_metric` ([documentation](./references/get-metric.md))
-- `+create_metric` ([documentation](./references/create-metric.md))
-- `+update_metric` ([documentation](./references/update-metric.md))
-- `+batch_edit_metadata` ([documentation](./references/batch-edit-metadata.md))
-- `+batch_create_metadata` ([documentation](./references/batch-create-metadata.md))
-- `+create_virtual_event` ([documentation](./references/create-virtual-event.md))
-- `+create_virtual_property` ([documentation](./references/create-virtual-property.md))
-
-### Project and Tracking (9)
-- `+get_project_config` ([documentation](./references/get-project-config.md))
-- `+list_project_users` ([documentation](./references/list-project-users.md))
-- `+get_track_program` ([documentation](./references/get-track-program.md))
-- `+save_track_items` ([documentation](./references/save-track-items.md))
-- `+delete_track_items` ([documentation](./references/delete-track-items.md))
-- `+create_project_mark_time` ([documentation](./references/create-project-mark-time.md))
-- `+update_project_mark_time` ([documentation](./references/update-project-mark-time.md))
-- `+list_project_mark_times` ([documentation](./references/list-project-mark-times.md))
-- `+delete_project_mark_times` ([documentation](./references/delete-project-mark-times.md))
-
-### Entity Catalog (1)
-- `+list_entities` ([documentation](./references/list-entities.md))
-
-## Quick Verification
-
-```bash
-ae-cli analysis_meta --help
-npm run verify:analysis-meta-tools
-# Example: use dry-run to preview the request (replace project_id with your actual project ID)
-ae-cli analysis_meta +list_events --project_id <YOUR_PROJECT_ID> --dry-run
-```
-
-## Reference Docs
-
-See the `references/` directory (20 per-command docs total).

package/skills/te-meta/references/list-metrics.md

@@ -1,33 +0,0 @@
-# analysis_meta +list_metrics (Metric Search)
-
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
-
-Domain: **Metadata Query**
-
-## Use Cases
-- List metric metadata in the project. Supports keyword filtering and returns metric IDs, names, display names, model types, remarks, and related metadata, but not metric calculation results.
-- List metric metadata in the project.
-
-## Command
-```bash
-ae-cli analysis_meta +list_metrics --project_id 1
-ae-cli analysis_meta +list_metrics --project_id 1 --query demo
-ae-cli analysis_meta +list_metrics --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-| `--query` / `-q` | No | Optional keyword filter. Performs fuzzy matching against metric names, display names, and remarks; if omitted, all metrics are returned. |
-
-## Decision Rules
-- First run should only pass the required parameter (`--project_id`), and add optional parameters only after the path is confirmed to work.
-- 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_metrics -> +create_metric -> +get_metric

package/skills/te-meta/references/list-project-mark-times.md

@@ -1,33 +0,0 @@
-# analysis_meta +list_project_mark_times (List Project Mark Times)
-
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
-
-Domain: **Project Configuration**
-
-## Use Cases
-- List project date markers. Returns marker IDs, timestamps, content, and visibility status.
-- List project date markers.
-
-## Commands
-```bash
-ae-cli analysis_meta +list_project_mark_times --project_id 1
-ae-cli analysis_meta +list_project_mark_times --project_id 1 --zone_offset 8
-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 |
-
-## 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 the result is empty, first confirm the project ID/keyword, then try loosening the filter conditions.
-
-## Recommended Chaining
-- +get_project_config -> +list_project_mark_times