the right page on the official Slack documentation site (
https://docs.slack.dev
) and
read
it as clean markdown, so answers come from the live docs rather than memory. The site exposes three machine-readable surfaces an agent can use directly, with no authentication and no Slack workspace:
A
search API method
:
GET https://docs.slack.dev/api/v1/search?query=&category=
returns ranked page hits as JSON. Scope every search with a
category
(guides, reference, a specific SDK, etc.); an uncategorized search skews heavily toward SDK pages.
Per-page markdown
every page is available at its URL
+
.md
(e.g.
/quickstart.md
).
Index files
:
/llms.txt
(a curated overview) and
/llms-sitemap.md
(a list of every markdown page).
If
$0
is provided, it is either a
docs.slack.dev
URL (jump to the
Fast Path
) or a topic to search (start at
Step 1
). For a broad "how do I build X on Slack?" question rather than one specific page, read
https://docs.slack.dev/llms.txt
first; it is a curated, LLM-oriented overview of the platform and the recommended build path.
Critical rules:
The docs are the
source of truth
. Do not answer a factual question about the Slack platform from memory; discover the page, fetch it, then answer from what it says.
Prefer the
.md
version
of any page over the HTML version. It is cleaner for reading and quoting.
Every fetched markdown page begins with a
Source:
line. Keep that URL so you can cite the page back to the developer.
Show more
Installs
1.3K
Repository
slackapi/slack-…s-plugin
GitHub Stars
140
First Seen
Jul 31, 2026
Security Audits
Gen Agent Trust Hub
Pass
Socket
Pass
Snyk
Warn