Slack vs Discord

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Discord
   Slack✓fullprobed8/10

   Slack has a confirmed llms.txt at docs.slack.dev/llms.txt (HTTP 200) plus llms-full-deno.txt variants, and its developer docs are explicitly agent-oriented (MCP server, AI build guides, quickstart) suitable for pointing an agent at. missing for 10: no independent/community confirmation of an agent successfully consuming llms.txt in practice, and OpenAPI-style machine spec endpoints under docs.slack.dev returned 404.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.slack.dev/llms.txt # Slack Developer Docs > The official documentation for building on the Slack p…”
   • [claimed-docs] “Once connected, your AI assistant can search channels, read messages, and use real conversation context to help you build.”
   • [claimed-docs] “You can create Slack-hosted workflows written in TypeScript using the Deno Slack SDK.”
   • [probe] “official MCP server documented at https://docs.slack.dev/ai/slack-mcp-server/”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.slack.dev/openapi.json, https://docs.slack.dev/swagger.json, https://docs.slack.dev/api…”

   proof ↗⚑ flag

   Discord✓fullprobed9/10

   Direct probe evidence confirms Discord's developer docs serve a working llms.txt (HTTP 200) with an index of documentation pages, and individual doc pages are also available in .md format explicitly for agent consumption, pointing back to the llms.txt index. Missing for 10: no independent third-party confirmation of agent usage/adoption beyond the probe itself.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.discord.com/llms.txt # Documentation - Discord - [Discord Developer Platform](https://docs.discord…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.discord.com/developers/intro.md > ## Documentation Index > Fetch the complete documentation index at…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Slack
   Slack✓fullclaimed7/10

   Slack's Web API (chat.postMessage etc.) is a pure HTTP interface callable without any UI, the Events API supports webhook/Socket Mode server-side listening, Workflow Builder supports webhook triggers to kick off automations from outside Slack, and the Slack CLI/Bolt SDKs let apps be built, deployed, and run non-interactively — all enabling headless automation suitable for CI-like use. Missing for 10: explicit CI/CD pipeline examples (e.g. GitHub Actions integration), and no documentation of running the CLI/SDKs specifically inside a CI runner or headless test harness.

   • [claimed-docs] “The Slack Web API is an interface for querying information from and enacting change in a Slack workspace.”
   • [claimed-docs] “Sends a message to a channel.”
   • [claimed-docs] “Webhook triggers for workflows - How to start a workflow from outside of Slack.”
   • [claimed-docs] “When you use the Events API, _Slack_ calls _you_. ... you can either use Socket Mode or you can designate a public HTTP endpoint”
   • [claimed-docs] “When you use the Events API, Slack calls you.”
   • [claimed-docs] “The Slack command-line interface (CLI) allows you to create and manage Slack apps from the command line.”
   • [claimed-docs] “Send data to or query data from Slack using any of more than 200 methods.”
   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [claimed-docs] “This quickstart guide covers how to create a Slack app using the Slack CLI and the Bolt frameworks, in either Python or JavaScript.”

   proof ↗⚑ flag

   Discord~partialclaimed6/10

   Discord's REST API, bot tokens, and webhooks are explicitly documented as usable without a GUI, including a direct example of 'CI/CD pipelines posting build results or deployment notifications' via webhooks, and bots can run headlessly against the Gateway/REST API using only a token. However there's no first-party CLI, headless test harness, or SDK-level guidance for running the whole platform in automated pipelines beyond webhooks/bots. Missing for 10: an official CLI or headless client mode, dedicated CI documentation/examples beyond webhooks, and independent confirmation of headless bot reliability in CI.

   • [claimed-docs] “CI/CD pipelines posting build results or deployment notifications”
   • [claimed-docs] “Send messages into Discord channels or receive event notifications from Discord delivered to your app over HTTP.”
   • [claimed-docs] “Webhooks are a low-effort way to post messages to channels in Discord. They do not require a bot user or authentication to use.”
   • [claimed-docs] “Authenticating with the Discord API can be done in one of two ways: 1. Using a bot token... 2. Using an OAuth2 bearer token”
   • [claimed-docs] “The Discord API is a REST API that allows you to interact with Discord data from your own applications.”

   proof ↗⚑ flag

3. ai-native userDrive the product through a documented public API

   weight 3 · round to Slack
   Slack✓fullprobed9/10

   Slack ships extensive documented public APIs (Web API with 200+ methods, Events API, Bolt/CLI SDKs, official OpenAPI/AsyncAPI specs in slackapi/slack-api-specs) plus an official MCP server enabling AI-native agents to search, message, upload files, manage lists/canvases — all first-party documented and independently verifiable via the public GitHub spec repo. missing for 10: no independent hands-on report specifically confirming the raw REST/Web API (vs MCP) working end-to-end from a third-party AI integrator, and the docs.slack.dev/openapi.json probe returned 404 suggesting the interactive spec isn't hosted at the expected discovery path.

   • [claimed-docs] “The Slack Web API is an interface for querying information from and enacting change in a Slack workspace.”
   • [claimed-docs] “The Slack Web API is an interface for querying information _from_ and enacting change _in_ a Slack workspace.”
   • [claimed-docs] “your integrated apps can search channels, send messages, and perform other Slack actions through MCP clients”
   • [claimed-docs] “The Slack MCP server provides tools for searching through Slack, retrieving and sending messages, managing canvases, managing users, uploadi…”
   • [claimed-docs] “Workspace admins can approve and manage all MCP client integrations, keeping your Slack data safe.”
   • [claimed-docs] “The Slack command-line interface (CLI) allows you to create and manage Slack apps from the command line.”
   • [claimed-docs] “This quickstart guide covers how to create a Slack app using the Slack CLI and the Bolt frameworks, in either Python or JavaScript.”
   • [claimed-docs] “Send data to or query data from Slack using any of more than 200 methods.”
   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [probe] “official MCP server documented at https://docs.slack.dev/ai/slack-mcp-server/”
   • [probe] “official CLI documented at https://docs.slack.dev/tools/slack-cli/”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.slack.dev/openapi.json, https://docs.slack.dev/swagger.json, https://docs.slack.dev/api…”

   proof ↗⚑ flag

   Discord✓fullprobed8/10

   Discord provides a well-documented REST API, Gateway WebSocket API, OAuth2, bot tokens, webhooks, and slash commands — all extensively documented for programmatic/AI-driven access (discord-docs-35, -10, -4, -5, -7). This gives an AI-native user a clear documented public API surface to drive the product. Missing for 10: no discoverable OpenAPI/Swagger spec (probe confirms 404s at standard paths), and no independent third-party verification of API completeness beyond first-party docs.

   • [claimed-docs] “The Discord API is a REST API that allows you to interact with Discord data from your own applications.”
   • [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild”
   • [claimed-docs] “Authenticating with the Discord API can be done in one of two ways: 1. Using a bot token... 2. Using an OAuth2 bearer token”
   • [claimed-docs] “Webhooks are a low-effort way to post messages to channels in Discord. They do not require a bot user or authentication to use.”
   • [claimed-docs] “Slash commands are the most common type of command and are accessed by typing `/` in the chat input, or by opening the command picker.”
   • [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild, …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.discord.com/openapi.json, https://docs.discord.com/swagger.json, https://docs.discord.c…”

   proof ↗⚑ flag

4. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Slack~partialclaimed4/10

   Slack's API model implies scoped bot/user tokens (the OpenAPI spec notes 'user and bot user token usage of public Web API methods') and admin approval of MCP client integrations is described as keeping data safe, suggesting some governance over agent access, but there is no explicit documentation of an OAuth-scopes system or a user-facing flow to mint least-privilege credentials specifically for an agent. Missing for 10: explicit OAuth scope list/granularity docs, a documented workflow for a user to generate a scoped token for an agent, and any admin/user UI for restricting agent permissions beyond MCP client approval.

   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [claimed-docs] “Workspace admins can approve and manage all MCP client integrations, keeping your Slack data safe.”
   • [claimed-docs] “A developer sandbox is an Enterprise org environment (a network of two or more Slack workspace instances) that can be used to build against …”

   proof ↗⚑ flag

   Discord~partialclaimed4/10

   Discord's API supports OAuth2 bearer tokens with defined scopes and bot tokens with granular permission bits (docs-4, docs-6, docs-17, docs-18, docs-27), which technically allow issuing narrower-than-full-access credentials for any integration, including an agent. However, there is no documentation framing this specifically for AI agents or describing least-privilege credential issuance workflows tailored to autonomous/agentic use. missing for 10: agent-specific scoped-credential guidance, examples of least-privilege bot/OAuth setups for AI agents, independent confirmation of scope granularity in practice.

   • [claimed-docs] “Authenticating with the Discord API can be done in one of two ways: 1. Using a bot token... 2. Using an OAuth2 bearer token”
   • [claimed-docs] “The first step in implementing OAuth2 is registering a developer application and retrieving your client ID and client secret.”
   • [claimed-docs] “Using a bot token found on the Bot page within your app’s settings... Using an OAuth2 bearer token gained through the OAuth2 API.”
   • [claimed-docs] “OAuth2 enables application developers to build applications that utilize authentication and data from the Discord API.”
   • [claimed-docs] “allows /users/@me/connections to return linked third-party accounts”

   proof ↗⚑ flag

5. ai-native userBuild against official SDKs

   weight 2 · round to Slack
   Slack✓fullclaimed9/10

   Slack ships multiple official SDKs (Bolt for Java, node-slack-sdk, Deno Slack SDK), an official CLI, Web API with published OpenAPI spec, Events API, and Block Kit docs, all clearly documented as first-party developer tooling for building AI-native/agentic integrations, plus a developer sandbox for safe testing. Missing for 10: independent/hands-on developer corroboration beyond official docs and a fully discoverable OpenAPI endpoint (probe found candidate paths 404 despite spec repo existing).

   • [claimed-docs] “Bolt for Java is a framework on the JVM that offers an abstraction layer to build Slack apps using modern platform features.”
   • [claimed-docs] “Send data to or query data from Slack using any of more than 200 methods.”
   • [claimed-docs] “You can create Slack-hosted workflows written in TypeScript using the Deno Slack SDK.”
   • [claimed-docs] “The Slack command-line interface (CLI) allows you to create and manage Slack apps from the command line.”
   • [claimed-docs] “This quickstart guide covers how to create a Slack app using the Slack CLI and the Bolt frameworks, in either Python or JavaScript.”
   • [claimed-docs] “The Slack Web API is an interface for querying information from and enacting change in a Slack workspace.”
   • [claimed-docs] “The Slack Web API is an interface for querying information _from_ and enacting change _in_ a Slack workspace.”
   • [claimed-docs] “The Events API is a streamlined way to build apps and bots that respond to activities in Slack.”
   • [claimed-docs] “A developer sandbox is an Enterprise org environment (a network of two or more Slack workspace instances) that can be used to build against …”
   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [claimed-docs] “Whether you're composing layouts for modals, messages, or tabs, the Block Kit building experience is the same — your app will be sculpting s…”

   proof ↗⚑ flag

   Discord✓fullclaimed8/10

   Discord provides extensive first-party documentation for building against official SDKs and APIs — the REST API, Gateway (WebSocket) API, OAuth2, Embedded App SDK, and a full Discord Social SDK with platform-specific guides for Unity, Unreal Engine, C++, iOS/Android, and web/mobile account linking. This gives builders (including AI-native developers) clear, well-documented interfaces to build bots, apps, and integrations. Missing for 10: independent/hands-on developer corroboration of SDK integration experience and AI-agent-specific SDK examples or tooling.

   • [claimed-docs] “Authenticating with the Discord API can be done in one of two ways: 1. Using a bot token... 2. Using an OAuth2 bearer token”
   • [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild”
   • [claimed-docs] “Our Embedded App SDK makes it quick and easy to ship native web apps, games, and interactive experiences.”
   • [claimed-docs] “The Discord API is a REST API that allows you to interact with Discord data from your own applications.”
   • [claimed-docs] “allowing them to connect with their friends and communities on Discord without leaving your game”
   • [claimed-docs] “This guide will walk you through integrating the Discord Social SDK into a Unity project.”
   • [claimed-docs] “Get started with the Discord Social SDK in C++ applications.”
   • [claimed-docs] “Integrate the Discord Social SDK into Unreal Engine games.”
   • [claimed-docs] “With the Discord Social SDK, you can offer a seamless social experience for your players, allowing them to connect with their friends and co…”

   proof ↗⚑ flag

6. ai-native userSubscribe to events via webhooks

   weight 2 · round to Slack
   Slack✓fullclaimed8/10

   Slack's Events API lets developers subscribe to specific event types via webhook (public HTTP endpoint) or Socket Mode, with Slack calling the subscriber's endpoint on events — a core webhook-subscription mechanism well documented for building AI/agentic integrations. Workflow Builder also supports webhook triggers for starting workflows externally, reinforcing webhook-based event subscription. missing for 10: independent/hands-on corroboration of webhook reliability at scale, and more explicit framing of Events API webhooks specifically for AI-native/agent consumption (most AI-agent docs emphasize MCP/Web API rather than raw event webhooks).

   • [claimed-docs] “Subscribe to only the events you want; don't worry about the ones you don't need.”
   • [claimed-docs] “When you use the Events API, Slack calls you.”
   • [claimed-docs] “When you use the Events API, _Slack_ calls _you_. ... you can either use Socket Mode or you can designate a public HTTP endpoint”
   • [claimed-docs] “The Events API is a streamlined way to build apps and bots that respond to activities in Slack.”
   • [claimed-docs] “With the Events API, _Slack_ calls _you_.”
   • [claimed-docs] “Webhook triggers for workflows - How to start a workflow from outside of Slack.”
   • [claimed-docs] “Webhook triggers for workflows”

   proof ↗⚑ flag

   Discord~partialclaimed6/10

   Discord's webhook docs explicitly state apps can 'receive event notifications from Discord delivered to your app over HTTP,' confirming webhook-based event subscription exists alongside the Gateway websocket API for events. However, the evidence pack gives only a single line on this capability with no detail on which events are supported, setup/config steps, or independent developer confirmation. Missing for 10: full list of subscribable event types, setup/configuration docs, and third-party/community validation of webhook event delivery in practice.

   • [claimed-docs] “Send messages into Discord channels or receive event notifications from Discord delivered to your app over HTTP.”
   • [claimed-docs] “Webhooks are a low-effort way to post messages to channels in Discord. They do not require a bot user or authentication to use.”
   • [claimed-docs] “They do not require a bot user or authentication to use.”
   • [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Slack
   Slack✓fullclaimed7/10

   Slack ships built-in AI features (intelligent daily briefing, Slackbot summaries/recaps, channel/thread summarization, workspace-wide semantic search across integrated data, meeting notes from huddles) that surface AI-generated insights directly inside the product, per slack-docs-13/14/15/16/19/34/52. missing for 10: independent/hands-on verification of insight quality and accuracy, and detail on how suggestions are surfaced/actioned beyond marketing copy.

   • [claimed-docs] “Today is your new intelligent briefing that signals what needs your attention based on your priorities.”
   • [claimed-docs] “Slackbot is your personal AI agent in Slack that understands you and your workspace, helping you prepare for upcoming meetings, analyze repo…”
   • [claimed-docs] “AI in Slack can summarize channels and threads and serve up daily recaps, giving you the information you need to stay organized and in the k…”
   • [claimed-docs] “Conversations with coworkers, PDFs, images for your social campaign, decks buried in Google Drive, support tickets, customer records from Sa…”
   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”
   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”
   • [claimed-docs] “if it's shared in or integrated into Slack, it's searchable.”

   proof ↗⚑ flag

   Discord—none0/10

   No evidence Discord itself generates AI insights or suggestions from a user's data; evidence only covers bots/APIs, webhooks, threads, Nitro perks, and the Social SDK, none of which describe native AI-generated insights inside the product.

   ⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Slack
   Slack✓fullclaimed7/10

   Slack's Workflow Builder lets users build no-code automations with triggers (including webhook triggers from outside Slack) and conditional branching that run autonomously in the background once configured, and the Events API/CLI/Bolt frameworks let developers build bots/apps that respond to activity without manual intervention. This directly satisfies the 'autonomous background automation' story for AI-native and non-technical users alike. missing for 10: independent/hands-on verification that these automations run reliably unattended over time, and explicit AI-agent-triggered automation examples beyond marketing copy

   • [claimed-docs] “Workflow Builder is a no-code way to build workflows, right in Slack. Any user can combine a limited set of steps and triggers to quickly se…”
   • [claimed-docs] “Webhook triggers for workflows - How to start a workflow from outside of Slack.”
   • [claimed-docs] “Add a branch to a workflow - How to add conditional branching that will present users with different options based on their interaction with…”
   • [claimed-docs] “Workflow Builder is a no-code way to build workflows, right in Slack.”
   • [claimed-docs] “Webhook triggers for workflows”
   • [claimed-docs] “Add a branch to a workflow”
   • [claimed-docs] “Subscribe to only the events you want; don't worry about the ones you don't need.”
   • [claimed-docs] “When you use the Events API, Slack calls you.”
   • [claimed-docs] “The Events API is a streamlined way to build apps and bots that respond to activities in Slack.”

   proof ↗⚑ flag

   Discord~partialclaimed5/10

   Discord's developer platform provides Gateway (persistent WebSocket) and webhook APIs that let bots run continuously in the background reacting to events, and third parties can build bots that act autonomously (e.g., CI/CD notifications). However, this requires custom bot development rather than a built-in no-code 'automation' feature for end users, and there's no evidence of a first-party AI-native automation/workflow builder. Missing for 10: native no-code automation/workflow feature for non-developer users, AI-specific automation tooling, and independent evidence of autonomous background agents working reliably in practice.

   • [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild”
   • [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild, …”
   • [claimed-docs] “Webhooks are a low-effort way to post messages to channels in Discord. They do not require a bot user or authentication to use.”
   • [claimed-docs] “CI/CD pipelines posting build results or deployment notifications”
   • [claimed-docs] “Send messages into Discord channels or receive event notifications from Discord delivered to your app over HTTP.”
   • [claimed-docs] “Authenticating with the Discord API can be done in one of two ways: 1. Using a bot token... 2. Using an OAuth2 bearer token”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Slack
   Slack✓fullclaimed7/10

   Slack ships Slackbot as a built-in AI agent that can summarize channels, prepare meeting briefs, analyze reports, answer open-ended questions, and act on tasks like updating deals or routing work to other agents (slack-docs-13,14,15,38,55,57,69). This is a native, in-product delegation capability, not just a third-party integration. Missing for 10: independent/hands-on user reports confirming Slackbot's agentic task delegation works as advertised, and more detail on the scope of actions it can autonomously perform beyond summarization/Q&A.

   • [claimed-docs] “Today is your new intelligent briefing that signals what needs your attention based on your priorities.”
   • [claimed-docs] “Slackbot is your personal AI agent in Slack that understands you and your workspace, helping you prepare for upcoming meetings, analyze repo…”
   • [claimed-docs] “AI in Slack can summarize channels and threads and serve up daily recaps, giving you the information you need to stay organized and in the k…”
   • [claimed-docs] “Update deals just by asking Slackbot”
   • [claimed-docs] “Slackbot can now dig deep on open-ended questions, not just quick ones.”
   • [claimed-docs] “Slackbot just got a full-screen workspace built for deeper work.”
   • [claimed-docs] “Route work through Slackbot. Coordinate work by routing requests to agents and get results delivered right back into your workflow.”

   proof ↗⚑ flag

   Discord—none0/10

   Discord's evidence covers building bots/apps via developer APIs, but there is no evidence of a built-in first-party AI assistant that users can delegate tasks to within the product itself.

   ⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Slack
   Slack✓fullclaimed7/10

   Slack ships Slackbot as an in-product AI agent that responds to natural-language requests (e.g., 'Update deals just by asking Slackbot', daily briefings, summarization, open-ended Q&A) and exposes an official MCP server so AI assistants can search, message, and manage Slack objects via natural language. This directly supports NL-command operation for AI-native users. missing for 10: independent/hands-on validation of Slackbot NL command accuracy and reliability, and clearer documentation of the scope/limits of what natural-language commands can trigger (vs. workflow builder's no-code but still menu-driven automations).

   • [claimed-docs] “Today is your new intelligent briefing that signals what needs your attention based on your priorities.”
   • [claimed-docs] “Slackbot is your personal AI agent in Slack that understands you and your workspace, helping you prepare for upcoming meetings, analyze repo…”
   • [claimed-docs] “AI in Slack can summarize channels and threads and serve up daily recaps, giving you the information you need to stay organized and in the k…”
   • [claimed-docs] “Update deals just by asking Slackbot”
   • [claimed-docs] “Slackbot can now dig deep on open-ended questions, not just quick ones.”
   • [claimed-docs] “Slackbot just got a full-screen workspace built for deeper work.”
   • [claimed-docs] “AI agents can now read, write, and manage your Slack Lists directly.”
   • [claimed-docs] “Once connected, your AI assistant can search channels, read messages, and use real conversation context to help you build.”
   • [claimed-docs] “your integrated apps can search channels, send messages, and perform other Slack actions through MCP clients”
   • [claimed-docs] “The Slack MCP server provides tools for searching through Slack, retrieving and sending messages, managing canvases, managing users, uploadi…”

   proof ↗⚑ flag

   Discord—none0/10

   Discord's documented command system is built around structured slash commands, buttons, and modals (discord-docs-7/8/9/19/28/48), not natural-language interpretation of user requests; no evidence shows Discord itself parses free-form natural language to drive actions. The axis is plausible for a chat platform but nothing in the evidence demonstrates it.

   • [claimed-docs] “Slash commands are the most common type of command and are accessed by typing `/` in the chat input, or by opening the command picker.”
   • [claimed-docs] “Buttons are clickable components that can be customized with different styles, texts, and emoji.”
   • [claimed-docs] “Modals are single-user pop-up interfaces that allow apps to collect form-like data.”
   • [claimed-docs] “Application commands provide users a native way to invoke an app in Discord.”
   • [claimed-docs] “Application commands provide users a native way to invoke an app in Discord. They often map to an app’s core features or functionality.”
   • [claimed-docs] “Interactive features like commands and message components allows users to invoke an app natively within Discord.”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Slack—none0/10

   Slack has API method reference docs (e.g. chat.postMessage) and an OpenAPI/AsyncAPI spec repo, but there is no evidence of an interactive, runnable API reference (e.g. a Swagger/try-it console); a direct probe for openapi.json/swagger.json on the docs site returned 404s, indicating no in-browser interactive reference exists.

   • [claimed-docs] “Sends a message to a channel.”
   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.slack.dev/openapi.json, https://docs.slack.dev/swagger.json, https://docs.slack.dev/api…”

   proof ↗⚑ flag

   Discord—none0/10

   Discord's developer docs describe REST/Gateway/OAuth2 concepts and provide markdown-based reference pages, but the probe explicitly found no OpenAPI/Swagger spec (all candidate paths 404'd) and no evidence of an interactive, runnable-example API console or sandbox exists in the pack.

   • [claimed-docs] “The Discord API is a REST API that allows you to interact with Discord data from your own applications.”
   • [claimed-docs] “Authenticating with the Discord API can be done in one of two ways:”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.discord.com/openapi.json, https://docs.discord.com/swagger.json, https://docs.discord.c…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to Slack
   Slack~partialprobed6/10

   An official OpenAPI 2.0 spec for the Web API (and AsyncAPI spec for Events API) exists in the slackapi/slack-api-specs GitHub repo, satisfying the core ask of a machine-readable spec. However, live probes show the obvious/expected locations on docs.slack.dev (openapi.json, swagger.json, etc.) all 404, meaning the spec isn't directly downloadable from the primary docs site and requires knowing about a separate GitHub repo. Missing for 10: direct download link from docs.slack.dev, first-party documentation pointing users to the spec repo, and independent confirmation the spec is kept in sync with the live API.

   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.slack.dev/openapi.json, https://docs.slack.dev/swagger.json, https://docs.slack.dev/api…”
   • [claimed-docs] “The Slack Web API is an interface for querying information from and enacting change in a Slack workspace.”
   • [claimed-docs] “The Slack Web API is an interface for querying information _from_ and enacting change _in_ a Slack workspace.”

   proof ↗⚑ flag

   Discord—none0/10

   Discord provides REST API documentation and an llms.txt for docs indexing, but a direct probe for OpenAPI/swagger specs at all standard paths (openapi.json, swagger.json, api/openapi.json, .well-known/openapi.json) returned 404s, indicating no downloadable machine-readable API spec is published.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.discord.com/openapi.json, https://docs.discord.com/swagger.json, https://docs.discord.c…”
   • [claimed-docs] “The Discord API is a REST API that allows you to interact with Discord data from your own applications.”

   proof ↗⚑ flag

3. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round to Slack
   Slack~partialclaimed6/10

   Slack maintains official OpenAPI specs for its Web API and a dated, running deprecation changelog with explicit migration windows (e.g., classic app deprecation date), which supports documented deprecation policy; the Web API and Events API references also show first-party API documentation. However, there's no explicit evidence of a formal API versioning scheme (e.g., v1/v2 endpoint versioning) beyond method-level docs and changelog dates. Missing for 10: explicit versioning scheme documentation, independent/community corroboration of deprecation practices being honored reliably.

   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [claimed-docs] “api.slack.com/changelog/deprecations is a running, dated log of API deprecation announcements with migration windows, e.g. "We'd like to upd…”
   • [claimed-docs] “The Slack Web API is an interface for querying information from and enacting change in a Slack workspace.”
   • [claimed-docs] “The Slack Web API is an interface for querying information _from_ and enacting change _in_ a Slack workspace.”

   proof ↗⚑ flag

   Discord—none0/10

   The evidence pack covers Discord's API surfaces (REST, Gateway, OAuth2, webhooks, Social SDK) but contains no documentation or mention of API versioning scheme, version deprecation timelines, or a changelog/deprecation policy for developers to rely on. Missing for 10: explicit API version documentation (e.g., v9/v10), a published deprecation policy, and changelog/migration guides.

   • [claimed-docs] “The Discord API is a REST API that allows you to interact with Discord data from your own applications.”
   • [claimed-docs] “Authenticating with the Discord API can be done in one of two ways: 1. Using a bot token... 2. Using an OAuth2 bearer token”
   • [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild”

   proof ↗⚑ flag

Apps

1. team-adminInstall prebuilt integrations from an app directory or marketplace

   weight 3 · round to Slack
   Slack✓fullclaimed8/10

   Slack explicitly advertises an App Directory with 2,600+ prebuilt apps (Salesforce, Jira, Google Drive, ChatGPT, etc.) and a help doc specifically for admins on how to add apps to a workspace. This directly matches the team-admin persona and app-platform theme. missing for 10: independent/hands-on confirmation of the admin install/approval workflow beyond the docs, and no detail on admin-specific approval controls for directory apps (only MCP client approval is mentioned).

   • [claimed-docs] “Choose from over 2,600 apps in the Slack App Directory — from Salesforce, Jira, Google Drive, ChatGPT, and more.”
   • [claimed-docs] “Add apps to your Slack workspace”
   • [claimed-docs] “Connect, simplify, and automate. Discover the power of apps and tools.”

   proof ↗⚑ flag

   Discord~partialclaimed6/10

   Discord's docs confirm an App Directory — a searchable hub where users can browse apps/bots by name, category, or collection and add them to servers — which functions as a marketplace for prebuilt integrations (bots/apps). However, the evidence is entirely first-party docs about developer discovery/listing mechanics, with no detail on the admin-side installation/permission flow or independent confirmation of the experience. Missing for 10: independent/hands-on evidence of the admin installation UX, documentation of admin permission controls for installing apps, and confirmation beyond discovery-focused developer docs.

   • [claimed-docs] “Once you've enabled discovery for your app, users can find it in the App Directory — a searchable hub where they can browse by name, categor…”
   • [claimed-docs] “Once you’ve enabled discovery for your app, users can find it in the App Directory — a searchable hub where they can browse by name, categor…”
   • [claimed-docs] “users can find it in the App Directory — a searchable hub where they can browse by name, category, or collection.”
   • [claimed-docs] “users can find it in the App Directory — a searchable hub where they can browse by name”
   • [claimed-docs] “Create shareable links to your app's profile page, store page, or specific items. Share these links in Discord, emails, or on your website.”

   proof ↗⚑ flag

2. developerRegister custom slash commands that users invoke from the message box

   weight 2 · round to Discord
   Slack—none0/10

   The evidence pack covers Slack's general app-platform tooling (CLI, Bolt frameworks, Web/Events APIs, Block Kit, Workflow Builder, MCP server) but never mentions slash commands specifically as a registrable app feature invoked from the message box.

   ⚑ flag

   Discord✓fullclaimed8/10

   Discord's docs clearly document slash commands ('application commands') as a native way for users to invoke apps by typing `/` in the chat box, with dedicated interactions/overview documentation covering registration and behavior. Missing for 10: independent hands-on developer corroboration and details on the actual registration API/code sample within this evidence pack.

   • [claimed-docs] “Slash commands are the most common type of command and are accessed by typing `/` in the chat input, or by opening the command picker.”
   • [claimed-docs] “Application commands provide users a native way to invoke an app in Discord.”
   • [claimed-docs] “Application commands provide users a native way to invoke an app in Discord. They often map to an app’s core features or functionality.”
   • [claimed-docs] “Interactive features like commands and message components allows users to invoke an app natively within Discord.”

   proof ↗⚑ flag

3. developerBuild apps with rich interactive UI inside chat — modals, buttons, and structured message layouts

   weight 2 · round to Slack
   Slack✓fullclaimed9/10

   Slack's Block Kit is explicitly documented as the JSON-based framework for building modals, messages, and tabs with the same building blocks, backed by chat.postMessage's structured 'blocks' parameter, plus SDKs (Bolt for Java/Python/JS, Node Slack SDK) and CLI tooling to build these apps. This directly matches the story of building rich interactive UI (modals, buttons, structured layouts) inside Slack chat. Missing for 10: no independent/hands-on developer corroboration of the Block Kit UI-building experience beyond first-party docs.

   • [claimed-docs] “Whether you're composing layouts for modals, messages, or tabs, the Block Kit building experience is the same — your app will be sculpting s…”
   • [claimed-docs] “A JSON-based array of structured blocks, presented as a URL-encoded string.”
   • [claimed-docs] “Sends a message to a channel.”
   • [claimed-docs] “This quickstart guide covers how to create a Slack app using the Slack CLI and the Bolt frameworks, in either Python or JavaScript.”
   • [claimed-docs] “Bolt for Java is a framework on the JVM that offers an abstraction layer to build Slack apps using modern platform features.”
   • [claimed-docs] “Send data to or query data from Slack using any of more than 200 methods.”
   • [claimed-docs] “The Slack command-line interface (CLI) allows you to create and manage Slack apps from the command line.”

   proof ↗⚑ flag

   Discord✓fullclaimed8/10

   Discord's developer docs explicitly document buttons, modals, slash/application commands, and message components as first-party interaction features for building rich in-chat UI (discord-docs-7,8,9,19,48). This directly matches the story's core ask. Missing for 10: no independent/hands-on developer corroboration of building a full interactive app, and no detail on select menus or full structured layout components beyond buttons/modals.

   • [claimed-docs] “Slash commands are the most common type of command and are accessed by typing `/` in the chat input, or by opening the command picker.”
   • [claimed-docs] “Buttons are clickable components that can be customized with different styles, texts, and emoji.”
   • [claimed-docs] “Modals are single-user pop-up interfaces that allow apps to collect form-like data.”
   • [claimed-docs] “Application commands provide users a native way to invoke an app in Discord.”
   • [claimed-docs] “Interactive features like commands and message components allows users to invoke an app natively within Discord.”
   • [claimed-docs] “Application commands provide users a native way to invoke an app in Discord. They often map to an app’s core features or functionality.”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round drawn
   Slack—none0/10

   Slack's Web API and MCP server document single-item actions (send one message, upload one file, create one list entry, etc.) with no documented batch/bulk endpoints or MCP tools for operating across many items in one call. Workflow Builder and automations are trigger-based, not bulk-operation mechanisms, and export tools are admin-only data dumps rather than AI-native bulk actions.

   ⚑ flag

   Discord—none0/10

   The evidence pack covers Discord's bot/API docs, OAuth2, webhooks, slash commands, and Social SDK, but nothing describes bulk endpoints or batch operations (e.g., bulk message delete, mass channel/role management) that an AI-native user could invoke to act on many items at once.

   ⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Slack
   Slack✓fullclaimed8/10

   Slack's Workflow Builder lets users define triggers, conditional branches, and webhook-based automations that fire actions on events (message posted, emoji reaction, webhook call, etc.), directly matching the story; the Events API further supports event-driven automation. missing for 10: independent/hands-on verification of workflow trigger reliability and no evidence of AI-native rule authoring beyond no-code builder.

   • [claimed-docs] “Workflow Builder is a no-code way to build workflows, right in Slack. Any user can combine a limited set of steps and triggers to quickly se…”
   • [claimed-docs] “Webhook triggers for workflows - How to start a workflow from outside of Slack.”
   • [claimed-docs] “Add a branch to a workflow - How to add conditional branching that will present users with different options based on their interaction with…”
   • [claimed-docs] “Webhook triggers for workflows”
   • [claimed-docs] “Add a branch to a workflow”
   • [claimed-docs] “Subscribe to only the events you want; don't worry about the ones you don't need.”
   • [claimed-docs] “When you use the Events API, Slack calls you.”
   • [claimed-docs] “The Events API is a streamlined way to build apps and bots that respond to activities in Slack.”

   proof ↗⚑ flag

   Discord~partialclaimed4/10

   Discord's Gateway API lets developer-built bots subscribe to server events and act on them, and webhooks let external systems post to Discord on events (e.g. CI/CD triggers), giving a technical path to event-driven automation. However, there is no evidence of a native, no-code 'if this then that' rule-builder for end users — all automation requires writing and hosting a bot/webhook integration. Missing for 10: a first-party no-code automation/rules UI, evidence of AI-native rule triggers, and independent confirmation that non-developer users can set this up.

   • [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild”
   • [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild, …”
   • [claimed-docs] “CI/CD pipelines posting build results or deployment notifications”
   • [claimed-docs] “Send messages into Discord channels or receive event notifications from Discord delivered to your app over HTTP.”
   • [claimed-docs] “Webhooks are a low-effort way to post messages to channels in Discord. They do not require a bot user or authentication to use.”

   proof ↗⚑ flag

Ai agents

1. ai-native userAdd an AI agent as a member of a channel that participates in conversations when mentioned

   weight 3 · round to Slack
   Slack✓fullclaimed7/10

   Slack's Events API lets bots/apps respond to activity in channels ('Slack calls you'), and its ecosystem explicitly supports adding AI agents like ChatGPT, Claude, and Slackbot as channel-integrated participants that act on mentions/requests (e.g. 'start using tools like ChatGPT, Claude... within your chats', 'Route work through Slackbot... routing requests to agents', 'Coding agents can now work with your whole team'). Combined with the CLI/Bolt SDKs for building bot apps that join channels, this shows the underlying capability is well supported. Missing for 10: explicit first-party documentation of the app_mention event/scope specifically triggering agent responses, and independent hands-on confirmation that a mentioned agent reliably replies in-channel.

   • [claimed-docs] “The Events API is a streamlined way to build apps and bots that respond to activities in Slack.”
   • [claimed-docs] “When you use the Events API, Slack calls you.”
   • [claimed-docs] “With the Events API, _Slack_ calls _you_.”
   • [claimed-docs] “Slackbot is your personal AI agent in Slack that understands you and your workspace, helping you prepare for upcoming meetings, analyze repo…”
   • [claimed-docs] “Coding agents can now work with your whole team, not just you.”
   • [claimed-docs] “Route work through Slackbot. Coordinate work by routing requests to agents and get results delivered right back into your workflow.”
   • [claimed-docs] “Easily connect agents, software, and all your apps in just a few clicks, and start using tools like ChatGPT, Claude, and Asana right within …”
   • [claimed-docs] “By connecting them to your conversations and data in Slack, agents like Agentforce, ChatGPT, Claude, Notion, Slackbot, and Writer become eve…”
   • [claimed-docs] “The Slack command-line interface (CLI) allows you to create and manage Slack apps from the command line.”
   • [claimed-docs] “This quickstart guide covers how to create a Slack app using the Slack CLI and the Bolt frameworks, in either Python or JavaScript.”

   proof ↗⚑ flag

   Discord~partialclaimed6/10

   Discord's developer docs show a full bot platform — bot tokens, Gateway API for real-time message/event delivery, and application commands — that supports building an AI agent as a bot member of a server/channel, which is the standard mechanism for mention-triggered response bots. However, the evidence never explicitly documents mention-detection or an AI-agent-specific integration pattern, and there's no first-party or hands-on example of an AI agent responding when @mentioned in a channel. Missing for 10: explicit docs/example on mention-based triggering, hands-on/independent evidence of an AI agent bot working this way in production.

   • [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild”
   • [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild, …”
   • [claimed-docs] “Authenticating with the Discord API can be done in one of two ways: 1. Using a bot token... 2. Using an OAuth2 bearer token”
   • [claimed-docs] “Application commands provide users a native way to invoke an app in Discord.”
   • [claimed-docs] “Slash commands are the most common type of command and are accessed by typing `/` in the chat input, or by opening the command picker.”
   • [claimed-docs] “Build bots and integrations on Discord, or connect your game with rich presence, voice chat, and more.”

   proof ↗⚑ flag

2. ai-native userHave an agent read and post channel messages through the official API using scoped tokens

   weight 3 · round drawn
   Slack✓fullclaimed8/10

   Slack's official Web API (chat.postMessage, chat.history-type methods via OpenAPI spec covering user/bot token usage) plus scoped OAuth tokens is well documented, enabling agents to read and post channel messages programmatically; the MCP server and SDKs (Bolt, node-slack-sdk) further formalize agent access with admin-approved scopes. missing for 10: no independent hands-on developer report confirming real-world token-scoping friction or reliability at scale, and no explicit doc excerpt enumerating channel-read scopes (e.g., channels:history) alongside chat:write in one place.

   • [claimed-docs] “The Slack Web API is an interface for querying information from and enacting change in a Slack workspace.”
   • [claimed-docs] “The Slack Web API is an interface for querying information _from_ and enacting change _in_ a Slack workspace.”
   • [claimed-docs] “Sends a message to a channel.”
   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [claimed-docs] “your integrated apps can search channels, send messages, and perform other Slack actions through MCP clients”
   • [claimed-docs] “The Slack MCP server provides tools for searching through Slack, retrieving and sending messages, managing canvases, managing users, uploadi…”
   • [claimed-docs] “Workspace admins can approve and manage all MCP client integrations, keeping your Slack data safe.”
   • [claimed-docs] “Send data to or query data from Slack using any of more than 200 methods.”

   proof ↗⚑ flag

   Discord✓fullclaimed8/10

   Discord's official REST/Gateway API supports bot tokens and OAuth2 bearer tokens scoped to specific permissions, allowing an agent (bot) to read and post channel messages via documented endpoints and real-time Gateway events. missing for 10: no independent hands-on confirmation of an AI agent specifically using scoped tokens for message read/post, and no explicit documentation of granular message-read/post scopes beyond general bot/OAuth2 token mechanics.

   • [claimed-docs] “Authenticating with the Discord API can be done in one of two ways: 1. Using a bot token... 2. Using an OAuth2 bearer token”
   • [claimed-docs] “Using a bot token found on the Bot page within your app’s settings... Using an OAuth2 bearer token gained through the OAuth2 API.”
   • [claimed-docs] “The Discord API is a REST API that allows you to interact with Discord data from your own applications.”
   • [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild”
   • [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild, …”
   • [claimed-docs] “OAuth2 enables application developers to build applications that utilize authentication and data from the Discord API.”
   • [claimed-docs] “The first step in implementing OAuth2 is registering a developer application and retrieving your client ID and client secret.”

   proof ↗⚑ flag

Bot api

1. developerPost a message into a channel with a simple incoming webhook URL

   weight 2 · round to Discord
   Slack~partialclaimed5/10

   Slack's docs evidence shows webhook-based triggers for Workflow Builder ("how to start a workflow from outside of Slack") and the chat.postMessage Web API method for sending messages, both of which can be used to post into a channel from an external system, but neither is the classic single-URL 'Incoming Webhook' integration developers commonly expect. Missing for 10: explicit documentation of the dedicated Incoming Webhooks app/URL for zero-config posting, and any hands-on confirmation that a bare webhook POST (without workflow setup or OAuth token) posts a message.

   • [claimed-docs] “Webhook triggers for workflows - How to start a workflow from outside of Slack.”
   • [claimed-docs] “Webhook triggers for workflows”
   • [claimed-docs] “Sends a message to a channel.”
   • [claimed-docs] “The Slack Web API is an interface for querying information from and enacting change in a Slack workspace.”

   proof ↗⚑ flag

   Discord✓fullclaimed9/10

   Discord's docs explicitly describe incoming webhooks as a low-effort way to post messages to channels without requiring a bot user or authentication, and give concrete use cases like CI/CD pipelines posting notifications via HTTP. This directly matches the story of simple webhook-based posting. Missing for 10: independent hands-on developer confirmation of the webhook flow working in practice.

   • [claimed-docs] “Webhooks are a low-effort way to post messages to channels in Discord. They do not require a bot user or authentication to use.”
   • [claimed-docs] “They do not require a bot user or authentication to use.”
   • [claimed-docs] “CI/CD pipelines posting build results or deployment notifications”
   • [claimed-docs] “Send messages into Discord channels or receive event notifications from Discord delivered to your app over HTTP.”

   proof ↗⚑ flag

2. developerBuild a bot that receives messages and events in real time through an events API or gateway connection

   weight 3 · round drawn
   Slack✓fullclaimed9/10

   Slack's Events API is explicitly documented to push real-time events to developer-built apps/bots via HTTP endpoint or Socket Mode, with subscription filtering, and this is complemented by SDKs (Bolt for Java, Node SDK) and quickstart guides for building bots. Missing for 10: independent hands-on developer corroboration of reliability/latency of the events pipeline beyond first-party docs.

   • [claimed-docs] “Subscribe to only the events you want; don't worry about the ones you don't need.”
   • [claimed-docs] “When you use the Events API, Slack calls you.”
   • [claimed-docs] “When you use the Events API, _Slack_ calls _you_. ... you can either use Socket Mode or you can designate a public HTTP endpoint”
   • [claimed-docs] “The Events API is a streamlined way to build apps and bots that respond to activities in Slack.”
   • [claimed-docs] “With the Events API, _Slack_ calls _you_.”
   • [claimed-docs] “Bolt for Java is a framework on the JVM that offers an abstraction layer to build Slack apps using modern platform features.”
   • [claimed-docs] “Send data to or query data from Slack using any of more than 200 methods.”
   • [claimed-docs] “This quickstart guide covers how to create a Slack app using the Slack CLI and the Bolt frameworks, in either Python or JavaScript.”

   proof ↗⚑ flag

   Discord✓fullclaimed9/10

   Discord's documented Gateway API explicitly provides secure WebSocket connections for apps to receive real-time events (channel updates, role creation, etc.), and bot token authentication plus REST API access complete the developer bot-building path. Webhooks are also documented as an alternative for receiving/posting event notifications over HTTP. Missing for 10: independent hands-on developer confirmation of gateway reliability/rate limits and no direct community corroboration of real-time event handling in production.

   • [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild”
   • [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild, …”
   • [claimed-docs] “Authenticating with the Discord API can be done in one of two ways: 1. Using a bot token... 2. Using an OAuth2 bearer token”
   • [claimed-docs] “The Discord API is a REST API that allows you to interact with Discord data from your own applications.”
   • [claimed-docs] “Send messages into Discord channels or receive event notifications from Discord delivered to your app over HTTP.”

   proof ↗⚑ flag

Ai notes

1. ai-native userGet AI-generated notes and recaps from meetings and huddles I attended or missed

   weight 2 · round to Slack
   Slack✓fullclaimed8/10

   Slack's docs directly claim AI note-taking for huddles (key takeaways, action items, who said what compiled at huddle end) and AI-generated channel/thread summaries and daily recaps for content missed, matching the story's core ask. Missing for 10: independent/hands-on corroboration of huddle-note accuracy or completeness, and no explicit confirmation that recaps cover 'missed' meetings specifically (recaps are framed around channels/threads more than scheduled meetings).

   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”
   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”
   • [claimed-docs] “AI in Slack can summarize channels and threads and serve up daily recaps, giving you the information you need to stay organized and in the k…”
   • [claimed-docs] “Create time-saving automations in a few clicks, translate conversations into any language, and even use AI to take meeting notes.”
   • [claimed-docs] “translate conversations into any language, and even use AI to take meeting notes”
   • [claimed-docs] “If it's shared in a huddle, it's saved in Slack. Any links, documents, and messages shared during a huddle are automatically saved once the …”
   • [claimed-docs] “If it's shared in a huddle, it's saved in Slack.”

   proof ↗⚑ flag

   Discord—none0/10

   No evidence of any AI-generated meeting notes, transcription, or recap feature for Discord voice/huddle calls; the evidence pack covers bots, APIs, webhooks, Social SDK, and Nitro perks but nothing about AI summarization of calls. Missing for 10: any documentation or feature reference to AI-generated call transcripts, summaries, or recap generation.

   ⚑ flag

Calls

1. team-adminStart an audio or video call directly from a channel or DM without leaving the app

   weight 3 · round to Slack
   Slack✓fullclaimed8/10

   Slack's Huddles feature lets any user click the headphones icon in a channel/DM header to instantly start audio or video calls with screen sharing, all inside the app, and includes admin-manageable extras like AI notes and saved shared content. missing for 10: no explicit documentation of admin-specific controls/permissions for enabling or restricting huddles, and no independent hands-on corroboration beyond Slack's own marketing docs.

   • [claimed-docs] “Simply click on the headphones icon in the conversation header to start a huddle with your team.”
   • [claimed-docs] “Huddles happen right in Slack. Instantly connect over audio or video and share screens so you can get more done where you're already working…”
   • [claimed-docs] “Bring the feeling of working side-by-side to a virtual space that lets you collaborate and co-create live.”
   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”
   • [claimed-docs] “If it's shared in a huddle, it's saved in Slack. Any links, documents, and messages shared during a huddle are automatically saved once the …”
   • [claimed-docs] “Emoji reactions. Colorful backgrounds. Delightful effects. In huddles, teams can express themselves to make being together even better.”

   proof ↗⚑ flag

   Discord—none0/10

   The evidence pack contains only developer/API documentation (bots, webhooks, OAuth2, Social SDK for games) and community commentary on unrelated topics like verification and moderation; none of it documents the core client feature of a user/admin starting a voice or video call directly from a text channel or DM inside the Discord app itself. Mentions of 'voice chat' (discord-docs-3, discord-docs-41) refer to the Social SDK for third-party games, not native in-app calling.

   • [claimed-docs] “Add rich presence, voice chat, and social features to your game across all platforms.”
   • [claimed-docs] “Build bots and integrations on Discord, or connect your game with rich presence, voice chat, and more.”

   proof ↗⚑ flag

2. team-adminShare my screen during a call for live collaboration

   weight 2 · round to Slack
   Slack✓fullclaimed7/10

   Slack huddles explicitly support instant audio/video connection with screen sharing directly in the conversation, usable by any team member including admins, per first-party docs (slack-docs-33, slack-docs-66, slack-docs-18). However, missing for 10: independent/hands-on corroboration of screen-share quality or reliability, and no explicit admin-specific controls or documentation around screen sharing during calls beyond the general huddles feature description.

   • [claimed-docs] “Huddles happen right in Slack. Instantly connect over audio or video and share screens so you can get more done where you're already working…”
   • [claimed-docs] “Huddles happen right in Slack. Instantly connect over audio or video and share screens so you can get more done where you’re already working…”
   • [claimed-docs] “Simply click on the headphones icon in the conversation header to start a huddle with your team.”
   • [claimed-docs] “Bring the feeling of working side-by-side to a virtual space that lets you collaborate and co-create live.”

   proof ↗⚑ flag

   Discord—none0/10

   The evidence pack contains extensive Discord developer/API docs and community commentary but no mention of native screen-sharing during voice/video calls, which is the core capability the story asks about. Absence of evidence for this mainstream Discord feature means it cannot be credited even though it likely exists in the product.

   ⚑ flag

External collaboration

1. team-adminCollaborate with external partners through guest accounts or shared channels with limited access

   weight 2 · round drawn
   Slack—none0/10

   The evidence pack contains no mention of guest accounts, Slack Connect, or shared/external channels with limited access — nothing about admin controls for external collaboration appears anywhere in the docs, community, or probe items. This is a mainstream, applicable capability for a workspace chat product, but absence of evidence means it cannot be credited.

   ⚑ flag

   Discord—none0/10

   The evidence pack shows Discord's developer platform, threads, and Nitro features but contains no mention of guest accounts, cross-org shared channels, or admin-controlled limited-access partner collaboration akin to Slack Connect. Threads (discord-docs-37, discord-docs-38) are an internal channel-branching feature, not external partner access control.

   ⚑ flag

Messaging model

1. team-adminOrganize conversations into public and private channels with membership controls

   weight 3 · round to Discord
   Slack—none0/10

   The evidence pack focuses almost entirely on Slack's AI/MCP tooling, developer SDKs, huddles, and integrations, with no first-party documentation describing channel creation, public vs. private channel types, or admin membership controls. The only channel-related mentions (e.g., MCP 'search channels', a raw SEO keyword list) do not document this admin capability.

   ⚑ flag

   Discord~partialclaimed5/10

   Evidence confirms Discord supports organizing conversations into public and private sub-conversations (Threads, including 'Private Threads... rolling out to all servers') via discord-docs-37/38, which aligns with channel-like organization, but the pack contains no documentation of full channel-level permission/role systems, member/channel visibility controls, or admin management of channel membership that would fully substantiate the 'membership controls' part of the story. Missing for 10: explicit docs on channel permission overwrites/roles, admin UI for private channel membership, and any independent confirmation of these controls working as described.

   • [claimed-docs] “A Thread is a quick way to branch a conversation off of a channel’s main feed without removing it from the channel itself.”
   • [claimed-docs] “Private Threads are now available for all servers! This exciting update is rolling out to both desktop and mobile users now.”

   proof ↗⚑ flag

2. team-adminReply in threads so side discussions stay attached to the original message

   weight 3 · round to Discord
   Slack~partialcommunity3/10

   No first-party Slack documentation in this evidence pack describes the threading/reply feature directly; the only evidence that threads exist comes from community complaints (comm-12, comm-14) confirming the feature is used but describing it as poorly notified, hard to find replies, and 'close to impossible to use' as a tiny side panel with missing capabilities (snippets/files/slash commands not working in threads). This suggests threads function but with real UX friction, not a clean full delivery. Missing for 10: official docs/screenshots describing thread-reply UX, independent confirmation that reply notifications and thread views work smoothly, and resolution of the cited usability complaints.

   • [community] “My biggest pain point is Slack's awful implementation of threads - you only get notified of new thread replies in a 'New Threads' view that …”
   • [community] “Zulip is a very good fit for open source communities, and much much better for communication than Slack. Slack encourages saying everything …”

   proof ↗⚑ flag

   Discord~partialclaimed6/10

   Discord's blog docs confirm threads let users branch off a channel's main feed without removing context, including private threads for servers, which supports side-discussions staying attached to the original message. However, evidence doesn't explicitly confirm 'reply in thread' UX specifics or admin-specific thread controls. missing for 10: explicit documentation of admin thread permission controls, reply-to-message-in-thread UX detail, independent/hands-on corroboration beyond blog announcement.

   • [claimed-docs] “A Thread is a quick way to branch a conversation off of a channel’s main feed without removing it from the channel itself.”
   • [claimed-docs] “Private Threads are now available for all servers! This exciting update is rolling out to both desktop and mobile users now.”
   • [claimed-docs] “Connect the Conversation with Threads on Discord”

   proof ↗⚑ flag

3. team-adminCatch up on busy channels efficiently because every conversation is organized under a named topic or thread

   weight 2 · round drawn
   Slack!disputedcontradicted5/10

   Slack does support channel/thread organization plus AI features to summarize channels and threads for catching up (slack-docs-15, slack-docs-19, slack-docs-34), but concrete hands-on community reports say the thread implementation itself is poorly organized and hard to use — notifications don't auto-update, threads are 'a tiny section off to the side,' and Slack 'encourages saying everything in the main channel' rather than threads (slack-comm-12, slack-comm-14). This directly contradicts the premise that conversations are cleanly organized under threads for efficient catch-up. Missing for 10: independent verification that threading/summarization actually resolves the catch-up problem in practice, admin-specific tooling for enforcing thread discipline.

   • [claimed-docs] “AI in Slack can summarize channels and threads and serve up daily recaps, giving you the information you need to stay organized and in the k…”
   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”
   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”
   • [community] “My biggest pain point is Slack's awful implementation of threads - you only get notified of new thread replies in a 'New Threads' view that …”
   • [community] “Zulip is a very good fit for open source communities, and much much better for communication than Slack. Slack encourages saying everything …”

   proof ↗⚑ flag

   Discord!disputedcontradicted5/10

   Discord docs confirm threads let you branch conversations off a channel's main feed to organize topics (discord-docs-37, discord-docs-38, discord-docs-54), which is the core mechanism the story asks for. However, independent community reports describe channels/threads as chaotic when busy and poorly organized for catch-up, noting messages 'gate' content and become 'very chaotic when a lot of people are posting' and that Discord's UI/UX makes content hard to find intuitively (discord-comm-9, discord-comm-11). Missing for 10: evidence of thread-based read-state/summary tools for admins, and resolution of the chaos/discoverability complaints from real users.

   • [claimed-docs] “A Thread is a quick way to branch a conversation off of a channel’s main feed without removing it from the channel itself.”
   • [claimed-docs] “Private Threads are now available for all servers! This exciting update is rolling out to both desktop and mobile users now.”
   • [claimed-docs] “Connect the Conversation with Threads on Discord”
   • [community] “Discord, Slack, Gitter all gate messages so much, they are not well indexed by search engines and very chaotic when a lot of people are post…”
   • [community] “I think Discord UI/UX is beyond terrible and Discord is nothing more than a terrible walled garden where none of the content has any discove…”

   proof ↗⚑ flag

Notifications

1. team-adminTune notifications per channel, keyword, and schedule so only what matters interrupts me

   weight 2 · round drawn
   Slack—none0/10

   The evidence pack contains no documentation on per-channel/keyword/schedule notification preferences (e.g., mute channels, keyword alerts, do-not-disturb scheduling) — Slack's actual notification settings are not represented anywhere in this pack, only unrelated AI, workflow, MCP, and integration docs. Missing for 10: any mention of notification preferences, keyword alerts, per-channel mute/schedule controls, or admin-level notification policy tools.

   ⚑ flag

   Discord—none0/10

   The evidence pack covers developer APIs, Nitro perks, Social SDK, threads, and community complaints, but contains no mention of Discord's actual notification settings features (per-channel mute/notification level, keyword/mention alerts, or scheduled quiet hours/Do Not Disturb) that a team-admin would use to tune interruptions.

   ⚑ flag

Compliance

1. platform-engineerReview audit logs of admin and user actions across the workspace

   weight 2 · round drawn
   Slack—none0/10

   The evidence pack includes only workspace data export/import documentation (e.g., slack-docs-22/23/35/36) and community complaints about export restrictions (slack-comm-2), but nothing that documents an audit log capability tracking admin and user actions across the workspace. This is a fair and applicable axis for an enterprise collaboration platform, so absence of evidence yields 'none' rather than 'na'.

   • [claimed-docs] “Export your workspace data | Slack”
   • [claimed-docs] “Guide to Slack import and export tools | Slack”
   • [claimed-docs] “Guide to Slack import and export tools”
   • [claimed-docs] “Export your workspace data”
   • [community] “Wow, Slack does not allow business customers to export their chats freely. Corporate Export requires legal/compliance justification and Slac…”

   proof ↗⚑ flag

   Discord—none0/10

   No evidence of any audit-log feature for admin/user actions across a Discord server or workspace; the evidence pack covers developer APIs, bots, Nitro, Social SDK, and community sentiment, but nothing about compliance/audit logging capabilities for platform engineers.

   ⚑ flag

2. platform-engineerEnforce message retention policies and legal holds for compliance and eDiscovery

   weight 2 · round drawn
   Slack—none0/10

   The evidence pack shows generic data export/import guides (slack-docs-22/23/35/36) and a community note that Corporate Export requires legal/compliance justification and Slack approval (slack-comm-2), but nothing documents actual retention-policy enforcement, legal-hold placement, or eDiscovery tooling. Missing for 10: retention policy configuration, legal hold mechanism, eDiscovery search/export APIs, admin documentation on compliance holds.

   • [claimed-docs] “Export your workspace data | Slack”
   • [claimed-docs] “Guide to Slack import and export tools | Slack”
   • [claimed-docs] “Guide to Slack import and export tools”
   • [claimed-docs] “Export your workspace data”
   • [community] “Wow, Slack does not allow business customers to export their chats freely. Corporate Export requires legal/compliance justification and Slac…”

   proof ↗⚑ flag

   Discord—none0/10

   No evidence in the pack references message retention policies, legal holds, eDiscovery workflows, or compliance export tooling for platform engineers; the docs cover developer APIs, bots, Social SDK, and Nitro features only.

   ⚑ flag

Exports

1. team-adminExport the full message history of my workspace in machine-readable formats, including private conversations where policy allows

   weight 3 · round to Slack
   Slack!disputedcontradicted5/10

   Slack does document official export tools for workspace data (slack-docs-22/23/35/36), which nominally support the compliance-export story, but community evidence directly contradicts free/easy access: Corporate Export of DMs and private channels requires legal/compliance justification and Slack's approval, and users questioned whether migrating years of full message history out of Slack is even feasible under these restrictions. Missing for 10: no first-party documentation of a machine-readable format spec (JSON/CSV schema details), no evidence addressing the approval-gate friction, and no independent confirmation that large-scale/private-channel exports actually work in practice.

   • [claimed-docs] “Export your workspace data | Slack”
   • [claimed-docs] “Guide to Slack import and export tools | Slack”
   • [claimed-docs] “Guide to Slack import and export tools”
   • [claimed-docs] “Export your workspace data”
   • [community] “Wow, Slack does not allow business customers to export their chats freely. Corporate Export requires legal/compliance justification and Slac…”
   • [community] “Is it even possible to migrate 10 years of message history out of Slack? Users questioned whether such an export was even feasible given Sla…”

   proof ↗⚑ flag

   Discord—none0/10

   No evidence of any compliance-export tool, eDiscovery feature, or admin capability to export full message history (including private conversations) in machine-readable formats; the pack only covers developer APIs, bots, webhooks, Nitro, and Social SDK, none of which provide bulk/team-admin export of message history.

   ⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Slack
   Slack~partialprobed6/10

   Slack ships an extensive Web API (200+ methods per slack-docs-74), an Events API, official OpenAPI/AsyncAPI specs (slack-supp-openapi-spec), a CLI, SDKs, and an MCP server covering messaging, search, canvases, lists, and file uploads (slack-docs-8, slack-docs-28-30, slack-docs-48). However, community evidence shows a concrete gap: exporting DMs and private channel content requires legal/compliance justification and Slack approval, not open self-serve API access (slack-comm-2, slack-comm-4), and moderation tooling is described as 'purposefully useless' compared to UI expectations (slack-comm-9). Missing for 10: verified parity for admin/compliance-only UI actions (e.g., full data export, moderation controls) via API, and a public discoverable OpenAPI schema (probe shows standard openapi.json paths 404, slack-probe-2).

   • [claimed-docs] “The Slack Web API is an interface for querying information from and enacting change in a Slack workspace.”
   • [claimed-docs] “Send data to or query data from Slack using any of more than 200 methods.”
   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [claimed-docs] “The Slack MCP server provides tools for searching through Slack, retrieving and sending messages, managing canvases, managing users, uploadi…”
   • [claimed-docs] “Sends a message to a channel.”
   • [community] “Wow, Slack does not allow business customers to export their chats freely. Corporate Export requires legal/compliance justification and Slac…”
   • [community] “Is it even possible to migrate 10 years of message history out of Slack? Users questioned whether such an export was even feasible given Sla…”
   • [community] “I think 'less capable moderation tools' really undersells how purposefully useless and nonexistent Slack's moderation tools are for open com…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.slack.dev/openapi.json, https://docs.slack.dev/swagger.json, https://docs.slack.dev/api…”

   proof ↗⚑ flag

   Discord~partialprobed5/10

   Discord's developer platform exposes a broad REST/Gateway API, OAuth2, webhooks, slash commands, interactions, and a Social SDK covering messaging, presence, and account linking, showing substantial API coverage of bot/integration functionality. However, this coverage is aimed at building bots/apps rather than giving an end-user full parity with everything doable in the Discord client (e.g., no evidence of API-equivalent actions for Nitro subscription features, personal account social actions, or general UI-only settings), and the probe confirms no discoverable OpenAPI spec, suggesting the API surface isn't exhaustively documented for 1:1 parity. missing for 10: evidence of full end-user (non-bot) API parity for all client actions, an official OpenAPI/spec confirming complete surface coverage, and independent confirmation that no UI action lacks an API equivalent.

   • [claimed-docs] “Build automated apps, commands, and integrations that run inside Discord servers.”
   • [claimed-docs] “Authenticating with the Discord API can be done in one of two ways: 1. Using a bot token... 2. Using an OAuth2 bearer token”
   • [claimed-docs] “Webhooks are a low-effort way to post messages to channels in Discord. They do not require a bot user or authentication to use.”
   • [claimed-docs] “Slash commands are the most common type of command and are accessed by typing `/` in the chat input, or by opening the command picker.”
   • [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild”
   • [claimed-docs] “The Discord API is a REST API that allows you to interact with Discord data from your own applications.”
   • [claimed-docs] “Send messages into Discord channels or receive event notifications from Discord delivered to your app over HTTP.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.discord.com/openapi.json, https://docs.discord.com/swagger.json, https://docs.discord.c…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Slack
   Slack!disputedcontradicted4/10

   Slack documents a workspace data export feature (slack-docs-22/23/35/36), but concrete community evidence shows this is heavily restricted in practice: Corporate Export of DMs/private channels requires legal/compliance justification and Slack's approval (slack-comm-2), users openly question whether multi-year history can even be exported (slack-comm-4), and Slack has shut down open-protocol (IRC/XMPP) access that once enabled third-party/portable access (slack-comm-11). There's no evidence the export format is genuinely open/interoperable rather than a locked-down archive. Missing for 10: documented open export format specification, independent confirmation of unrestricted self-service export, and no contradicting reports of approval gating.

   • [claimed-docs] “Export your workspace data | Slack”
   • [claimed-docs] “Guide to Slack import and export tools | Slack”
   • [claimed-docs] “Guide to Slack import and export tools”
   • [claimed-docs] “Export your workspace data”
   • [community] “Wow, Slack does not allow business customers to export their chats freely. Corporate Export requires legal/compliance justification and Slac…”
   • [community] “Is it even possible to migrate 10 years of message history out of Slack? Users questioned whether such an export was even feasible given Sla…”
   • [community] “Slack decided to close down IRC and XMPP gateways, ending third-party client access via open protocols; the IRC gateway was the only thing t…”

   proof ↗⚑ flag

   Discord—none0/10

   No evidence of a user-facing data export/portability feature or open-format data takeout for personal Discord data; the evidence pack covers developer APIs, bots, Nitro, and community complaints (e.g., loss of contact info on server bans, walled-garden criticism) rather than any account data-export capability. Missing for 10: documented data export/takeout tool, open-format (e.g., JSON) download of messages/DMs/servers, and any account deletion+portability workflow.

   • [community] “One day I came to discover that Discord had banned the server for allegedly violating something. I wish I had written down everyone's emails…”
   • [community] “I think Discord UI/UX is beyond terrible and Discord is nothing more than a terrible walled garden where none of the content has any discove…”
   • [claimed-docs] “The Discord API is a REST API that allows you to interact with Discord data from your own applications.”

   proof ↗⚑ flag

Pricing

1. team-adminKeep my team on a free tier without losing access to older message history

   weight 2 · round to Slack
   Slack!disputedcontradicted4/10

   Slack marketing claims 'Unlimited message history' (slack-docs-43), but this benefit is documented on the pricing page and is know to apply to paid tiers, and multiple community reports concretely describe free workspaces having message/storage limits enforced, with older messages disappearing once a few thousand messages are exceeded (slack-comm-10, slack-comm-15). This directly contradicts the idea that a team-admin can stay on a free tier indefinitely without losing history. Missing for 10: an explicit first-party statement about free-tier retention limits, and any first-party pricing-page confirmation that free tier does NOT purge history.

   • [claimed-docs] “Unlimited message history Every message, file, and conversation shared in Slack is saved and fully searchable.”
   • [community] “So much information that would reduce support burdens is buried in Slacks and Discords. It can't be found through Google, and if you aren't …”
   • [community] “I have like 7 Slacks, 2 paid and 5 hobby ones I use once a month. Slack pushing storage/message limits on free workspaces feels like a tiny …”

   proof ↗⚑ flag

   Discord—none0/10

   No evidence in the pack addresses message history retention, archiving limits, or free-tier data access policies for Discord servers; the docs cover developer APIs, Nitro perks, and unrelated community topics.

   ⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Slack—none0/10

   No evidence in the pack mentions data residency, regional storage options, or geographic data controls for Slack; the evidence covers MCP servers, APIs, workflows, and AI features but nothing about choosing where data is stored. This is a fair axis for an enterprise SaaS product, but absence of evidence means it cannot be credited.

   ⚑ flag

   Discord—none0/10

   No evidence in the pack of Discord offering data residency/region selection controls for where user data is stored; documentation covers bots, APIs, SDKs, and Nitro features but nothing about data locality controls.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Slack—none0/10

   No evidence in the pack addresses AI training data opt-out or controls preventing Slack/customer data from being used to train AI models; the pack covers unrelated AI features (search, summarization, MCP server) and export/pricing controversies but nothing about AI-training data usage or opt-out settings.

   ⚑ flag

   Discord—none0/10

   No evidence of any AI-training data opt-out control, privacy setting, or policy statement addressing use of user data for AI/ML model training; evidence pack covers developer platform, bots, Nitro features, and unrelated community complaints (verification, moderation, breaches).

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Slack
   Slack!disputedcontradicted3/10

   Slack documents workspace export/import tools (data retention/deletion-adjacent controls), but community evidence explicitly says business customers can't freely export their own chats — Corporate Export requires legal/compliance justification and Slack's approval, and even feasibility of full history export is questioned. This directly contradicts the notion of straightforward user/admin control over data retention and deletion. Missing for 10: explicit documentation of configurable retention periods, deletion policies/workflows, and independent confirmation that exports/deletions can be self-served without gatekeeping.

   • [claimed-docs] “Export your workspace data | Slack”
   • [claimed-docs] “Guide to Slack import and export tools | Slack”
   • [claimed-docs] “Guide to Slack import and export tools”
   • [claimed-docs] “Export your workspace data”
   • [community] “Wow, Slack does not allow business customers to export their chats freely. Corporate Export requires legal/compliance justification and Slac…”
   • [community] “Is it even possible to migrate 10 years of message history out of Slack? Users questioned whether such an export was even feasible given Sla…”

   proof ↗⚑ flag

   Discord—none0/10

   The evidence pack contains no documentation of data retention settings, data export, or account/message deletion controls for Discord users; it only shows unrelated developer API docs and community complaints about ID verification and a data breach, none of which describe actual retention/deletion controls.

   ⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Slack—none0/10

   No evidence in the pack addresses telemetry or usage-tracking opt-out controls for Slack; the privacy/data-export items (slack-comm-2, slack-docs-22/23/35/36) relate to data export/retention, not telemetry opt-out. This axis plausibly applies to a SaaS collaboration product, but no supporting capability is documented.

   ⚑ flag

   Discord—none0/10

   No evidence of any telemetry opt-out or privacy/data-tracking settings; the evidence pack covers developer APIs, Nitro features, and community complaints about verification/breaches, none of which address telemetry opt-out controls.

   ⚑ flag

Ai catchup

1. ai-native userGet AI-generated summaries and recaps of channels and threads I missed

   weight 2 · round to Slack
   Slack✓fullclaimed8/10

   Slack's first-party AI features docs explicitly state AI in Slack can summarize channels and threads and serve daily recaps (slack-docs-15), backed by Slackbot as an intelligent daily briefing/agent (slack-docs-13, slack-docs-14) and huddle note-taking/recaps (slack-docs-19, slack-docs-34). This directly matches the story of AI-generated summaries/recaps of missed channels/threads. Missing for 10: independent/hands-on verification of summary quality or accuracy, and no community evidence corroborating real-world reliability of this specific feature (community evidence pack focuses on unrelated pain points like pricing/export/threads UX).

   • [claimed-docs] “Today is your new intelligent briefing that signals what needs your attention based on your priorities.”
   • [claimed-docs] “Slackbot is your personal AI agent in Slack that understands you and your workspace, helping you prepare for upcoming meetings, analyze repo…”
   • [claimed-docs] “AI in Slack can summarize channels and threads and serve up daily recaps, giving you the information you need to stay organized and in the k…”
   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”
   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”

   proof ↗⚑ flag

   Discord—none0/10

   No evidence of any native Discord feature that generates AI summaries or recaps of missed channels/threads; docs cover bots, OAuth2, webhooks, threads, Social SDK, and Nitro perks but nothing about AI-generated recap/summary functionality. A third-party bot could theoretically add this, but no such capability is evidenced for Discord itself.

   • [claimed-docs] “A Thread is a quick way to branch a conversation off of a channel’s main feed without removing it from the channel itself.”
   • [claimed-docs] “Private Threads are now available for all servers! This exciting update is rolling out to both desktop and mobile users now.”
   • [claimed-docs] “Connect the Conversation with Threads on Discord”

   proof ↗⚑ flag

Search

1. team-adminSearch the full message history with filters like sender, channel, and date

   weight 3 · round to Slack
   Slack~partialclaimed6/10

   Slack docs confirm full, unlimited searchable message history (slack-docs-43, slack-docs-16/52) and Slack's native search supports filtering, but the evidence pack does not explicitly document admin-specific advanced search operators (from:, in:, before:/after:) or an admin-console-level cross-workspace search UI beyond general user search claims; the MCP server also offers 'searching through Slack' but is a separate API-driven tool rather than the admin search UI itself. missing for 10: explicit documentation of native in-app search filter syntax (sender/channel/date), evidence of admin-level search scope (e.g. Enterprise-wide search across workspaces), and independent/hands-on confirmation of filter functionality.

   • [claimed-docs] “Unlimited message history Every message, file, and conversation shared in Slack is saved and fully searchable.”
   • [claimed-docs] “Conversations with coworkers, PDFs, images for your social campaign, decks buried in Google Drive, support tickets, customer records from Sa…”
   • [claimed-docs] “if it's shared in or integrated into Slack, it's searchable.”
   • [claimed-docs] “The Slack MCP server provides tools for searching through Slack, retrieving and sending messages, managing canvases, managing users, uploadi…”

   proof ↗⚑ flag

   Discord—none0/10

   The evidence pack contains no documentation or first-party reference to Discord's message search feature or its filters (sender, channel, date); all docs items focus on the developer API, bots, Nitro, and Social SDK. Community evidence even suggests messages are 'chaotic' and poorly indexed, but that speaks to external search engines, not an admin search UI, so it doesn't confirm the capability either.

   • [community] “Discord, Slack, Gitter all gate messages so much, they are not well indexed by search engines and very chaotic when a lot of people are post…”

   proof ↗⚑ flag

Workflow builder

1. team-adminBuild no-code workflows triggered by events, schedules, or form submissions inside the chat tool

   weight 3 · round to Slack
   Slack✓fullclaimed8/10

   Slack's Workflow Builder is documented as a no-code way to build workflows directly in Slack, supporting event/schedule/form-submission triggers, webhook triggers, and conditional branching. missing for 10: independent/hands-on corroboration of the builder in use, and detail on schedule-based triggers specifically beyond webhook/event mentions.

   • [claimed-docs] “Workflow Builder is a no-code way to build workflows, right in Slack. Any user can combine a limited set of steps and triggers to quickly se…”
   • [claimed-docs] “Webhook triggers for workflows - How to start a workflow from outside of Slack.”
   • [claimed-docs] “Add a branch to a workflow - How to add conditional branching that will present users with different options based on their interaction with…”
   • [claimed-docs] “Workflow Builder is a no-code way to build workflows, right in Slack.”
   • [claimed-docs] “Webhook triggers for workflows”
   • [claimed-docs] “Add a branch to a workflow”

   proof ↗⚑ flag

   Discord—none0/10

   Discord's evidence pack shows only developer-oriented building blocks—webhooks, bot tokens, Gateway API events, slash commands—which require writing and hosting code, not a no-code workflow builder for triggers/schedules/forms. There is no mention of any built-in no-code automation canvas, scheduled triggers, or form-submission triggers akin to Slack Workflow Builder or Zapier.

   • [claimed-docs] “Webhooks are a low-effort way to post messages to channels in Discord. They do not require a bot user or authentication to use.”
   • [claimed-docs] “The Gateway API lets apps open secure WebSocket connections with Discord to receive events about actions that take place in a server/guild”
   • [claimed-docs] “CI/CD pipelines posting build results or deployment notifications”
   • [claimed-docs] “Send messages into Discord channels or receive event notifications from Discord delivered to your app over HTTP.”
   • [claimed-docs] “Modals are single-user pop-up interfaces that allow apps to collect form-like data.”

   proof ↗⚑ flag