@thinkingai/ae-cli 6.1.28 → 6.1.30

package/skills/ae-community/references/community-scenario-capabilities.md

@@ -0,0 +1,137 @@
+# Community Scenario Capabilities
+
+Use this reference when the user needs a workflow that is not covered by one legacy curated
+`community +...` command. The capabilities below are Gateway L3 unless explicitly shown as an L1/L2
+command. Always discover and inspect the live capability before constructing input:
+
+```bash
+ae-cli capability search "<user intent>" --domain community
+ae-cli capability inspect <capability-id>
+ae-cli capability validate <capability-id> --input '<json>'
+ae-cli capability run <capability-id> --input '<json>'
+```
+
+Use either `validate` or `dry-run` while correcting input; do not run both by default. Copy every
+int64 ID exactly and keep it as a JSON integer or quoted string accepted by the inspected schema.
+
+## Admission decisions
+
+| Candidate area | Decision | Reason |
+|---|---|---|
+| Bounded full-text evidence | L1: `community evidence fetch` | Deduplicates up to 20 real locators, verifies response identity, and reports a text budget and per-item failures. |
+| Space and source discovery | L2: `community spaces list`, `community sources list` | They remove ID guessing and close the reporting prerequisite chain with typed int64 flags. |
+| Comments, workbench, visual analysis, tag/hotspot/risk/keyword queries | L3 capabilities | They have stable read contracts, but a static alias would add no value beyond discovery and schema inspection. |
+| Comment image evidence | Reuse `community.content.post_detail` | Images belong to the post/video evidence contract; the independent comment result has no stable comment-image field. |
+| Livestream report status | Reuse `community.content.livestream_analysis` | Its `status` is already the authoritative state: `0` processing, `1` finished, `2` ready, `3` error. |
+| Tag refresh, report generation, keyword/risk/alert mutations | Do not add yet | The analysis workflows do not require mutation, and these writes do not yet have a stable Gateway dry-run contract. |
+| Dedicated chat permission | Do not invent | No deployed chat-specific Apollo permission function exists. Trust the inspected capability metadata and never claim dedicated isolation. |
+
+## Foundation: space, source, and channel IDs
+
+```bash
+ae-cli community spaces list
+ae-cli community sources list --space-id <space-id>
+ae-cli community +get_channel_info --space-id <space-id>
+```
+
+Use `community.space.get` only after selecting a space and when its metadata is needed. The L2
+`community sources list` command is backed by `community.source.list`. Source discovery requires
+data-configuration view permission; a permission error is not evidence that no sources exist.
+
+## Workbench and saved reports
+
+Use this chain for “what reports exist?”, “show the preset metric”, or “inspect this saved report”:
+
+1. `community.dashboard.preset_catalog` discovers the eight stable preset keys.
+2. `community.dashboard.preset_report` runs one preset for a date range and optional channels.
+3. `community.visual.report_list` searches saved visual reports.
+4. `community.visual.report_detail` returns the selected report's graph shape and saved config.
+
+Do not treat the preset catalog as current dashboard layout. It is a side-effect-free catalog; it
+does not initialize or modify dashboard state.
+
+## Post and comment evidence closure
+
+Use this sequence when a summary must be supported by raw discussion evidence:
+
+1. `community.content.search_posts` finds candidate posts or videos.
+2. `community.content.post_detail` returns the subject, media/image evidence, tags, and initial comments.
+3. `community.content.list_comments` independently pages a flat comment list with stable reply/root identifiers; it does not return a complete reply tree.
+4. Apply its date, sentiment, and `tag_filters` fields to narrow the evidence set.
+5. Use `community.content.comments_summary` and `community.content.comment_tag_analysis` for aggregates.
+
+Never claim that `list_comments` returns comment-level images. Cite post/video images from
+`post_detail`, and cite flat comment text and returned stable comment IDs from `list_comments`.
+
+## Livestream chain
+
+1. Discover rooms with `community.content.livestream_rooms`.
+2. List sessions with `community.content.livestream_list`, then inspect a session with
+   `community.content.livestream_detail`.
+3. Use `community.live.follower_trend` for daily room follower changes.
+4. Use `community.content.livestream_analysis` for both the AI report and generation status.
+
+If report status is `2` (`ready`), report that generation has not started. Do not trigger report
+generation automatically; no stable read-only capability performs that write.
+
+## Chat chain
+
+The detailed identity and service-metric safeguards remain in `community-chat-analysis.md`.
+Additional discovery routes are:
+
+- `community.chat.top_keywords` for an explicit ranked keyword list;
+- `community.chat.list_intent_rules` for configured intent meanings;
+- `community.chat.list_servers` for server discovery before segmented comparisons.
+
+Do not infer a server-by-room-type result from `list_servers`, and do not calculate service KPIs
+without the complete staff roster required by the chat workflow.
+
+## Metadata-driven visual analysis
+
+Use this strict order:
+
+1. `community.visual.metadata` returns supported filters, dimension properties, metrics, and static quotas.
+2. `community.visual.filter_values` discovers actual values for a selected metadata field and date range.
+3. Build `community.visual.analysis` input only from returned metadata. Include at least one `quotas`
+   or `formulas` item.
+4. Preserve the exact query and the raw axis `value` fields from the result.
+5. Pass that query and selected raw values to `community.visual.drilldown` to retrieve source content.
+
+Never invent `column_name`, `table_type`, calculation symbols, metric codes, group definitions, or
+formula aliases. Labels are for presentation; drill-down uses raw axis values.
+
+## Tag definition and refresh plan
+
+Start from `community.content.corpus_tags`, select a real `tagId`, then call
+`community.tag.detail` with both `game_id` and `tag_id`. The result contains the rule definition,
+corpus range, `refreshStatus`, refresh type/interval/hour, and update timestamps. The capability
+rejects a tag that belongs to a different space.
+
+This is inspection only. Do not promise that a refresh was scheduled or run.
+
+## Daily summary and topic evidence
+
+1. `community.hot.summary_dates` discovers dates that actually have summaries.
+2. `community.hot.daily_summary` returns the selected day's ranked hotspots and opinions.
+3. `community.hot.hotspot_evidence` pages the source content behind one `hotspotId`.
+4. `community.hot.topic_detail` gives topic aggregates.
+5. `community.hot.topic_resources` closes the topic-to-content evidence loop for a selected date range.
+
+Use available dates instead of repeatedly guessing dates with no generated summary.
+
+## Risk configuration inspection
+
+Use `community.risk.type_catalog` to discover supported rule templates, then
+`community.risk.rules` for space-specific rules and `community.risk.alerts` for alert configuration.
+Use `community.content.risk_content` only after that discovery when the user needs matching risky
+content and trends. Keep rule configuration separate from detected content.
+
+## Keyword discovery
+
+`community.keyword.groups` lists configured main/sub-keyword relationships.
+`community.keyword.ranking` returns high-frequency unmerged keywords for a date range. These are
+read-only inspection abilities, not management writes; never claim a keyword or group was changed.
+
+## Query and evidence quality
+
+See [community-query-evidence.md](community-query-evidence.md) for the query contract, A100-only contributor drill-down, cumulative interaction semantics, and bounded evidence command. Do not treat formula base content as numerator evidence or assume that a result has a snapshot.

