slack-web
Slack web automation via agent-browser. Use when the user asks to check Slack, read messages, send messages, reply in threads, search Slack, check notifications, react to messages, send DMs, or any Slack communication task. Triggers include "check my Slack", "send a message on Slack", "reply to that Slack thread", "search Slack for...", "what's new on Slack", "read my DMs", "react to that message", "check Slack notifications", "message [person] on Slack".
- License 许可
- MIT
- 最近更新
- 2026-07-29
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- slack-web
- description
- Slack web automation via agent-browser. Use when the user asks to check Slack, read messages, send messages, reply in threads, search Slack, check notifications, react to messages, send DMs, or any Slack communication task. Triggers include "check my Slack", "send a message on Slack", "reply to that Slack thread", "search Slack for...", "what's new on Slack", "read my DMs", "react to that message", "check Slack notifications", "message [person] on Slack".
- allowed-tools
- Bash(agent-browser:*)
02 资源文件 1
- 参考文档references/workflows.md3.0 KB
03 SKILL.md 正文
Slack Web Automation
Interact with Slack through its web interface using agent-browser.
Core Workflow
Every Slack interaction follows this pattern:
- Restore session:
agent-browser state load ~/.slack-auth-state.json - Open Slack:
agent-browser --headed open "https://app.slack.com" - Snapshot:
agent-browser snapshot -i -c(get refs) - Interact: Use refs to click, type, navigate
- Re-snapshot: After every action — Slack's DOM changes constantly
# Restore and open
agent-browser state load ~/.slack-auth-state.json
agent-browser --headed open "https://app.slack.com"
agent-browser wait --load networkidle
agent-browser set viewport 1920 1080
# Verify logged in (URL should contain /client/)
agent-browser get url
# Navigate with quick switcher
agent-browser press "Meta+k"
agent-browser wait 500
agent-browser snapshot -i
agent-browser fill @eXX "general"
agent-browser wait 1000
agent-browser snapshot -i
agent-browser click @eXX
agent-browser wait --load networkidle
# Read messages
agent-browser snapshot -c
Authentication
First-Time Login (Manual)
agent-browser --headed open "https://app.slack.com"
# PAUSE — tell user to log in manually
# After login confirmed:
agent-browser get url # verify /client/ in URL
agent-browser state save ~/.slack-auth-state.json
Restore Session
agent-browser state load ~/.slack-auth-state.json
agent-browser --headed open "https://app.slack.com"
agent-browser wait --load networkidle
agent-browser get url
# If URL contains "signin" → session expired, user must re-login
Actions
Read Messages
# Navigate to channel (quick switcher is fastest)
agent-browser press "Meta+k"
agent-browser wait 500
agent-browser snapshot -i
agent-browser fill @eXX "channel-name"
agent-browser wait 1000
agent-browser snapshot -i
agent-browser click @eXX
agent-browser wait --load networkidle
# Read
agent-browser snapshot -c
Send a Message
# In the target channel, find compose box
agent-browser snapshot -i
# Look for textbox with "Message #channel" placeholder
agent-browser click @eXX # compose area
agent-browser type @eXX "Your message"
agent-browser press "Enter"
agent-browser wait 1000
agent-browser snapshot -c # verify sent
Use type not fill — Slack's compose box is contenteditable.
Reply to Thread
agent-browser snapshot -c
agent-browser hover @eXX # hover message to show toolbar
agent-browser snapshot -i
agent-browser click @eXX # reply/thread button
agent-browser wait --load networkidle
agent-browser snapshot -i
agent-browser click @eXX # thread compose box
agent-browser type @eXX "Thread reply"
agent-browser press "Enter"
Send DM
agent-browser press "Meta+k"
agent-browser wait 500
agent-browser snapshot -i
agent-browser fill @eXX "Person Name"
agent-browser wait 1000
agent-browser snapshot -i
agent-browser click @eXX # person result
agent-browser wait --load networkidle
agent-browser snapshot -i
agent-browser click @eXX # compose box
agent-browser type @eXX "Your DM"
agent-browser press "Enter"
Search
agent-browser press "Meta+g" # Slack search
agent-browser wait 500
agent-browser snapshot -i
agent-browser fill @eXX "search query"
agent-browser press "Enter"
agent-browser wait --load networkidle
agent-browser snapshot -c
React with Emoji
agent-browser snapshot -c
agent-browser hover @eXX # hover over message
agent-browser snapshot -i
agent-browser click @eXX # emoji/reaction button (smiley icon)
agent-browser wait 500
agent-browser snapshot -i
agent-browser fill @eXX "thumbsup" # emoji search
agent-browser wait 500
agent-browser snapshot -i
agent-browser click @eXX # emoji result
Check Notifications
# Click "Activity" in sidebar or navigate:
agent-browser snapshot -i -c
agent-browser click @eXX # Activity link
agent-browser wait --load networkidle
agent-browser snapshot -c
Check Unreads
agent-browser snapshot -i -c
# Look for bold channel names or "Unreads" section
agent-browser click @eXX # Unreads link
agent-browser wait --load networkidle
agent-browser snapshot -c
Critical Rules
- ALWAYS re-snapshot after every action — refs invalidate constantly
- Use
--headedmode so user can see and intervene - Set viewport 1920x1080 — Slack hides features at small widths
- Use
Meta+k(quick switcher) as primary navigation - Use
typenotfillfor compose boxes (contenteditable) - Wait after actions:
agent-browser wait --load networkidle - Save auth state often:
agent-browser state save ~/.slack-auth-state.json
Semantic Locator Fallbacks
When refs don't match:
agent-browser find text "general" click
agent-browser find role textbox fill "Hello"
agent-browser find placeholder "Message #general" type "Hello"
agent-browser find role button click --name "Send"
Debugging
agent-browser screenshot /tmp/slack-debug.png
agent-browser get url
agent-browser snapshot # full unfiltered tree
Deep-Dive References
| Reference | When to Use |
|---|---|
| references/workflows.md | Full workflow examples |
04 同仓库更多 Skills
using-agent-skills
Discovers and invokes the right @runecraft/spells skill for the current task. Use when starting a session, when a request is ambiguous about which workflow to apply, or when you need to pick among the 13-skill Arcanum catalog. EN triggers: /skill, which skill, pick a skill, what skill should I use, skill discovery, meta skill. PT triggers: qual skill, qual habilidade, descobrir skill, qual fluxo usar. Do NOT use for: actual implementation work (route to the specific skill instead), unrelated standalone tasks outside the Arcanum catalog, or runtime-specific configuration (e.g., opencode.json / Claude Code plugin paths).
typescript-patterns
TypeScript best practices and patterns for type-safe, maintainable code. Covers discriminated unions, generics, const assertions, type narrowing, and common anti-patterns. Extends (does not override) project tsconfig. EN triggers: /typescript, TypeScript patterns, TS best practices, type safety, discriminated unions, generics, type narrowing. PT triggers: /typescript, padrões TypeScript, boas práticas TS, segurança de tipos, unions discriminadas, genéricos. Do NOT use for: JavaScript-only projects, runtime performance, or replacing project tsconfig rules.
test-driven-development
Drives development with tests — fail first, then make them pass, then refactor. Use when implementing any logic, fixing any bug, or changing any behavior. EN triggers: /test, write tests first, TDD, prove it, 80/15/5 pyramid, Beyonce Rule. PT triggers: /teste, testes primeiro, provar com teste, pirâmide 80/15/5. Do NOT use for: production incident triage (use /debug), or cosmetic-only changes with no behavioral surface.
spec-driven
Feature planning and implementation with 4 adaptive phases — Specify, Design, Tasks, Execute. Auto-sizes depth by complexity. Creates atomic tasks with verification criteria, atomic git commits, and requirement traceability. Features an independent Verifier (author != verifier, evidence-or-zero), persistent decision log (STATE.md), and test-coverage-matrix-driven tests, plus a self-improving lessons layer that turns verification failures into reusable project-local guidance. Stack-agnostic. Use when planning features (requirements, design, task breakdown), implementing with verification and atomic commits, or validating/verifying an implementation against a spec. Triggers (PT/EN): "specify feature", "vamos especificar", "discutir feature", "discutir este caso", "design", "design da feature", "tarefas", "quebrar em tarefas", "implementar", "build", "validar", "verify work", "UAT", "validar implementação", "record decision", "pause work", "pausar trabalho", "resume work", "retomar trabalho". Do NOT use for architecture decomposition analysis (use architecture skills) or technical design docs (treat as Complex scope: discuss gray areas + architecture-focused design).
skill-forge
Designs, authors, validates, and optimizes new Agent Skills from scratch. Use when creating a new skill, packaging a workflow as a skill, improving a skill's triggering accuracy, or evaluating whether a skill improves output quality. Covers the full lifecycle: DISCOVER, DESIGN, AUTHOR, VALIDATE, OPTIMIZE, DELIVER. Produces skills that follow the open SKILL.md format (YAML frontmatter + Markdown body, progressive disclosure, validation loops). EN triggers: /forge, create a skill, write a skill, build a skill, new skill, author a skill, package this as a skill, validate a skill, improve skill triggering, optimize skill description, evaluate skill quality. PT triggers: /forge, criar uma skill, escrever uma skill, construir uma skill, nova skill, empacotar como skill, validar skill, melhorar disparo, otimizar descrição de skill. Do NOT use for: discovering which existing skill to apply (use a dispatch/meta skill), planning feature implementation, or designing software architecture.
shipping-and-launch
Prepares production launches with a pre-launch checklist, staged rollout, monitoring, and a rollback strategy — plus feature flag lifecycle (off → internal → beta → GA). Use when deploying a feature to production for the first time, releasing a significant change, or planning a rollout. EN triggers: /ship, pre-launch checklist, staged rollout, feature flag, rollback plan, monitoring. PT triggers: /shippar, checklist pré-lançamento, rollout gradual, feature flag, plano de rollback. Do NOT use for: pre-production development work, or one-off internal tools with no user exposure.