Agent skill

Slack E2E

by openclaw in openclaw/openclaw

Test Slack with Convex-leased user OAuth or QA bots; check credentials, exercise owned messages, prove Gateway behavior, and distinguish API evidence from real Slack client interactions.

MITAuto-check passedTesting & QA

Install Slack E2E

skills CLI
$ npx skills add openclaw/openclaw --skill slack-e2e -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install openclaw/openclaw slack-e2e --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/slack-e2e .claude/skills/slack-e2e && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
slack-e2e
GitHub stars
392k
Token cost
~1.7k tokens
SKILL.md length
733 words
Files
5 (incl. scripts)
Skills in repo
93
Repo updated
First seen
Licence
MIT

At a glance

Test Slack with Convex-leased user OAuth or QA bots; check credentials, exercise owned messages, prove Gateway behavior, and distinguish API evidence from real Slack client interactions.

  • Works in 4 steps: Use the existing Convex login above. No… → Inspect the available scenarios and run… → Run the native lifecycle recipe → …
  • Tasks that involve End-to-end testing
  • SKILL.md covers Choose the proof, User OAuth: no QA Lab run, Existing Gateway lane and Evidence boundary, plus 1 more section
  • Runs JavaScript scripts from its folder; calls pnpm, node and bunx

What it does

Slack E2E is an agent skill from openclaw/openclaw. Test Slack with Convex-leased user OAuth or QA bots; check credentials, exercise owned messages, prove Gateway behavior, and distinguish API evidence from real Slack client interactions.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts (for example `features.md`, `runtime.md` and `user-oauth.md`).

It sits in Testing & QA, covering End-to-end testing and OAuth and OpenID Connect. It works with Slack. The repository describes itself as: The AI that really does things. Any OS. Any Platform. The lobster way. 🦞. The licence is MIT.

When your agent uses it

  • Tasks that involve End-to-end testing
  • Tasks that involve OAuth and OpenID Connect

Example prompts

  • “/slack-e2e”

Requirements

  • Node.js

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Use the existing Convex login above. No Slack tokens, broker secrets, model
  2. Inspect the available scenarios and run readiness
  3. Run the native lifecycle recipe
  4. Read the summary, evidence, and cleanup result before claiming success.

What it can do on your machine

Read from SKILL.md and the folder at commit 1eb5970. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (JavaScript), which the agent can run.

    Shell commands in SKILL.md call:

    • pnpm
    • node
    • bunx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm and bunx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Slack E2E loads about 1.7k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 733 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~49
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from openclaw/openclaw at commit 1eb5970, republished under its MIT licence (© openclaw). 733 words, ~1,745 tokens.

Download SKILL.mdSave it as .claude/skills/slack-e2e/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
slack-e2e
description
Test Slack with Convex-leased user OAuth or QA bots; check credentials, exercise owned messages, prove Gateway behavior, and distinguish API evidence from real Slack client interactions.

Slack agent E2E

Choose the proof

GoalEntry pointBoundary
Check shared user OAuthRead-only command belowUser/workspace identity and channel history; no Gateway
Exercise user-authored textSame command with --smokeCreate, read, edit, delete, verify absence; no Gateway reply claim
Prove OpenClaw ingress, replies, tools, files, or restartExisting QA Lab lane belowLeased driver/SUT bots and an isolated Gateway
Prove real clicks, slash commands, or renderingAuthorized Slack clientActual client observation, not reconstructed API data

Start from a source checkout with normal dependencies and an existing Convex login. If needed, ask the operator to run convex login or the cached bunx --no-install convex login. The broker provides the authorized pool; agents do not need to copy Slack tokens. Login alone cannot supply a missing pool credential or grant Slack permissions.

User OAuth: no QA Lab run

bash
node .agents/skills/slack-e2e/scripts/user-oauth-smoke.mjs
node .agents/skills/slack-e2e/scripts/user-oauth-smoke.mjs --smoke

The default is read-only in Slack; both modes acquire, heartbeat, and release a Convex lease. --smoke creates one synthetic, unmentioned top-level message, checks stored authorship, edits it, and deletes that exact message. Existing workspace listeners can still observe it. Each command uses a new private artifact directory and prints a safe result plus its path.

Read user OAuth setup and recovery for the pool payload, permissions, result interpretation, and failure handling. This skill-owned command reuses the existing lease helper; it changes no QA Lab code or release lane and starts no Gateway or model. It does not add a user-driver option to qa slack.

Existing Gateway lane

