Slack

Skill 102 of 200

Slack Search

Guidance for effectively searching Slack to find messages, files, channels, and people

2 minutes · 439 words · 15 sections

Install

$ npx skills add anthropics/knowledge-work-plugins --skill slack-search

$ npx skills add anthropics/knowledge-work-plugins

» /plugin marketplace add anthropics/knowledge-work-plugins

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

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

Begin with a simple keyword or natural language question.
If too many results, add filters (in:, from:, date ranges).
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.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/anthropics/knowledge-work-plugins, branch main, last pushed 23 September 2026.

Licence

Apache-2.0 — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

200 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 27 distinct layouts observed: bio-research/skills/*/SKILL.md, cowork-plugin-management/skills/*/SKILL.md, customer-support/skills/*/SKILL.md, data/skills/*/SKILL.md, design/skills/*/SKILL.md, engineering/skills/*/SKILL.md, enterprise-search/skills/*/SKILL.md, finance/skills/*/SKILL.md, human-resources/skills/*/SKILL.md, legal/skills/*/SKILL.md, marketing/skills/*/SKILL.md, operations/skills/*/SKILL.md, partner-built/apollo/skills/*/SKILL.md, partner-built/brand-voice/skills/*/SKILL.md, partner-built/common-room/skills/*/SKILL.md, partner-built/slack/skills/*/SKILL.md, partner-built/zoom-plugin/skills/*/SKILL.md, partner-built/zoom-plugin/skills/contact-center/*/SKILL.md, partner-built/zoom-plugin/skills/meeting-sdk/*/SKILL.md, partner-built/zoom-plugin/skills/meeting-sdk/web/*/SKILL.md, partner-built/zoom-plugin/skills/video-sdk/*/SKILL.md, partner-built/zoom-plugin/skills/virtual-agent/*/SKILL.md, partner-built/zoom-plugin/skills/zoom-mcp/*/SKILL.md, pdf-viewer/skills/*/SKILL.md, product-management/skills/*/SKILL.md, productivity/skills/*/SKILL.md, sales/skills/*/SKILL.md.

Issue colours

Resolved from the awesome-design-md registry — hue 39°, chroma 0.113. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Typefaces

Display: Copernicus is not available to us; set in Newsreader.

We never load a typeface at request time from a third-party origin, so a brand face we do not already self-host is substituted rather than fetched.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Removed “Slack Search”, a leading h1 that duplicated the skill title.

Spec compliance

53 editorial notes across 41 of 200 skills. They are printed in the margin of each skill rather than as errors here.

and 31 more.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .claude-plugin/marketplace.json by Anthropic, declaring 120 plugins. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /anthropics/knowledge-work-plugins.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

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

When to Use

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

Begin with a simple keyword or natural language question.
If too many results, add filters (in:, from:, date ranges).
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.