package/skills/ae-community/references/community-weekly-report.md

@@ -12,8 +12,9 @@ You are "Director of Community Operations + Senior Data Analyst". The goal is no
 ## Time deduction rules
 
 1. The user clearly gives the date: query strictly according to the user scope.
-2. The user does not provide a date: automatically retrieve the past 7 days (`endTime=yesterday`, `startTime=endTime-7d`).
-3. Don’t interrupt the process due to lack of time.
+2. The user does not provide a date: automatically retrieve the past 7 days (`endTime=yesterday`, `startTime=endTime-6d`).
+3. These bounds include both dates: state the exact seven calendar days and service timezone. Use the preceding seven days for an equal-length comparison. Missing or failed data is unknown, never zero.
+4. For filtered questions, use the same effective visual query for all comparisons and evidence. An unfiltered overview is not the denominator of a filtered search.
 
 ## Required tool chain
 
@@ -24,7 +25,9 @@ You are "Director of Community Operations + Senior Data Analyst". The goal is no
 5. `+get_risk_content` (compliance risk control)
 6. `+get_hot_topics` (hotspot assisted verification)
 
-## Output structure (must be complete)
+## Output structure
+
+Mark unsupported or unavailable sections explicitly. Never invent results to fill this template.
 
 1. **Core summary of the report**: Setting the tone for this week + hot keywords
 2. **Overview indicator board**: total volume, sentiment distribution, channel matrix (table)

package/skills/ae-community/references/get_channel_info.md

