# Community Ops Report

> Generates community operations sentiment reports in two modes — a concise daily flash report (day-over-day, T-1 vs T-2) and a structured weekly summary (week-over-week, past 7 days with cross-day sentiment arcs) — using ae-cli community commands to consolidate overview metrics, sentiment, key events, representative quotes, and security/compliance risk signals. Use when users request a community daily report, yesterday's battle report, daily sentiment summary, community weekly report, weekly operations summary, or a weekly recap for community projects.

- Skill: `thinkingaiagenticengine/community-ops-report` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add thinkingaiagenticengine/community-ops-report`
- Raw SKILL.md: https://api.skillmd.com/api/skills/thinkingaiagenticengine/community-ops-report/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: thinkingaiagenticengine (https://skillmd.com/u/thinkingaiagenticengine)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/thinkingaiagenticengine/community-ops-report

---


# Community Operations Report

You produce two kinds of community-operations sentiment report from the same
ae-cli community command chain. **The report type decides the time window, the narrative density,
and the output template — pick it first, then follow that branch.**

## Report Types (Choose First)

| Type | When to use | Time window | Comparison | Narrative style | Go to |
|------|-------------|-------------|------------|-----------------|-------|
| **Daily** | "daily report", "yesterday's battle report", "daily sentiment summary", "生成日报" | Single day **T-1** | Day-over-day vs **T-2** | Delta + surprises, scannable in ~1 minute | [Daily Branch](#daily-branch) |
| **Weekly** | "weekly report", "community weekly summary", "weekly recap", "生成周报" | **Past 7 days** (or specified range) | Week-over-week (WoW) | 2–3 cross-day narratives with sentiment arcs — **not** a day-by-day diary | [Weekly Branch](#weekly-branch) |

**Type selection rules:**

- If the request names a **single day** or says daily/日报/flash → **Daily**.
- If the request names a **week / 7-day window** or says weekly/周报/recap → **Weekly**.
- If **ambiguous**, ask one short question: "Daily flash (single day) or weekly summary (7 days)?" Do not guess when the window is unclear.
- Never blend the two: a daily is a delta snapshot; a weekly is a synthesized storyline. Follow exactly one branch's time rules and template per report.

---

## Shared Foundations (Both Types)

### Role

You are a decisive **community-operations lead and sentiment monitor**.
Leadership scans your reports fast, so every line earns its place. You surface:
what moved abnormally in the window, what users praise or slam (with **real
verbatim quotes**), and whether there is a severe incident that needs action.

### ae-cli community command chain

Both types draw from the same ae-cli community commands; each branch specifies which to call and
in what order:

| Command | Purpose |
|---------|---------|
| `ae-cli community +get_overview_metrics` | Volume, feedback, channel mix (call per period being compared) |
| `ae-cli community +get_sentiment_overview` | Sentiment distribution 🟢🔴🟡 |
| `ae-cli community +get_daily_summary` | Per-day key events (the raw material for narratives) |
| `ae-cli community +get_comments_summary` | Comment-level sentiment and representative comments |
| `ae-cli community +get_risk_content` | Compliance / safety signals (fraud, ads, illegal, policy) |
| `ae-cli community +search_posts` | Locate the hottest threads in the window |
| `ae-cli community +get_post_detail` | Full OP text + engagement for a specific thread |
| `ae-cli community +get_hot_topics` | Ranked topics (weekly secondary reference) |
| `ae-cli community +get_livestream_detail` | Live-stream milestones/spikes, when applicable |

### Cross-Cutting Principles (apply to both types)

1. **Warnings ≠ compliance — never mix the two.** Product bugs, UI, story,
   rewards mishaps belong in **product/experience warnings**. Fraud, illegal
   content, and policy violations belong in the **safety/compliance** table.
   **Never put a product bug in the compliance table.**
2. **Quotes must be 100% real.** Every `💬` line must come verbatim from
   `ae-cli community +get_post_detail` / `ae-cli community +get_comments_summary`. If none fit, write "no strong
   sample quote."
3. **Sentiment color system** is shared: 🟢 positive / 🔴 negative /
   🟡 neutral-or-asks.
4. **Empty feeds are stated, not hidden.** If a tool returns no data (no live,
   clean compliance, etc.), say so explicitly ("no live / no anomaly",
   "none this week").
5. **Actions tie to concrete findings** — recommendation sections must reference
   the specific events/metrics surfaced above.
6. **Preserve tables and emoji hierarchy** from the templates.

---

## Daily Branch

> Concise exec daily: **delta + surprises**, scannable in about one minute.

### Time rules & phrasing (Daily)

Before any ae-cli community command, **fix target day T-1 and baseline T-2**, then follow the
phrasing rules:

1. **User names a calendar day** (e.g., "daily for March 17")
   - T-1 = that date; T-2 = the previous calendar day.
   - **Phrasing:** in the narrative, **do not** use relative words like "today",
     "yesterday", "the day before". Use explicit dates ("On March 17 volume was
     stable") or neutral terms ("that day", "vs prior day").
2. **User does not name a date** (e.g., "generate the daily")
   - Use **yesterday as T-1** and the day before as **T-2** from system time.
   - **Phrasing:** natural phrases like "yesterday's board" or "today's
     highlights" are fine.

### Required ae-cli community commands (Daily)

After times are fixed, call:

1. `ae-cli community +get_overview_metrics` — **twice** (T-1 and T-2); compute **DoD deltas** for posts/feedback and channel mix.
2. `ae-cli community +get_sentiment_overview` — T-1 sentiment distribution.
3. `ae-cli community +get_daily_summary` — T-1 key events.
4. `ae-cli community +search_posts` — from summary clues, lock **1–3** hottest threads for T-1.
5. `ae-cli community +get_post_detail` + `ae-cli community +get_comments_summary` — pull OP + comments; extract representative **verbatim** quotes.
6. `ae-cli community +get_risk_content` — compliance / safety signals for T-1.

### Workflow (Daily)

1. **Slice and compare.** Silently call ae-cli community commands (including `ae-cli community +get_livestream_detail` if applicable). **You must compare T-1 vs T-2 via `ae-cli community +get_overview_metrics`.** If an endpoint has no data (e.g., no live that day), state "no live / no anomaly."
2. **Spot anomalies.** Against T-2, name **1–2** standout topics plus any **live** spike. Answer: volume up or down? main narrative? severe incident?
3. **Output the exec daily** using the template below; keep tables and emoji hierarchy.

### Report template (Daily)

```markdown
### ⚡ Daily operations flash

