Browser automation for checking messages, navigating channels, and extracting data from Slack workspaces.
Works with
Connect to existing Slack sessions or open Slack in a browser, then use snapshots to identify interactive elements and take actions like clicking channels, searching, or reading messages
Core workflow: connect, snapshot to find element refs, navigate to channels or tabs, extract text or capture screenshots as evidence
Supports common tasks including checking unreads via Activity
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionslackExecute the skills CLI command in your project's root directory to begin installation:
Fetches slack from vercel-labs/agent-browser and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate slack. Access via /slack in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
27.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
27.7K
stars
Interact with Slack workspaces to check messages, extract data, and automate common tasks.
Connect to an existing Slack browser session or open Slack:
# 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:
agent-browser snapshot -i
@e1, @e2, etc.)# 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
# 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
# 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
# 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
# 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)
# 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
When you need to document findings from Slack:
# 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
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)After clicking on a channel, you'll see tabs:
Click tab refs to switch views and get different information.
# Get a message or element's text
agent-browser get text @e_message_ref
# 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)
# After expanding unreads section:
agent-browser snapshot -i | grep -c "treeitem"
# Each treeitem with a channel name in the unreads section is one unread
agent-browser connect 9222 if Slack is already open. This is faster than opening a new browser.snapshot -i to identify refs before clicking buttons.snapshot --json for machine-readable output.sleep 1 between rapid interactions to let the UI update.agent-browser scroll down 300 --selector ".p-sidebar" to scroll within the Slack sidebar if channel list is long.agent-browser console
agent-browser errors
agent-browser get url
agent-browser get title
agent-browser screenshot page-state.png
#!/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"
? in Slack for shortcut listMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Solid pick for teams standardizing on skills: slack is focused, and the summary matches what you get after install.
slack fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
slack fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
slack reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in slack — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
slack has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for slack matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: slack is the kind of skill you can hand to a new teammate without a long onboarding doc.
slack fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
slack is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 70