@@ -1,7 +1,7 @@
 # ae-community +get_channel_info
 
 
-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).
+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, then call `+search_posts`, `+get_post_detail`, `+get_comments_summary`, `+get_livestream_list`, etc. If the space ID is unknown, run `ae-cli community spaces list` first.
 
 Mapping command: `ae-cli community +get_channel_info`
 
@@ -9,12 +9,15 @@ Mapping command: `ae-cli community +get_channel_info`
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--space-id` | number | yes | community space ID |
-| `--game-id` | number | yes | game/space ID |
+| `--space-id` | int64 | yes | Community space ID returned by `community spaces list` |
+| `--game-id` | int64 | no | Deprecated compatibility alias; omit it, or make it equal to `--space-id` |
 
 ## Example
 
 ```bash
 # Get channel list
-ae-cli community +get_channel_info --space-id 1 --game-id 1
+ae-cli community +get_channel_info --space-id 1
 ```
+
+Copy returned channel IDs exactly. JSON output preserves IDs outside JavaScript's safe integer range
+as strings.

package/skills/ae-community/references/get_comment_tag_analysis.md

@@ -9,8 +9,8 @@ Mapping command: `ae-cli community +get_comment_tag_analysis`
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--space-id` | number | yes | community space ID |
-| `--game-id` | number | yes | game/space ID |
+| `--space-id` | int64 | yes | Community space ID returned by `community spaces list` |
+| `--game-id` | int64 | no | Deprecated compatibility alias; omit it, or make it equal to `--space-id` |
 | `--channel-id` | number | yes | channel ID |
 | `--uuid` | string | yes | content UUID |
 | `--resource-type` | number | Yes | Resource type: `0` for posts, `1` for videos |
@@ -23,7 +23,7 @@ Mapping command: `ae-cli community +get_comment_tag_analysis`
 ```bash
 # Analyze comment tags
 ae-cli community +get_comment_tag_analysis \
-  --space-id 1 --game-id 1 \
+  --space-id 1 \
   --channel-id 1 --uuid <uuid> \
   --resource-type 0 --tag-code "sentiment"
 ```

package/skills/ae-community/references/get_comments_summary.md

@@ -9,8 +9,8 @@ Mapping command: `ae-cli community +get_comments_summary`
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--space-id` | number | yes | community space ID |
-| `--game-id` | number | yes | game/space ID |
+| `--space-id` | int64 | yes | Community space ID returned by `community spaces list` |
+| `--game-id` | int64 | no | Deprecated compatibility alias; omit it, or make it equal to `--space-id` |
 | `--channel-id` | number | yes | channel ID |
 | `--uuid` | string | yes | content UUID |
 | `--start-time` | string | No | Earliest comment publish date, format yyyy-MM-dd, default is the publishing time of the post |
@@ -21,12 +21,12 @@ Mapping command: `ae-cli community +get_comments_summary`
 ```bash
 # Get comment summary
 ae-cli community +get_comments_summary \
-  --space-id 1 --game-id 1 \
+  --space-id 1 \
   --channel-id 1 --uuid <uuid>
 
 #Specify time range
 ae-cli community +get_comments_summary \
-  --space-id 1 --game-id 1 \
+  --space-id 1 \
   --channel-id 1 --uuid <uuid> \
   --start-time 2024-01-01 --end-time 2024-01-07
 ```

package/skills/ae-community/references/get_corpus_tags.md

@@ -9,12 +9,12 @@ Mapping command: `ae-cli community +get_corpus_tags`
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--space-id` | number | yes | community space ID |
-| `--game-id` | number | yes | game/space ID |
+| `--space-id` | int64 | yes | Community space ID returned by `community spaces list` |
+| `--game-id` | int64 | no | Deprecated compatibility alias; omit it, or make it equal to `--space-id` |
 
 ## Example
 
 ```bash
 # Get the tag list
-ae-cli community +get_corpus_tags --space-id 1 --game-id 1
+ae-cli community +get_corpus_tags --space-id 1
 ```

package/skills/ae-community/references/get_daily_summary.md

@@ -9,8 +9,8 @@ Mapping command: `ae-cli community +get_daily_summary`
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--space-id` | number | yes | community space ID |
-| `--game-id` | number | yes | game/space ID |
+| `--space-id` | int64 | yes | Community space ID returned by `community spaces list` |
+| `--game-id` | int64 | no | Deprecated compatibility alias; omit it, or make it equal to `--space-id` |
 | `--date` | string | Yes | Date, format yyyy-MM-dd |
 
 ## Example
@@ -18,5 +18,5 @@ Mapping command: `ae-cli community +get_daily_summary`
 ```bash
 # Get daily report
 ae-cli community +get_daily_summary \
