@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,120 +1,114 @@
|
|
|
1
1
|
# te-community community-hottopic-insight
|
|
2
2
|
|
|
3
|
-
>
|
|
3
|
+
> * * Prerequisites: * * Read [`../te-shared/SKILL.md'] (../te-shared/SKILL.md)
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
Topic analysis: Automatically collect corpus, intelligently identify industry attributes, and output a structured Topic Analysis that includes a core summary, an overview of sentiment and the context of events, core hot discussions, sentiment slices, social media channel insights, and operational recommendations.
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
Triggering scenario: Triggered when the user requests "Analyze topic", "Generate topic analysis report" or "Topic analysis".
|
|
8
8
|
|
|
9
|
-
|
|
9
|
+
# # Analysis process
|
|
10
10
|
|
|
11
|
-
1.
|
|
12
|
-
2.
|
|
13
|
-
3.
|
|
11
|
+
1. * * `get_hot_topics` * *: Get topic information (topicId, startTime, endTime)
|
|
12
|
+
2. * * `search_posts` * *: Search related posts by topic ID, * * Focus on recording the time, total number and distribution of posts by channel * *
|
|
13
|
+
3. * * `get_post_detail` * *: Grab high-profile content details (up to 10)
|
|
14
14
|
|
|
15
|
-
|
|
15
|
+
# # Entity and Time Rules
|
|
16
16
|
|
|
17
|
-
-
|
|
18
|
-
-
|
|
19
|
-
-
|
|
17
|
+
- [Topic name] must be extracted from user input
|
|
18
|
+
- If the user does not provide it, the user must ask the core analysis object
|
|
19
|
+
- If the user does not specify a specific time, * * the current system time is automatically pushed forward by 7-14 days as the query cycle * *
|
|
20
20
|
|
|
21
|
-
|
|
21
|
+
Core Requirements
|
|
22
22
|
|
|
23
|
-
-
|
|
24
|
-
-
|
|
25
|
-
-
|
|
26
|
-
-
|
|
23
|
+
- * * Dynamic traceability authenticity * *: must be strongly dependent on the post's real publishing time
|
|
24
|
+
- * * Evolutionary chains of "Time - Events - Topics - Emotions" must be clearly identified * *
|
|
25
|
+
- In chronological order, extract "what happened at what time, what was mainly discussed at that time, what was the emotion"
|
|
26
|
+
- If you can't catch the timestamp, please truthfully explain that "due to data limitations, it is impossible to generate an accurate timeline", and it is strictly forbidden to fabricate a false history of development
|
|
27
27
|
|
|
28
|
-
|
|
28
|
+
# # Output structure
|
|
29
29
|
|
|
30
|
-
|
|
30
|
+
* *⚠️ Mandatory: The report must be output in strict accordance with the structure of the following six parts, no parts may be omitted, and the order or format may not be changed. * *
|
|
31
31
|
|
|
32
|
-
|
|
33
|
-
-
|
|
34
|
-
-
|
|
32
|
+
# # # I. Summary of Core Content
|
|
33
|
+
- Event Overview: Summarize what everyone is talking about in one sentence
|
|
34
|
+
- The evolution of sentiment: such as "experienced a sharp reversal from the positive expectation of the previous period to the collapse of the reputation of the factor value problem after the launch"
|
|
35
35
|
|
|
36
|
-
|
|
36
|
+
# # # II. Overview of Public Opinion Data and Dynamic Evolution
|
|
37
37
|
|
|
38
|
-
|
|
39
|
-
-
|
|
40
|
-
-
|
|
41
|
-
-
|
|
38
|
+
* * Quantitative📊 sentiment statistics * *:
|
|
39
|
+
- Total number of current topics
|
|
40
|
+
- Overview of the number of content in each channel
|
|
41
|
+
- Overall Sentiment Ratio
|
|
42
42
|
|
|
43
|
-
|
|
43
|
+
* * Trends in🔥 popularity * *: Describe popularity trends
|
|
44
44
|
|
|
45
|
-
|
|
46
|
-
-
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
-
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
45
|
+
* * * Dynamic Public Opinion Evolution Vein (🔴Core must be itemized, not omitted) * *:
|
|
46
|
+
- * * `[MM-DD]` | Phase 1: [Phase naming, e.g. prospective warm-up period - expecting to be full] * *
|
|
47
|
+
- * * Trigger Node * *: [What happened at that time, ex: the official release of the live demo PV]
|
|
48
|
+
- * * Core Focus * *: [What players are talking about, e.g., motion fluency, fine art modeling]
|
|
49
|
+
- * * Emotional direction * *: [ex:🟢 extremely positive expectations, players are highly rated]
|
|
50
|
+
- * * `[MM-DD]` | Phase 2: [Phase name, e.g. live/new story launch] * *
|
|
51
|
+
- * * Trigger Node * *: [ex: Core mechanism was tampered with after update]
|
|
52
|
+
- * * Core Focus * *: [ex: Accusation of official misinformation, request for refund of deposit]
|
|
53
|
+
- * * Emotional direction * *🔴: [ex: Negative outburst]
|
|
54
|
+
- * * `[MM-DD]` | Phase 3: [Phase Naming, e.g. Current Status/Official Response] * *
|
|
55
|
+
- * * Trigger Node * *: [ex: official apology blue sticker description]
|
|
56
|
+
- * * Core Focus * *: [ex: Is the compensation plan justified in a tug-of-war?]
|
|
57
|
+
- * * Emotional direction * *: [ex:🟡 Negative emotions ease slightly, turn to wait and see for confirmation]
|
|
58
58
|
|
|
59
|
-
|
|
59
|
+
* Note: The number of stages increases or decreases according to the actual discussion escalation process *
|
|
60
60
|
|
|
61
|
-
|
|
62
|
-
|
|
61
|
+
# # # III. Summary of Core Hotspot Discussions
|
|
62
|
+
Objectively distill the 2-3 core specific issues that are currently the loudest and most controversial, regardless of emotions
|
|
63
63
|
|
|
64
|
-
|
|
64
|
+
# # # IV. Emotional Slicing and Opinion Analysis
|
|
65
65
|
|
|
66
|
-
|
|
67
|
-
-
|
|
68
|
-
-
|
|
69
|
-
-
|
|
70
|
-
|
|
71
|
-
|
|
66
|
+
* *🔴 Negative Emotional Slice * *
|
|
67
|
+
- * * Focus Issue * *: [Specific Issue]
|
|
68
|
+
- * * High frequency word cloud * *: [keyword list]
|
|
69
|
+
- * * Typical Player Soundtrack * *:
|
|
70
|
+
- "[True Comment 1]"
|
|
71
|
+
- "[True Comment 2]"
|
|
72
72
|
|
|
73
|
-
|
|
74
|
-
-
|
|
75
|
-
-
|
|
76
|
-
-
|
|
77
|
-
|
|
78
|
-
|
|
73
|
+
* *🟡 Neutral Emotion Slice * *
|
|
74
|
+
- * * Focus Issue * *: [Specific Issue]
|
|
75
|
+
- * * High frequency word cloud * *: [keyword list]
|
|
76
|
+
- * * Typical Player Soundtrack * *:
|
|
77
|
+
- "[True Comment 1]"
|
|
78
|
+
- "[True Comment 2]"
|
|
79
79
|
|
|
80
|
-
|
|
81
|
-
-
|
|
82
|
-
-
|
|
83
|
-
-
|
|
84
|
-
|
|
85
|
-
|
|
80
|
+
* *🟢 Positive Emotional Slice * *
|
|
81
|
+
- * * Focus Issue * *: [Specific Issue]
|
|
82
|
+
- * * High frequency word cloud * *: [keyword list]
|
|
83
|
+
- * * Typical Player Soundtrack * *:
|
|
84
|
+
- "[True Comment 1]"
|
|
85
|
+
- "[True Comment 2]"
|
|
86
86
|
|
|
87
|
-
|
|
87
|
+
* *⚠️ Note: The player's soundtrack must use "" to quote authentic reviews, and fabrication is strictly forbidden. * *
|
|
88
88
|
|
|
89
|
-
|
|
90
|
-
|
|
89
|
+
# # # V. Content insights across social media platforms
|
|
90
|
+
Compare of detailed data from different channels and characteristics of sentiment
|
|
91
91
|
|
|
92
|
-
|
|
92
|
+
# # # VI. Suggestions for Operation and Response from an Industry Perspective
|
|
93
93
|
|
|
94
|
-
|
|
95
|
-
-
|
|
96
|
-
-
|
|
94
|
+
* *⚡ Emergency Intervention (Firefighting Strategies for Crisis Response) * *
|
|
95
|
+
- Risk Assessment: [Specific Risks]
|
|
96
|
+
- Suggested action: [Specific action]
|
|
97
97
|
|
|
98
|
-
|
|
99
|
-
-
|
|
100
|
-
-
|
|
98
|
+
* 🚀 * Homeostasis (amplification strategy for operational activation) * *
|
|
99
|
+
- Opportunity Point Identification: [Specific Opportunity]
|
|
100
|
+
- Suggested Tactics: [Specific Tactics]
|
|
101
101
|
|
|
102
|
-
|
|
102
|
+
# # User input example
|
|
103
103
|
|
|
104
104
|
```bash
|
|
105
|
-
"
|
|
106
|
-
"
|
|
107
|
-
"
|
|
105
|
+
"Analyze the topic of # new UI redesign #"
|
|
106
|
+
"Generate the analysis report for the XX version of the comprehensive review topic"
|
|
107
|
+
"Analyze XX topics for me"
|
|
108
108
|
```
|
|
109
109
|
|
|
110
|
-
|
|
111
|
-
|
|
112
|
-
|
|
113
|
-
-
|
|
114
|
-
-
|
|
115
|
-
- [ ] 已调用 `get_post_detail` 获取高热度内容详情
|
|
116
|
-
- [ ] 报告包含完整的六个部分
|
|
117
|
-
- [ ] 第二部分包含"动态舆情演变脉络"(按时间线)
|
|
118
|
-
- [ ] 第四部分包含三个情绪切片(正面/中立/负面)
|
|
119
|
-
- [ ] 所有玩家原声都用「」引用真实评论
|
|
120
|
-
- [ ] 第六部分分为"紧急干预"和"顺势引导"两部分
|
|
110
|
+
# # Execute Checklist
|
|
111
|
+
|
|
112
|
+
- Typical soundtracks must be traced back to real posts/comments.
|
|
113
|
+
- Channel insights must reflect platform differences, not just data.
|
|
114
|
+
- Suggestions are divided into “emergency intervention” and “homeopathic guidance”.
|
|
@@ -1,84 +1,85 @@
|
|
|
1
1
|
# te-community community-weekly-report
|
|
2
2
|
|
|
3
|
-
>
|
|
3
|
+
> **Prerequisite:** Read [`../te-shared/SKILL.md`](../te-shared/SKILL.md)
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
Community Operation Weekly Summary: Summarize a week's data, focus on the "Daily Summary" to connect the core escalating discussion events of the week, and output a "Community Operations Weekly Summary Report."
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
Trigger: Use this when the user asks for "generate weekly report", "community operation weekly report", "weekly summary" and "review of the past week".
|
|
8
8
|
|
|
9
|
-
##
|
|
9
|
+
## Roles and Goals
|
|
10
10
|
|
|
11
|
-
|
|
12
|
-
2. **调用 MCP 工具**:
|
|
13
|
-
- `get_overview_metrics`:获取周度概览指标
|
|
14
|
-
- `get_daily_summary`:获取每日舆情与内容摘要
|
|
15
|
-
- `get_sentiment_overview`:获取全盘情感分布
|
|
16
|
-
- `get_comments_summary`:获取评论趋势分析
|
|
17
|
-
- `get_risk_content`:获取合规风控趋势
|
|
18
|
-
- `get_hot_topics`:获取榜单话题
|
|
11
|
+
You are "Director of Community Operations + Senior Data Analyst". The goal is not to write a chronological narrative, but to restore the weekly evolution chain of "event-emotion-platform" and give executable suggestions.
|
|
19
12
|
|
|
20
|
-
##
|
|
13
|
+
## Time deduction rules
|
|
21
14
|
|
|
22
|
-
1.
|
|
23
|
-
2.
|
|
15
|
+
1. The user clearly gives the date: query strictly according to the user scope.
|
|
16
|
+
2. The user does not provide a date: automatically retrieve the past 7 days (`endTime=yesterday`, `startTime=endTime-7d`).
|
|
17
|
+
3. Don’t interrupt the process due to lack of time.
|
|
24
18
|
|
|
25
|
-
##
|
|
19
|
+
## Required tool chain
|
|
26
20
|
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
21
|
+
1. `get_overview_metrics` (weekly total and channel distribution)
|
|
22
|
+
2. `get_daily_summary` (daily context, weekly report core input)
|
|
23
|
+
3. `get_sentiment_overview` (sentiment structure)
|
|
24
|
+
4. `get_comments_summary` (emotion changes on the comment side)
|
|
25
|
+
5. `get_risk_content` (compliance risk control)
|
|
26
|
+
6. `get_hot_topics` (hotspot assisted verification)
|
|
31
27
|
|
|
32
|
-
##
|
|
28
|
+
## Output structure (must be complete)
|
|
33
29
|
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
-
|
|
30
|
+
1. **Core summary of the report**: Setting the tone for this week + hot keywords
|
|
31
|
+
2. **Overview indicator board**: total volume, sentiment distribution, channel matrix (table)
|
|
32
|
+
3. **Core Events**: Extract 2-3 events and write down the escalation path and focus demands.
|
|
33
|
+
4. **Platform Insights**: Discussion styles and core differences across different channels
|
|
34
|
+
5. **Early Warning and Risk Control** (two independent tables)
|
|
35
|
+
- Early warning: Bug/mechanism/plot/experience issues
|
|
36
|
+
- Risk control: black/gray-market activity/advertising/sensitive violations/flamebait/content designed to provoke conflict, etc.
|
|
37
|
+
6. **Action suggestions for next week**: Problem closed loop, distribution strategy, monitoring focus
|
|
37
38
|
|
|
38
|
-
###
|
|
39
|
+
### 2. Overview of statistical indicators
|
|
39
40
|
|
|
40
|
-
|
|
|
41
|
+
| Indicator categories | Data | Weekly |
|
|
41
42
|
|---------|------|--------|
|
|
42
|
-
|
|
|
43
|
-
|
|
|
44
|
-
|
|
|
43
|
+
| Total content of the market | Specific values | ↑/↓ X% |
|
|
44
|
+
| Overall sentiment distribution | Positive/neutral/negative proportion | Changing trends |
|
|
45
|
+
| Channel volume distribution matrix | Data of each channel | Channel comparison |
|
|
45
46
|
|
|
46
|
-
###
|
|
47
|
+
### 3. Insights into this week’s core events and sentiment context
|
|
47
48
|
|
|
48
|
-
|
|
49
|
-
-
|
|
50
|
-
|
|
51
|
-
|
|
49
|
+
**Tracking of core sentiment events this week**:
|
|
50
|
+
- **Big Event 1**: [Event Name]
|
|
51
|
+
- **Fermentation context**: [Timeline review]
|
|
52
|
+
- **Public Opinion Focus/Demand**: [Core Viewpoint]
|
|
52
53
|
|
|
53
|
-
|
|
54
|
-
-
|
|
54
|
+
**User comments and emotional dynamic evolution**:
|
|
55
|
+
- Sentiment trend analysis
|
|
55
56
|
|
|
56
|
-
###
|
|
57
|
-
|
|
57
|
+
### 4. In-depth insights into each platform
|
|
58
|
+
Horizontally compare the tone differences of different social media platforms
|
|
58
59
|
|
|
59
|
-
###
|
|
60
|
+
### 5. Community early warning and safety risk control
|
|
60
61
|
|
|
61
|
-
**⚠️
|
|
62
|
+
**⚠️ Early warning information**
|
|
62
63
|
|
|
63
|
-
|
|
|
64
|
+
| Warning level | Warning trigger items | Community spread | Core performance | Suggested follow-up actions |
|
|
64
65
|
|---------|-----------|-----------|---------|-------------|
|
|
65
|
-
|
|
|
66
|
+
| High/medium/low | Specific problems | Scope of impact | Specific performance | Handling suggestions |
|
|
66
67
|
|
|
67
|
-
**🛡️
|
|
68
|
+
**🛡️ Security compliance and risk control interception**
|
|
68
69
|
|
|
69
|
-
|
|
|
70
|
+
| Risk control level | Violation type | Discovery channels | Violation facts | Disposal suggestions |
|
|
70
71
|
|---------|---------|---------|-------------|---------|
|
|
71
|
-
|
|
|
72
|
+
| Serious/General | Violation type | Channel name | Specific facts | Handling suggestions |
|
|
72
73
|
|
|
73
|
-
###
|
|
74
|
-
-
|
|
75
|
-
-
|
|
74
|
+
### 6. Operation suggestions and planning for next week
|
|
75
|
+
- short term advice
|
|
76
|
+
- Focus on next week
|
|
76
77
|
|
|
77
|
-
##
|
|
78
|
+
## Example
|
|
78
79
|
|
|
79
80
|
```bash
|
|
80
|
-
#
|
|
81
|
-
"
|
|
82
|
-
"
|
|
83
|
-
"
|
|
81
|
+
# User input example
|
|
82
|
+
"Generate weekly report"
|
|
83
|
+
"Last week's community operations weekly report"
|
|
84
|
+
"Weekly Summary"
|
|
84
85
|
```
|
|
@@ -1,21 +1,21 @@
|
|
|
1
1
|
# te-community get_channel_info
|
|
2
2
|
|
|
3
|
-
>
|
|
3
|
+
> **Prerequisite:** Read [`../te-shared/SKILL.md`](../te-shared/SKILL.md)
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
Get the list of valid channels for the community space, including channel IDs and names. **This is the prerequisite step for most commands that require `--channel-id` / `--channel-id-list`: First get the real channel ID here, and then call `search_posts`, `get_post_detail`, `get_comments_summary`, `get_livestream_list`, etc. with parameters (subject to the reference of each command).
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
Mapping command: `ae-cli community get_channel_info`
|
|
8
8
|
|
|
9
9
|
## Flags
|
|
10
10
|
|
|
11
|
-
| Flag |
|
|
11
|
+
| Flag | Type | Required | Description |
|
|
12
12
|
|------|------|------|------|
|
|
13
|
-
| `--space-id` | number |
|
|
14
|
-
| `--game-id` | number |
|
|
13
|
+
| `--space-id` | number | yes | community space ID |
|
|
14
|
+
| `--game-id` | number | yes | game/space ID |
|
|
15
15
|
|
|
16
|
-
##
|
|
16
|
+
## Example
|
|
17
17
|
|
|
18
18
|
```bash
|
|
19
|
-
#
|
|
20
|
-
|
|
19
|
+
# Get channel list
|
|
20
|
+
ae-cli community get_channel_info --space-id 1 --game-id 1
|
|
21
21
|
```
|
|
@@ -1,29 +1,29 @@
|
|
|
1
1
|
# te-community get_comment_tag_analysis
|
|
2
2
|
|
|
3
|
-
>
|
|
3
|
+
> **Prerequisite:** Read [`../te-shared/SKILL.md`](../te-shared/SKILL.md)
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
Comment tag analysis: Specify the tag code and return the count and time trend of each tag value.
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
Mapping command: `ae-cli community get_comment_tag_analysis`
|
|
8
8
|
|
|
9
9
|
## Flags
|
|
10
10
|
|
|
11
|
-
| Flag |
|
|
11
|
+
| Flag | Type | Required | Description |
|
|
12
12
|
|------|------|------|------|
|
|
13
|
-
| `--space-id` | number |
|
|
14
|
-
| `--game-id` | number |
|
|
15
|
-
| `--channel-id` | number |
|
|
16
|
-
| `--uuid` | string |
|
|
17
|
-
| `--resource-type` | number |
|
|
18
|
-
| `--tag-code` | string |
|
|
19
|
-
| `--start-time` | string |
|
|
20
|
-
| `--end-time` | string |
|
|
13
|
+
| `--space-id` | number | yes | community space ID |
|
|
14
|
+
| `--game-id` | number | yes | game/space ID |
|
|
15
|
+
| `--channel-id` | number | yes | channel ID |
|
|
16
|
+
| `--uuid` | string | yes | content UUID |
|
|
17
|
+
| `--resource-type` | number | Yes | Resource type: `0` for posts, `1` for videos |
|
|
18
|
+
| `--tag-code` | string | Yes | Tag code (obtain via `get_corpus_tags`) |
|
|
19
|
+
| `--start-time` | string | No | Earliest comment publish date, format yyyy-MM-dd, default is the publishing time of the post |
|
|
20
|
+
| `--end-time` | string | No | Latest comment publish date, format yyyy-MM-dd |
|
|
21
21
|
|
|
22
|
-
##
|
|
22
|
+
## Example
|
|
23
23
|
|
|
24
24
|
```bash
|
|
25
|
-
#
|
|
26
|
-
|
|
25
|
+
# Analyze comment tags
|
|
26
|
+
ae-cli community get_comment_tag_analysis \
|
|
27
27
|
--space-id 1 --game-id 1 \
|
|
28
28
|
--channel-id 1 --uuid <uuid> \
|
|
29
29
|
--resource-type 0 --tag-code "sentiment"
|
|
@@ -1,32 +1,32 @@
|
|
|
1
1
|
# te-community get_comments_summary
|
|
2
2
|
|
|
3
|
-
>
|
|
3
|
+
> **Prerequisite:** Read [`../te-shared/SKILL.md`](../te-shared/SKILL.md)
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
Get a summary of comment analysis for a post, including sentiment distribution and time trends. Only aggregate statistics are returned, no raw review list.
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
Mapping command: `ae-cli community get_comments_summary`
|
|
8
8
|
|
|
9
9
|
## Flags
|
|
10
10
|
|
|
11
|
-
| Flag |
|
|
11
|
+
| Flag | Type | Required | Description |
|
|
12
12
|
|------|------|------|------|
|
|
13
|
-
| `--space-id` | number |
|
|
14
|
-
| `--game-id` | number |
|
|
15
|
-
| `--channel-id` | number |
|
|
16
|
-
| `--uuid` | string |
|
|
17
|
-
| `--start-time` | string |
|
|
18
|
-
| `--end-time` | string |
|
|
13
|
+
| `--space-id` | number | yes | community space ID |
|
|
14
|
+
| `--game-id` | number | yes | game/space ID |
|
|
15
|
+
| `--channel-id` | number | yes | channel ID |
|
|
16
|
+
| `--uuid` | string | yes | content UUID |
|
|
17
|
+
| `--start-time` | string | No | Earliest comment publish date, format yyyy-MM-dd, default is the publishing time of the post |
|
|
18
|
+
| `--end-time` | string | No | Latest comment publish date, format yyyy-MM-dd |
|
|
19
19
|
|
|
20
|
-
##
|
|
20
|
+
## Example
|
|
21
21
|
|
|
22
22
|
```bash
|
|
23
|
-
#
|
|
24
|
-
|
|
23
|
+
# Get comment summary
|
|
24
|
+
ae-cli community get_comments_summary \
|
|
25
25
|
--space-id 1 --game-id 1 \
|
|
26
26
|
--channel-id 1 --uuid <uuid>
|
|
27
27
|
|
|
28
|
-
#
|
|
29
|
-
|
|
28
|
+
#Specify time range
|
|
29
|
+
ae-cli community get_comments_summary \
|
|
30
30
|
--space-id 1 --game-id 1 \
|
|
31
31
|
--channel-id 1 --uuid <uuid> \
|
|
32
32
|
--start-time 2024-01-01 --end-time 2024-01-07
|
|
@@ -1,21 +1,21 @@
|
|
|
1
1
|
# te-community get_corpus_tags
|
|
2
2
|
|
|
3
|
-
>
|
|
3
|
+
> **Prerequisite:** Read [`../te-shared/SKILL.md`](../te-shared/SKILL.md)
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
Query the list of available corpus tags for filtering.
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
Mapping command: `ae-cli community get_corpus_tags`
|
|
8
8
|
|
|
9
9
|
## Flags
|
|
10
10
|
|
|
11
|
-
| Flag |
|
|
11
|
+
| Flag | Type | Required | Description |
|
|
12
12
|
|------|------|------|------|
|
|
13
|
-
| `--space-id` | number |
|
|
14
|
-
| `--game-id` | number |
|
|
13
|
+
| `--space-id` | number | yes | community space ID |
|
|
14
|
+
| `--game-id` | number | yes | game/space ID |
|
|
15
15
|
|
|
16
|
-
##
|
|
16
|
+
## Example
|
|
17
17
|
|
|
18
18
|
```bash
|
|
19
|
-
#
|
|
20
|
-
|
|
19
|
+
# Get the tag list
|
|
20
|
+
ae-cli community get_corpus_tags --space-id 1 --game-id 1
|
|
21
21
|
```
|
|
@@ -1,23 +1,23 @@
|
|
|
1
1
|
# te-community get_daily_summary
|
|
2
2
|
|
|
3
|
-
>
|
|
3
|
+
> **Prerequisite:** Read [`../te-shared/SKILL.md`](../te-shared/SKILL.md)
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
Community daily news for a given day: hot list rankings and selected opinions (positive/negative).
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
Mapping command: `ae-cli community get_daily_summary`
|
|
8
8
|
|
|
9
9
|
## Flags
|
|
10
10
|
|
|
11
|
-
| Flag |
|
|
11
|
+
| Flag | Type | Required | Description |
|
|
12
12
|
|------|------|------|------|
|
|
13
|
-
| `--space-id` | number |
|
|
14
|
-
| `--game-id` | number |
|
|
15
|
-
| `--date` | string |
|
|
13
|
+
| `--space-id` | number | yes | community space ID |
|
|
14
|
+
| `--game-id` | number | yes | game/space ID |
|
|
15
|
+
| `--date` | string | Yes | Date, format yyyy-MM-dd |
|
|
16
16
|
|
|
17
|
-
##
|
|
17
|
+
## Example
|
|
18
18
|
|
|
19
19
|
```bash
|
|
20
|
-
#
|
|
21
|
-
|
|
20
|
+
# Get daily report
|
|
21
|
+
ae-cli community get_daily_summary \
|
|
22
22
|
--space-id 1 --game-id 1 --date 2024-01-01
|
|
23
23
|
```
|
|
@@ -1,26 +1,26 @@
|
|
|
1
1
|
# te-community get_hot_topics
|
|
2
2
|
|
|
3
|
-
>
|
|
3
|
+
> **Prerequisite:** Read [`../te-shared/SKILL.md`](../te-shared/SKILL.md)
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
Ranking of hot topics within a time range.
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
Mapping command: `ae-cli community get_hot_topics`
|
|
8
8
|
|
|
9
9
|
## Flags
|
|
10
10
|
|
|
11
|
-
| Flag |
|
|
11
|
+
| Flag | Type | Required | Description |
|
|
12
12
|
|------|------|------|------|
|
|
13
|
-
| `--space-id` | number |
|
|
14
|
-
| `--game-id` | number |
|
|
15
|
-
| `--start-time` | string |
|
|
16
|
-
| `--end-time` | string |
|
|
17
|
-
| `--order-by` | number |
|
|
13
|
+
| `--space-id` | number | yes | community space ID |
|
|
14
|
+
| `--game-id` | number | yes | game/space ID |
|
|
15
|
+
| `--start-time` | string | No | Topic statistics start time, format yyyy-MM-dd |
|
|
16
|
+
| `--end-time` | string | No | Topic statistics end time, format yyyy-MM-dd |
|
|
17
|
+
| `--order-by` | number | No | Sort: 0 by popularity desc, 1 by start time desc |
|
|
18
18
|
|
|
19
|
-
##
|
|
19
|
+
## Example
|
|
20
20
|
|
|
21
21
|
```bash
|
|
22
|
-
#
|
|
23
|
-
|
|
22
|
+
# Get hot topics
|
|
23
|
+
ae-cli community get_hot_topics \
|
|
24
24
|
--space-id 1 --game-id 1 \
|
|
25
25
|
--start-time 2024-01-01 --end-time 2024-01-07
|
|
26
26
|
```
|
|
@@ -1,23 +1,23 @@
|
|
|
1
1
|
# te-community get_livestream_analysis
|
|
2
2
|
|
|
3
|
-
>
|
|
3
|
+
> **Prerequisite:** Read [`../te-shared/SKILL.md`](../te-shared/SKILL.md)
|
|
4
4
|
|
|
5
|
-
AI
|
|
5
|
+
AI-generated single livestream analysis report: highlight periods (with indicators and AI interpretation) and emotional views.
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
Mapping command: `ae-cli community get_livestream_analysis`
|
|
8
8
|
|
|
9
9
|
## Flags
|
|
10
10
|
|
|
11
|
-
| Flag |
|
|
11
|
+
| Flag | Type | Required | Description |
|
|
12
12
|
|------|------|------|------|
|
|
13
|
-
| `--space-id` | number |
|
|
14
|
-
| `--game-id` | number |
|
|
15
|
-
| `--stream-id` | string |
|
|
13
|
+
| `--space-id` | number | yes | community space ID |
|
|
14
|
+
| `--game-id` | number | yes | game/space ID |
|
|
15
|
+
| `--stream-id` | string | Yes | Livestream session ID, streamId from `get_livestream_list` |
|
|
16
16
|
|
|
17
|
-
##
|
|
17
|
+
## Example
|
|
18
18
|
|
|
19
19
|
```bash
|
|
20
|
-
|
|
20
|
+
ae-cli community get_livestream_analysis \
|
|
21
21
|
--space-id 1 --game-id 1 \
|
|
22
22
|
--stream-id <stream-id>
|
|
23
23
|
```
|