slack

Slack team communication platform. Use for team chat.

7 stars

byG1Joshi

View on GitHub Installation ↓

Best use case

slack is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Slack team communication platform. Use for team chat.

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

$curl -o ~/.claude/skills/slack/SKILL.md --create-dirs "https://raw.githubusercontent.com/G1Joshi/Agent-Skills/main/skills/tools/slack/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/slack/SKILL.md inside 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?

Slack team communication platform. Use for team chat.

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

Slack is the OS of work. 2025 turns it into an **Agentic OS** where AI agents can read messages, summarize threads, and trigger workflow actions autonomously.

## When to Use

- **Corporate Comms**: The standard for 99% of tech companies.
- **Ops Triggers**: "ChatOps" (deploy from Slack).
- **Huddles**: Quick voice/screen sharing.

## Core Concepts

### Block Kit

UI framework for building interactive messages and modals.

### Workflow Builder

No-code automation ("When user joins channel, send DM").

### Apps

Integrations (GitHub, Linear, Jira).

## Best Practices (2025)

**Do**:

- **Use Canvas**: Store persistent info (team links) in a channel canvas.
- **Use Huddles**: Faster than Zoom for quick syncs.
- **Use "Catch Up"**: The mobile swipe interface to clear unreads.

**Don't**:

- **Don't use `@channel`**: Unless the building is on fire.

## References

- [Slack API](https://api.slack.com/)