engagement-inbox-manager Checked

Use when the user asks to "triage our comments, DMs, and mentions", "draft replies to this thread", "can we repost this fan post", or "set up inbox SLAs and an escalation path"; produces a ranked triage queue with register detection (sincere / ironic / performative / parasocial, sentiment-inversion table included — "this is so bad" under a comedy register is praise), a commenter taxonomy (troll monitor-only / rager / misguided / unhappy-customer / advocate) with a response-tier ladder and per-channel SLAs, an escalation matrix ending at the crisis path, a moderation ladder plus house rules for owned spaces, and a UGC curation-and-rights mode whose dated permission entries route to the channel registry — every reply is a ranked DRAFT a human posts; nothing is ever auto-sent. Not for launch-window feedback triage — use launch-feedback-synthesizer. 评论私信提及分诊/语域识别/回复草稿/UGC授权

Engagement Inbox Manager

Runs the always-on inbox — comments, DMs, mentions — as a hosting discipline: read the register before the sentiment, classify the commenter before the reply, and turn everything answerable into ranked drafts a human posts. It is the Host-phase workhorse of the ECHO loop and feeds four ECHO H sub-items directly: the UGC-permission fact base the **H2** veto is judged against, inbox SLA attainment (**H3**), the live escalation matrix with named owners (**H8**), and the owned-space moderation ladder and house rules (**H9**) — see echo-benchmark.md (../../../references/echo-benchmark.md). The per-channel SLA tiers, cadence commitments, and ugc-permissions.md status it works from live in channel-registry (../../../protocol/channel-registry/SKILL.md), and social-quality-auditor (../social-quality-auditor/SKILL.md) scores H against the logs this skill leaves behind.

**Scope guard**: this skill triages and drafts — it never ships. Output is a ranked queue of DRAFT replies for human posting; it never auto-sends, auto-replies, mass-DMs, or schedules engagement on any platform, and on 小红书/微信公众号/视频号/抖音 automation is a hard 风控/封号 red line. It does not score the ECHO profile result or run the ECHO vetoes (social-quality-auditor (../social-quality-auditor/SKILL.md)), own the crisis severity ladder or the pause-the-queue rule (crisis-response-planner (../crisis-response-planner/SKILL.md) — this skill's escalation matrix *ends* there), triage launch-window feedback (launch-feedback-synthesizer (../../../launch/prove/launch-feedback-synthesizer/SKILL.md)), or negotiate paid UGC terms (creator-registry (../../../protocol/creator-registry/SKILL.md) + contract-helper (../../../influencer/activate/contract-helper/SKILL.md)). It never writes memory/channels/ records — permission entries and activity lines go to memory/events/channels.ndjson via an authorized operation: propose request to registry-events.py only; channel-registry (../../../protocol/channel-registry/SKILL.md) is the sole writer.

Use when the user asks to "triage our comments, DMs, and mentions", "draft replies to this thread", "can we repost this fan post", or "set up inbox SLAs and an escalation path"; produces a ranked triage queue with register detection (sincere / ironic / performative / parasocial, sentiment-inversion table included — "this is so bad" under a comedy register is praise), a commenter taxonomy (troll monitor-only / rager / misguided / unhappy-customer / advocate) with a response-tier ladder and per-channel SLAs, an escalation matrix ending at the crisis path, a moderation ladder plus house rules for owned spaces, and a UGC curation-and-rights mode whose dated permission entries route to the channel registry — every reply is a ranked DRAFT a human posts; nothing is ever auto-sent. Not for launch-window feedback triage — use launch-feedback-synthesizer. 评论私信提及分诊/语域识别/回复草稿/UGC授权

Engagement Inbox Manager

Runs the always-on inbox — comments, DMs, mentions — as a hosting discipline: read the register before the sentiment, classify the commenter before the reply, and turn everything answerable into ranked drafts a human posts. It is the Host-phase workhorse of the ECHO loop and feeds four ECHO H sub-items directly: the UGC-permission fact base the **H2** veto is judged against, inbox SLA attainment (**H3**), the live escalation matrix with named owners (**H8**), and the owned-space moderation ladder and house rules (**H9**) — see echo-benchmark.md (../../../references/echo-benchmark.md). The per-channel SLA tiers, cadence commitments, and ugc-permissions.md status it works from live in channel-registry (../../../protocol/channel-registry/SKILL.md), and social-quality-auditor (../social-quality-auditor/SKILL.md) scores H against the logs this skill leaves behind.

**Scope guard**: this skill triages and drafts — it never ships. Output is a ranked queue of DRAFT replies for human posting; it never auto-sends, auto-replies, mass-DMs, or schedules engagement on any platform, and on 小红书/微信公众号/视频号/抖音 automation is a hard 风控/封号 red line. It does not score the ECHO profile result or run the ECHO vetoes (social-quality-auditor (../social-quality-auditor/SKILL.md)), own the crisis severity ladder or the pause-the-queue rule (crisis-response-planner (../crisis-response-planner/SKILL.md) — this skill's escalation matrix *ends* there), triage launch-window feedback (launch-feedback-synthesizer (../../../launch/prove/launch-feedback-synthesizer/SKILL.md)), or negotiate paid UGC terms (creator-registry (../../../protocol/creator-registry/SKILL.md) + contract-helper (../../../influencer/activate/contract-helper/SKILL.md)). It never writes memory/channels/ records — permission entries and activity lines go to memory/events/channels.ndjson via an authorized operation: propose request to registry-events.py only; channel-registry (../../../protocol/channel-registry/SKILL.md) is the sole writer.

Quick Start