slack-search
Skill165 starsChanged 2 months agoMITView on GitHub
Use when locating messages, files, channels, or people across Slack, or gathering context before answering, with the search MCP tools (slack_search_public, slack_search_public_and_private, slack_search_channels, slack_search_users). Covers search modifiers (in:, from:, before:), file-type filters, natural-language vs. keyword search, and reading results in context.
3 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- anthropics/knowledge-work-pluginsedited, first seen Oct 13, 2026
- edu6565/claude-skillsedited, first seen Oct 11, 2026
- NiazMorshed2007/jcredited, first seen Sep 20, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 3
- anthropics/knowledge-work-plugins★ 35k88% same
- NiazMorshed2007/jcr★ 19100% same
- edu6565/claude-skills★ 088% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- block-kitSkill
- create-slack-appSkill
- deploy-slack-appSkill
- slack-apiSkill
- slack-cliSkill
- slack-docsSkill
- slack-messagingSkill
- test-slack-appSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 4 are common, 0 are distinctive, and 9 are very specific to this project.
4
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
If too many results, add filters (in:, from:, date ranges).
- Common: line 29
If too few results, remove filters and try synonyms or related terms.
- Common: line 38
Don't rely on a single search.
- Common: line 40
Search for the topic first
- Very specific: line 93
All the standard modifiers above (in:, from:, dates, etc.) work with file searches too.
- Common: line 106
After finding relevant messages:
- Very specific: line 108
Use slack_read_thread to get the full thread context for any threaded message.
- Very specific: line 109
Use slack_read_channel with oldest/latest timestamps to read surrounding messages for context.
- Very specific: line 110
Use slack_read_user_profile to identify who a user is when their ID appears in results.
- Very specific: line 111
Use slack_read_file to read the contents of a file surfaced by a file search.
- Very specific: line 112
Use slack_list_channel_members to see who is in a channel you found.
- Very specific: line 117
Parentheses don't work: Don't try to group search terms with ().
- Very specific: line 119
Private channel access: Use slack_search_public_and_private when you need to include private channels, but note this requires user consent.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
- 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 channelin:<#C123456>: Search in channel by ID-in:channel-name: Exclude a channelin:<@U123456>orin:@username: 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:<@U123456>: Messages sent to a specific userto:me: Messages sent directly to youcreator:@username: Canvases created by a specific person
Content Filters
is:thread: Only threaded messagesis:saved: Only your saved messageshas:pin: Pinned messageshas:link: Messages containing linkshas:file: Messages with file attachmentshas::emoji:: Messages with a specific reactionhasmy::emoji:: Messages you reacted to with a specific reaction
Date Filters
before:YYYY-MM-DD: Messages before a dateafter:YYYY-MM-DD: Messages after a dateon:YYYY-MM-DD: Messages on a specific dateduring:month: Messages during a specific month (e.g.,during:january)
Text Matching
"exact phrase": Match an exact phrase-word: Exclude messages containing a wordwild*: Wildcard matching (minimum 3 characters before*)
File Search
To search for files, set the content_types="files" parameter and use a type: filter in the query:
type:images,type:documents,type:pdfs,type:spreadsheets,type:presentationstype:canvases,type:lists,type:emails,type:audio,type:videos
Example: content_types="files" type:pdfs budget after:2025-01-01
All the standard modifiers above (in:, from:, dates, etc.) work with file searches too.
Useful Parameters
Beyond the query string, the search tools accept parameters that materially improve results:
sort:score(relevance, default) ortimestamp(newest first); pair withsort_dir(asc/desc).content_types:messages(default) orfiles.only_my_channels: restrict to channels you're a member of.limit: results per page (capped at 20); paginate with the returnedcursor.
Following Up on Results
After finding relevant messages:
- Use
slack_read_threadto get the full thread context for any threaded message. - Use
slack_read_channelwitholdest/latesttimestamps to read surrounding messages for context. - Use
slack_read_user_profileto identify who a user is when their ID appears in results. - Use
slack_read_fileto read the contents of a file surfaced by a file search. - Use
slack_list_channel_membersto see who is in a channel you found.
Common Pitfalls
- Boolean operators don't work.
AND,OR,NOTare not supported. Use spaces (implicit AND) and-for exclusion. (Repeating the same modifier, e.g. twofrom:, ORs those values together.) - 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_channelfor the most recent messages. - Private channel access. Use
slack_search_public_and_privatewhen you need to include private channels, but note this requires user consent.
Notes
- Scope: this skill owns searching workspace content: messages, files, channels, and people inside Slack. To search and read the official Slack platform documentation at docs.slack.dev (conceptual and how-to questions about Slack features), use the
slack-docsskill instead.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

