Skill

spec-slack-research

Searches Slack for organizational context—decisions, constraints, discussion arcs—producing a synthesized research digest with cross-analysis and value assessment. Use for planning, brainstorming, or tasks needing team knowledge.

developer-tools

npx claudepluginhub sunrain520/spec-first

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Search Slack for organizational context and receive an interpreted research digest.

SKILL.md

Similar Skills

slack-search

10.9k

Guides effective Slack searches for messages, files, channels, and people using tools, modifiers (in:, from:, dates), strategies, and file filters.

slack-by-salesforce

Slack Search

Guides effective Slack searches for messages, files, channels, and people using tools like slack_search_public, modifiers (in:, from:, dates), and strategies to narrow broad queries.

slack

slack-explorer

Explores and searches Slack messages, channels, and threads via Node.js CLI commands. Use to search conversations, read channel history, get thread replies, or list channels.

5 files

routine

Stats

Stars23

Forks4

Last CommitApr 25, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

spec-slack-research

Search Slack for organizational context and receive an interpreted research digest.

Usage

spec-slack-research [topic or question] spec-slack-research

Examples

spec-slack-research free trial spec-slack-research What did we say about free trial recently? spec-slack-research free trial in #proj-reverse-trial spec-slack-research onboarding flow after:2026-03-01

The input can be a keyword, a natural language question, or include Slack search modifiers like channel hints (in:#channel) and date filters (after:YYYY-MM-DD). The agent extracts the topic and formulates searches from whatever form the input takes.

Execution

If no argument is provided, ask what topic to research. Use the platform's blocking question tool: AskUserQuestion in Claude Code (call ToolSearch with select:AskUserQuestion first if its schema isn't loaded) or request_user_input in Codex. Fall back to asking in plain text only when no blocking tool exists in the harness or the call errors (e.g., Codex edit modes) — not because a schema load is required. Never silently skip the question.

Dispatch spec-slack-researcher with the user's topic as the task prompt. Omit the mode parameter so the user's configured permission settings apply.

The agent handles everything from here -- Slack MCP discovery, search execution, thread reads, and synthesis. It returns a digest with:

Workspace identifier so the user can verify the correct Slack instance was searched

Research-value assessment (high / moderate / low / none) with justification

Findings organized by topic with source channels and dates

Cross-cutting analysis surfacing patterns across findings

If the agent reports that Slack is unavailable (MCP not connected or auth expired), relay the message to the user. Do not attempt alternative research methods.