@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,124 +1,124 @@
|
|
|
1
1
|
# te-community community-analyzing-theme-comment
|
|
2
2
|
|
|
3
|
-
>
|
|
3
|
+
> **Prerequisite:** Read [`../te-shared/SKILL.md`](../te-shared/SKILL.md)
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
In-depth analysis of topic comment areas: Conduct in-depth analysis of the comment areas of specified posts or videos, and generate an in-depth analysis report including comment trends, opinion distribution, and summary.
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
Trigger scenario: Use this skill when users need to conduct in-depth analysis of the comment area of a specified topic (post or video).
|
|
8
8
|
|
|
9
|
-
##
|
|
9
|
+
## Analysis process
|
|
10
10
|
|
|
11
|
-
1.
|
|
12
|
-
2.
|
|
13
|
-
3.
|
|
14
|
-
4.
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
11
|
+
1. **Identify target post/video**: Get UUID, channelId and resourceType, or search via `search_posts`
|
|
12
|
+
2. **Get comment area data**: Call `get_post_detail` to obtain the target content details and comment area
|
|
13
|
+
3. **Get the complete comment area in paging**: loop through all comments and eliminate meaningless content such as irrigation and pure expressions.
|
|
14
|
+
4. **In-depth analysis**:
|
|
15
|
+
- Comment trend analysis (time trend, sentiment distribution trend)
|
|
16
|
+
- Opinion analysis (extracting positive/negative opinions and representative comments)
|
|
17
|
+
- Summary analysis (market data, opinion analysis, ecological analysis)
|
|
18
18
|
|
|
19
|
-
##
|
|
19
|
+
## Execution process
|
|
20
20
|
|
|
21
|
-
|
|
22
|
-
-
|
|
23
|
-
-
|
|
24
|
-
-
|
|
21
|
+
**Step 1: Identify Target Posts/Videos**
|
|
22
|
+
- Check if the user has explicitly specified the post or video to be analyzed (UUID, channelId, resourceType)
|
|
23
|
+
- If the user has provided the above information, jump directly to step 2
|
|
24
|
+
- If the user does not specify a target, the `search_posts` tool needs to be used to search for suitable posts
|
|
25
25
|
|
|
26
|
-
|
|
27
|
-
-
|
|
28
|
-
-
|
|
29
|
-
-
|
|
30
|
-
-
|
|
26
|
+
**Step 2: Get comment area data**
|
|
27
|
+
- Use the `get_post_detail` tool to get the details and comments section of the target content
|
|
28
|
+
- Get the complete comment area in pagination (pageSize recommended is 100)
|
|
29
|
+
- Check the number of comments and the hasMore field in the returned results
|
|
30
|
+
- If hasMore is true, continue calling to get the next page
|
|
31
31
|
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
-
|
|
35
|
-
-
|
|
36
|
-
-
|
|
37
|
-
-
|
|
32
|
+
**Comment filtering rules**:
|
|
33
|
+
When obtaining and storing comments, the following content that has no analytical significance needs to be eliminated:
|
|
34
|
+
- **Spoiled comments**: Repeated posting of the same or similar content, content that swipes the screen
|
|
35
|
+
- **Pure emoticons/symbols**: Contains only emoticons and symbol combinations (such as "???", "!!!")
|
|
36
|
+
- **No substance**: Comments with less than 3 characters
|
|
37
|
+
- **System Message**: Official automatically generated message
|
|
38
38
|
|
|
39
|
-
|
|
39
|
+
**Step 3: In-depth analysis**
|
|
40
40
|
|
|
41
|
-
**3.1
|
|
42
|
-
-
|
|
43
|
-
-
|
|
41
|
+
**3.1 Comment Trend Analysis**
|
|
42
|
+
- Comment time trend: statistics on the time distribution of comments published, summarized by day
|
|
43
|
+
- Sentiment distribution trend: Statistics on changes in the proportion of positive, neutral, and negative comments by day
|
|
44
44
|
|
|
45
|
-
**3.2
|
|
46
|
-
-
|
|
47
|
-
-
|
|
48
|
-
-
|
|
49
|
-
-
|
|
50
|
-
-
|
|
51
|
-
-
|
|
45
|
+
**3.2 Viewpoint analysis**
|
|
46
|
+
- Text clustering and topic extraction of all valid comments
|
|
47
|
+
- Identify recurring keywords and phrases
|
|
48
|
+
- Merge semantically similar views
|
|
49
|
+
- Differentiate between positive and negative viewpoints
|
|
50
|
+
- Each opinion includes: opinion title, opinion description, number of matching comments, representative comments (up to 10)
|
|
51
|
+
- **Handling Opposing Viewpoints**: Allow diametrically opposed positive and negative views on the same thing to exist, and do not merge opposing views.
|
|
52
52
|
|
|
53
|
-
**3.3
|
|
54
|
-
-
|
|
55
|
-
-
|
|
56
|
-
-
|
|
53
|
+
**3.3 Summary analysis**
|
|
54
|
+
- Summary of market data: total number of comments, overall sentiment distribution, peak comment time
|
|
55
|
+
- Summary of opinion analysis: main positive opinions, main negative opinions, points of conflict of opinions, core needs of players
|
|
56
|
+
- Ecological analysis of the comment area: overall atmosphere, relevance of comments and content, core user group characteristics, potential risks and opportunities
|
|
57
57
|
|
|
58
|
-
##
|
|
58
|
+
## Output structure (must be complete)
|
|
59
59
|
|
|
60
|
-
###
|
|
61
|
-
-
|
|
62
|
-
-
|
|
63
|
-
-
|
|
64
|
-
-
|
|
65
|
-
-
|
|
60
|
+
### 1. Basic information
|
|
61
|
+
- **Post/Video Title**: Title content
|
|
62
|
+
- **Source Channel**: Channel name
|
|
63
|
+
- **Published**: Release date
|
|
64
|
+
- **Analysis Time Range**: The time period for analysis
|
|
65
|
+
- **Number of valid comments**: The number after excluding invalid comments
|
|
66
66
|
|
|
67
|
-
###
|
|
67
|
+
### 2. Comment trends
|
|
68
68
|
|
|
69
|
-
|
|
69
|
+
**Time Trend**
|
|
70
70
|
|
|
71
|
-
|
|
|
71
|
+
| Date | Number of comments | Percentage |
|
|
72
72
|
|------|--------|------|
|
|
73
|
-
| YYYY-MM-DD |
|
|
73
|
+
| YYYY-MM-DD | Quantity | X% |
|
|
74
74
|
|
|
75
|
-
|
|
75
|
+
**Emotion Distribution**
|
|
76
76
|
|
|
77
|
-
|
|
|
77
|
+
| Date | Positive | Neutral | Negative |
|
|
78
78
|
|------|------|------|------|
|
|
79
79
|
| YYYY-MM-DD | X% | X% | X% |
|
|
80
80
|
|
|
81
|
-
###
|
|
81
|
+
### 3. Viewpoint analysis
|
|
82
82
|
|
|
83
|
-
|
|
83
|
+
**Positive View**
|
|
84
84
|
|
|
85
|
-
|
|
86
|
-
-
|
|
87
|
-
-
|
|
88
|
-
-
|
|
89
|
-
|
|
90
|
-
|
|
85
|
+
**Viewpoint 1: [Viewpoint Title]**
|
|
86
|
+
- **Viewpoint Description**: [Detailed Description]
|
|
87
|
+
- **Number of matching comments**: X
|
|
88
|
+
- **Representative comments**:
|
|
89
|
+
- "[Comment 1]"
|
|
90
|
+
- "[Comment 2]"
|
|
91
91
|
|
|
92
|
-
|
|
92
|
+
**Negative opinions (can be multiple)**
|
|
93
93
|
|
|
94
|
-
|
|
95
|
-
-
|
|
96
|
-
-
|
|
97
|
-
-
|
|
98
|
-
|
|
99
|
-
|
|
94
|
+
**Viewpoint 1: [Viewpoint Title]**
|
|
95
|
+
- **Viewpoint Description**: [Detailed Description]
|
|
96
|
+
- **Number of matching comments**: X
|
|
97
|
+
- **Representative comments**:
|
|
98
|
+
- "[Comment 1]"
|
|
99
|
+
- "[Comment 2]"
|
|
100
100
|
|
|
101
|
-
###
|
|
101
|
+
### 4. Summary
|
|
102
102
|
|
|
103
|
-
|
|
104
|
-
-
|
|
103
|
+
**Broad market data summary**:
|
|
104
|
+
- Total number of comments, overall sentiment distribution, peak comment time
|
|
105
105
|
|
|
106
|
-
|
|
107
|
-
-
|
|
108
|
-
-
|
|
109
|
-
-
|
|
110
|
-
-
|
|
106
|
+
**Summary of opinion analysis**:
|
|
107
|
+
- Mainly positive points
|
|
108
|
+
- Mainly negative points
|
|
109
|
+
- Points of conflict of opinions
|
|
110
|
+
- Players’ core needs
|
|
111
111
|
|
|
112
|
-
|
|
113
|
-
-
|
|
114
|
-
-
|
|
115
|
-
-
|
|
116
|
-
-
|
|
112
|
+
**Ecological Analysis and Suggestions**:
|
|
113
|
+
- Overall atmosphere
|
|
114
|
+
- Relevance of comments and content
|
|
115
|
+
- Characteristics of core user groups
|
|
116
|
+
-Potential risks and opportunities
|
|
117
117
|
|
|
118
|
-
##
|
|
118
|
+
## Example
|
|
119
119
|
|
|
120
120
|
```bash
|
|
121
|
-
#
|
|
122
|
-
"
|
|
123
|
-
"
|
|
121
|
+
# User input example
|
|
122
|
+
"Analyze the comment area of this post"
|
|
123
|
+
"Help me deeply analyze the user feedback of this video"
|
|
124
124
|
```
|
|
@@ -1,71 +1,71 @@
|
|
|
1
1
|
# te-community community-character-analysis
|
|
2
2
|
|
|
3
|
-
>
|
|
3
|
+
> **Prerequisite:** Read [`../te-shared/SKILL.md`](../te-shared/SKILL.md)
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
Role-specific in-depth analysis: In-depth diagnosis for a single role, instead of regular daily/weekly reports, the "Role-specific in-depth analysis report" is output.
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
Trigger: Use this when the user asks for "in-depth analysis of a certain character", "character sentiment insight", "deep-dive analysis of of a certain character's discussion", and "character analysis".
|
|
8
8
|
|
|
9
|
-
##
|
|
9
|
+
## Analysis process
|
|
10
10
|
|
|
11
|
-
1. **`get_sentiment_overview
|
|
12
|
-
2. **`get_hot_topics
|
|
13
|
-
3. **`search_posts
|
|
14
|
-
4. **`get_post_detail` & `get_comments_summary
|
|
11
|
+
1. **`get_sentiment_overview`**: Get the core word cloud of the character under positive and negative discussions to set the tone of the current overall reputation
|
|
12
|
+
2. **`get_hot_topics`**: Confirm whether the character has formed a hot topic in the community
|
|
13
|
+
3. **`search_posts`**: Search for recent hot posts using "character name + core controversial words"
|
|
14
|
+
4. **`get_post_detail` & `get_comments_summary`**: Extract the core views of the post and emotional feedback in the comment area
|
|
15
15
|
|
|
16
|
-
##
|
|
16
|
+
## Entity extraction and deduction rules
|
|
17
17
|
|
|
18
|
-
-
|
|
19
|
-
-
|
|
20
|
-
-
|
|
18
|
+
- [Core Analysis Role] must be extracted from user input (such as "Role", "Role A")
|
|
19
|
+
- If the user doesn't say anything, please clearly ask "Which character do you want to analyze in depth?"
|
|
20
|
+
- If the user does not specify a time, **automatically push forward 7-14 days from the current system time as the query period**
|
|
21
21
|
|
|
22
|
-
##
|
|
22
|
+
## Core Constraints
|
|
23
23
|
|
|
24
|
-
-
|
|
25
|
-
-
|
|
26
|
-
|
|
27
|
-
|
|
24
|
+
- **Reject fake claims**: Must explain "why" and give evidence of posts/comments.
|
|
25
|
+
- **Strictly distinguish between early warning and risk control**:
|
|
26
|
+
- Alerts: experience risks (mechanics, numerical values, plot, art, performance)
|
|
27
|
+
-Risk Control: risk of violation (causing war, illegal production, leakage, rumors)
|
|
28
28
|
|
|
29
|
-
##
|
|
29
|
+
## Output structure
|
|
30
30
|
|
|
31
|
-
###
|
|
32
|
-
|
|
31
|
+
### 1. Character’s current ecology and community impression
|
|
32
|
+
Use a very insightful paragraph to summarize the character’s current true position in the player’s mind.
|
|
33
33
|
|
|
34
|
-
###
|
|
34
|
+
### 2. Discussion popularity and emotional portrait matrix
|
|
35
35
|
|
|
36
|
-
|
|
|
36
|
+
| Dimensions | Data/Description |
|
|
37
37
|
|------|----------|
|
|
38
|
-
|
|
|
39
|
-
|
|
|
40
|
-
|
|
|
38
|
+
| Emotional fundamentals | Positive/neutral/negative ratio |
|
|
39
|
+
| Main forum for sentiment | Main discussion channel |
|
|
40
|
+
| High frequency word co-occurrence | Core keywords |
|
|
41
41
|
|
|
42
|
-
###
|
|
42
|
+
### 3. In-depth deep-dive analysis of of players’ core needs and focus
|
|
43
43
|
|
|
44
|
-
**✨
|
|
45
|
-
-
|
|
46
|
-
-
|
|
44
|
+
**✨ Core Values and Highlight Experience**
|
|
45
|
+
- **Extraction of player voices**: [Summary]
|
|
46
|
+
- **Typical original voice/support case**: "[Real comments]"
|
|
47
47
|
|
|
48
|
-
**🧨
|
|
49
|
-
-
|
|
50
|
-
-
|
|
48
|
+
**🧨 Analysis of core pain points**
|
|
49
|
+
- **Dismantling of deep demands**: [Analysis]
|
|
50
|
+
- **Typical original voice/support case**: "[Real comments]"
|
|
51
51
|
|
|
52
|
-
###
|
|
53
|
-
-
|
|
54
|
-
-
|
|
52
|
+
### 4. Operation strategy
|
|
53
|
+
- **Public Opinion Direction Guidance**: Specific Suggestions
|
|
54
|
+
- **Version/Optimization Forward Planning**: Direction for improvement
|
|
55
55
|
|
|
56
|
-
###
|
|
56
|
+
### 5. Warning content
|
|
57
57
|
|
|
58
|
-
**⚠️
|
|
58
|
+
**⚠️ Warning content**
|
|
59
59
|
|
|
60
|
-
|
|
|
60
|
+
| Danger level | Warning triggers | Community spread | Core performance | Suggested follow-up actions |
|
|
61
61
|
|---------|-----------|-----------|---------|-------------|
|
|
62
|
-
|
|
|
62
|
+
| High/medium/low | Specific problems | Scope of impact | Specific performance | Handling suggestions |
|
|
63
63
|
|
|
64
|
-
##
|
|
64
|
+
## Example
|
|
65
65
|
|
|
66
66
|
```bash
|
|
67
|
-
#
|
|
68
|
-
"
|
|
69
|
-
"
|
|
70
|
-
"
|
|
67
|
+
# User input example
|
|
68
|
+
"A deep analysis of the role"
|
|
69
|
+
"Help me break down the discussion of character A"
|
|
70
|
+
"Analyze the sentiment of XX character"
|
|
71
71
|
```
|
|
@@ -1,82 +1,85 @@
|
|
|
1
1
|
# te-community community-daily-report
|
|
2
2
|
|
|
3
|
-
>
|
|
3
|
+
> **Prerequisite:** Read [`../te-shared/SKILL.md`](../te-shared/SKILL.md)
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
Daily brief: Generate a concise "User Operations Daily Brief" covering daily macro trends, breaking sentiment signals, and safety/compliance risks, with T-1 vs T-2 comparison.
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
Trigger: Use this when the user asks for "generate daily report", "yesterday's battle report" or "daily sentiment summary".
|
|
8
8
|
|
|
9
|
-
##
|
|
9
|
+
## Roles and Goals
|
|
10
10
|
|
|
11
|
-
|
|
12
|
-
2
|
|
13
|
-
- `get_overview_metrics`(两次):获取 T-1 和 T-2 的发帖/反馈总数,计算环比涨跌幅
|
|
14
|
-
- `get_sentiment_overview`:获取目标日情感分布
|
|
15
|
-
- `get_daily_summary`:获取目标日核心事件摘要
|
|
16
|
-
- `search_posts`:搜索目标日高热度话题原帖
|
|
17
|
-
- `get_post_detail` + `get_comments_summary`:提取真实用户原话
|
|
18
|
-
- `get_risk_content`:获取安全合规风控数据
|
|
11
|
+
You are the "User Operations Director + Public Opinion Monitoring Expert". The core task is to quickly answer three things:
|
|
12
|
+
1) Whether the overall trend on the target date rose or fell relative to the previous day; 2) What is the most important focus of sentiment on the day; 3) Are there any risks that need to be dealt with immediately?
|
|
19
13
|
|
|
20
|
-
##
|
|
14
|
+
## Time deduction and speech rules
|
|
21
15
|
|
|
22
|
-
1.
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
2.
|
|
26
|
-
|
|
27
|
-
|
|
16
|
+
1. **The user clearly specifies the date** (for example: "Publish the daily report on March 17"):
|
|
17
|
+
- The target date is the specified date, and the comparison date is automatically calculated as the previous day.
|
|
18
|
+
- **Red line of speech**: In the text of the report, relative time pronouns such as "today", "yesterday" and "the day before yesterday" are absolutely prohibited**, and specific dates or objective pronouns must be used (such as: "Surge in volume on that day", "Compared to the previous day")
|
|
19
|
+
2. **The user did not explicitly specify the date** (such as only saying "generate daily report"):
|
|
20
|
+
- Automatically use yesterday as the target day (T-1) and the day before yesterday as the comparison day (T-2)
|
|
21
|
+
- Allows the use of relative terms such as "yesterday/today's highlights"
|
|
28
22
|
|
|
29
|
-
##
|
|
23
|
+
## Required tool chain
|
|
30
24
|
|
|
31
|
-
-
|
|
32
|
-
|
|
33
|
-
|
|
25
|
+
1. `get_overview_metrics` (called twice: T-1 and T-2)
|
|
26
|
+
2. `get_sentiment_overview` (target day sentiment distribution)
|
|
27
|
+
3. `get_daily_summary` (target day event summary)
|
|
28
|
+
4. `search_posts` (locating core hot posts)
|
|
29
|
+
5. `get_post_detail` + `get_comments_summary` (extract the real original sound)
|
|
30
|
+
6. `get_risk_content` (compliance risk)
|
|
34
31
|
|
|
35
|
-
##
|
|
32
|
+
## Core Constraints
|
|
36
33
|
|
|
37
|
-
|
|
38
|
-
-
|
|
39
|
-
-
|
|
40
|
-
- **当日热词**:高频关键词
|
|
34
|
+
- **Minimalism, rejecting long forms**: focus on describing "incremental information" and "sudden anomalies"
|
|
35
|
+
- **Absolute isolation of early warning and risk control**: Product bugs, UI complaints, and event feedback are classified as "Business Experience"; illegal products, politics, pornography, gambling and drugs, and illegal advertising are written into "Compliance Risk Control"
|
|
36
|
+
- **The original voice of the user is absolutely authentic**: it must be 100% derived from real text, **It is absolutely prohibited to fabricate or conjecture what the user said**
|
|
41
37
|
|
|
42
|
-
|
|
38
|
+
## Output structure
|
|
43
39
|
|
|
44
|
-
|
|
40
|
+
### 1. Core Overview
|
|
41
|
+
- **Summary Overview**: Summarize the core events of the day in one sentence
|
|
42
|
+
- **Data Overview**: Month-on-month changes in key indicators
|
|
43
|
+
- **Hot words of the day**: high-frequency keywords
|
|
44
|
+
|
|
45
|
+
### 2. Single-day core dashboard
|
|
46
|
+
|
|
47
|
+
| Indicator categories | Data | Month-on-month changes |
|
|
45
48
|
|---------|------|---------|
|
|
46
|
-
|
|
|
47
|
-
|
|
|
48
|
-
|
|
|
49
|
+
| Total sound volume of the market | Specific value | ↑/↓ X% |
|
|
50
|
+
| Sentiment of the day | Positive/neutral/negative proportion | Changing trends |
|
|
51
|
+
| Main volume position | Distribution of various channels | Channel comparison |
|
|
49
52
|
|
|
50
|
-
###
|
|
53
|
+
### 3. Core Focus and User Insights
|
|
51
54
|
|
|
52
|
-
|
|
53
|
-
-
|
|
54
|
-
|
|
55
|
-
|
|
55
|
+
**Core Focus**:
|
|
56
|
+
- Focus 1: [Event Description]
|
|
57
|
+
- **User Feedback**: [Feedback Summary]
|
|
58
|
+
- **Typical original voice**: "[Real user comments]"
|
|
56
59
|
|
|
57
|
-
|
|
60
|
+
**User Sentiment Summary**
|
|
58
61
|
|
|
59
|
-
|
|
|
62
|
+
| Emotional Tendencies | Main Trigger Points | Possible Impact |
|
|
60
63
|
|---------|-----------|-----------|
|
|
61
|
-
|
|
|
64
|
+
| Positive/Negative/Neutral | Specific reasons | Impact analysis |
|
|
62
65
|
|
|
63
|
-
###
|
|
66
|
+
### 4. Risk control tips and operational suggestions
|
|
64
67
|
|
|
65
|
-
|
|
68
|
+
**Safety Compliance Risk Control**
|
|
66
69
|
|
|
67
|
-
|
|
|
70
|
+
| Risk control type | Number of findings | Main performance | Disposal suggestions |
|
|
68
71
|
|---------|---------|---------|---------|
|
|
69
|
-
|
|
|
72
|
+
| Specific type | Quantity | Specific performance | Treatment suggestions |
|
|
70
73
|
|
|
71
|
-
###
|
|
72
|
-
-
|
|
73
|
-
-
|
|
74
|
+
### 5. Operation suggestions and future node suggestions
|
|
75
|
+
- short term advice
|
|
76
|
+
- Mid- to long-term focus
|
|
74
77
|
|
|
75
|
-
##
|
|
78
|
+
## Example
|
|
76
79
|
|
|
77
80
|
```bash
|
|
78
|
-
#
|
|
79
|
-
"
|
|
80
|
-
"
|
|
81
|
-
"
|
|
81
|
+
# User input example
|
|
82
|
+
"Generate daily report"
|
|
83
|
+
"Publish the daily report for March 17th"
|
|
84
|
+
"Yesterday's Battle Report"
|
|
82
85
|
```
|