slack-search

This skill provides guidance for effectively searching Slack to find messages, files, and information.

Works with

Claude CodeCursorClineWindsurfCodexGooseGitHub CopilotZed

0

total installs

0

this week

11.0K

GitHub stars

0

upvotes

Install Skill

Run in your terminal

$npx skills add https://github.com/anthropics/knowledge-work-plugins --skill slack-search

0

installs

0

this week

11.0K

stars

Installation Guide

How to use slack-search on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your machine
  • Node.js 16+ with npm — verify with node --version
  • Active project directory where you want to add slack-search
2

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/anthropics/knowledge-work-plugins --skill slack-search

Fetches slack-search from anthropics/knowledge-work-plugins and configures it for Cursor.

3

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/slack-search

Restart Cursor to activate slack-search. Access via /slack-search in your agent's command palette.

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

Documentation

Slack Search

This skill provides guidance for effectively searching Slack to find messages, files, and information.

When to Use

Apply this skill whenever you need to find information in Slack — including when a user asks you to locate messages, conversations, files, or people, or when you need to gather context before answering a question about what's happening in Slack.

Search Tools Overview

Tool Use When
slack_search_public Searching public channels only. Does not require user consent.
slack_search_public_and_private Searching all channels including private, DMs, and group DMs. Requires user consent.
slack_search_channels Finding channels by name or description.
slack_search_users Finding people by name, email, or role.

Search Strategy

Start Broad, Then Narrow

  1. Begin with a simple keyword or natural language question.
  2. If too many results, add filters (in:, from:, date ranges).
  3. If too few results, remove filters and try synonyms or related terms.

Choose the Right Search Mode

  • Natural language questions (e.g., "What is the deadline for project X?") — Best for fuzzy, conceptual searches where you don't know exact keywords.
  • Keyword search (e.g., project X deadline) — Best for finding specific, exact content.

Use Multiple Searches

Don't rely on a single search. Break complex questions into smaller searches:

  • Search for the topic first
  • Then search for specific people's contributions
  • Then search in specific channels

Search Modifiers Reference

Location Filters

  • in:channel-name — Search within a specific channel
  • in:<#C123456> — Search in channel by ID
  • -in:channel-name — Exclude a channel
  • in:<@U123456> — Search in DMs with a user

User Filters

  • from:<@U123456> — Messages from a specific user (by ID)
  • from:username — Messages from a user (by Slack username)
  • to:me — Messages sent directly to you

Content Filters

  • is:thread — Only threaded messages
  • has:pin — Pinned messages
  • has:link — Messages containing links
  • has:file — Messages with file attachments
  • has::emoji: — Messages with a specific reaction

Date Filters

  • before:YYYY-MM-DD — Messages before a date
  • after:YYYY-MM-DD — Messages after a date
  • on:YYYY-MM-DD — Messages on a specific date
  • during:month — Messages during a specific month (e.g., during:january)

Text Matching

  • "exact phrase" — Match an exact phrase
  • -word — Exclude messages containing a word
  • wild* — Wildcard matching (minimum 3 characters before *)

File Search

To search for files, use the content_types="files" parameter with type filters:

  • type:images — Image files
  • type:documents — Document files
  • type:pdfs — PDF files
  • type:spreadsheets — Spreadsheet files
  • type:canvases — Slack Canvases

Example: content_types="files" type:pdfs budget after:2025-01-01

Following Up on Results

After finding relevant messages:

  • Use slack_read_thread to get the full thread context for any threaded message.
  • Use slack_read_channel with oldest/latest timestamps to read surrounding messages for context.
  • Use slack_read_user_profile to identify who a user is when their ID appears in results.

Common Pitfalls

  • Boolean operators don't work. AND, OR, NOT are not supported. Use spaces (implicit AND) and - for exclusion.
  • Parentheses don't work. Don't try to group search terms with ().
  • Search is not real-time. Very recent messages (last few seconds) may not appear in search results. Use slack_read_channel for the most recent messages.
  • Private channel access. Use slack_search_public_and_private when you need to include private channels, but note this requires user consent.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Steps

  1. 1Install product management skill
  2. 2Start with user story generation for known feature
  3. 3Progress to competitive analysis: research 2-3 competitors
  4. 4Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5Draft stakeholder communications and refine based on feedback
  6. 6Build template library for recurring PM tasks
  7. 7Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use when

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid when

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Related Skills

Reviews

4.861 reviews
  • A
    Ama DialloDec 28, 2024

    slack-search fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • A
    Ama AbbasDec 24, 2024

    Registry listing for slack-search matched our evaluation — installs cleanly and behaves as described in the markdown.

  • C
    Chen HarrisDec 20, 2024

    Registry listing for slack-search matched our evaluation — installs cleanly and behaves as described in the markdown.

  • C
    Chen WhiteDec 8, 2024

    slack-search reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • C
    Chen JacksonDec 8, 2024

    slack-search is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • I
    Isabella RobinsonDec 4, 2024

    Useful defaults in slack-search — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • A
    Ama MensahNov 27, 2024

    slack-search fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • A
    Amina ThompsonNov 19, 2024

    slack-search is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • I
    Isabella MartinezNov 3, 2024

    We added slack-search from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • A
    Ama OkaforOct 22, 2024

    slack-search fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 61

1 / 7

Discussion

Comments — not star reviews
  • No comments yet — start the thread.