What problem does it solve? Teams react to yeaboi's Slack posts with thumbs, pause emojis, and typed replies, but there is no visibility into whether those gestures registered, what they changed, or why some were refused. This Skill reads the two-way Slack lane's history so you can answer exactly what happened to each reaction or reply. ## Core Features & Use Cases - Event history lookup: Query slack_inbound_history to see every Slack event with its outcome — applied, deferred, refused, ignored, unauthorized, stale, or in flight — plus the refusal reason in the system's own words. - Reader health checks: Inspect recent_polls to confirm the polling job is running, or diagnose skipped_no_token, skipped_no_channel, skipped_no_allowlist, and Slack API failures. - Identity resolution: Use slack_identities_list to map Slack member ids to team roster names when attributing typed corrections. - Use Case: A user asks why their thumbs-down on a standup signal did nothing. You check the history, find the event was refused because the signal is no longer in the report, and relay the exact reason. ## Quick Start Ask the assistant to check whether your recent Slack reaction or reply to a yeaboi post was applied and what outcome it received.