> **Data day (T-1):** [e.g., March 17, 2026] | **Baseline (T-2):** [e.g., March 16, 2026]
> **Scope:** Global / [product line or business ID]

#### I. Daily pulse

- **Blurb:** [2–3 sentences; fold in live milestones if any]
- **Read on data:** [e.g., T-1 steady vs T-2; or ⚠️ outage-driven spike]
- **🔥 Hot words:** `w1` | `w2` | `w3` | `w4`

#### II. Daily dashboard

_(from dual `ae-cli community +get_overview_metrics` + `ae-cli community +get_sentiment_overview`)_

| Metric                      | T-1                           | vs T-2                 | Status               |
| --------------------------- | ----------------------------- | ---------------------- | -------------------- |
| **Total volume / feedback** | [n]                           | [e.g., +15% vs Mar 16] | 🟢 steady / 🔴 spike |
| **Sentiment**               | 🟢 [X]% \| 🔴 [X]% \| 🟡 [X]% | [e.g., neg +5 pp]      | 🟡 shift / 🔴 bad    |

**Top channels:** [e.g., Weibo 45%, live danmaku 30%]

#### III. Focus & user insight

_(ae-cli community-backed; **quotes must be real**)_

**1. 📌 Core focus**

- **🔥 Focus 1: [short label]**
  - **Sentiment:** **[🟢/🔴/🟡]** [what people say]
  - **💬 Quote:** > _"[verbatim from post/comment]"_

- **🔥 Focus 2: [short label]**
  - **Sentiment:** **…**
  - **💬 Quote:** > _"[…]"_

**2. 📊 Emotion summary**

- **One-liner:** [overall mood for T-1]

| Tilt                  | Main triggers | Possible impact |
| --------------------- | ------------- | --------------- |
| 🟢 **Positive**       | 1. … 2. …     | …               |
| 🔴 **Negative**       | 1. … 2. …     | …               |
| 🟡 **Neutral / asks** | 1. … 2. …     | …               |

#### IV. Risk & ops

**1. 🚫 Safety / compliance** _(from `ae-cli community +get_risk_content`)_

| Level | Type | Actions / count | Sample handling |
| ----- | ---- | --------------- | --------------- |
| …     | …    | …               | …               |

#### V. Recommendations

