slack-thread-triagelisted

Scan a Slack channel, classify threads by action type (product, project, technical, no-action), and tag them with emoji reactions. Already-tagged threads are skipped on subsequent runs. This skill should be used when triaging Slack channels for actionable threads, or as part of a recurring triage workflow.
matthull/my-skills · ★ 0 · AI & Automation · score 72

Install: claude install-skill matthull/my-skills

# Slack Thread Triage Router Scan a Slack channel, read threads that need attention, classify each by action type, and tag with emoji reactions. On subsequent runs, already-tagged threads are skipped — making this idempotent and safe to run repeatedly. ## Invocation ``` /slack-thread-triage <channel> [hours_back] ``` - **channel** (required): Slack channel name, e.g. `#eng-team` or `eng-team` - **hours_back** (optional, default: 24): How far back to scan Example: `/slack-thread-triage #eng-team 48` ## Reaction Posting Use `mcp__egregore-mcp__add_reaction(channel, message_ts, emoji)` to tag threads after classification. - **channel**: channel name (e.g. `#eng-team`) - **message_ts**: timestamp of the message to react to (from scan_channel output) - **emoji**: emoji name without colons (e.g. `bookmark`, `wrench`, `file_folder`, `white_check_mark`) ## Triage Categories | Category | Emoji | Slack Name | Signals | Tagged? | |----------|-------|------------|---------|---------| | Product | 📋 | `bookmark` | Needs product decision, prioritization call, feature scoping, user-facing tradeoff, or stakeholder input | Yes | | Project | 🗂️ | `file_folder` | Needs project management action: timeline, dependency coordination, resource allocation, status tracking | Yes | | Technical | 🔧 | `wrench` | Needs technical action: bug fix, architecture decision, code review, infrastructure change, investigation | Yes | | No action | — | — | Informational, already resolved, or FYI-only. *