slack-search
Guidance for effectively searching Slack to find messages, files, channels, and people
- License 许可
- Apache-2.0
- 所属仓库
- monoes/monomind
- 最近更新
- 2026-11-10
- Stars
- ★ 23
- Forks
- 2
01 前言 Front Matter
- name
- slack-search
- tags
- []
- tools
- []
- source
- https://github.com/anthropics/knowledge-work-plugins
- license
- Apache-2.0
- description
- Guidance for effectively searching Slack to find messages, files, channels, and people
- source_path
- partner-built/slack/skills/slack-search
- source_commit
- 8444efcd48f7012f09797778a36a33e73d0861f4
02 资源文件 1
- 许可证LICENSE.txt11.3 KB
03 SKILL.md 正文
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>— 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 messageshas:pin— Pinned messageshas:link— Messages containing linkshas:file— Messages with file attachmentshas::emoji:— Messages 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, use the content_types="files" parameter with type filters:
type:images— Image filestype:documents— Document filestype:pdfs— PDF filestype:spreadsheets— Spreadsheet filestype: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_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.
Common Pitfalls
- Boolean operators don't work.
AND,OR,NOTare 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_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.
04 同仓库更多 Skills
zk-steward
Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.
writing-plans
Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.
write-spec
Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.
write-query
Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.
workflow-automation
Org role guidance for workflow automation: build and maintain CI/CD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.
workflow-architect
Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.