@thinkingai/ae-cli 1.0.1 → 1.0.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +16 -13
- package/dist/auth-BQC5DBE7.js +19 -0
- package/dist/auth-DXKYLMO7.js +81 -0
- package/dist/chunk-3CDLNXTD.js +218 -0
- package/dist/chunk-53FNNCZW.js +174 -0
- package/dist/chunk-EBFUVWIZ.js +127 -0
- package/dist/chunk-ZYXIGPG7.js +148 -0
- package/dist/client-T4VODLA6.js +16 -0
- package/dist/community-FVDAWGS4.js +684 -0
- package/dist/config-V7AXKDMB.js +242 -0
- package/dist/index.js +16 -15
- package/dist/raw-G3GKHAPZ.js +61 -0
- package/dist/te-analysis-CHFTDN55.js +871 -0
- package/dist/te-audience-M6LQY6M7.js +350 -0
- package/dist/te-common-BLQ7DVGC.js +144 -0
- package/dist/te-dataops-V4OTKY35.js +1853 -0
- package/dist/te-engage-DXE4R5EW.js +1470 -0
- package/dist/te-meta-FMM7KCVI.js +479 -0
- package/package.json +7 -5
- package/skills/te-analysis/SKILL.md +10 -10
- package/skills/te-analysis/references/build-entity-details-sql.md +10 -10
- package/skills/te-analysis/references/build-event-details-sql.md +10 -10
- package/skills/te-analysis/references/create-alert.md +4 -4
- package/skills/te-analysis/references/create-dashboard.md +4 -4
- package/skills/te-analysis/references/create-or-update-dashboard-note.md +4 -4
- package/skills/te-analysis/references/create-public-access-link.md +4 -4
- package/skills/te-analysis/references/create-report.md +10 -10
- package/skills/te-analysis/references/create-result-cluster.md +4 -4
- package/skills/te-analysis/references/drilldown-user-events.md +6 -6
- package/skills/te-analysis/references/drilldown-users.md +4 -4
- package/skills/te-analysis/references/get-alert-definition-schema.md +3 -3
- package/skills/te-analysis/references/get-alert.md +3 -3
- package/skills/te-analysis/references/get-analysis-query-schema.md +4 -4
- package/skills/te-analysis/references/get-filter-schema.md +3 -3
- package/skills/te-analysis/references/get-groupby-schema.md +3 -3
- package/skills/te-analysis/references/get-report-definition.md +3 -3
- package/skills/te-analysis/references/get-table-columns.md +3 -3
- package/skills/te-analysis/references/list-alerts.md +4 -4
- package/skills/te-analysis/references/list-dashboards.md +4 -4
- package/skills/te-analysis/references/list-public-access-links.md +3 -3
- package/skills/te-analysis/references/list-reports.md +4 -4
- package/skills/te-analysis/references/load-filters.md +4 -4
- package/skills/te-analysis/references/query-adhoc.md +10 -10
- package/skills/te-analysis/references/query-dashboard-detail.md +3 -3
- package/skills/te-analysis/references/query-dashboard-report-data.md +9 -9
- package/skills/te-analysis/references/query-entity-details.md +10 -10
- package/skills/te-analysis/references/query-event-details.md +10 -10
- package/skills/te-analysis/references/query-report-data.md +11 -11
- package/skills/te-analysis/references/update-alert.md +4 -4
- package/skills/te-analysis/references/update-dashboard.md +4 -4
- package/skills/te-analysis/references/update-public-access-link.md +4 -4
- package/skills/te-audience/SKILL.md +5 -5
- package/skills/te-audience/references/create-cluster.md +10 -10
- package/skills/te-audience/references/create-tag.md +10 -10
- package/skills/te-audience/references/get-cluster-definition-schema.md +9 -9
- package/skills/te-audience/references/get-clusters-by-name.md +3 -3
- package/skills/te-audience/references/get-tag-definition-schema.md +3 -3
- package/skills/te-audience/references/get-tags-by-name.md +3 -3
- package/skills/te-audience/references/list-cluster-members.md +4 -4
- package/skills/te-audience/references/list-clusters.md +4 -4
- package/skills/te-audience/references/list-tag-members.md +4 -4
- package/skills/te-audience/references/list-tags.md +4 -4
- package/skills/te-audience/references/refresh-cluster.md +3 -3
- package/skills/te-audience/references/refresh-tag.md +3 -3
- package/skills/te-audience/references/update-cluster.md +9 -9
- package/skills/te-audience/references/update-tag.md +10 -10
- package/skills/te-common/SKILL.md +2 -2
- package/skills/te-common/references/get-resource-url.md +5 -5
- package/skills/te-common/references/list-projects.md +3 -3
- package/skills/te-community/SKILL.md +61 -69
- package/skills/te-community/references/community-activity-analysis.md +43 -43
- package/skills/te-community/references/community-analyzing-official-content.md +47 -47
- package/skills/te-community/references/community-analyzing-theme-comment.md +87 -87
- package/skills/te-community/references/community-character-analysis.md +44 -44
- package/skills/te-community/references/community-daily-report.md +56 -53
- package/skills/te-community/references/community-hottopic-insight.md +81 -87
- package/skills/te-community/references/community-weekly-report.md +54 -53
- package/skills/te-community/references/get_channel_info.md +9 -9
- package/skills/te-community/references/get_comment_tag_analysis.md +15 -15
- package/skills/te-community/references/get_comments_summary.md +15 -15
- package/skills/te-community/references/get_corpus_tags.md +9 -9
- package/skills/te-community/references/get_daily_summary.md +10 -10
- package/skills/te-community/references/get_hot_topics.md +12 -12
- package/skills/te-community/references/get_livestream_analysis.md +9 -9
- package/skills/te-community/references/get_livestream_detail.md +19 -19
- package/skills/te-community/references/get_livestream_list.md +13 -13
- package/skills/te-community/references/get_livestream_overview.md +11 -11
- package/skills/te-community/references/get_livestream_room_metrics.md +12 -12
- package/skills/te-community/references/get_livestream_rooms.md +12 -12
- package/skills/te-community/references/get_overview_metrics.md +12 -12
- package/skills/te-community/references/get_post_detail.md +21 -21
- package/skills/te-community/references/get_risk_content.md +23 -23
- package/skills/te-community/references/get_sentiment_overview.md +16 -16
- package/skills/te-community/references/get_tag_trends.md +13 -13
- package/skills/te-community/references/get_topic_detail.md +12 -12
- package/skills/te-community/references/search_posts.md +26 -26
- package/skills/te-dataops/SKILL.md +390 -392
- package/skills/te-dataops/references/dataops-flow-create.md +87 -87
- package/skills/te-dataops/references/dataops-flow-monitor.md +65 -65
- package/skills/te-dataops/references/dataops-integration.md +90 -85
- package/skills/te-dataops/references/dataops-query.md +58 -58
- package/skills/te-dataops/references/dataops-table.md +63 -63
- package/skills/te-engage/SKILL.md +103 -103
- package/skills/te-engage/references/add-approver.md +11 -11
- package/skills/te-engage/references/add-channel.md +34 -34
- package/skills/te-engage/references/approver-list.md +8 -8
- package/skills/te-engage/references/cancel-query-by-request-id.md +10 -10
- package/skills/te-engage/references/channel-detail.md +13 -13
- package/skills/te-engage/references/channel-list.md +15 -15
- package/skills/te-engage/references/config-channel-detail.md +10 -10
- package/skills/te-engage/references/config-channel-list.md +11 -11
- package/skills/te-engage/references/config-item-analysis-report.md +21 -21
- package/skills/te-engage/references/config-item-detail.md +10 -10
- package/skills/te-engage/references/config-item-list.md +8 -8
- package/skills/te-engage/references/config-item-strategy-comparison.md +14 -14
- package/skills/te-engage/references/config-item-trigger-report.md +26 -26
- package/skills/te-engage/references/copy-config-template.md +16 -16
- package/skills/te-engage/references/delete-channel.md +11 -11
- package/skills/te-engage/references/delete-config-channel.md +11 -11
- package/skills/te-engage/references/delete-config-item.md +12 -12
- package/skills/te-engage/references/delete-flow.md +11 -11
- package/skills/te-engage/references/flow-ab-split-node-report.md +29 -29
- package/skills/te-engage/references/flow-detail.md +19 -19
- package/skills/te-engage/references/flow-list.md +8 -8
- package/skills/te-engage/references/flow-node-config-schema.md +11 -11
- package/skills/te-engage/references/flow-node-detail-report.md +30 -30
- package/skills/te-engage/references/flow-node-overview-report.md +27 -27
- package/skills/te-engage/references/flow-process-report.md +32 -32
- package/skills/te-engage/references/manage-flow.md +44 -44
- package/skills/te-engage/references/manage-strategy.md +37 -37
- package/skills/te-engage/references/manage-task.md +20 -20
- package/skills/te-engage/references/modify-flow-base-info.md +14 -14
- package/skills/te-engage/references/save-flow.md +264 -263
- package/skills/te-engage/references/strategy-detail.md +16 -16
- package/skills/te-engage/references/strategy-list.md +10 -10
- package/skills/te-engage/references/task-data-detail.md +47 -47
- package/skills/te-engage/references/task-data-overview.md +23 -23
- package/skills/te-engage/references/task-detail.md +18 -18
- package/skills/te-engage/references/task-experiment-report.md +26 -26
- package/skills/te-engage/references/task-list.md +35 -35
- package/skills/te-engage/references/task-metric-detail.md +31 -31
- package/skills/te-engage/references/task-stats.md +31 -31
- package/skills/te-engage/references/update-channel-status.md +13 -13
- package/skills/te-engage/references/update-config-channel-status.md +14 -14
- package/skills/te-engage/references/validate-flow-node-config.md +15 -15
- package/skills/te-engage/references/whitelist-list.md +8 -8
- package/skills/te-meta/SKILL.md +5 -5
- package/skills/te-meta/references/batch-create-metadata.md +4 -4
- package/skills/te-meta/references/batch-edit-metadata.md +3 -3
- package/skills/te-meta/references/create-metric.md +12 -12
- package/skills/te-meta/references/create-project-mark-time.md +4 -4
- package/skills/te-meta/references/create-virtual-event.md +10 -10
- package/skills/te-meta/references/create-virtual-property.md +8 -8
- package/skills/te-meta/references/delete-project-mark-times.md +3 -3
- package/skills/te-meta/references/delete-track-items.md +3 -3
- package/skills/te-meta/references/get-metric.md +3 -3
- package/skills/te-meta/references/get-project-config.md +3 -3
- package/skills/te-meta/references/get-track-program.md +3 -3
- package/skills/te-meta/references/list-entities.md +4 -4
- package/skills/te-meta/references/list-events.md +4 -4
- package/skills/te-meta/references/list-metrics.md +4 -4
- package/skills/te-meta/references/list-project-mark-times.md +4 -4
- package/skills/te-meta/references/list-project-users.md +3 -3
- package/skills/te-meta/references/list-properties.md +4 -4
- package/skills/te-meta/references/save-track-items.md +3 -3
- package/skills/te-meta/references/update-metric.md +10 -10
- package/skills/te-meta/references/update-project-mark-time.md +4 -4
- package/skills/te-shared/SKILL.md +8 -8
- package/skills/te-community/references/community-release-analysis.md +0 -79
- package/skills/te-dataops/references/dataops-operations.md +0 -107
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
#
|
|
1
|
+
# analysis_audience +update_tag (Update Tag)
|
|
2
2
|
|
|
3
3
|
> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
|
|
4
4
|
|
|
@@ -6,7 +6,7 @@ Domain: **Tag Management**
|
|
|
6
6
|
|
|
7
7
|
## Use Cases
|
|
8
8
|
- Prerequisite helper: first call `+get_tag_definition_schema` to get the structure, then call this tool.
|
|
9
|
-
- When updating `definition`, you must first supplement it with real project metadata; at minimum, first call `
|
|
9
|
+
- When updating `definition`, you must first supplement it with real project metadata; at minimum, first call `analysis_meta +list_events` and `analysis_meta +list_properties`.
|
|
10
10
|
- 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.
|
|
11
11
|
|
|
12
12
|
## Required Prerequisites (MUST only when updating definition)
|
|
@@ -18,16 +18,16 @@ Domain: **Tag Management**
|
|
|
18
18
|
|
|
19
19
|
## Prerequisite Call Chain (run only when updating definition)
|
|
20
20
|
1. First determine `--type` (condition / metric / first_last / sql).
|
|
21
|
-
2. Read `get-tag-definition-schema.md`, then call `
|
|
22
|
-
3. Read `list-events.md`, then call `
|
|
23
|
-
4. Read `list-properties.md`, then call `
|
|
21
|
+
2. Read `get-tag-definition-schema.md`, then call `ae-cli analysis_audience +get_tag_definition_schema` to obtain the structure.
|
|
22
|
+
3. Read `list-events.md`, then call `ae-cli analysis_meta +list_events --project_id 1`.
|
|
23
|
+
4. Read `list-properties.md`, then call `ae-cli analysis_meta +list_properties --project_id 1`.
|
|
24
24
|
5. Build the new `definition` based on the schema + metadata, then run `+update_tag`.
|
|
25
25
|
|
|
26
26
|
## Commands
|
|
27
27
|
```bash
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
28
|
+
ae-cli analysis_audience +update_tag --project_id 1 --tag_name demo --display_name "Demo v2"
|
|
29
|
+
ae-cli analysis_audience +update_tag --project_id 1 --tag_name demo --type condition --definition '{}' --zone_offset 8
|
|
30
|
+
ae-cli analysis_audience +update_tag --dry-run
|
|
31
31
|
```
|
|
32
32
|
|
|
33
33
|
## Parameters
|
|
@@ -38,7 +38,7 @@ te-cli te_audience +update_tag --dry-run
|
|
|
38
38
|
| `--display_name` | No | New tag display name. Length: 1-80 |
|
|
39
39
|
| `--remark` | No | New tag remark |
|
|
40
40
|
| `--type` | No | New tag type. Supported values: condition, metric, first_last, sql |
|
|
41
|
-
| `--definition` | No | New tag definition JSON. If provided, MUST call `+get_tag_definition_schema` first, then fill valid event/property names from `
|
|
41
|
+
| `--definition` | No | New tag definition JSON. If provided, MUST call `+get_tag_definition_schema` first, then fill valid event/property names from `analysis_meta` metadata commands in the same `project_id`. |
|
|
42
42
|
| `--zone_offset` | No | Optional time zone offset for tag computation. Valid range: -12 to 14 (supports decimals like 5.5). |
|
|
43
43
|
|
|
44
44
|
## Decision Rules
|
|
@@ -56,5 +56,5 @@ te-cli te_audience +update_tag --dry-run
|
|
|
56
56
|
- If the result after writing is not as expected, immediately re-read the corresponding list/get interfaces and compare before and after.
|
|
57
57
|
|
|
58
58
|
## Recommended Chain
|
|
59
|
-
- +get_tag_definition_schema ->
|
|
59
|
+
- +get_tag_definition_schema -> analysis_meta +list_events -> analysis_meta +list_properties -> +update_tag
|
|
60
60
|
- +list_tags -> +get_tags_by_name -> +update_tag
|
|
@@ -4,7 +4,7 @@ version: 1.0.0
|
|
|
4
4
|
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."
|
|
5
5
|
metadata:
|
|
6
6
|
requires:
|
|
7
|
-
bins: ["
|
|
7
|
+
bins: ["ae-cli"]
|
|
8
8
|
---
|
|
9
9
|
|
|
10
10
|
# te-common
|
|
@@ -126,7 +126,7 @@ If the ID cannot be extracted or link generation fails, you must explain the fai
|
|
|
126
126
|
|
|
127
127
|
1. Execute the main write-operation command.
|
|
128
128
|
2. Extract `project_id`, `resource_type`, `resource_id` from the input or return value.
|
|
129
|
-
3. Call `
|
|
129
|
+
3. Call `ae-cli analysis_common +get_resource_url --project_id <id> --resource_type <type> --resource_id <id>`.
|
|
130
130
|
4. Output the main result + `markdown_link` (clickable) / `raw_url`.
|
|
131
131
|
|
|
132
132
|
## Unified Command Entry
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
# te-common resource link completion (call
|
|
1
|
+
# te-common resource link completion (call analysis_common +get_resource_url)
|
|
2
2
|
|
|
3
3
|
> **Prerequisite:** Read [`../../te-shared/SKILL.md`](../../te-shared/SKILL.md)
|
|
4
4
|
|
|
@@ -16,8 +16,8 @@ Domain: **cross-module post-write constraint**
|
|
|
16
16
|
|
|
17
17
|
## Command
|
|
18
18
|
```bash
|
|
19
|
-
|
|
20
|
-
|
|
19
|
+
ae-cli analysis_common +get_resource_url --project_id 1 --resource_type dashboard --resource_id 1
|
|
20
|
+
ae-cli analysis_common +get_resource_url --dry-run
|
|
21
21
|
```
|
|
22
22
|
|
|
23
23
|
## Parameters
|
|
@@ -28,5 +28,5 @@ te-cli te_common +get_resource_url --dry-run
|
|
|
28
28
|
| `--resource_id` | Yes | Numeric resource ID |
|
|
29
29
|
|
|
30
30
|
## Recommended Chaining
|
|
31
|
-
- `+create_*` -> `
|
|
32
|
-
- `+update_*` -> `
|
|
31
|
+
- `+create_*` -> `analysis_common +get_resource_url`
|
|
32
|
+
- `+update_*` -> `analysis_common +get_resource_url`
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
#
|
|
1
|
+
# analysis_common +list_projects (view projects accessible to the current user)
|
|
2
2
|
|
|
3
3
|
> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
|
|
4
4
|
|
|
@@ -15,8 +15,8 @@ Domain: **project discovery / cross-module pre-query**
|
|
|
15
15
|
|
|
16
16
|
## Command
|
|
17
17
|
```bash
|
|
18
|
-
|
|
19
|
-
|
|
18
|
+
ae-cli analysis_common +list_projects
|
|
19
|
+
ae-cli analysis_common +list_projects --dry-run
|
|
20
20
|
```
|
|
21
21
|
|
|
22
22
|
## Parameters
|
|
@@ -1,133 +1,125 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: te-community
|
|
3
3
|
version: 1.0.0
|
|
4
|
-
description: "TE
|
|
4
|
+
description: "TE community analysis: post search, comment sentiment, topic trends, risky content, livestream data"
|
|
5
5
|
metadata:
|
|
6
6
|
requires:
|
|
7
|
-
bins: ["
|
|
8
|
-
cliHelp: "
|
|
7
|
+
bins: ["ae-cli"]
|
|
8
|
+
cliHelp: "ae-cli community --help"
|
|
9
9
|
---
|
|
10
10
|
|
|
11
11
|
# te-community
|
|
12
12
|
|
|
13
|
-
>
|
|
13
|
+
> **Prerequisite:** Read [`../te-shared/SKILL.md`](../te-shared/SKILL.md) to learn about authentication, global parameters and security constraints.
|
|
14
14
|
|
|
15
|
-
##
|
|
15
|
+
## Overview
|
|
16
16
|
|
|
17
|
-
`te-community`
|
|
17
|
+
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.
|
|
18
18
|
|
|
19
|
-
|
|
19
|
+
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.
|
|
20
20
|
|
|
21
|
-
##
|
|
21
|
+
## Common parameters
|
|
22
22
|
|
|
23
|
-
|
|
|
23
|
+
| Parameters | Description |
|
|
24
24
|
|------|------|
|
|
25
|
-
| `--space-id` |
|
|
26
|
-
| `--game-id` |
|
|
25
|
+
| `--space-id` | Community space ID |
|
|
26
|
+
| `--game-id` | Game/space identification |
|
|
27
27
|
|
|
28
|
-
##
|
|
28
|
+
## Channel ID prerequisite: `get_channel_info`
|
|
29
29
|
|
|
30
|
-
|
|
30
|
+
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.
|
|
31
31
|
|
|
32
|
-
##
|
|
32
|
+
## Array parameter format
|
|
33
33
|
|
|
34
|
-
|
|
34
|
+
Multi-valued parameters are separated by commas:
|
|
35
35
|
```
|
|
36
36
|
--channel-id-list 1,2,3
|
|
37
37
|
--keywords tag1,tag2
|
|
38
38
|
--sentiment-types 0,1
|
|
39
39
|
```
|
|
40
40
|
|
|
41
|
-
##
|
|
41
|
+
## Date format
|
|
42
42
|
|
|
43
|
-
|
|
43
|
+
All date parameters use `yyyy-MM-dd` format, such as `--start-time 2024-01-01`.
|
|
44
44
|
|
|
45
|
-
##
|
|
45
|
+
## Reference documentation (subcommand navigation)
|
|
46
46
|
|
|
47
|
-
|
|
47
|
+
Open the corresponding file as needed to view instructions and examples (one page per command):
|
|
48
48
|
|
|
49
|
-
-
|
|
50
|
-
-
|
|
51
|
-
-
|
|
52
|
-
-
|
|
53
|
-
-
|
|
54
|
-
-
|
|
55
|
-
-
|
|
56
|
-
-
|
|
57
|
-
-
|
|
58
|
-
-
|
|
59
|
-
-
|
|
60
|
-
-
|
|
61
|
-
-
|
|
62
|
-
-
|
|
63
|
-
-
|
|
64
|
-
-
|
|
65
|
-
-
|
|
66
|
-
-
|
|
67
|
-
-
|
|
49
|
+
- Search posts or videos by keyword/time period: [search_posts](references/search_posts.md)
|
|
50
|
+
- Got the `post-id`, view the details of a single piece of content: [get_post_detail](references/get_post_detail.md)
|
|
51
|
+
- Query the list of available analysis tags: [get_corpus_tags](references/get_corpus_tags.md)
|
|
52
|
+
- Quickly view the overall sentiment and summary of the comment area: [get_comments_summary](references/get_comments_summary.md)
|
|
53
|
+
- Analyze the distribution and proportion of comment tags: [get_comment_tag_analysis](references/get_comment_tag_analysis.md)
|
|
54
|
+
- View sentiment trends (by time period): [get_sentiment_overview](references/get_sentiment_overview.md)
|
|
55
|
+
- View the community overview (posts, interactions, etc.): [get_overview_metrics](references/get_overview_metrics.md)
|
|
56
|
+
- Identify current hot topics: [get_hot_topics](references/get_hot_topics.md)
|
|
57
|
+
- Drill down to view the details of a topic: [get_topic_detail](references/get_topic_detail.md)
|
|
58
|
+
- Observe trends for specific tags: [get_tag_trends](references/get_tag_trends.md)
|
|
59
|
+
- Generate/view single-day community summary (daily): [get_daily_summary](references/get_daily_summary.md)
|
|
60
|
+
- Troubleshoot risk content and security compliance issues: [get_risk_content](references/get_risk_content.md)
|
|
61
|
+
- Get the list of livestream rooms and determine the room range: [get_livestream_rooms](references/get_livestream_rooms.md)
|
|
62
|
+
- View the live session history list: [get_livestream_list](references/get_livestream_list.md)
|
|
63
|
+
- Check the details of a livestream session: [get_livestream_detail](references/get_livestream_detail.md)
|
|
64
|
+
- Livestream session AI analysis report (highlight slices and emotional views): [get_livestream_analysis](references/get_livestream_analysis.md)
|
|
65
|
+
- Check the overall performance of the livestream module within the time period: [get_livestream_overview](references/get_livestream_overview.md)
|
|
66
|
+
- View the annual metrics of a single livestream room: [get_livestream_room_metrics](references/get_livestream_room_metrics.md)
|
|
67
|
+
- Get the channel list and basic channel information: [get_channel_info](references/get_channel_info.md)
|
|
68
68
|
|
|
69
|
-
##
|
|
69
|
+
## Advanced analysis skills
|
|
70
70
|
|
|
71
|
-
|
|
71
|
+
The following skills are called based on the MCP tool chain combination and are used to generate structured in-depth analysis.
|
|
72
72
|
|
|
73
|
-
### community-activity-analysis
|
|
73
|
+
### community-activity-analysis (activity-specific operation insight analysis)
|
|
74
74
|
|
|
75
|
-
|
|
75
|
+
In-depth evaluation of in-game activities or marketing events, including exposure impact, community sentiment, UGC ecosystem response, and long-tail effects.
|
|
76
76
|
|
|
77
|
-
|
|
77
|
+
For details, see: [`references/community-activity-analysis.md`](references/community-activity-analysis.md)
|
|
78
78
|
|
|
79
79
|
---
|
|
80
80
|
|
|
81
|
-
### community-daily-report
|
|
81
|
+
### community-daily-report (Daily Express)
|
|
82
82
|
|
|
83
|
-
|
|
83
|
+
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).
|
|
84
84
|
|
|
85
|
-
|
|
85
|
+
For details, see: [`references/community-daily-report.md`](references/community-daily-report.md)
|
|
86
86
|
|
|
87
87
|
---
|
|
88
88
|
|
|
89
|
-
### community-character-analysis
|
|
89
|
+
### community-character-analysis (character-specific in-depth analysis)
|
|
90
90
|
|
|
91
|
-
|
|
91
|
+
In-depth analysis of specific game character ecology, players' emotional motivations and core needs, focusing on root causes rather than superficial phenomena.
|
|
92
92
|
|
|
93
|
-
|
|
93
|
+
For details, see: [`references/community-character-analysis.md`](references/community-character-analysis.md)
|
|
94
94
|
|
|
95
95
|
---
|
|
96
96
|
|
|
97
|
-
### community-hottopic-insight
|
|
97
|
+
### community-hottopic-insight (topic analysis)
|
|
98
98
|
|
|
99
|
-
|
|
99
|
+
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.
|
|
100
100
|
|
|
101
|
-
|
|
101
|
+
For details, see: [`references/community-hottopic-insight.md`](references/community-hottopic-insight.md)
|
|
102
102
|
|
|
103
103
|
---
|
|
104
104
|
|
|
105
|
-
### community-
|
|
105
|
+
### community-weekly-report (weekly summary of community operations)
|
|
106
106
|
|
|
107
|
-
|
|
107
|
+
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."
|
|
108
108
|
|
|
109
|
-
|
|
109
|
+
For details, see: [`references/community-weekly-report.md`](references/community-weekly-report.md)
|
|
110
110
|
|
|
111
111
|
---
|
|
112
112
|
|
|
113
|
-
### community-
|
|
113
|
+
### community-analyzing-official-content (official content analysis)
|
|
114
114
|
|
|
115
|
-
|
|
115
|
+
Analyze recently published official content for a specified game in the community module, then classify and summarize it using the predefined categories.
|
|
116
116
|
|
|
117
|
-
|
|
117
|
+
For details, see: [`references/community-analyzing-official-content.md`](references/community-analyzing-official-content.md)
|
|
118
118
|
|
|
119
119
|
---
|
|
120
120
|
|
|
121
|
-
### community-analyzing-
|
|
121
|
+
### community-analyzing-theme-comment (in-depth analysis of the theme comment area)
|
|
122
122
|
|
|
123
|
-
|
|
123
|
+
Conduct in-depth analysis of comments on specified posts or videos, then produce a report covering trend shifts, viewpoint distribution, and key takeaways.
|
|
124
124
|
|
|
125
|
-
|
|
126
|
-
|
|
127
|
-
---
|
|
128
|
-
|
|
129
|
-
### community-analyzing-theme-comment(主题评论区深度分析)
|
|
130
|
-
|
|
131
|
-
对指定帖子或视频的评论区进行深度分析,生成包含评论走势、观点分布和总结的深度分析报告。
|
|
132
|
-
|
|
133
|
-
详见:[`references/community-analyzing-theme-comment.md`](references/community-analyzing-theme-comment.md)
|
|
125
|
+
For details, see: [`references/community-analyzing-theme-comment.md`](references/community-analyzing-theme-comment.md)
|
|
@@ -1,68 +1,68 @@
|
|
|
1
1
|
# te-community community-activity-analysis
|
|
2
2
|
|
|
3
|
-
>
|
|
3
|
+
> **Prerequisite:** Read [`../te-shared/SKILL.md`](../te-shared/SKILL.md)
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
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".
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
Trigger scenario: When the user asks to "analyze a certain activity", "generate activity review", "see feedback from XX activity" or "evaluate marketing effectiveness".
|
|
8
8
|
|
|
9
|
-
##
|
|
9
|
+
## Analysis process
|
|
10
10
|
|
|
11
|
-
1.
|
|
12
|
-
2.
|
|
13
|
-
3.
|
|
14
|
-
4.
|
|
15
|
-
5.
|
|
11
|
+
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
|
|
12
|
+
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
|
|
13
|
+
3. **Word-of-mouth and pain points deep-dive analysis of**: Call `get_sentiment_overview` to analyze positive and negative high-frequency keywords
|
|
14
|
+
4. **Fixed-point blasting evidence collection**: Call `search_posts` -> `get_post_detail` -> `get_comments_summary` to obtain real player cases
|
|
15
|
+
5. **Risk Control and Red Line Checking**: Call `get_risk_content` to check compliance risk content
|
|
16
16
|
|
|
17
|
-
##
|
|
17
|
+
## Core Constraints
|
|
18
18
|
|
|
19
|
-
-
|
|
20
|
-
-
|
|
21
|
-
|
|
22
|
-
|
|
19
|
+
- **Reject false claims**: You must write down the specific reasons and attach supporting posts or comments.
|
|
20
|
+
- **Strictly distinguish between early warning and risk control**:
|
|
21
|
+
- Early Warning: Event experience issues (mechanism, bugs, rewards, liveliness)
|
|
22
|
+
- Risk control: Risks of violations (black/gray-market activity, leaks, wars, advertising, etc.)
|
|
23
23
|
|
|
24
|
-
##
|
|
24
|
+
## Output structure
|
|
25
25
|
|
|
26
|
-
###
|
|
27
|
-
-
|
|
28
|
-
-
|
|
26
|
+
### 1. Activity overview and core data
|
|
27
|
+
- Set the tone for the event
|
|
28
|
+
- Core sound volume and exposure indicators (including tables)
|
|
29
29
|
|
|
30
|
-
###
|
|
31
|
-
-
|
|
32
|
-
-
|
|
30
|
+
### 2. Insights into community feedback and sentiment highlights
|
|
31
|
+
- **Activity Highlights and Highlights** (with typical acoustic support)
|
|
32
|
+
- **Core slots and experience pain points** (including typical original sound support)
|
|
33
33
|
|
|
34
|
-
###
|
|
35
|
-
-
|
|
36
|
-
-
|
|
34
|
+
### 3. Content dissemination and secondary innovation ecological mining
|
|
35
|
+
- Core out-of-circle topics/meme culture
|
|
36
|
+
- Inventory of secondary innovation output potential
|
|
37
37
|
|
|
38
|
-
###
|
|
39
|
-
-
|
|
40
|
-
-
|
|
38
|
+
### 4. Impact on community ecology
|
|
39
|
+
-Activity pulling effect
|
|
40
|
+
- Player structure/genre evolution
|
|
41
41
|
|
|
42
|
-
###
|
|
43
|
-
-
|
|
44
|
-
-
|
|
45
|
-
-
|
|
42
|
+
### 5. Inspiration and optimization suggestions for operational strategies
|
|
43
|
+
- Design pitfalls in follow-up activities
|
|
44
|
+
- Long-tail marketing strategies
|
|
45
|
+
- Livestream/publicity side review
|
|
46
46
|
|
|
47
|
-
###
|
|
47
|
+
### 6. Activity warning and compliance risk control
|
|
48
48
|
|
|
49
|
-
**⚠️
|
|
49
|
+
**⚠️ Event sentiment and experience warning**
|
|
50
50
|
|
|
51
|
-
|
|
|
51
|
+
| Warning level | Warning trigger items | Community spread | Core performance | Suggested follow-up actions |
|
|
52
52
|
|---------|-----------|-----------|---------|-------------|
|
|
53
|
-
|
|
|
53
|
+
| High/medium/low | Specific problems | Scope of impact | Specific performance | Handling suggestions |
|
|
54
54
|
|
|
55
|
-
**⛔
|
|
55
|
+
**⛔ Community compliance and risk control interception**
|
|
56
56
|
|
|
57
|
-
|
|
|
57
|
+
| Risk control level | Violation type | Discovery channels | Violation facts | Disposal suggestions |
|
|
58
58
|
|---------|---------|---------|-------------|---------|
|
|
59
|
-
|
|
|
59
|
+
| Serious/General | Violation type | Channel name | Specific facts | Handling suggestions |
|
|
60
60
|
|
|
61
|
-
##
|
|
61
|
+
## Example
|
|
62
62
|
|
|
63
63
|
```bash
|
|
64
|
-
#
|
|
65
|
-
"
|
|
66
|
-
"
|
|
67
|
-
"
|
|
64
|
+
# User input example
|
|
65
|
+
"Help me analyze the feedback on such and such activities"
|
|
66
|
+
"Generate an activity review report for the half-anniversary celebration"
|
|
67
|
+
"Evaluate the effectiveness of this marketing campaign"
|
|
68
68
|
```
|
|
@@ -1,72 +1,72 @@
|
|
|
1
1
|
# te-community community-analyzing-official-content
|
|
2
2
|
|
|
3
|
-
>
|
|
3
|
+
> **Prerequisite:** Read [`../te-shared/SKILL.md`](../te-shared/SKILL.md)
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
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.
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
Trigger scenario: Use this skill when the user wants to know the official release content of the specified game in the near future.
|
|
8
8
|
|
|
9
|
-
##
|
|
9
|
+
## Analysis process
|
|
10
10
|
|
|
11
|
-
1.
|
|
12
|
-
2.
|
|
13
|
-
3.
|
|
14
|
-
4.
|
|
11
|
+
1. **Confirm analysis time**: Get the start date and end date (recommended not to exceed 30 days)
|
|
12
|
+
2. **Query official content**: Call `search_posts` and set the `official: true` parameter
|
|
13
|
+
3. **Content Classification Analysis**: Classified by four categories: game announcements, community activities, linkages, and promotional materials
|
|
14
|
+
4. **Formatted output**: Generate a structured official content analysis report
|
|
15
15
|
|
|
16
|
-
##
|
|
16
|
+
## Execution process
|
|
17
17
|
|
|
18
|
-
|
|
19
|
-
-
|
|
20
|
-
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
- ⚠️
|
|
18
|
+
**Step 1: Confirm analysis time**
|
|
19
|
+
- **If the user has specified the analysis time**: Record the time range (start time, end time) and enter step 2
|
|
20
|
+
- **If the user does not specify the analysis time**: Inform the user to provide the following information before proceeding:
|
|
21
|
+
- Start date of analysis
|
|
22
|
+
- The end date of the analysis
|
|
23
|
+
- ⚠️ The time range is recommended to be no more than 30 days to ensure query efficiency and content readability
|
|
24
24
|
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
-
|
|
28
|
-
-
|
|
25
|
+
**Step 2: Check official content**
|
|
26
|
+
Use the `search_posts` tool to query official published content within a specified time range.
|
|
27
|
+
- Calling parameters: `gameId`, `startTime`, `endTime`, `official: true`, `pagerHeader`
|
|
28
|
+
- Focus on recording the total number of topics, channel distribution and timestamp of each post
|
|
29
29
|
|
|
30
|
-
|
|
31
|
-
|
|
30
|
+
**Step 3: Content Classification and Analysis**
|
|
31
|
+
Classification analysis according to the following four categories
|
|
32
32
|
|
|
33
|
-
##
|
|
33
|
+
## Content classification criteria
|
|
34
34
|
|
|
35
|
-
|
|
|
35
|
+
| Category | Definition | Information to be extracted |
|
|
36
36
|
|------|------|----------------|
|
|
37
|
-
|
|
|
38
|
-
|
|
|
39
|
-
|
|
|
40
|
-
|
|
|
37
|
+
| **Game Announcement** | Announcement and introduction of new game content such as new versions and new activities | Activity/version/new card pool content, game elements, duration (resident activities return to "Resident") |
|
|
38
|
+
| **Community Activities** | Activities that promote players to post, reply, and create in the community, usually with physical rewards or community titles | Publishing platform, activity requirements, duration, and reward content |
|
|
39
|
+
| **Linkage** | Announcement of linkage activities outside the game | Linkage brand/IP, linkage time, linkage form (in-game linkage ownership game announcement) |
|
|
40
|
+
| **Promotional Materials** | General promotional materials (pictures, comics, character quotes, etc.) | Related characters/content, material form |
|
|
41
41
|
|
|
42
|
-
##
|
|
42
|
+
## Cross-platform merge rules
|
|
43
43
|
|
|
44
|
-
-
|
|
45
|
-
-
|
|
44
|
+
- **Game announcements, linkages, and promotional materials**: If the same content is released on multiple platforms and the content is consistent, merge it into one, and indicate "multi-platform release" in the summary
|
|
45
|
+
- **Community Activities**: Each platform is listed separately and is not merged (because the activity rules of different platforms may be different)
|
|
46
46
|
|
|
47
|
-
##
|
|
47
|
+
## Output structure
|
|
48
48
|
|
|
49
|
-
###
|
|
50
|
-
-
|
|
51
|
-
-
|
|
52
|
-
-
|
|
49
|
+
### 1. Analysis summary
|
|
50
|
+
- **Game**: Game name
|
|
51
|
+
- **Analysis time**: start date - end date
|
|
52
|
+
- **TOTAL OFFICIAL CONTENT**: Total quantity
|
|
53
53
|
|
|
54
|
-
###
|
|
55
|
-
|
|
54
|
+
### 2. Game Announcement
|
|
55
|
+
Contents list (sorted by time)
|
|
56
56
|
|
|
57
|
-
###
|
|
58
|
-
|
|
57
|
+
### 3. Community activities
|
|
58
|
+
Content list (sorted by platform and time)
|
|
59
59
|
|
|
60
|
-
###
|
|
61
|
-
|
|
60
|
+
### 4. Linkage
|
|
61
|
+
Contents list (sorted by time)
|
|
62
62
|
|
|
63
|
-
###
|
|
64
|
-
|
|
63
|
+
### 5. Promotional materials
|
|
64
|
+
Contents list (sorted by time)
|
|
65
65
|
|
|
66
|
-
##
|
|
66
|
+
## Example
|
|
67
67
|
|
|
68
68
|
```bash
|
|
69
|
-
#
|
|
70
|
-
"
|
|
71
|
-
"
|
|
69
|
+
# User input example
|
|
70
|
+
"Analyze the official releases of the past week"
|
|
71
|
+
"Help me sort out this month's official announcements"
|
|
72
72
|
```
|