slack-integration_skill

This skill helps you manage and interact with Slack data and workflows by leveraging Membrane integrations for channels, users, and messages.
  • Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill slack-integration

  • _meta.json457 B
  • SKILL.md5.7 KB

Overview

This skill integrates Slack into your automation and data workflows, letting you manage channels, messages, users, files, reminders, and more. It uses Membrane as the integration layer so authentication, pagination, and retries are handled for you. Use the provided actions or proxy raw Slack API requests when you need finer control.

How this skill works

The skill talks to Slack through Membrane CLI commands. Membrane stores and refreshes credentials, exposes a catalog of pre-built actions (list-conversations, post-message, get-user-info, etc.), and can proxy arbitrary Slack API endpoints when an action is not available. You create or reuse a Membrane connection, list or search actions, then run actions with JSON inputs to interact with Slack data.

When to use it

  • Archive or back up Slack channels, messages, and files programmatically.
  • Automate routine Slack workflows: post messages, create channels, invite users, or set reminders.
  • Query team membership or user information for audits and reporting.
  • Search messages or fetch conversation history for compliance or analysis.
  • Delete or clean up files and messages across channels.

Best practices

  • Prefer Membrane pre-built actions over raw API calls to benefit from built-in auth, pagination, and error handling.
  • Discover actions before building custom requests by running action list with an appropriate intent.
  • Never collect Slack API keys locally; create a Membrane connection so credentials are managed server-side.
  • Use Membrane proxy only when actions don’t cover your use case, and pass JSON bodies for structured payloads.
  • Run list operations with sensible limits and paging to avoid large responses and rate limits.

Example use cases

  • Create a scheduled job that exports conversation history from specific channels to an archive storage.
  • Build an automation that posts status updates to a team channel after your CI pipeline finishes.
  • Search messages containing a keyword across all channels and compile results for compliance review.
  • Invite new hires to relevant channels and add them to user groups during onboarding.
  • Bulk-delete old files from a shared channel as part of storage cleanup.

FAQ

Run the Membrane CLI login command to authenticate; Membrane opens a browser for OAuth and stores credentials for future use.

Can I call Slack endpoints not covered by actions?

Yes — use Membrane's request proxy to send arbitrary HTTP requests to Slack with automatic auth headers and base URL handling.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational