High Priority
Deploy /community.txt Protocol
Establish a machine-readable summary of your entire community hierarchy specifically for AI agents and community intelligence platforms.
Create a text file at /community.txt with a brief overview of your Slack community's purpose and core channels.
Include markdown-style links to your most important community resources, onboarding guides, and public-facing documentation.
Add a 'FAQ' section within the file to directly answer common queries about community guidelines, membership, and engagement.
Configure your Slack communities crawler protocols effortlessly.
Join 2,000+ teams scaling with AI.
High Priority
CommunityBot Selective Indexing
Fine-tune which sections of your community's public-facing content should be ingested by specialized community intelligence crawlers like those used by Slack's AI features or third-party analytics tools.
User-agent: CommunityBot Allow: /channels/general/ Allow: /channels/announcements/ Disallow: /channels/private-testing/
Verify your crawler permissions using a simulated bot crawler tool or by monitoring initial access logs.
Monitor crawl frequency in your server logs to ensure CommunityBot is accessing the intended public community data nodes.
Medium Priority
Semantic Channel Structure for Ingestion
Utilize clear channel naming conventions and topic organization to help LLM crawlers understand the hierarchy and purpose of your community content.
Group related topics under parent channels or use prefixes (e.g., 'support-', 'product-') to signal content themes.
Employ channel descriptions that clearly articulate the purpose and expected discussion topics within each channel.
Ensure pinned messages and channel topic fields are updated regularly with relevant, concise information.
High Priority
RAG-Friendly Community Snippet Optimization
Structure community discussions and documentation so they can be easily 'chunked' and utilized by Retrieval-Augmented Generation (RAG) pipelines for community insights and support.
Keep discussions and knowledge base articles within a logical context window, ideally under 500 words per distinct topic.
Avoid ambiguous references; ensure context is self-contained or explicitly links to the primary subject or channel.
Eliminate vague pronouns and replace them with specific channel names, user roles, or feature identifiers (e.g., 'the #support channel', 'community managers').
