Slack Developer scores 70/100 (Grade C), passing 11 of 22 checks (50%). The documentation is broadly accessible to AI agents but has 6 areas that could be improved to better serve automated tooling.
# Agent Score Fix Report — Slack Developer URL: https://api.slack.com/docs Score: 70/100 (Grade C) I need help improving the AI-readiness of the documentation at https://api.slack.com/docs. Agent Score found 4 failing checks and 2 warnings. ## Failing Checks (4) - [content-discoverability] Llms Txt Directive: No llms.txt directive found in any of 1 pages - [markdown-availability] Markdown Url Support: No pages support .md URLs (0/1 tested) - [markdown-availability] Content Negotiation: Server ignores Accept: text/markdown header (0/1 pages return markdown) - [url-stability] Http Status Codes: 1 of 1 pages return 200 for non-existent URLs (soft 404) ## Warnings (2) - [page-size] Content Start Position: 1 of 1 pages have content starting at 10–50% (worst 27%) - [url-stability] Redirect Behavior: 1 of 1 pages use cross-host redirects ## Fix Instructions For each issue above, please: 1. Analyze the documentation site at https://api.slack.com/docs 2. Implement the specific fix 3. Verify the fix would cause the check to pass ### Common fixes: - **No llms.txt**: Create /llms.txt following https://llmstxt.org — list all doc pages in markdown format - **No .md URL support**: Configure your docs platform to serve pages at equivalent .md URLs (e.g. /docs/quickstart.md) - **No content negotiation**: Return markdown when request includes Accept: text/markdown header - **Large page size**: Reduce nav boilerplate, inline scripts, and repetitive markup - **No sitemap**: Generate /sitemap.xml listing all documentation URLs - **Auth walls**: Ensure docs pages return 200 without requiring login cookies or tokens - **No Last-Modified header**: Configure your server/CDN to include Last-Modified response headers - **Tab content hidden**: Ensure tabbed content is rendered in the HTML (not JS-only) so agents can read all variants ## Run afdocs Locally for More Detail To get deeper visibility into what's failing, run afdocs against your docs: npx afdocs https://api.slack.com/docs --fixes --verbose - **--fixes**: Adds "Fix:" lines to the output for each warn/fail check with actionable remediation steps - **-v, --verbose**: Shows per-page details (specific URLs, character counts, error codes) for checks with issues — useful for per-URL visibility into what's failing
CHECK RESULTS
How your docs scored
markdown-url-supportNo pages support .md URLs (0/1 tested)
content-negotiationServer ignores Accept: text/markdown header (0/1 pages return markdown)
http-status-codes1 of 1 pages return 200 for non-existent URLs (soft 404)
redirect-behavior1 of 1 pages use cross-host redirects
cache-header-hygieneAll 2 endpoints have appropriate cache headers
llms-txt-freshnessNo page URLs found in llms.txt
markdown-content-paritySkipped: dependency check did not pass
auth-gate-detectionAll 1 pages are publicly accessible
auth-alternative-accessAll docs pages are publicly accessible; no alternative access paths needed
content-start-position1 of 1 pages have content starting at 10–50% (worst 27%)
rendering-strategyAll 1 pages contain server-rendered content
page-size-htmlAll 1 pages convert under 50K chars (median 13K, 64% boilerplate)
page-size-markdownSkipped: dependency check did not pass
llms-txt-directiveNo llms.txt directive found in any of 1 pages
llms-txt-existsllms.txt found at 1 location(s)
llms-txt-validllms.txt follows the proposed structure (H1, blockquote, heading-delimited link sections)
llms-txt-sizellms.txt is 40,604 characters (under 50,000 threshold)
llms-txt-links-resolveAll 10 links are external and resolve (165 total links)
llms-txt-links-markdownAll 165 links are external; cannot assess markdown support
tabbed-content-serializationNo tabbed content detected across 1 pages
section-header-qualityNo tabbed content found; header quality check not applicable
markdown-code-fence-validityAll 0 code fences properly closed across 1 pages