-  --space-id 1 --game-id 1 --date 2024-01-01
+  --space-id 1 --date 2024-01-01
 ```

package/skills/ae-community/references/get_hot_topics.md

@@ -9,8 +9,8 @@ Mapping command: `ae-cli community +get_hot_topics`
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--space-id` | number | yes | community space ID |
-| `--game-id` | number | yes | game/space ID |
+| `--space-id` | int64 | yes | Community space ID returned by `community spaces list` |
+| `--game-id` | int64 | no | Deprecated compatibility alias; omit it, or make it equal to `--space-id` |
 | `--start-time` | string | No | Topic statistics start time, format yyyy-MM-dd |
 | `--end-time` | string | No | Topic statistics end time, format yyyy-MM-dd |
 | `--order-by` | number | No | Sort: 0 by popularity desc, 1 by start time desc |
@@ -20,6 +20,6 @@ Mapping command: `ae-cli community +get_hot_topics`
 ```bash
 # Get hot topics
 ae-cli community +get_hot_topics \
-  --space-id 1 --game-id 1 \
+  --space-id 1 \
   --start-time 2024-01-01 --end-time 2024-01-07
 ```

package/skills/ae-community/references/get_livestream_analysis.md

@@ -9,14 +9,14 @@ Mapping command: `ae-cli community +get_livestream_analysis`
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--space-id` | number | yes | community space ID |
-| `--game-id` | number | yes | game/space ID |
+| `--space-id` | int64 | yes | Community space ID returned by `community spaces list` |
+| `--game-id` | int64 | no | Deprecated compatibility alias; omit it, or make it equal to `--space-id` |
 | `--stream-id` | string | Yes | Livestream session ID, streamId from `get_livestream_list` |
 
 ## Example
 
 ```bash
 ae-cli community +get_livestream_analysis \
-  --space-id 1 --game-id 1 \
+  --space-id 1 \
   --stream-id <stream-id>
 ```

package/skills/ae-community/references/get_livestream_detail.md

@@ -9,8 +9,8 @@ Mapping command: `ae-cli community +get_livestream_detail`
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--space-id` | number | yes | community space ID |
-| `--game-id` | number | yes | game/space ID |
+| `--space-id` | int64 | yes | Community space ID returned by `community spaces list` |
+| `--game-id` | int64 | no | Deprecated compatibility alias; omit it, or make it equal to `--space-id` |
 | `--stream-id` | string | Yes | Live session ID, obtained from get_livestream_list |
 | `--activity-types` | string | No | Interaction type filtering: 0 danmaku, 1 gift, 2 eye-catching message, 3 premium, comma separated |
 | `--anchor-time` | string | No | Interaction anchor time, format yyyy-MM-dd HH:mm |
@@ -24,10 +24,10 @@ Mapping command: `ae-cli community +get_livestream_detail`
 ```bash
 # Get livestream details
 ae-cli community +get_livestream_detail \
-  --space-id 1 --game-id 1 --stream-id <stream-id>
+  --space-id 1 --stream-id <stream-id>
 
 # Filter danmaku types
 ae-cli community +get_livestream_detail \
-  --space-id 1 --game-id 1 --stream-id <stream-id> \
+  --space-id 1 --stream-id <stream-id> \
   --activity-types 0,1
 ```

package/skills/ae-community/references/get_livestream_list.md

@@ -9,8 +9,8 @@ Mapping command: `ae-cli community +get_livestream_list`
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--space-id` | number | yes | community space ID |
-| `--game-id` | number | yes | game/space ID |
+| `--space-id` | int64 | yes | Community space ID returned by `community spaces list` |
+| `--game-id` | int64 | no | Deprecated compatibility alias; omit it, or make it equal to `--space-id` |
 | `--channel-id` | number | no | Channel ID (obtain via `get_livestream_rooms`) |
 | `--room-id` | string | No | Room ID (obtain via `get_livestream_rooms`) |
 | `--start-time` | string | No | Start date for statistics, format yyyy-MM-dd |
@@ -21,5 +21,5 @@ Mapping command: `ae-cli community +get_livestream_list`
 ```bash
 # Get the livestream session list
 ae-cli community +get_livestream_list \
