How do I install the Slack Context skill?

Run npx skillmds@latest add dubsopenhub/slack-context in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Slack Context safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Slack Context?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Slack Context free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Slack Context?

DUBSOpenHub (@dubsopenhub) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Slack Context by dubsopenhub — Agent Skill

Name: Slack Context
Author: DUBSOpenHub

Slack Context

Use when the user asks to "fetch context from Slack", "read this Slack thread", "get requirements from Slack", "extract Slack conversation", or provides a Slack permalink. Uses `gh slack read` — no background scraping, no MCP server. Always warn about security and request confirmation before using Slack data.

DUBSOpenHub Updated Sep 21, 2026

File contents

Slack Context — Read Slack Threads On Demand

Retrieves Slack thread content using gh slack read for specific, user-initiated requests. No background scraping. No persistent MCP connection. Every fetch requires explicit user consent.

⚠️ Security Requirements

BEFORE fetching any Slack content:

Display this warning:

⚠️  SECURITY WARNING
You're about to fetch Slack messages that may contain:
• Personal information (PII)
• Confidential business information
• Private conversations
• Credentials or secrets

Continue? (y/n)

After fetching, display content and ask for confirmation before using it.
Remind the user to redact sensitive data.

When to Use

Trigger phrases:

"Fetch context from this Slack thread: [url]"
"Read this Slack conversation and help me with what we discussed"
"Get the requirements from this Slack chat"
"Use this Slack thread as context"

Appropriate:

Technical implementation discussions
Feature requests in team channels
Bug reports with reproduction steps
Open design discussions

Refuse these:

Customer support conversations
Private DMs (unless explicit permission)
HR or personnel matters
Security incident details
Anything marked confidential

Process

Step 1: Extract Slack URL

Validate the permalink format:

https://[workspace].slack.com/archives/[CHANNEL_ID]/p[TIMESTAMP]

Step 2: Get User Consent

Always show the security warning. Stop if user declines.

Step 3: Fetch Thread

gh slack read <slack-permalink>

Step 4: Display and Confirm

Show the full content. Ask the user to review for sensitive info. Only proceed after explicit confirmation.

Step 5: Summarize and Use

Extract key technical details. Focus on decisions and requirements, not opinions about people. Reference the Slack URL for attribution.

Error Handling

Extension not installed:

gh extension install rneatherway/gh-slack

Not authenticated:

eval $(gh slack auth -t github)

Invalid URL: Must match slack.com/archives/C[A-Z0-9]*/p[0-9]*

Boundaries

Will:

Fetch specific Slack threads via gh slack read
Always warn and request confirmation
Summarize technical discussions
Extract requirements and decisions

Will not:

Scrape or search Slack broadly
Run as a background MCP server
Fetch without explicit user consent
Store or cache Slack content
Override a user's "no"

---name: slack-contextdescription: Use when the user asks to "fetch context from Slack", "read this Slack thread", "get requirements from Slack", "extract Slack conversation", or provides a Slack permalink. Uses `gh slack read` — no background scraping, no MCP server. Always warn about security and request confirmation before using Slack data.---# Slack Context — Read Slack Threads On DemandRetrieves Slack thread content using `gh slack read` for specific, user-initiatedrequests. No background scraping. No persistent MCP connection. Every fetchrequires explicit user consent.## ⚠️ Security Requirements**BEFORE fetching any Slack content:**1. Display this warning:```⚠️ SECURITY WARNINGYou're about to fetch Slack messages that may contain:• Personal information (PII)• Confidential business information• Private conversations• Credentials or secretsContinue? (y/n)```2. After fetching, display content and ask for confirmation before using it.3. Remind the user to redact sensitive data.## When to Use**Trigger phrases:**- "Fetch context from this Slack thread: [url]"- "Read this Slack conversation and help me with what we discussed"- "Get the requirements from this Slack chat"- "Use this Slack thread as context"**Appropriate:**- Technical implementation discussions- Feature requests in team channels- Bug reports with reproduction steps- Open design discussions**Refuse these:**- Customer support conversations- Private DMs (unless explicit permission)- HR or personnel matters- Security incident details- Anything marked confidential## Process### Step 1: Extract Slack URLValidate the permalink format:```https://[workspace].slack.com/archives/[CHANNEL_ID]/p[TIMESTAMP]```### Step 2: Get User ConsentAlways show the security warning. Stop if user declines.### Step 3: Fetch Thread```bashgh slack read <slack-permalink>```### Step 4: Display and ConfirmShow the full content. Ask the user to review for sensitive info.Only proceed after explicit confirmation.### Step 5: Summarize and UseExtract key technical details. Focus on decisions and requirements,not opinions about people. Reference the Slack URL for attribution.## Error Handling**Extension not installed:**```bashgh extension install rneatherway/gh-slack```**Not authenticated:**```basheval $(gh slack auth -t github)```**Invalid URL:**Must match `slack.com/archives/C[A-Z0-9]*/p[0-9]*`## Boundaries**Will:**- Fetch specific Slack threads via `gh slack read`- Always warn and request confirmation- Summarize technical discussions- Extract requirements and decisions**Will not:**- Scrape or search Slack broadly- Run as a background MCP server- Fetch without explicit user consent- Store or cache Slack content- Override a user's "no"

Frequently asked questions