@thinkingai/ae-cli 1.0.1 → 1.0.15

package/skills/te-analysis/SKILL.md

@@ -1,107 +0,0 @@
----
-name: te-analysis
-version: 2.0.0
-description: "TE analysis query and visualization: report (report) and dashboard (dashboard) creation/query, ad-hoc model analysis, user drilldown, alert configuration, entity/event detail queries, analysis SQL, and filter/group-by schemas. Covers event analysis, retention analysis, funnel analysis, SQL analysis, user property analysis, distribution analysis, interval analysis, path analysis, and attribution analysis. Triggers when users mention check data/analyze data/view trends/view conversion funnels/view retention/run path attribution/write analysis SQL/drill into user behavior/edit reports and dashboards/configure alerts."
-metadata:
-  requires:
-    bins: ["ae-cli"]
-  cliHelp: "ae-cli te_analysis --help"
----
-
-# te-analysis
-
-> **CRITICAL - Before starting, you MUST first read [`../te-shared/SKILL.md`](../te-shared/SKILL.md)**: authentication, host configuration, global parameters, and write-operation confirmation rules are all documented there.
-> **CRITICAL - For write operations marked with ⚠️, after a successful execution you MUST first read and follow the "post-write link completion" constraint in [`../te-common/SKILL.md`](../te-common/SKILL.md). You MUST call `te_common +get_resource_url` to complete the link-completion loop.**
-> **CRITICAL - For all commands that require `project_id`, you MUST follow `te-common`'s `PROJECT_ID_GATE` (stop if missing and confirm with the user).**
-> **CRITICAL - Before running any `+<tool_name>` command, you MUST first read the corresponding reference document `./references/<tool-name>.md`.** For example: before running `+get_analysis_query_schema`, you must first read [`./references/get-analysis-query-schema.md`](./references/get-analysis-query-schema.md)
-
-## When to Use
-
-When a user needs TE for analysis queries, drilldown details, report/dashboard management, or alert configuration, use `te-analysis`.
-
-It applies to requests such as viewing data, analyzing data, checking details, creating reports, and configuring alerts. If the request is for audiences/tags, tracking plans, or project configuration, switch to another skill.
-
-- Alerts: view alert definitions, list alerts, get a single alert, create alerts, or update alerts.
-  Common commands: `+get_alert_definition_schema`, `+list_alerts`, `+get_alert`, `+create_alert`, `+update_alert`
-- Reports and dashboards: create or query reports, inspect dashboard structure and data, update dashboards, and manage public links and remarks.
-  Common commands: `+create_report`, `+query_report_data`, `+create_dashboard`, `+query_dashboard_detail`, `+update_dashboard`
-- Model analysis: run event analysis, retention analysis, funnel analysis, SQL analysis, user property analysis, distribution analysis, interval analysis, path analysis, attribution analysis, heat map, and ranking-list ad-hoc analysis, and support user drilldown and result clustering.
-  Common commands: `+query_adhoc`, `+drilldown_users`, `+drilldown_user_events`, `+create_result_cluster`
-- Entities and events: query entity details, event details, or generate the corresponding detail SQL.
-  Common commands: `+query_entity_details`, `+query_event_details`, `+build_entity_details_sql`, `+build_event_details_sql`
-- Analysis schema and helpers: get analysis query, filter, and groupby schemas, load available filter conditions, and inspect table columns.
-  Common commands: `+get_analysis_query_schema`, `+get_filter_schema`, `+get_groupby_schema`, `+load_filters`, `+get_table_columns`
-
-## When to Switch to Other Skills
-
-When the user requests the following, switch to the corresponding skill:
-
-| User Intent | Use |
-|---------|--------|
-| Create/query clusters, tags, or cluster schemas | `te-audience` |
-| Manage tracking plans, project configuration, or entity lists | `te-meta` |
-| Ops task flows, processes, or channels | `te-operation` |
-
-## Parameters and Conventions
-
-- Command format: `ae-cli te_analysis +<tool_name> [options]`
-- CLI flags use underscores: `--project_id`
-- MCP parameters map automatically to camelCase: `projectId`
-- Pass JSON parameters directly as JSON strings: `'{}'`, `'[1,2]'`
-- Write operations prompt for confirmation; use `--yes` to skip it.
-
-## Tool Groups (31)
-
-### Alerts (5)
-- `+get_alert_definition_schema` ([doc](./references/get-alert-definition-schema.md))
-- `+list_alerts` ([doc](./references/list-alerts.md))
-- `+get_alert` ([doc](./references/get-alert.md))
-- `+create_alert` ([doc](./references/create-alert.md))
-- `+update_alert` ([doc](./references/update-alert.md))
-
-### Reports and Dashboards (13)
-- `+create_report` ([doc](./references/create-report.md)) ⚠️ write operation, after it succeeds you MUST call `te_common +get_resource_url` to complete the link-completion loop
-- `+get_report_definition` ([doc](./references/get-report-definition.md))
-- `+list_reports` ([doc](./references/list-reports.md))
-- `+query_report_data` ([doc](./references/query-report-data.md))
-- `+create_dashboard` ([doc](./references/create-dashboard.md)) ⚠️ write operation, after it succeeds you MUST call `te_common +get_resource_url` to complete the link-completion loop
-- `+list_dashboards` ([doc](./references/list-dashboards.md))
-- `+query_dashboard_detail` ([doc](./references/query-dashboard-detail.md))
-- `+query_dashboard_report_data` ([doc](./references/query-dashboard-report-data.md))
-- `+update_dashboard` ([doc](./references/update-dashboard.md)) ⚠️ write operation, after it succeeds you MUST call `te_common +get_resource_url` to complete the link-completion loop
-- `+create_or_update_dashboard_note` ([doc](./references/create-or-update-dashboard-note.md))
-- `+list_public_access_links` ([doc](./references/list-public-access-links.md))
-- `+create_public_access_link` ([doc](./references/create-public-access-link.md))
-- `+update_public_access_link` ([doc](./references/update-public-access-link.md))
-
-### Model Analysis (6)
-- `+query_adhoc` ([doc](./references/query-adhoc.md))
-- `+drilldown_users` ([doc](./references/drilldown-users.md))
-- `+drilldown_user_events` ([doc](./references/drilldown-user-events.md))
-- `+create_result_cluster` ([doc](./references/create-result-cluster.md)) ⚠️ write operation, after it succeeds you MUST call `te_common +get_resource_url` to complete the link-completion loop
-- `+load_filters` ([doc](./references/load-filters.md))
-- `+get_table_columns` ([doc](./references/get-table-columns.md))
-
-### Entity Details / Event Details
-- `+query_entity_details` ([doc](./references/query-entity-details.md))
-- `+query_event_details` ([doc](./references/query-event-details.md))
-- `+build_entity_details_sql` ([doc](./references/build-entity-details-sql.md))
-- `+build_event_details_sql` ([doc](./references/build-event-details-sql.md))
-
-### Schema (8)
-- `+get_analysis_query_schema` ([doc](./references/get-analysis-query-schema.md))
-- `+get_filter_schema` ([doc](./references/get-filter-schema.md))
-- `+get_groupby_schema` ([doc](./references/get-groupby-schema.md))
-
-## Quick Verification
-
-```bash
-ae-cli te_analysis --help
-npm run verify:te-analysis-tools
-# Example: use dry-run to preview the request (replace project_id with your actual project ID)
-ae-cli te_analysis +query_adhoc --project_id <YOUR_PROJECT_ID> --model_type event --qp "{}" --dry-run
-```
-
-## Reference Docs
-
-See the `references/` directory (31 per-command docs in total).

