slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
Best use case
slack is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
Teams using slack should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/slack/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How slack Compares
| Feature / Agent | slack | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Slack Automation Interact with Slack workspaces to check messages, extract data, and automate common tasks. ## Quick Start Connect to an existing Slack browser session or open Slack: ```bash # Connect to existing session on port 9222 (typical for already-open Slack) agent-browser connect 9222 # Or open Slack if not already running agent-browser open https://app.slack.com ``` Then take a snapshot to see what's available: ```bash agent-browser snapshot -i ``` ## Core Workflow 1. **Connect/Navigate**: Open or connect to Slack 2. **Snapshot**: Get interactive elements with refs (`@e1`, `@e2`, etc.) 3. **Navigate**: Click tabs, expand sections, or navigate to specific channels 4. **Extract/Interact**: Read data or perform actions 5. **Screenshot**: Capture evidence of findings ```bash # Example: Check unread channels agent-browser connect 9222 agent-browser snapshot -i # Look for "More unreads" button agent-browser click @e21 # Ref for "More unreads" button agent-browser screenshot slack-unreads.png ``` ## Common Tasks ### Checking Unread Messages ```bash # Connect to Slack agent-browser connect 9222 # Take snapshot to locate unreads button agent-browser snapshot -i # Look for: # - "More unreads" button (usually near top of sidebar) # - "Unreads" toggle in Activity tab (shows unread count) # - Channel names with badges/bold text indicating unreads # Navigate to Activity tab to see all unreads in one view agent-browser click @e14 # Activity tab (ref may vary) agent-browser wait 1000 agent-browser screenshot activity-unreads.png # Or check DMs tab agent-browser click @e13 # DMs tab agent-browser screenshot dms.png # Or expand "More unreads" in sidebar agent-browser click @e21 # More unreads button agent-browser wait 500 agent-browser screenshot expanded-unreads.png ``` ### Navigating to a Channel ```bash # Search for channel in sidebar or by name agent-browser snapshot -i # Look for channel name in the list (e.g., "engineering", "product-design") # Click on the channel treeitem ref agent-browser click @e94 # Example: engineering channel ref agent-browser wait --load networkidle agent-browser screenshot channel.png ``` ### Finding Messages/Threads ```bash # Use Slack search agent-browser snapshot -i agent-browser click @e5 # Search button (typical ref) agent-browser fill @e_search "keyword" agent-browser press Enter agent-browser wait --load networkidle agent-browser screenshot search-results.png ``` ### Extracting Channel Information ```bash # Get list of all visible channels agent-browser snapshot --json > slack-snapshot.json # Parse for channel names and metadata # Look for treeitem elements with level=2 (sub-channels under sections) ``` ### Checking Channel Details ```bash # Open a channel agent-browser click @e_channel_ref agent-browser wait 1000 # Get channel info (members, description, etc.) agent-browser snapshot -i agent-browser screenshot channel-details.png # Scroll through messages agent-browser scroll down 500 agent-browser screenshot channel-messages.png ``` ### Taking Notes/Capturing State When you need to document findings from Slack: ```bash # Take annotated screenshot (shows element numbers) agent-browser screenshot --annotate slack-state.png # Take full-page screenshot agent-browser screenshot --full slack-full.png # Get current URL for reference agent-browser get url # Get page title agent-browser get title ``` ## Sidebar Structure Understanding Slack's sidebar helps you navigate efficiently: ``` - Threads - Huddles - Drafts & sent - Directories - [Section Headers - External connections, Starred, Channels, etc.] - [Channels listed as treeitems] - Direct Messages - [DMs listed] - Apps - [App shortcuts] - [More unreads] button (toggles unread channels list) ``` Key refs to look for: - `@e12` - Home tab (usually) - `@e13` - DMs tab - `@e14` - Activity tab - `@e5` - Search button - `@e21` - More unreads button (varies by session) ## Tabs in Slack After clicking on a channel, you'll see tabs: - **Messages** - Channel conversation - **Files** - Shared files - **Pins** - Pinned messages - **Add canvas** - Collaborative canvas - Other tabs depending on workspace setup Click tab refs to switch views and get different information. ## Extracting Data from Slack ### Get Text Content ```bash # Get a message or element's text agent-browser get text @e_message_ref ``` ### Parse Accessibility Tree ```bash # Full snapshot as JSON for programmatic parsing agent-browser snapshot --json > output.json # Look for: # - Channel names (name field in treeitem) # - Message content (in listitem/document elements) # - User names (button elements with user info) # - Timestamps (link elements with time info) ``` ### Count Unreads ```bash # After expanding unreads section: agent-browser snapshot -i | grep -c "treeitem" # Each treeitem with a channel name in the unreads section is one unread ``` ## Best Practices - **Connect to existing sessions**: Use `agent-browser connect 9222` if Slack is already open. This is faster than opening a new browser. - **Take snapshots before clicking**: Always `snapshot -i` to identify refs before clicking buttons. - **Re-snapshot after navigation**: After navigating to a new channel or section, take a fresh snapshot to find new refs. - **Use JSON snapshots for parsing**: When you need to extract structured data, use `snapshot --json` for machine-readable output. - **Pace interactions**: Add `sleep 1` between rapid interactions to let the UI update. - **Check accessibility tree**: The accessibility tree shows what screen readers (and your automation) can see. If an element isn't in the snapshot, it may be hidden or require scrolling. - **Scroll in sidebar**: Use `agent-browser scroll down 300 --selector ".p-sidebar"` to scroll within the Slack sidebar if channel list is long. ## Limitations - **Cannot access Slack API**: This uses browser automation, not the Slack API. No OAuth, webhooks, or bot tokens needed. - **Session-specific**: Screenshots and snapshots are tied to the current browser session. - **Rate limiting**: Slack may rate-limit rapid interactions. Add delays between commands if needed. - **Workspace-specific**: You interact with your own workspace -- no cross-workspace automation. ## Debugging ### Check console for errors ```bash agent-browser console agent-browser errors ``` ### Get current page state ```bash agent-browser get url agent-browser get title agent-browser screenshot page-state.png ``` ## Example: Full Unread Check ```bash #!/bin/bash # Connect to Slack agent-browser connect 9222 # Take initial snapshot echo "=== Checking Slack unreads ===" agent-browser snapshot -i > snapshot.txt # Check Activity tab for unreads agent-browser click @e14 # Activity tab agent-browser wait 1000 agent-browser screenshot activity.png ACTIVITY_RESULT=$(agent-browser get text @e_main_area) echo "Activity: $ACTIVITY_RESULT" # Check DMs agent-browser click @e13 # DMs tab agent-browser wait 1000 agent-browser screenshot dms.png # Check unread channels in sidebar agent-browser click @e21 # More unreads button agent-browser wait 500 agent-browser snapshot -i > unreads-expanded.txt agent-browser screenshot unreads.png # Summary echo "=== Summary ===" echo "See activity.png, dms.png, and unreads.png for full details" ``` ## References - **Slack docs**: https://slack.com/help - **Web experience**: https://app.slack.com - **Keyboard shortcuts**: Type `?` in Slack for shortcut list
Related Skills
what-not-to-do-as-product-manager
Anti-patterns and mistakes to avoid as a product manager. Use when evaluating leadership behaviors, improving team dynamics, reflecting on management practices, or onboarding new product managers.
visual-cues-cta-psychology
Design effective CTAs using visual attention and gaze psychology principles. Use when designing landing pages, button hierarchies, conversion elements, or optimizing user attention flow through interfaces.
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
value-realization
Analyze if end users discover clear value. Use when evaluating product concepts, analyzing adoption, or uncertain about direction.
user-story-fundamentals
Capture requirements from user perspective with structured user stories. Use when writing backlog items, defining acceptance criteria, prioritizing features, or communicating requirements between product and development.
typescript-satisfies-operator
Guides proper usage of TypeScript's satisfies operator vs type annotations. Use this skill when deciding between type annotations (colon) and satisfies, validating object shapes while preserving literal types, or troubleshooting type inference issues.
typescript-interface-vs-type
Guides when to use interface vs type in TypeScript. Use this skill when defining object types, extending types, or choosing between interface and type aliases.
typescript-best-practices
Guides TypeScript best practices for type safety, code organization, and maintainability. Use this skill when configuring TypeScript projects, deciding on typing strategies, writing async code, or reviewing TypeScript code quality.
typescript-advanced-types
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.
trust-psychology
Build trust signals that reduce perceived risk and enable user action. Use when designing landing pages, checkout flows, onboarding experiences, or any conversion point where user hesitation is a barrier.
theme-epic-story
Structure product work hierarchically using themes, epics, and stories. Use when organizing backlogs, planning releases, communicating with stakeholders, or breaking down large initiatives into manageable work.
tailwind-v4-configuration
Configure Tailwind CSS v4 with CSS-first approach. Use when installing, migrating from v3, setting up build tools (Vite/PostCSS/CLI), customizing themes with @theme, or configuring plugins.