extract-colleague-decisions

Colleague Decisions

Answers a recurring question: "What did my colleagues actually decide today?" A day of Slack produces many messages, most of them chatter, acknowledgements, and questions, with a handful of real decisions inside. This skill searches Slack for each colleague's authored messages in a day, then reads them and pulls out the decisions, so you can catch up on what changed without reading every thread.

The judgement is the point: telling a decision from chatter is a reading task, not a keyword match. slackx conversations search only gets the messages in front of you; you decide what counts.

Prerequisites

• SLACK_TOKEN (and SLACK_COOKIE for xoxc/web tokens) in .env, found by searching up from the working directory. Source it before invoking slackx.
• COLLEAGUES in .env: a comma-separated list of Slack usernames (e.g. alice.smith,bob.jones). Resolve it with ~/.agents/scripts/get-env COLLEAGUES.
• slackx on PATH; install if missing:

  if ! command -v slackx &>/dev/null; then
    git clone https://github.com/TomzxCode/slackx /tmp/slackx
    uv tool install /tmp/slackx
  fi
  

• jq for filtering the search JSON.
• Optional: JEV_ENDPOINT and JEV_TOKEN in the environment, only for the classify_message.py accelerator. The script reads them (or --endpoint/--token) and has no host baked in. Skip them if you classify by reading.

Workflow

1. Resolve inputs

Determine the target day: the argument if given (YYYY-MM-DD or yesterday), otherwise today. Compute the window (see the slackx skill for why Slack's day operators are bracketed this way):

TARGET=2026-09-18                       # or: date +%Y-%m-%d
PREV=$(date -d "$TARGET - 1 day" +%Y-%m-%d)
NEXT=$(date -d "$TARGET + 1 day" +%Y-%m-%d)

Resolve the colleagues and source credentials:

set -a; source .env; set +a
COLLEAGUES=$(~/.agents/scripts/get-env COLLEAGUES)

If COLLEAGUES is empty, stop and tell the user to set it. Do not guess handles.