-  --space-id 1 --game-id 1 --channel-id 1
+  --space-id 1 --channel-id 1
 ```

package/skills/ae-community/references/get_livestream_overview.md

@@ -9,8 +9,8 @@ Mapping command: `ae-cli community +get_livestream_overview`
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--space-id` | number | yes | community space ID |
-| `--game-id` | number | yes | game/space ID |
+| `--space-id` | int64 | yes | Community space ID returned by `community spaces list` |
+| `--game-id` | int64 | no | Deprecated compatibility alias; omit it, or make it equal to `--space-id` |
 | `--start-time` | string | No | Start date for statistics, format yyyy-MM-dd |
 | `--end-time` | string | No | End date for statistics, format yyyy-MM-dd |
 
@@ -19,6 +19,6 @@ Mapping command: `ae-cli community +get_livestream_overview`
 ```bash
 # Get livestream overview
 ae-cli community +get_livestream_overview \
-  --space-id 1 --game-id 1 \
+  --space-id 1 \
   --start-time 2024-01-01 --end-time 2024-01-07
 ```

package/skills/ae-community/references/get_livestream_room_metrics.md

@@ -9,8 +9,8 @@ Mapping command: `ae-cli community +get_livestream_room_metrics`
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--space-id` | number | yes | community space ID |
-| `--game-id` | number | yes | game/space ID |
+| `--space-id` | int64 | yes | Community space ID returned by `community spaces list` |
+| `--game-id` | int64 | no | Deprecated compatibility alias; omit it, or make it equal to `--space-id` |
 | `--channel-id` | number | Yes | Channel ID (obtain via `get_livestream_rooms`) |
 | `--room-id` | string | yes | Room ID (obtain via `get_livestream_rooms`) |
 | `--year` | string | No | Year, format yyyy, default is the current year |
@@ -20,6 +20,6 @@ Mapping command: `ae-cli community +get_livestream_room_metrics`
 ```bash
 # Get the annual indicators of the livestream room
 ae-cli community +get_livestream_room_metrics \
-  --space-id 1 --game-id 1 \
+  --space-id 1 \
   --channel-id 1 --room-id <room-id> --year 2024
 ```

package/skills/ae-community/references/get_livestream_rooms.md

@@ -9,8 +9,8 @@ Mapping command: `ae-cli community +get_livestream_rooms`
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--space-id` | number | yes | community space ID |
-| `--game-id` | number | yes | game/space ID |
+| `--space-id` | int64 | yes | Community space ID returned by `community spaces list` |
+| `--game-id` | int64 | no | Deprecated compatibility alias; omit it, or make it equal to `--space-id` |
 | `--channel-id-list` | string | No | List of channel IDs, comma separated |
 | `--start-time` | string | No | Start date for statistics, format yyyy-MM-dd |
 | `--end-time` | string | No | End date for statistics, format yyyy-MM-dd |
@@ -20,6 +20,6 @@ Mapping command: `ae-cli community +get_livestream_rooms`
 ```bash
 # Search livestream room
 ae-cli community +get_livestream_rooms \
-  --space-id 1 --game-id 1 \
+  --space-id 1 \
   --start-time 2024-01-01 --end-time 2024-01-07
 ```

package/skills/ae-community/references/get_overview_metrics.md

@@ -9,8 +9,8 @@ Mapping command: `ae-cli community +get_overview_metrics`
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--space-id` | number | yes | community space ID |
-| `--game-id` | number | yes | game/space ID |
+| `--space-id` | int64 | yes | Community space ID returned by `community spaces list` |
+| `--game-id` | int64 | no | Deprecated compatibility alias; omit it, or make it equal to `--space-id` |
 | `--channel-id-list` | string | No | List of channel IDs, comma separated |
 | `--start-time` | string | Yes | Start date for statistics, format yyyy-MM-dd |
 | `--end-time` | string | Yes | End date for statistics, format yyyy-MM-dd |
@@ -20,6 +20,6 @@ Mapping command: `ae-cli community +get_overview_metrics`
 ```bash
 # Get overall indicators
 ae-cli community +get_overview_metrics \
