OpenParable
Skip to content
← Back to skills

Slack Context Fetcher

Apps & Automation
slack-context-fetcher

Slack Context Fetcher is an Agent Skill for apps & automation published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Fetches Slack thread content using a Slack bot for ticket context enrichment. Use when tickets reference Slack threads or discussions.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/communication/slack-context-fetcher/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/slack-context-fetcher, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Slack Context Fetcher

Fetches Slack thread content when tickets reference Slack discussions. Assumes SLACK_BOT_TOKEN environment variable is set.

Prerequisites

  • SLACK_BOT_TOKEN env var set (xoxb-... token)
  • Bot added to relevant channels

Workflow

1. Detect Slack References

Parse ticket description for Slack links:

Pattern: https://{workspace}.slack.com/archives/{channel_id}/p{timestamp}
Example: https://comfy-org.slack.com/archives/C07ABCD1234/p1234567890123456

Extract:

  • channel_id: C07ABCD1234
  • thread_ts: 1234567890.123456 (insert decimal before last 6 digits)

2. Fetch Thread Content

CHANNEL="C07ABCD1234"
THREAD_TS="1234567890.123456"

curl -s -H "Authorization: Bearer $SLACK_BOT_TOKEN" \
  "https://slack.com/api/conversations.replies?channel=$CHANNEL&ts=$THREAD_TS" | \
  jq '.messages[] | {user: .user, text: .text, ts: .ts}'

3. Resolve User Names

curl -s -H "Authorization: Bearer $SLACK_BOT_TOKEN" \
  "https://slack.com/api/users.info?user=$USER_ID" | \
  jq -r '.user.real_name'

4. Format for Context

## Slack Thread Context

**Thread:** [Link](https://comfy-org.slack.com/archives/C07.../p1234...)
**Participants:** Alice, Bob, Charlie
**Messages:** 12

### Full Thread

**Alice** (2024-01-15 10:30):

> Original message about the issue...

**Bob** (2024-01-15 10:45):

> Response with context...

5. Save to Run Directory

echo "$SLACK_CONTEXT" > "$RUN_DIR/slack-context.md"

jq '.slackThreads += [{"url": "...", "fetched": "...", "messages": N}]' \
  "$RUN_DIR/ticket.json" > tmp && mv tmp "$RUN_DIR/ticket.json"

Integration with ticket-intake

During ticket-intake, if Slack URLs detected:

  1. Parse channel ID and thread timestamp
  2. Fetch thread content
  3. Save to slack-context.md
  4. Include in research context

Error Handling

ErrorCauseResolution
channel_not_foundInvalid channel IDVerify URL
not_in_channelBot not addedAdd bot to channel
invalid_authBad tokenCheck SLACK_BOT_TOKEN

Output Artifacts

FileLocationDescription
slack-context.mdruns/{ticket-id}/slack-context.mdThread content
ticket.jsonruns/{ticket-id}/ticket.jsonUpdated with slack refs