Use the source-checkout QA Lab owner for Gateway proof, not a separate bot runner. A run owns a leased driver/SUT pair, a temporary Gateway, native fixture receipts, and private artifacts. The driver has no Socket Mode connection: the SUT Gateway exclusively owns the app token and event delivery.

  1. Use the existing Convex login above. No Slack tokens, broker secrets, model credentials, app creation, or scope grants belong in the command line.

  2. Inspect the available scenarios and run readiness:

    bash
    pnpm openclaw qa slack --list-scenarios
    pnpm openclaw qa slack --doctor --output-dir .artifacts/qa-e2e/slack-doctor

    Doctor checks the actual lease: distinct bot identities in one workspace, both bots' channel access, the owned Gateway connection, and advertised OAuth scopes. Known missing scopes fail with their actor and exact names. Missing scope metadata means mutation capability is unverified, not granted. Missing optional file/reaction scopes do not block text-only flows; they block the affected native operations before dispatch. Doctor's full lifecycle capability verdict remains separate from mandatory connection readiness. A pool/login/permission failure is an owner prerequisite, not a reason to rotate credentials until one passes. Every subsequent run checks its own lease.

  3. Run the native lifecycle recipe:

    bash
    pnpm openclaw qa slack \
      --scenario-file qa/scenarios/channels/slack-e2e-lifecycle.yaml \
      --output-dir .artifacts/qa-e2e/slack-lifecycle

    --doctor and --scenario-file default to Convex, the CI role, and mock-openai. This is real Slack/Gateway transport with a deterministic model. Explicit overrides remain available; ordinary curated qa slack defaults do not change. Use a unique output directory per run. Additional --scenario-file arguments select additional complete YAML scenarios.

  4. Read the summary, evidence, and cleanup result before claiming success. Choose feature recipes for native operations or model-tool evidence, and runtime recipes for config/restart, custom flows, cancellation, artifacts, and recovery.

Show full SKILL.md (229 more words)Show less

Evidence boundary

SurfaceWhat automation proves
Mention/quiet ingress, owned edits/deletes, reactions, upload, thread repliesFixture/API operations and explicit stored readback; not model tool calls
Correlated SUT replyA stored reply from the leased SUT after ingress; mock or live model must be named
Gateway debug-proxy captureSlack accepted a Gateway API write; neither Socket Mode event delivery nor rendering
Block Kit, file IDs, reaction stateStored structure/identity only
Human slash invocation, real button clicks, Agent View, visible rendering, human typingManual/Mantis client lane; bot/API evidence is insufficient

For visual or human-interaction requests, use an authorized, logged-in Slack client; the maintained Mantis workflow is in docs/concepts/qa-e2e-automation/operator-flow.md. Check which surface it actually captured: --approval-checkpoints renders API message data, not the Slack client. A Slack sign-in screenshot is not proof of a workspace action. Preserve inspected client screenshots alongside native evidence. Posting slash text through the API is not a slash invocation; Gateway approval RPCs are not button clicks. Do not infer typing from assistant status or start another Socket Mode recorder with the SUT app token.

Completion

Report scenario/model lane, stored native identities or safe counts, artifact paths, cleanup outcome, missing permissions, and any manual-only gap. Keep raw Gateway capture, channel IDs, messages, media, and lease material private; publish only sanitized proof. A successful API response with failed stored readback, an uncertain send, or failed cleanup is not an end-to-end pass.

© openclaw, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (scripts) in .agents/skills/slack-e2e of openclaw/openclaw.

  • SKILL.md
  • features.md
  • runtime.md
  • scripts/user-oauth-smoke.mjs
  • user-oauth.md

Open the folder on GitHubat commit 1eb5970

Compare with similar skills

Slack E2E next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Slack E2E compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Slack E2E this skillopenclaw/openclaw392k—~1.7kAutomated safety check: PassMIT
Avm Tf TestingAzure/terraform-azurerm-avm-ptn-alz135—~1.8kAutomated safety check: PassMIT
Nexu E2E Testnexu-io/nexu3.3k—~1.7kAutomated safety check: PassMIT
Emulate Seedyonatangross/orchestkit289—~4.5kAutomated safety check: PassMIT
Electron App Automationvercel-labs/agent-browser44k5 repos~1.7kAutomated safety check: PassApache-2.0
Openloomi Connectorsmelandlabs/openloomi1k—~3.3kAutomated safety check: PassApache-2.0