-  --space-id 1 --game-id 1 \
+  --space-id 1 \
   --start-time 2024-01-01 --end-time 2024-01-07
 ```

package/skills/ae-community/references/get_post_detail.md

@@ -9,8 +9,8 @@ Mapping command: `ae-cli community +get_post_detail`
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--space-id` | number | yes | community space ID |
-| `--game-id` | number | yes | game/space ID |
+| `--space-id` | int64 | yes | Community space ID returned by `community spaces list` |
+| `--game-id` | int64 | no | Deprecated compatibility alias; omit it, or make it equal to `--space-id` |
 | `--channel-id` | number | yes | channel ID |
 | `--uuid` | string | yes | content UUID |
 | `--resource-type` | number | Yes | Resource type: `0` for posts, `1` for videos |
@@ -26,12 +26,12 @@ Mapping command: `ae-cli community +get_post_detail`
 ```bash
 # Get post details
 ae-cli community +get_post_detail \
-  --space-id 1 --game-id 1 \
+  --space-id 1 \
   --channel-id 1 --uuid <uuid> --resource-type 0
 
 # Get video details and page comments
 ae-cli community +get_post_detail \
-  --space-id 1 --game-id 1 \
+  --space-id 1 \
   --channel-id 1 --uuid <uuid> --resource-type 1 \
   --reply-page-num 1 --reply-page-size 20
 ```

package/skills/ae-community/references/get_risk_content.md

@@ -9,8 +9,8 @@ Mapping command: `ae-cli community +get_risk_content`
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--space-id` | number | yes | community space ID |
-| `--game-id` | number | yes | game/space ID |
+| `--space-id` | int64 | yes | Community space ID returned by `community spaces list` |
+| `--game-id` | int64 | no | Deprecated compatibility alias; omit it, or make it equal to `--space-id` |
 | `--start-time` | string | Yes | Lower limit of release time for risky content, format yyyy-MM-dd |
 | `--end-time` | string | yes | upper limit of release time for risky content, format yyyy-MM-dd |
 | `--risk-codes` | string | No | List of risk type codes, comma separated |
@@ -25,18 +25,18 @@ Mapping command: `ae-cli community +get_risk_content`
 ```bash
 # Query risk content
 ae-cli community +get_risk_content \
-  --space-id 1 --game-id 1 \
+  --space-id 1 \
   --start-time 2024-01-01 --end-time 2024-01-07
 
 # Filter by risk type
 ae-cli community +get_risk_content \
-  --space-id 1 --game-id 1 \
+  --space-id 1 \
   --start-time 2024-01-01 --end-time 2024-01-07 \
   --risk-codes 1,2
 
 # Keyword search
 ae-cli community +get_risk_content \
-  --space-id 1 --game-id 1 \
+  --space-id 1 \
   --start-time 2024-01-01 --end-time 2024-01-07 \
 --search-word "violating keywords"
 ```

package/skills/ae-community/references/get_sentiment_overview.md

@@ -9,8 +9,8 @@ Mapping command: `ae-cli community +get_sentiment_overview`
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--space-id` | number | yes | community space ID |
-| `--game-id` | number | yes | game/space ID |
+| `--space-id` | int64 | yes | Community space ID returned by `community spaces list` |
+| `--game-id` | int64 | no | Deprecated compatibility alias; omit it, or make it equal to `--space-id` |
 | `--channel-id-list` | string | No | List of channel IDs, comma separated |
 | `--start-time` | string | Yes | Start date for statistics, format yyyy-MM-dd |
 | `--end-time` | string | Yes | End date for statistics, format yyyy-MM-dd |
@@ -22,12 +22,12 @@ Mapping command: `ae-cli community +get_sentiment_overview`
 ```bash
 #emotionoverview
 ae-cli community +get_sentiment_overview \
-  --space-id 1 --game-id 1 \
+  --space-id 1 \
   --start-time 2024-01-01 --end-time 2024-01-07
 
 # Limit the number of returns
 ae-cli community +get_sentiment_overview \
-  --space-id 1 --game-id 1 \
+  --space-id 1 \
   --start-time 2024-01-01 --end-time 2024-01-07 \
   --limit 50
 ```

package/skills/ae-community/references/get_tag_trends.md

@@ -9,8 +9,8 @@ Mapping command: `ae-cli community +get_tag_trends`
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--space-id` | number | yes | community space ID |
-| `--game-id` | number | yes | game/space ID |
+| `--space-id` | int64 | yes | Community space ID returned by `community spaces list` |
+| `--game-id` | int64 | no | Deprecated compatibility alias; omit it, or make it equal to `--space-id` |
 | `--tag-code` | string | Yes | Tag code (obtain via `get_corpus_tags`) |
 | `--channel-id-list` | string | No | List of channel IDs, comma separated |
 | `--start-time` | string | No | Start date for statistics, format yyyy-MM-dd |
@@ -21,7 +21,7 @@ Mapping command: `ae-cli community +get_tag_trends`
 ```bash
 # Get tag trends
 ae-cli community +get_tag_trends \
