Source: raw/Claude_Tag_+_Slack_Will_Change_How_You_Work_Forever.md

Creator: Ben AI · URL: https://www.youtube.com/watch?v=F5DXjhBqV9I · Duration: 16:30 · Platform: YouTube · Uploaded: 2026-06-28

Ben recorded this five days after Claude Tag launched, after a week of rolling it out inside his agency. It is the wiki’s only click-by-click setup of the admin side: connecting Slack, building “access bundles” (the agent profiles the official explainer calls identities), adding your own skills through a GitHub marketplace, turning a channel into a specialist agent that runs without being tagged, and loading a second brain so the whole team shares one context layer. The product facts (plans, sandboxing, identity model, later release changes) live in the main Claude Tag article; this page is the how-to.

Key Takeaways

  • Admin setup runs in the browser. claude.ai → Organization settings → Claude Tag tab. Ben hit errors in Claude Desktop during the beta and recommends the web app.
  • An access bundle is an agent profile: connectors (under Credentials), Instructions, Plugins and GitHub Repositories. Make one general bundle that every channel gets by default, then add specialist bundles per channel.
  • Your own skills need a GitHub marketplace. At recording time the Plugins tab listed only official plugins. Ask Claude Code to “help me build a skill marketplace with the skills in my account on GitHub”, connect GitHub, and the marketplace appears in the Plugins list to switch on.
  • Channel instructions make agents autonomous. “Whenever a new lead appears in this channel, run the lead researcher” fires on a Calendly notification with nobody tagging Claude.
  • Scheduled tasks are created by asking in Slack, and appear in the admin console with the audit logs.
  • Memory sits at channel and workspace level. Ben adds a standing instruction to the general agent to remember important facts, so memory files accumulate.
  • Two ways to load a second brain: upload a zip into Claude Tag memory (simple, but locked inside Claude Tag) or connect it as a GitHub repository (stays usable from other AI tools).

What Ben uses it for

  • Skills in Slack. Tagged in a thread, Claude ran his title-ideation skill, pulling transcripts of earlier videos first. Teammates added ideas in the same thread, which is the “multiplayer” use the Claude Tag article describes.
  • Specialist channel agents. In the marketing channel the agent has his YouTube repurposing skills, so “repurpose our most recent YouTube video into a LinkedIn post” runs a fixed workflow. Non-technical staff get the workflow without knowing how to prompt or which skill to call.
  • Unprompted lead research. In the sales channel a Calendly booking notice triggers the lead researcher bundle (Apify, Firecrawl and VidIQ; captions “Appify” and “Fire Call”). It finds the lead’s LinkedIn, scrapes the company site and posts a summary plus a call-prep page with company description, person summary, suggested agenda and likely objections.
  • Daily brief. “Can you please send over a daily brief every morning at 9:00 a.m. about what happened across our business in the last 24 hours. Please deliver a dashboard.”
  • Visibility as an adoption tool. Because channel threads are public, managers see what staff use AI for, and non-technical staff learn by watching colleagues. Ben’s agency has found Slack “one of the best ways to increase AI adoption across a business.” This matches Claire Vo’s public-thread argument in the main article.

Setup, step by step

  1. Check the plan. Team or Enterprise only (consistent with the launch facts).
  2. Connect Slack. Organization settings → Claude Tag → enable → Connect. Copy the message shown, paste it into Slack, copy the code Claude replies with, and paste the code back into the settings page.
  3. Build the general agent. In the apps tab, click + to create an access bundle and name it (for example “general agent”).
    • Credentials: connect the connectors it may use; this works as in Claude Desktop.
    • Instructions: behaviour rules, guardrails, answer style. Add “remember important facts” here.
    • Plugins: official plugins only by default.
  4. Add your own skills. In Claude Code, ask for a skill marketplace on GitHub built from your skills (free, about three minutes in his estimate; Claude gives the steps and links). Connect GitHub under Repositories with +, then find the marketplace by name under Plugins and switch it on. His shows as “Binyai Suite” in the captions. See Distributing Team Skills as a Plugin Marketplace for the marketplace pattern.
  5. Add channels. Slack tab → + → paste the channel ID. In Slack: right-click the channel → channel details → view channel details → copy the ID at the bottom.
  6. Give each channel its bundle and instructions. Example from his sales channel: the general bundle plus a lead-researcher bundle, and the instruction to run the researcher on every new lead. Add tone rules too: “be concise when answering in this channel, our sales reps are busy.”
  7. Schedule work from Slack. Ask in a chat; check the Access bundles, Audit logs and scheduled-task views in the console afterwards.
  8. Load the second brain (next section).

Loading a second brain

RouteHowTrade-off
Zip into memoryZip your context files, give the zip to Claude in a Slack chat and tell it to upload it to memory. Claude restructures it into company-wide memory (his has “hundreds of context files”)Simplest. Lives only inside Claude Tag, so other AI tools and your Desktop can’t use it. Keep it fresh with scheduled tasks that update memory
GitHub repositoryPut the second brain in a GitHub repo, then in the general agent’s Repositories tab connect GitHub and select it (his is captioned “Benny I OS main”)Stays in sync with other AI tools that read the same repo

With either route, a question such as “summarize everything the team has worked on last month” draws on the shared context. Ben points out that agencies selling second-brain or AI-OS setups can deliver them to clients’ non-technical staff this way. For building the second brain itself see Ben’s Five-Skill AIOS Setup.

Try It

  1. Create one general access bundle with two or three read-only connectors and a “remember important facts” instruction; invite it to one channel.
  2. Publish a GitHub skill marketplace from your existing skills and switch it on for that bundle.
  3. Pick one notification-driven channel (new bookings, new tickets) and write a one-line channel instruction that runs a named skill on every new post. Read the audit log after the first week.
  4. Push a second brain in through GitHub rather than a zip if anyone on the team also uses it from Claude Code or another tool.

Open Questions

  • Access bundles vs identities. “Access bundles” is the console label Ben shows in June 2026. Anthropic’s explainer describes per-channel identities that inherit a workspace baseline; whether one channel can stack several bundles exactly as Ben shows, and how that maps onto the identity model, is not stated in either source.
  • Custom plugins without GitHub. Ben expects Anthropic to make this easier; check whether the Plugins tab now lists non-official plugins directly.
  • Zip-upload memory size limits and how Claude Tag restructures uploaded files were not shown.
  • Ben’s adoption claims (“99% of people in businesses are not using Claude Code or even a Claude desktop yet”; Anthropic “already rolled out something similar in Notion”) are his own and unsourced.