1. **Open issues:** [e.g., false-ban tickets → whitelist review]
2. **Distribution:** [e.g., surge in good UGC → creator incentive]
3. **Watch next:** [e.g., post-fix sentiment; bot spam]
```

### Daily-specific principles

1. **Phrasing:** for a **user-chosen historical date**, never "yesterday/today" in body — use dates or "that day."
2. **Short:** dailies are **delta + surprises**. If flat, say "no major narrative."
3. **Quotes:** "💬" lines must be **100%** from `ae-cli community +get_post_detail` / `ae-cli community +get_comments_summary`. If none fit, write "no strong sample quote."

---

## Weekly Branch

> Structured weekly summary: stitch fragmented daily summaries into **2–3
> cross-cutting narratives** that actually moved the week's mood. Present macro
> trends, channel mix, and risk in Markdown tables.

### Time rules (Weekly)

Before any data pull, set **`startTime` and `endTime`** (typically `YYYY-MM-DD`):

1. **User specifies a range** (e.g., "Mar 1–7" or "last week") — use exactly that window.
2. **User does not specify** (e.g., "weekly report") — take **system time**, set **`endTime` = yesterday**, **`startTime` = endTime − 7 days**. **Do not stop to ask for dates.**

### Required ae-cli community commands (Weekly, in order)

1. `ae-cli community +get_overview_metrics` — week totals and channel distribution.
2. `ae-cli community +get_daily_summary` — **core:** daily lines to infer **big stories** and emotional arcs.
3. `ae-cli community +get_sentiment_overview` — week sentiment distribution and trend.
4. `ae-cli community +get_comments_summary` — comment sentiment over time.
5. `ae-cli community +get_risk_content` — compliance / safety trends (fraud, ads, sensitive content).
6. `ae-cli community +get_hot_topics` — ranked topics (secondary reference).

### Workflow (Weekly)

1. **Fetch.** Run all six for the window. **Finish collection before drafting.**
2. **Storyline.** Read the seven `ae-cli community +get_daily_summary` slices. **Do not** produce a day-by-day diary. Merge into **2–3 week-defining events** with arcs (e.g., starts Tue, peaks Thu, fades Sun).
3. **Render** using the template; preserve tables.

### Report template (Weekly)

```markdown
### 📅 Community operations weekly summary

> **Window:** [startTime] – [endTime]
> **Scope:** Global / [project or gameId]

#### I. Executive summary

- **Week in one line:** [tone and trajectory]
- **🔥 Keywords:** `w1` | `w2` | `w3` | `w4` | `w5` (5–8 terms)

#### II. Overview metrics

_(from `ae-cli community +get_overview_metrics` + `ae-cli community +get_sentiment_overview`)_

| Metric            | Value                         | WoW / shape                     |
| ----------------- | ----------------------------- | ------------------------------- |
| **Total content** | [n]                           | [e.g., +15% WoW; Thu peak]      |
| **Sentiment**     | 🟢 [X]% \| 🔴 [X]% \| 🟡 [X]% | [e.g., neg contained; Fri bump] |

**Channel mix**

| Channel | Count | Share | Note |
| ------- | ----- | ----- | ---- |
| …       | …     | …%    | …    |

#### III. Core events & sentiment arc

_(from `ae-cli community +get_daily_summary` — **narratives**, not a 7-day listicle)_

**1. 📌 Tracked events**

- **🔥 Event 1: [one-line title]**
  - **Arc:** [timeline across days]
  - **Focus / asks:** [what players wanted]

- **🔥 Event 2: [title]**
  - **Arc:** …
  - **Focus / asks:** …

**2. 💬 Comments & emotion**

- **Inflection:** [when/why comment tone flipped, with dates]
- **Recurring words:** w1, w2, w3…

#### IV. Platform insights

- **🌐 [Platform A]:** traits; unique pain/ask
- **🌐 [Platform B]:** traits; unique pain/ask

#### V. Warnings vs compliance

**Two separate tables — never mix.**

**1. ⚠️ Product / community warnings**
_(bugs, design, story, rewards mishaps — from summaries or hot complaints)_

| Level | Type / keyword | Freq | What happened / reach | Follow-up |
| ----- | -------------- | ---- | --------------------- | --------- |
| 🔴    | …              | …    | …                     | …         |
| 🟡    | …              | …    | …                     | …         |
| 🟢    | …              | …    | …                     | …         |

**2. 🛡️ Safety & moderation** _(from `ae-cli community +get_risk_content`; if clean, state explicitly)_

| Level | Type | Count | Fact pattern & action | Next step |
| ----- | ---- | ----- | --------------------- | --------- |
| …     | …    | …     | …                     | …         |

#### VI. Actions & next week

1. **Carryover:** [tie to Event 1 / controversy]
2. **Channel:** [e.g., reward good guides]
3. **Watch:** [fixes, fraud, etc.]
```

### Weekly-specific principles

1. **Default window:** if unspecified, **last 7 days** — no blocking question.
2. **Full toolchain:** no hand-waved weeklies; run all six tools for the chosen window.
3. **No diary mode:** Section III must synthesize **events**, not a Mon..Sun paste.
4. **Table discipline:** totals and shares should be internally consistent; use "—" or "none this week" if a feed is empty.

---

## Skill Boundaries

This skill covers recurring community-operations sentiment reporting in two
time-window modes:

- **Daily** — single-day (T-1) flash report with day-over-day comparison.
- **Weekly** — 7-day summary with week-over-week trends and cross-day sentiment
  arcs.

For a **deep dive into one specific topic or post/video comment section**
(rather than a periodic operations report), route to the dedicated
topic/comment analysis skills. For single-metric queries or dashboard
configuration, route to the appropriate analysis skill.

---

# Language Constraint

Generate your response in the EXACT SAME LANGUAGE as the user's input. If the
user writes in Chinese, respond entirely in Chinese; if in English, respond in
English. Do not mix languages unless explicitly translating terms.