-  --space-id 1 --game-id 1 \
+  --space-id 1 \
   --tag-code "game_version" \
   --start-time 2024-01-01 --end-time 2024-01-07
 ```

package/skills/ae-community/references/get_topic_detail.md

@@ -9,8 +9,8 @@ Mapping command: `ae-cli community +get_topic_detail`
 
 | Flag | Type | Required | Description |
 |------|------|------|------|
-| `--space-id` | number | yes | community space ID |
-| `--game-id` | number | yes | game/space ID |
+| `--space-id` | int64 | yes | Community space ID returned by `community spaces list` |
+| `--game-id` | int64 | no | Deprecated compatibility alias; omit it, or make it equal to `--space-id` |
 | `--topic-id` | string | yes | Topic ID, obtained from get_hot_topics |
 | `--start-time` | string | Yes | Statistics start date, format yyyy-MM-dd, priority is given to the start time of the topic |
 | `--end-time` | string | Yes | Statistics end date, format yyyy-MM-dd, priority is given to the end time of the topic |
@@ -20,7 +20,7 @@ Mapping command: `ae-cli community +get_topic_detail`
 ```bash
 # Get topic details
 ae-cli community +get_topic_detail \
-  --space-id 1 --game-id 1 \
+  --space-id 1 \
   --topic-id <topic-id> \
   --start-time 2024-01-01 --end-time 2024-01-07
 ```

package/skills/ae-community/references/list_sources.md

@@ -0,0 +1,28 @@
+# List Configured Community Sources
+
+Use this L2 command when an ingestion or reporting workflow needs the exact source and channel IDs
+configured in a selected community space.
+
+## Command
+
+```bash
+ae-cli community sources list --space-id <space-id>
+```
+
+## Input
+
+| Flag | Required | Description |
+|---|---|---|
+| `--space-id` | yes | Positive signed int64 space ID returned by `community spaces list`. |
+
+The command is backed by `community.source.list` and requires the product's data-configuration view
+permission. A permission error does not mean that the space has no data sources.
+
+## Output and next step
+
+Each source includes its `sourceId`, `sourceName`, `sourceType`, `channelId`, and `channelName`, plus
+the configured template/config metadata. Preserve every digit of IDs exactly.
+
+For `community data report`, select the source that matches the real data producer, then pass its
+`sourceId` as `--source-id` and its `channelId` as `--channel-id`. Do not choose a source by position
+in the list and never fabricate a missing source.

package/skills/ae-community/references/list_spaces.md

@@ -0,0 +1,39 @@
+# ae-community spaces list
+
+List the community spaces available to the authenticated user. Run this before curated community
+analysis when the real `spaceId` is unknown.
+
+Mapping command: `ae-cli community spaces list`
+
+Capability: `community.space.list`
+
+## Flags
+
+No command-specific flags are required. Authentication and host selection use the standard ae-cli
+configuration and global flags.
+
+## Example
+
+```bash
+ae-cli community spaces list
+```
+
+Use the returned `spaceId` as `--space-id` for `+get_channel_info` and the other curated commands.
+IDs outside JavaScript's safe integer range are emitted as strings in JSON. Copy all digits exactly
+and never convert an ID to a floating-point number.
+
+## Returned count and failures
+
+A successful array response includes `meta.returned_count`, calculated by the CLI from the number
+of entries in `data`. Use it when reporting how many entries this call returned; verify that the
+number matches the rows you display. It is not a global total or a count of unique space IDs.
+If the server also supplies `returned_count`, the CLI's array count takes precedence. Other server
+metadata, including `total` when present, is preserved with its original meaning.
+
+The count describes the original response before any `--jq` projection or filtering. If you filter
+the displayed rows locally, state the displayed count separately rather than presenting
+`meta.returned_count` as the filtered count.
+
+`ok: true`, `data: []`, and `meta.returned_count: 0` mean this successful call returned no visible
+spaces. Authentication, permission, routing, and capability failures remain failures; never turn
+them into an empty successful list or infer zero available spaces from an error.