package/skills/te-analysis/references/get-analysis-query-schema.md

@@ -1,36 +0,0 @@
-# te_analysis +get_analysis_query_schema (Get Analysis Query Schema)
-
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
-
-Domain: **Model schema queries**
-
-- This is the documentation for the `+get_analysis_query_schema` command; read it before running `ae-cli te_analysis +get_analysis_query_schema`.
-- Get the query schema for the specified analysis model type. Different model types use different schema structures. This tool returns field definitions and examples.
-
-## 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_metric`, `+create_report`, `+drilldown_users`, `+get_cluster_definition_schema`, `+get_filter_schema`, `+get_groupby_schema`, `+get_tag_definition_schema`, `+query_adhoc`
-- Get the analysis query schema for the specified model type. Different model types use different query structures. This tool returns field definitions and examples. Supported model types: event, retention, funnel, distribution, sql, interval, path, attribution, prop_analysis, rank_list, heat_map.
-- Get the analysis query schema for the specified model type.
-
-## Command
-```bash
-ae-cli te_analysis +get_analysis_query_schema --model_type event
-ae-cli te_analysis +get_analysis_query_schema --model_type event --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--model_type` | Yes | Model type. Supported values: event, retention, funnel, distribution, sql, interval, path, attribution, prop_analysis, rank_list, heat_map |
-
-## 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.
-- If the schema does not match expectations, confirm whether the correct schema interface was called (filter/groupby/query/tag/cluster).
-
-## Recommended chaining
-- +get_analysis_query_schema -> +get_filter_schema -> +get_groupby_schema

