@thinkingai/ae-cli 1.0.1 → 1.0.15

package/skills/{te-audience/references/update-cluster.md → ae-analysis/references/update_cluster.md}

@@ -1,32 +1,33 @@
-# te_audience +update_cluster (Update Cluster)
+# analysis_audience +update_cluster (Update Cluster)
 
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
 
 Domain: **Cluster Management**
 
 ## Use Cases
 - Prerequisite helper: first call `+get_cluster_definition_schema` to get the structure, then supplement it with the project's real metadata (events and properties).
+- When updating `definition`, metadata must be verified in the same session and `project_id`: first definition update in this session must call `analysis_meta +list_events` and `analysis_meta +list_properties`; later updates should reuse session-verified results first.
 - Update a user cluster definition. Supports updating the display name, remark, type, or definition. Updating only the display name or remark does not trigger recomputation.
 
 ## Required Prerequisites (MUST only when updating definition)
 - If this request includes `--definition`, you must first read and follow these reference docs:
-  - [`./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)
-- Do not submit a new `definition` until the above docs have been read and the prerequisite commands have been run.
+  - [`./get_cluster_definition_schema.md`](./get_cluster_definition_schema.md)
+  - [`./list_events.md`](./list_events.md)
+  - [`./list_properties.md`](./list_properties.md)
+- Do not submit a new `definition` until the above docs have been read and metadata has been verified: first definition update in this session for the same `project_id` must run metadata commands; if session-verified metadata already exists, reuse it first.
 
 ## Prerequisite Call Chain (run only when updating definition)
 1. First determine `--type` (condition / sql).
-2. Read `get-cluster-definition-schema.md`, then call `te-cli te_audience +get_cluster_definition_schema --cluster_type <condition|sql>` to obtain the structure.
-3. Read `list-events.md`, then call `te-cli te_meta +list_events --project_id 1`.
-4. Read `list-properties.md`, then call `te-cli te_meta +list_properties --project_id 1`.
+2. Read `get_cluster_definition_schema.md`, then call `ae-cli analysis_audience +get_cluster_definition_schema --cluster_type <condition|sql>` to obtain the structure progressively. Start with base mode; request `examples` only if base is insufficient; request `full` only for complex, ambiguous, or repeatedly failing definition updates.
+3. Read `list_events.md`. If this is the first definition update in the current session for this `project_id` (or metadata is not yet verified), call `ae-cli analysis_meta +list_events --project_id <project_id>`; otherwise, reuse the session-verified event metadata first.
+4. Read `list_properties.md`. If this is the first definition update in the current session for this `project_id` (or metadata is not yet verified), call `ae-cli analysis_meta +list_properties --project_id <project_id>`; otherwise, reuse the session-verified property metadata first.
 5. Build the new `definition` based on the schema + metadata, then run `+update_cluster`.
 
 ## Commands
 ```bash
-te-cli te_audience +update_cluster --project_id 1 --cluster_name demo --display_name "Demo v2"
-te-cli te_audience +update_cluster --project_id 1 --cluster_name demo --type condition --definition '{}' --zone_offset 8
-te-cli te_audience +update_cluster --dry-run
+ae-cli analysis_audience +update_cluster --project_id <project_id> --cluster_name demo --display_name "Demo v2"
+ae-cli analysis_audience +update_cluster --project_id <project_id> --cluster_name demo --type condition --definition '{}' --zone_offset 8
+ae-cli analysis_audience +update_cluster --dry-run
 ```
 
 ## Parameters
@@ -37,13 +38,14 @@ te-cli te_audience +update_cluster --dry-run
 | `--display_name` | No | New cluster display name. Length: 1-80 |
 | `--remark` | No | New cluster remark |
 | `--type` | No | New cluster type. Supported values: condition and sql. It is recommended to provide this when updating the definition. |
-| `--definition` | No | New cluster definition JSON. If provided, MUST call `+get_cluster_definition_schema` first, then fill valid event/property names from `te_meta` metadata commands in the same `project_id`. |
+| `--definition` | No | New cluster definition JSON. If provided, MUST call `+get_cluster_definition_schema` first, then fill valid event/property names from metadata verified in the same `project_id` (first definition update queries `analysis_meta` metadata commands; later updates in the same session should reuse verified results first). |
 | `--zone_offset` | No | Optional time zone offset for cluster computation. Valid range: -12 to 14 (supports decimals like 5.5). |
 
 ## Decision Rules
 - If you are not updating `definition` (only updating `display_name`/`remark`), you can skip the schema and metadata prerequisite chain.
 - When updating `definition`, it cannot be written from experience alone; it must satisfy both the schema structure and the project's real metadata.
-- Before calling `list_events` / `list_properties`, you must first read the corresponding reference docs.
+- Use progressive schema loading: base first, examples only when needed, full only as a last resort. Do not request full schema for simple cluster updates when the intent is clear.
+- Before calling `list_events` / `list_properties`, you must first read the corresponding reference docs. Query metadata on the first definition update in this session for the same `project_id`; after that, prefer reusing session-verified metadata.
 - For the first execution, it is recommended to pass only the required parameters (`--project_id`, `--cluster_name`) and add optional parameters after confirming the path works.
 - Wrap JSON parameters in single quotes (e.g. `--definition '{}'`) to avoid shell escaping issues.
 - When troubleshooting across projects, first confirm whether `--project_id` matches the current permissions and target environment.
@@ -55,5 +57,5 @@ te-cli te_audience +update_cluster --dry-run
 - If the result after writing is not as expected, immediately re-read the corresponding list/get interfaces and compare before and after.
 
 ## Recommended Chain
-- +get_cluster_definition_schema -> te_meta +list_events -> te_meta +list_properties -> +update_cluster
+- +get_cluster_definition_schema -> (first definition update or refresh) analysis_meta +list_events -> analysis_meta +list_properties -> +update_cluster
 - +list_clusters -> +get_clusters_by_name -> +update_cluster

package/skills/{te-analysis/references/update-dashboard.md → ae-analysis/references/update_dashboard.md}

@@ -1,6 +1,6 @@
-# te_analysis +update_dashboard (update dashboard)
+# analysis +update_dashboard (update dashboard)
 
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
 
 Domain: **Dashboard Management**
 
@@ -16,9 +16,9 @@ Domain: **Dashboard Management**
 
 ## Commands
 ```bash
-ae-cli te_analysis +update_dashboard --project_id 1 --dashboard_id 1
-ae-cli te_analysis +update_dashboard --project_id 1 --dashboard_id 1 --dashboard_name demo --report_ids '[1001]' --member_authorities '{"1001":"READ"}'
-ae-cli te_analysis +update_dashboard --dry-run
+ae-cli analysis +update_dashboard --project_id <project_id> --dashboard_id 1
+ae-cli analysis +update_dashboard --project_id <project_id> --dashboard_id 1 --dashboard_name demo --report_ids '[1001]' --member_authorities '{"1001":"READ"}'
+ae-cli analysis +update_dashboard --dry-run
 ```
 
 ## Parameters

package/skills/{te-meta/references/update-metric.md → ae-analysis/references/update_metric.md}

@@ -1,6 +1,6 @@
-# te_meta +update_metric (Update Metric)
+# analysis_meta +update_metric (Update Metric)
 
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
 
 Domain: **Metadata Query**
 
@@ -11,23 +11,23 @@ Domain: **Metadata Query**
 
 ## MUST Prerequisites
 - Before updating `--events` / `--params`, you must first read and follow these reference documents:
-  - [`../../te-analysis/references/get-analysis-query-schema.md`](../../te-analysis/references/get-analysis-query-schema.md)
-  - [`./list-events.md`](./list-events.md)
-  - [`./list-properties.md`](./list-properties.md)
+  - [`./get_analysis_query_schema.md`](./get_analysis_query_schema.md)
+  - [`./list_events.md`](./list_events.md)
+  - [`./list_properties.md`](./list_properties.md)
 - Do not submit new `events` / `params` until the document review and prerequisite command calls above are complete.
 
 ## Prerequisite Call Chain (Required for Updating events/params)
 1. Determine `--model_type` first (`event` / `retention`).
-2. Read `get-analysis-query-schema.md`, then call `te-cli te_analysis +get_analysis_query_schema --model_type <event|retention>` to get the structure.
-3. Read `list-events.md`, then call `te-cli te_meta +list_events --project_id 1`.
-4. Read `list-properties.md`, then call `te-cli te_meta +list_properties --project_id 1`.
+2. Read `get_analysis_query_schema.md`, then call `ae-cli analysis +get_analysis_query_schema --model_type <event|retention>` to get the structure.
+3. Read `list_events.md`, then call `ae-cli analysis_meta +list_events --project_id <project_id>`.
+4. Read `list_properties.md`, then call `ae-cli analysis_meta +list_properties --project_id <project_id>`.
 5. Build the new `events` / `params` from the schema + metadata, then execute `+update_metric`.
 
 ## Commands
 ```bash
-te-cli te_meta +update_metric --project_id 1 --metric_id 1 --name demo --display_name demo --model_type event --events '[]'
-te-cli te_meta +update_metric --project_id 1 --metric_id 1 --name demo --display_name demo --remark demo --model_type event --events '[]' --params '{}'
-te-cli te_meta +update_metric --dry-run
+ae-cli analysis_meta +update_metric --project_id <project_id> --metric_id 1 --name demo --display_name demo --model_type event --events '[]'
+ae-cli analysis_meta +update_metric --project_id <project_id> --metric_id 1 --name demo --display_name demo --remark demo --model_type event --events '[]' --params '{}'
+ae-cli analysis_meta +update_metric --dry-run
 ```
 
 ## Parameters
@@ -39,8 +39,8 @@ te-cli te_meta +update_metric --dry-run
 | `--display_name` | Yes | Metric display name |
 | `--remark` | No | Optional metric remark |
 | `--model_type` | Yes | Metric model type. Currently supports event and retention. |
-| `--events` | Yes | Metric event JSON. MUST follow `+get_analysis_query_schema` for the selected `model_type`, and use fields validated by `te_meta +list_events` / `te_meta +list_properties` in the same `project_id`. |
-| `--params` | No | Metric params JSON. If provided, MUST follow the schema from `+get_analysis_query_schema` and use project metadata from `te_meta +list_events` / `te_meta +list_properties`. |
+| `--events` | Yes | Metric event JSON. MUST follow `+get_analysis_query_schema` for the selected `model_type`, and use fields validated by `analysis_meta +list_events` / `analysis_meta +list_properties` in the same `project_id`. |
+| `--params` | No | Metric params JSON. If provided, MUST follow the schema from `+get_analysis_query_schema` and use project metadata from `analysis_meta +list_events` / `analysis_meta +list_properties`. |
 
 ## Decision Rules
 - `events` / `params` must not be handwritten by intuition alone: they must satisfy both the schema structure and the project's real metadata constraints.
@@ -57,5 +57,5 @@ te-cli te_meta +update_metric --dry-run
 - If the result after writing does not match expectations, immediately reread the corresponding list/get interfaces for before-and-after comparison.
 
 ## Recommended Chaining
-- +get_analysis_query_schema -> te_meta +list_events -> te_meta +list_properties -> +update_metric
+- +get_analysis_query_schema -> analysis_meta +list_events -> analysis_meta +list_properties -> +update_metric
 - +list_metrics -> +get_metric -> +update_metric

package/skills/{te-meta/references/update-project-mark-time.md → ae-analysis/references/update_project_mark_time.md}

@@ -1,6 +1,6 @@
-# te_meta +update_project_mark_time (Update Project Date Marker)
+# analysis_meta +update_project_mark_time (Update Project Date Marker)
 
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
 
 Domain: **Project Configuration**
 
@@ -10,9 +10,9 @@ Domain: **Project Configuration**
 
 ## Command
 ```bash
-te-cli te_meta +update_project_mark_time --mark_time_id 1 --project_id 1 --marked_at '2026-04-09 10:00' --content demo
-te-cli te_meta +update_project_mark_time --mark_time_id 1 --project_id 1 --marked_at '2026-04-09 10:00' --zone_offset 8 --content demo --is_visible 1
-te-cli te_meta +update_project_mark_time --dry-run
+ae-cli analysis_meta +update_project_mark_time --mark_time_id 1 --project_id <project_id> --marked_at '2026-04-09 10:00' --content demo
+ae-cli analysis_meta +update_project_mark_time --mark_time_id 1 --project_id <project_id> --marked_at '2026-04-09 10:00' --zone_offset 8 --content demo --is_visible 1
+ae-cli analysis_meta +update_project_mark_time --dry-run
 ```
 
 ## Parameters

package/skills/{te-analysis/references/update-public-access-link.md → ae-analysis/references/update_public_access_link.md}

@@ -1,6 +1,6 @@
-# te_analysis +update_public_access_link (Update Public Access Link)
+# analysis +update_public_access_link (Update Public Access Link)
 
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
 
 Domain: **Dashboard management**
 
@@ -10,9 +10,9 @@ Domain: **Dashboard management**
 
 ## Command
 ```bash
-ae-cli te_analysis +update_public_access_link --project_id 1 --link_id 1 --access_controls '{}' --effective_at "2026-04-09 10:00:00" --expires_at "2026-04-10 10:00:00"
-ae-cli te_analysis +update_public_access_link --project_id 1 --company_id 1 --link_id 1 --access_controls '{}' --remark demo --effective_at "2026-04-09 10:00:00" --expires_at "2026-04-10 10:00:00"
-ae-cli te_analysis +update_public_access_link --dry-run
+ae-cli analysis +update_public_access_link --project_id <project_id> --link_id 1 --access_controls '{}' --effective_at "2026-04-09 10:00:00" --expires_at "2026-04-10 10:00:00"
+ae-cli analysis +update_public_access_link --project_id <project_id> --company_id 1 --link_id 1 --access_controls '{}' --remark demo --effective_at "2026-04-09 10:00:00" --expires_at "2026-04-10 10:00:00"
+ae-cli analysis +update_public_access_link --dry-run
 ```
 
 ## Parameters

package/skills/{te-audience/references/update-tag.md → ae-analysis/references/update_tag.md}

@@ -1,33 +1,33 @@
-# te_audience +update_tag (Update Tag)
+# analysis_audience +update_tag (Update Tag)
 
-> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+> **Prerequisite:** Follow the Global AE CLI Rules in [`../SKILL.md`](../SKILL.md).
 
 Domain: **Tag Management**
 
 ## Use Cases
 - Prerequisite helper: first call `+get_tag_definition_schema` to get the structure, then call this tool.
-- When updating `definition`, you must first supplement it with real project metadata; at minimum, first call `te_meta +list_events` and `te_meta +list_properties`.
+- When updating `definition`, metadata must be verified in the same session and `project_id`: first definition update in this session must call `analysis_meta +list_events` and `analysis_meta +list_properties`; later updates should reuse session-verified results first.
 - Update a user tag definition. Supports updating the display name, remark, type, and tag definition. Updating only the display name or remark does not trigger recomputation.
 
 ## Required Prerequisites (MUST only when updating definition)
 - If this request includes `--definition`, you must first read and follow these reference docs:
-  - [`./get-tag-definition-schema.md`](./get-tag-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)
-- Do not submit a new `definition` until the above docs have been read and the prerequisite commands have been run.
+  - [`./get_tag_definition_schema.md`](./get_tag_definition_schema.md)
+  - [`./list_events.md`](./list_events.md)
+  - [`./list_properties.md`](./list_properties.md)
+- Do not submit a new `definition` until the above docs have been read and metadata has been verified: first definition update in this session for the same `project_id` must run metadata commands; if session-verified metadata already exists, reuse it first.
 
 ## Prerequisite Call Chain (run only when updating definition)
 1. First determine `--type` (condition / metric / first_last / sql).
-2. Read `get-tag-definition-schema.md`, then call `te-cli te_audience +get_tag_definition_schema` to obtain the structure.
-3. Read `list-events.md`, then call `te-cli te_meta +list_events --project_id 1`.
-4. Read `list-properties.md`, then call `te-cli te_meta +list_properties --project_id 1`.
+2. Read `get_tag_definition_schema.md`, then call `ae-cli analysis_audience +get_tag_definition_schema --type <condition|metric|first_last|sql>` to obtain the structure progressively. Start with base mode; request `examples` only if base is insufficient; request `full` only for complex, ambiguous, or repeatedly failing definition updates.
+3. Read `list_events.md`. If this is the first definition update in the current session for this `project_id` (or metadata is not yet verified), call `ae-cli analysis_meta +list_events --project_id <project_id>`; otherwise, reuse the session-verified event metadata first.
+4. Read `list_properties.md`. If this is the first definition update in the current session for this `project_id` (or metadata is not yet verified), call `ae-cli analysis_meta +list_properties --project_id <project_id>`; otherwise, reuse the session-verified property metadata first.
 5. Build the new `definition` based on the schema + metadata, then run `+update_tag`.
 
 ## Commands
 ```bash
-te-cli te_audience +update_tag --project_id 1 --tag_name demo --display_name "Demo v2"
-te-cli te_audience +update_tag --project_id 1 --tag_name demo --type condition --definition '{}' --zone_offset 8
-te-cli te_audience +update_tag --dry-run
+ae-cli analysis_audience +update_tag --project_id <project_id> --tag_name demo --display_name "Demo v2"
+ae-cli analysis_audience +update_tag --project_id <project_id> --tag_name demo --type condition --definition '{}' --zone_offset 8
+ae-cli analysis_audience +update_tag --dry-run
 ```
 
 ## Parameters
@@ -38,13 +38,14 @@ te-cli te_audience +update_tag --dry-run
 | `--display_name` | No | New tag display name. Length: 1-80 |
 | `--remark` | No | New tag remark |
 | `--type` | No | New tag type. Supported values: condition, metric, first_last, sql |
-| `--definition` | No | New tag definition JSON. If provided, MUST call `+get_tag_definition_schema` first, then fill valid event/property names from `te_meta` metadata commands in the same `project_id`. |
+| `--definition` | No | New tag definition JSON. If provided, MUST call `+get_tag_definition_schema` first, then fill valid event/property names from metadata verified in the same `project_id` (first definition update queries `analysis_meta` metadata commands; later updates in the same session should reuse verified results first). |
 | `--zone_offset` | No | Optional time zone offset for tag computation. Valid range: -12 to 14 (supports decimals like 5.5). |
 
 ## Decision Rules
 - If you are not updating `definition` (only updating `display_name`/`remark`), you can skip the schema and metadata prerequisite chain.
 - When updating `definition`, it cannot be written from experience alone; it must satisfy both the schema structure and the project's real metadata.
-- Before calling `list_events` / `list_properties`, you must first read the corresponding reference docs.
+- Use progressive schema loading: base first, examples only when needed, full only as a last resort. Do not request full schema for simple tag updates when the intent is clear.
+- Before calling `list_events` / `list_properties`, you must first read the corresponding reference docs. Query metadata on the first definition update in this session for the same `project_id`; after that, prefer reusing session-verified metadata.
 - For the first execution, it is recommended to pass only the required parameters (`--project_id`, `--tag_name`) and add optional parameters after confirming the path works.
 - Wrap JSON parameters in single quotes (e.g. `--definition '{}'`) to avoid shell escaping issues.
 - When troubleshooting across projects, first confirm whether `--project_id` matches the current permissions and target environment.
@@ -56,5 +57,5 @@ te-cli te_audience +update_tag --dry-run
 - If the result after writing is not as expected, immediately re-read the corresponding list/get interfaces and compare before and after.
 
 ## Recommended Chain
-- +get_tag_definition_schema -> te_meta +list_events -> te_meta +list_properties -> +update_tag
+- +get_tag_definition_schema -> (first definition update or refresh) analysis_meta +list_events -> analysis_meta +list_properties -> +update_tag
 - +list_tags -> +get_tags_by_name -> +update_tag

package/skills/ae-community/SKILL.md

@@ -0,0 +1,305 @@
+---
+name: ae-community
+version: 2.0.0
+description: "AE community analysis: post search, comment sentiment, topic trends, risky content, livestream data. Includes AE CLI authentication, global parameters, and safety rules (self-contained)."
+metadata:
+  requires:
+    bins: ["ae-cli"]
+  cliHelp: "ae-cli community --help"
+---
+
+# ae-community
+
+> **CRITICAL - This skill is self-contained.** Use the Global AE CLI Rules below; do not require a separate shared skill for community-side tasks.
+
+The AE Community domain provides social data analysis: post/video search, comment analytics, sentiment and topics, risk monitoring, and livestream metrics. Commands run as **`ae-cli community +<subcommand>`** — every community subcommand uses the **`+` prefix**.
+
+| Route (MCP) | CLI service | Responsibility |
+|-------------|-------------|----------------|
+| `community_content` | `community` | Posts, comments, corpus tags, search, livestream content, risk content |
+| `community_analysis` | `community` | Channel list, overview metrics, sentiment, tag trends |
+| `community_hot` | `community` | Daily summary, hot topics, topic drill-down |
+
+---
+
+## Global AE CLI Rules
+
+AE CLI (`ae-cli`) is the command-line tool for the ThinkingEngine data analysis platform, used by AI Agents and human users. For community-side requests, prefer `ae-cli` and this skill’s reference docs over model memory.
+
+### Authentication
+
+You must authenticate before use. Authentication priority:
+
+1. Environment variable `TE_TOKEN` (highest priority, suitable for CI/scripts)
+2. Cached token (`~/.ae-cli/tokens.json`, valid for 20 hours)
+3. macOS automatically extracts it from Chrome (macOS only)
+
+**Authentication commands**
+
+```bash
+# Automatic macOS authentication (extract token from Chrome)
+ae-cli auth login
+
+# Manually set token
+ae-cli auth set-token <token>
+
+# View authentication status
+ae-cli auth status
+
+# Log out
+ae-cli auth logout
+```
+
+**Multi-environment support**
+
+```bash
+# Specify host
+ae-cli auth login --host ta-staging.example.com
+ae-cli auth set-token <token> --host ta-staging.example.com
+
+# Configure default host
+ae-cli config set defaultHost ta-staging.example.com
+```
+
+### Global parameters
+
+All commands support the following global parameters:
+
+| Parameter | Description | Default |
+|------|------|--------|
+| `--host <host>` | AE instance address | defaultHost from config or ta.thinkingdata.cn |
+| `--format <json\|table>` | Output format | json |
+| `--jq <expr>` | jq filter expression | - |
+| `--dry-run` | Show the request only, do not execute it | false |
+| `--yes` | Skip confirmation for write operations | false |
+
+### Output format
+
+**JSON (default)**
+
+```json
+{
+  "ok": true,
+  "data": { ... }
+}
+```
+
+**Table**
+
+```bash
+ae-cli analysis_meta +list_events --project_id <YOUR_PROJECT_ID> --format table
+```
+
+**jq filtering**
+
+```bash
+ae-cli analysis_meta +list_events --project_id <YOUR_PROJECT_ID> --jq '.'
+```
+
+### Error handling
+
+Error output goes to stderr, in the following format:
+
+```json
+{
+  "ok": false,
+  "error": {
+    "type": "auth | api | validation | config",
+    "message": "...",
+    "hint": "..."
+  }
+}
+```
+
+Exit code: success `0`, error `1`.
+
+### Security constraints
+
+- Commands with `risk: read` execute directly
+- Commands with `risk: write` require confirmation unless `--yes` is passed
+- Use `--dry-run` to preview the request that will be sent
+
+### Command structure
+
+```bash
+ae-cli <domain> +<command> [flags]
+ae-cli api <METHOD> <PATH> [--params] [--data]
+```
+
+**Community** commands use the domain `community` (this skill). Other AE domains include: `analysis` (analysis), `analysis_audience` (audience), `analysis_meta` (metadata), `analysis_common` (common), `operation` (operations).
+
+---
+
+## Overview
+
+Typical use cases:
+
+- Search and inspect posts or videos, then drill into detail and comment analytics
+- Track sentiment, keywords/tags, and macro overview metrics by time range
+- Monitor risky or moderated content
+- Analyze livestream rooms, sessions, and AI-generated session reports
+- Produce daily/weekly/activity-style reports via composite references under `references/community-*.md`
+
+For per-command flags and copy-paste examples, use the files in [`references/`](references/).
+
+---
+
+## Parameter conventions
+
+| Item | Description |
+|------|-------------|
+| `--space-id` | Community space ID (number) |
+| `--game-id` | Game / space identifier (number) |
+| `--channel-id` / `--channel-id-list` | Often required after you know channel IDs (see **Channel ID prerequisite** below) |
+| Globals | Same as other domains: `--host`, `--mcp-url`, `--format`, `--jq`, `--dry-run`, `--yes` |
+
+- **Lists (comma-separated):** e.g. `--channel-id-list 1,2,3`, `--keywords a,b`, `--sentiment-types 0,1`
+- **Dates:** `yyyy-MM-dd` for range endpoints (e.g. `--start-time`, `--end-time`, `--date`)
+
+---
+
+## Core concepts
+
+### Channel ID prerequisite (`+get_channel_info`)
+
+Many commands need **`--channel-id`** or **`--channel-id-list`** (post detail, comment summaries, live lists, channel-scoped search). If you only have `--space-id` / `--game-id`, run:
+
+```bash
+ae-cli community +get_channel_info --space-id <id> --game-id <id>
+```
+
+Then use returned channel IDs in follow-up commands. Details: [`references/get_channel_info.md`](references/get_channel_info.md).
+
+---
+
+## Scenario routing
+
+Route users to composite workflows when intent matches:
+
+| User intent | Start here |
+|-------------|------------|
+| Single-day ops brief, T-1 vs T-2 | [`community-daily-report.md`](references/community-daily-report.md) |
+| Weekly roll-up | [`community-weekly-report.md`](references/community-weekly-report.md) |
+| Activity / campaign insight | [`community-activity-analysis.md`](references/community-activity-analysis.md) |
+| One character / IP deep dive | [`community-character-analysis.md`](references/community-character-analysis.md) |
+| Single topic timeline + actions | [`community-hottopic-insight.md`](references/community-hottopic-insight.md) |
+| Official post taxonomy | [`community-analyzing-official-content.md`](references/community-analyzing-official-content.md) |
+| Comment thread deep dive | [`community-analyzing-theme-comment.md`](references/community-analyzing-theme-comment.md) |
+
+---
+
+## Common scenarios
+
+### 1. Search and content drill-down
+
+```bash
+ae-cli community +search_posts --space-id 1 --game-id 1 \
+  --start-time 2026-04-01 --end-time 2026-04-07
+
+ae-cli community +get_post_detail --space-id 1 --game-id 1 \
+  --channel-id 1 --uuid <uuid> --resource-type 0
+
+ae-cli community +get_comments_summary --space-id 1 --game-id 1 \
+  --channel-id 1 --uuid <uuid>
+```
+
+### 2. Analysis and sentiment
+
+```bash
+ae-cli community +get_channel_info --space-id 1 --game-id 1
+
+ae-cli community +get_overview_metrics --space-id 1 --game-id 1 \
+  --start-time 2026-04-01 --end-time 2026-04-07
+
+ae-cli community +get_sentiment_overview --space-id 1 --game-id 1 \
+  --start-time 2026-04-01 --end-time 2026-04-07
+```
+
+### 3. Hot topics and daily snapshot
+
+```bash
+ae-cli community +get_hot_topics --space-id 1 --game-id 1
+
+ae-cli community +get_daily_summary --space-id 1 --game-id 1 --date 2026-04-01
+```
+
+### 4. Livestream
+
+```bash
+ae-cli community +get_livestream_list --space-id 1 --game-id 1
+
+ae-cli community +get_livestream_detail --space-id 1 --game-id 1 --stream-id <id>
+
+ae-cli community +get_livestream_analysis --space-id 1 --game-id 1 --stream-id <id>
+```
+
+---
+
+## Dry-run debugging
+
+```bash
+ae-cli --dry-run community +get_channel_info --space-id 1 --game-id 1
+ae-cli --dry-run community +search_posts --space-id 1 --game-id 1 \
+  --start-time 2026-04-01 --end-time 2026-04-07
+```
+
+---
+
+## References (per-command)
+
+| Topic | Document |
+|-------|----------|
+| Channel list (prerequisite) | [`get_channel_info.md`](references/get_channel_info.md) |
+| Search posts/videos | [`search_posts.md`](references/search_posts.md) |
+| Post/video detail | [`get_post_detail.md`](references/get_post_detail.md) |
+| Corpus tags / `tagCode` | [`get_corpus_tags.md`](references/get_corpus_tags.md) |
+| Comment summary | [`get_comments_summary.md`](references/get_comments_summary.md) |
+| Comment tag analysis | [`get_comment_tag_analysis.md`](references/get_comment_tag_analysis.md) |
+| Sentiment overview | [`get_sentiment_overview.md`](references/get_sentiment_overview.md) |
+| Overview metrics | [`get_overview_metrics.md`](references/get_overview_metrics.md) |
+| Hot topics | [`get_hot_topics.md`](references/get_hot_topics.md) |
+| Topic detail | [`get_topic_detail.md`](references/get_topic_detail.md) |
+| Tag trends | [`get_tag_trends.md`](references/get_tag_trends.md) |
+| Daily summary | [`get_daily_summary.md`](references/get_daily_summary.md) |
+| Risk content | [`get_risk_content.md`](references/get_risk_content.md) |
+| Live rooms / list / detail / analysis / overview / room metrics | [`get_livestream_rooms.md`](references/get_livestream_rooms.md), [`get_livestream_list.md`](references/get_livestream_list.md), [`get_livestream_detail.md`](references/get_livestream_detail.md), [`get_livestream_analysis.md`](references/get_livestream_analysis.md), [`get_livestream_overview.md`](references/get_livestream_overview.md), [`get_livestream_room_metrics.md`](references/get_livestream_room_metrics.md) |
+
+---
+
+## Command groups
+
+Commands below are shown **without** the `ae-cli community` prefix; all use the `+` prefix on the CLI.
+
+### Content (`community_content`)
+
+`+get_livestream_list`, `+get_livestream_detail`, `+get_livestream_analysis`, `+get_post_detail`, `+get_comments_summary`, `+get_comment_tag_analysis`, `+get_corpus_tags`, `+get_risk_content`, `+search_posts`, `+get_livestream_overview`, `+get_livestream_rooms`, `+get_livestream_room_metrics`
+
+### Analysis (`community_analysis`)
+
+`+get_channel_info`, `+get_overview_metrics`, `+get_sentiment_overview`, `+get_tag_trends`
+
+### Hot (`community_hot`)
+
+`+get_daily_summary`, `+get_hot_topics`, `+get_topic_detail`
+
+---
+
+## Composite scenario skills
+
+Structured multi-step reports (MCP tool chains) — open the linked reference for full workflows.
+
+| Skill | Purpose |
+|-------|---------|
+| [`community-activity-analysis.md`](references/community-activity-analysis.md) | Activity / marketing event insight |
+| [`community-daily-report.md`](references/community-daily-report.md) | Daily express (T-1 vs T-2) |
+| [`community-character-analysis.md`](references/community-character-analysis.md) | Character / IP deep analysis |
+| [`community-hottopic-insight.md`](references/community-hottopic-insight.md) | Single-topic evolution and actions |
+| [`community-weekly-report.md`](references/community-weekly-report.md) | Weekly operations summary |
+| [`community-analyzing-official-content.md`](references/community-analyzing-official-content.md) | Official content taxonomy |
+| [`community-analyzing-theme-comment.md`](references/community-analyzing-theme-comment.md) | Themed comment-area analysis |
+
+---
+
+## Write operations
+
+Most community commands are **read-only**. If new write-capable commands are added later, confirm user intent and use `--yes` where the CLI marks **`risk: write`**.

package/skills/ae-community/references/community-activity-analysis.md

@@ -0,0 +1,67 @@
+# ae-community community-activity-analysis
+
+
+Event-specific operation insight analysis: In-depth evaluation of the exposure effect, community reputation, second-generation ecology and long-tail impact of in-game activities or marketing events, and output a standard "Event-Specific Operation Insight Report".
+
+Trigger scenario: When the user asks to "analyze a certain activity", "generate activity review", "see feedback from XX activity" or "evaluate marketing effectiveness".
+
+## Analysis process
+
+1. **Basic market and trend analysis**: Call `+get_overview_metrics` and `+get_daily_summary` to obtain the overall volume and sentiment before and after the event
+2. **Drill down on topics and hot searches**: Call `+get_hot_topics` and `+get_topic_detail` to deeply analyze the sentiment distribution of a specific topic
+3. **Word-of-mouth and pain points deep-dive analysis of**: Call `+get_sentiment_overview` to analyze positive and negative high-frequency keywords
+4. **Fixed-point blasting evidence collection**: Call `+search_posts` -> `+get_post_detail` -> `+get_comments_summary` to obtain real player cases
+5. **Risk Control and Red Line Checking**: Call `+get_risk_content` to check compliance risk content
+
+## Core Constraints
+
+- **Reject false claims**: You must write down the specific reasons and attach supporting posts or comments.
+- **Strictly distinguish between early warning and risk control**:
+- Early Warning: Event experience issues (mechanism, bugs, rewards, liveliness)
+- Risk control: Risks of violations (black/gray-market activity, leaks, wars, advertising, etc.)
+
+## Output structure
+
+### 1. Activity overview and core data
+- Set the tone for the event
+- Core sound volume and exposure indicators (including tables)
+
+### 2. Insights into community feedback and sentiment highlights
+- **Activity Highlights and Highlights** (with typical acoustic support)
+- **Core slots and experience pain points** (including typical original sound support)
+
+### 3. Content dissemination and secondary innovation ecological mining
+- Core out-of-circle topics/meme culture
+- Inventory of secondary innovation output potential
+
+### 4. Impact on community ecology
+-Activity pulling effect
+- Player structure/genre evolution
+
+### 5. Inspiration and optimization suggestions for operational strategies
+- Design pitfalls in follow-up activities
+- Long-tail marketing strategies
+- Livestream/publicity side review
+
+### 6. Activity warning and compliance risk control
+
+**⚠️ Event sentiment and experience warning**
+
+| Warning level | Warning trigger items | Community spread | Core performance | Suggested follow-up actions |
+|---------|-----------|-----------|---------|-------------|
+| High/medium/low | Specific problems | Scope of impact | Specific performance | Handling suggestions |
+
+**⛔ Community compliance and risk control interception**
+
+| Risk control level | Violation type | Discovery channels | Violation facts | Disposal suggestions |
+|---------|---------|---------|-------------|---------|
+| Serious/General | Violation type | Channel name | Specific facts | Handling suggestions |
+
+## Example
+
+```bash
+# User input example
+"Help me analyze the feedback on such and such activities"
+"Generate an activity review report for the half-anniversary celebration"
+"Evaluate the effectiveness of this marketing campaign"
+```