Similar skills

  • Avm Tf Testing

    Azure/terraform-azurerm-avm-ptn-alz

    Official

    A skill your agent uses for AVM Terraform validation, provider-mocked unit tests, real-Azure integration tests, E2E example tests, PowerShell hooks, OIDC, policy checks, and Avm.Authoring CI behavior.

    135 GitHub stars~1.8k tokensUpdated 2 days ago
    Testing & QAAuto-check passed
  • Nexu E2E Test

    nexu-io/nexu

    A skill your agent uses when verifying OpenClaw gateway fixes end-to-end, testing skill loading after restart, or running integration tests against the local Nexu+OpenClaw stack.

    3.3k GitHub stars~1.7k tokensUpdated 5 mo ago
    Testing & QAAuto-check passed
  • Emulate Seed

    yonatangross/orchestkit

    Generate emulate seed configs for stateful API emulation. An agent skill from yonatangross/orchestkit.

    289 GitHub stars~4.5k tokensUpdated today
    Backend & APIsAuto-check passed
  • Electron App Automation

    vercel-labs/agent-browser

    Official

    Automates Electron desktop apps such as VS Code, Slack or Discord by connecting agent-browser to their Chrome DevTools Protocol port.

    44k GitHub starsUsed in 5 repos~1.7k tokens
    Productivity & AutomationAuto-check passed
  • Openloomi Connectors

    melandlabs/openloomi

    openloomi Connectors tools - manage the native 7 messaging integrations and pair with the composio skill for the 1000+ apps OAuth layer (Slack, Discord, X, Gmail, Outlook, Google…

    1k GitHub stars~3.3k tokensUpdated 14 days ago
    Productivity & AutomationAuto-check passed
  • Socialite Development

    hexlet-volunteers/hexlet-sicp

    Manages OAuth social authentication with Laravel Socialite. An agent skill from hexlet-volunteers/hexlet-sicp.

    114 GitHub starsUsed in 5 repos~1.2k tokens
    Backend & APIsAuto-check passed

More from openclaw/openclaw

All 93 skills in this repo
  • Openclaw Live Updater

    openclaw/openclaw

    Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.

    392k GitHub stars~3.7k tokensUpdated today
    Auto-check passed
  • Tmux

    openclaw/openclaw

    Control tmux sessions/panes for interactive CLIs: list, capture output, send keys, paste text, monitor prompts.

    392k GitHub starsUsed in 2 repos~640 tokens
    Auto-check passed
  • Feishu Doc

    openclaw/openclaw

    Feishu document read/write workflows. An agent skill from openclaw/openclaw.

    392k GitHub stars~516 tokensUpdated today
    Auto-check passed
  • Openclaw PR Maintainer

    openclaw/openclaw

    Review, triage, repair, or land OpenClaw issues and pull requests with current-source evidence and the native maintainer workflow.

    392k GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Browser Automation

    openclaw/openclaw

    A skill your agent uses when controlling web pages with the OpenClaw browser tool, especially multi-step flows, login checks, tab management, or recovery from stale refs/timeouts.

    392k GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Clawsweeper

    openclaw/openclaw

    A skill your agent uses for all ClawSweeper work: OpenClaw issue/PR sweep reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed…

    392k GitHub stars~3k tokensUpdated today
    Auto-check passed

Works with

Questions about Slack E2E

What does Slack E2E do?

Test Slack with Convex-leased user OAuth or QA bots; check credentials, exercise owned messages, prove Gateway behavior, and distinguish API evidence from real Slack client interactions. Slack E2E is an agent skill from openclaw/openclaw. Test Slack with Convex-leased user OAuth or QA bots; check credentials, exercise owned messages, prove Gateway behavior, and distinguish API evidence from real Slack client interactions.

When should I use Slack E2E?

Slack E2E fits situations like: tasks that involve End-to-end testing; tasks that involve OAuth and OpenID Connect.

How do I install Slack E2E in Claude Code?

Run `npx skills add openclaw/openclaw --skill slack-e2e -a claude-code`. Or copy the skill folder (.agents/skills/slack-e2e in openclaw/openclaw) into .claude/skills/slack-e2e in your project. Claude Code loads it when a task matches its description.

How do I install Slack E2E in Codex?

Run `npx skills add openclaw/openclaw --skill slack-e2e -a codex`. Or copy the skill folder (.agents/skills/slack-e2e in openclaw/openclaw) into .agents/skills/slack-e2e in your project. Codex loads it when a task matches its description.

Can I use Slack E2E in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openclaw/openclaw --skill slack-e2e -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/slack-e2e, .gemini/skills/slack-e2e, .github/skills/slack-e2e and .opencode/skills/slack-e2e in your project.

What does Slack E2E need to run?

Going by SKILL.md and its folder, Slack E2E needs JavaScript for the scripts in its folder and the command-line tools its instructions call (pnpm, node and bunx). Our summary lists: Node.js.

Does Slack E2E access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Slack E2E safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Slack E2E use?

Slack E2E is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Slack E2E use?

About 1.7k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Slack E2E?

Skills that share tags, products or a category with Slack E2E: Avm Tf Testing (Azure/terraform-azurerm-avm-ptn-alz, 135 stars), Nexu E2E Test (nexu-io/nexu, 3.3k stars), Emulate Seed (yonatangross/orchestkit, 289 stars) and Electron App Automation (vercel-labs/agent-browser, 44k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Slack E2E?

openclaw (a GitHub organization) maintains it in openclaw/openclaw, which has 391,610 GitHub stars. The repository holds 93 skills in this directory. The repository was last updated on October 8, 2026.

Source: openclaw/openclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.