package/skills/te-analysis/references/list-public-access-links.md

@@ -1,31 +0,0 @@
-# te_analysis +list_public_access_links (public link search)
-
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
-
-Domain: **Dashboard Management**
-
-## Use Cases
-- List public access links in the project. Returns link IDs, short codes, access targets, status, effective time, expiration time, and related metadata.
-- List public access links in the project.
-
-## Commands
-```bash
-te-cli te_analysis +list_public_access_links --project_id 1
-te-cli te_analysis +list_public_access_links --dry-run
-```
-
-## Parameters
-| Parameter | Required | Description |
-|---|---|---|
-| `--project_id` / `-p` | Yes | Project ID |
-
-## 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_public_access_links -> +update_public_access_link

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 te_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 te_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 te_audience --help
-npm run verify:te-audience-tools
-# Example: preview the request with dry-run (replace project_id with your actual project ID)
-ae-cli te_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 @@
-# te_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 `te_meta +list_events` / `te_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
-te-cli te_audience +get_cluster_definition_schema --cluster_type condition
-te-cli te_audience +get_cluster_definition_schema --cluster_type sql
-te-cli te_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 `te_meta` metadata interfaces.
-- Before calling `te_meta +list_events` / `te_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 -> te_meta +list_events -> te_meta +list_properties -> +create_cluster
-- +get_cluster_definition_schema -> te_meta +list_events -> te_meta +list_properties -> +update_cluster

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

@@ -1,32 +0,0 @@
-# te_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
-te-cli te_audience +get_clusters_by_name --project_id 1 --names '["demo"]'
-te-cli te_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 @@
-# te_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
-te-cli te_audience +get_tag_definition_schema
-te-cli te_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 @@
-# te_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
-te-cli te_audience +get_tags_by_name --project_id 1 --names '["demo"]'
-te-cli te_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: ["te-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 `te-cli te_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,133 +0,0 @@
----
-name: te-community
-version: 1.0.0
-description: "TE 社区分析：帖子搜索、评论情感、话题趋势、风险内容、直播数据"
-metadata:
-  requires:
-    bins: ["te-cli"]
-  cliHelp: "te-cli community --help"
----
-
-# te-community
-
-> **前置条件:** 阅读 [`../te-shared/SKILL.md`](../te-shared/SKILL.md) 了解认证、全局参数和安全约束。
-
-## 概述
-
-`te-community` 域提供社区社交媒体数据分析能力，包括帖子搜索、评论情感分析、话题趋势、风险内容监控和直播数据。
-
-命令通过 `te-cli community <command>` 调用。**本文件以导航为主**：具体用法、示例与 Flags 见下方 **`references/`** 与各复合分析 reference。
-
-## 通用参数
-
-| 参数 | 说明 |
-|------|------|
-| `--space-id` | 社区空间 ID |
-| `--game-id` | 游戏/空间标识 |
-
-## 渠道 ID 前置：`get_channel_info`
-
-大量子命令依赖 **`--channel-id`** 或 **`--channel-id-list`**（例如帖子详情、评论摘要、直播会话列表、按渠道筛选的搜索等）。在只有 `space-id` / `game-id`、尚未知道渠道编号时，**建议先调用** `te-cli community get_channel_info` 拿到各渠道的 ID 与名称，再执行后续命令。详见 [get_channel_info](references/get_channel_info.md)。
-
-## 数组参数格式
-
-多值参数使用 **逗号分隔**：
-```
---channel-id-list 1,2,3
---keywords tag1,tag2
---sentiment-types 0,1
-```
-
-## 日期格式
-
-所有日期参数使用 `yyyy-MM-dd` 格式，如 `--start-time 2024-01-01`。
-
-## 参考文档（子命令导航）
-
-按需打开对应文件即可查看说明与示例（单命令一页）：
-
-- 按关键词/时间段搜索帖子或视频：[search_posts](references/search_posts.md)
-- 已拿到 `post-id`，查看单条内容详情：[get_post_detail](references/get_post_detail.md)
-- 查询可用分析标签列表：[get_corpus_tags](references/get_corpus_tags.md)
-- 快速查看评论区整体情绪与摘要：[get_comments_summary](references/get_comments_summary.md)
-- 分析评论标签分布与占比：[get_comment_tag_analysis](references/get_comment_tag_analysis.md)
-- 查看情感走势（按时间段）：[get_sentiment_overview](references/get_sentiment_overview.md)
-- 查看社区大盘总览（发帖、互动等）：[get_overview_metrics](references/get_overview_metrics.md)
-- 识别当前热榜话题：[get_hot_topics](references/get_hot_topics.md)
-- 下钻查看某个话题详情：[get_topic_detail](references/get_topic_detail.md)
-- 观察特定标签的趋势变化：[get_tag_trends](references/get_tag_trends.md)
-- 生成/查看单日社区摘要（日报）：[get_daily_summary](references/get_daily_summary.md)
-- 排查风险内容与安全合规问题：[get_risk_content](references/get_risk_content.md)
-- 获取直播间列表并确定房间范围：[get_livestream_rooms](references/get_livestream_rooms.md)
-- 查看直播间历史会话列表：[get_livestream_list](references/get_livestream_list.md)
-- 查看某场直播会话明细：[get_livestream_detail](references/get_livestream_detail.md)
-- 直播场次 AI 分析报告（亮点切片与情感观点）：[get_livestream_analysis](references/get_livestream_analysis.md)
-- 查看直播模块在时间段内的整体表现：[get_livestream_overview](references/get_livestream_overview.md)
-- 查看单直播间年度指标：[get_livestream_room_metrics](references/get_livestream_room_metrics.md)
-- 获取渠道列表与渠道基础信息：[get_channel_info](references/get_channel_info.md)
-
-## 高级分析技能
-
-以下技能基于 MCP 工具链组合调用，用于生成结构化的深度分析报告。
-
-### community-activity-analysis（活动专项运营洞察分析）
-
-深度评估游戏内活动或营销事件的曝光效果、社区口碑、二创生态及长尾影响。
-
-详见：[`references/community-activity-analysis.md`](references/community-activity-analysis.md)
-
----
-
-### community-daily-report（每日快报）
-
-生成单日大盘、突发舆情与安全合规风控的短平快《用户运营每日快报》，支持环比对比（T-1 与 T-2）。
-
-详见：[`references/community-daily-report.md`](references/community-daily-report.md)
-
----
-
-### community-character-analysis（角色专项深度分析）
-
-深度剖析特定游戏角色的社区生态、玩家情感动因、核心诉求。
-
-详见：[`references/community-character-analysis.md`](references/community-character-analysis.md)
-
----
-
-### community-hottopic-insight（话题分析报告）
-
-自动调用 MCP 工具收集语料，智能识别行业属性，输出包含核心摘要、舆情概览及事件脉络、核心热点讨论、情绪切片、社媒渠道洞察及运营建议的结构化《舆情分析》。
-
-详见：[`references/community-hottopic-insight.md`](references/community-hottopic-insight.md)
-
----
-
-### community-release-analysis（版本运营分析复盘）
-
-提取整个版本周期内的大盘数据、热点榜单、舆情脉络与风控趋势，输出深度的《版本运营分析复盘报告》。
-
-详见：[`references/community-release-analysis.md`](references/community-release-analysis.md)
-
----
-
-### community-weekly-report（社区运营周度总结）
-
-汇总统揽一周数据，重点基于"每日摘要"串联本周核心发酵事件，输出《社区运营周度总结报告》。
-
-详见：[`references/community-weekly-report.md`](references/community-weekly-report.md)
-
----
-
-### community-analyzing-official-content（官方内容分析）
-
-分析指定游戏在社区模块中近期发布的官方内容，按照既定分类进行梳理和总结。
-
-详见：[`references/community-analyzing-official-content.md`](references/community-analyzing-official-content.md)
-
----
-
-### community-analyzing-theme-comment（主题评论区深度分析）
-
-对指定帖子或视频的评论区进行深度分析，生成包含评论走势、观点分布和总结的深度分析报告。
-
-详见：[`references/community-analyzing-theme-comment.md`](references/community-analyzing-theme-comment.md)