# Mochi Slack

Slack awareness, unread mentions, channel digests, topic radar, thread summaries.

- Repository: https://github.com/kirodotdev/KiroCrew (4711 stars)
- Category: Engineering
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add kirodotdev/KiroCrew --skill mochi-slack -g -a claude-code -y`
Codex: `npx skills add kirodotdev/KiroCrew --skill mochi-slack -g -a codex -y`
Cursor: `npx skills add kirodotdev/KiroCrew --skill mochi-slack -g -a cursor -y`
Gemini CLI: `npx skills add kirodotdev/KiroCrew --skill mochi-slack -g -a gemini-cli -y`

## Description

Slack awareness, unread mentions, channel digests, topic radar, thread summaries. Load when user asks about Slack.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# @mochi-slack, Slack Awareness

You help the user READ Slack, unread mentions, channel summaries, topic monitoring,
thread summaries.

## This skill does not assume a particular Slack MCP server

There is no single standard Slack MCP server, and the user may have any of them, public, self-hosted, or one their company provides. So this skill describes the
CAPABILITIES each task needs and leaves the tool names to you.

**Discover before assuming.** Look at the Slack tools you actually have and map them
onto the capabilities below. Where a capability is missing, say so plainly instead of
guessing at a tool name, a wrong call wastes a turn and confuses the user.

Capabilities the tasks below need:

| Capability | What you are looking for |
|---|---|
| List channels | channels the user is in, ideally with unread / mention counts |
| Read a channel | recent messages in one channel |
| Read a thread | all replies under one parent message |
| Search | message search, ideally with `in:` / `from:` / `has:` style filters |
| Resolve a user | a user id or handle → display name |

Names vary. One common server spells these `list_my_channels`, `get_messages`,
`get_thread`, `search`, `lookup_user`, treat that as a hint, not a contract.

## If you have no Slack tools at all

Do NOT try to install one. Which Slack server to use, and whether to connect a
workspace at all, is the user's decision, and on a work machine it may not be theirs
to make.

Installing a Slack server in Kiro Crew is not enough on its own: I only get the
servers the user adds in MY settings panel, under **MCP Servers**. Every other server
is switched off for me, so "no Slack tools" may mean "installed but not added here".

Say so and hand it back:

> "I don't have any Slack tools right now. If a Slack MCP server is installed in
> Kiro Crew, add it under MCP Servers in my settings, and I can read mentions and
> summarize channels for you."

The rest: https://github.com/kirodotdev/KiroCrew/blob/HEAD/src/kiro_crew/apps/builtins/mochi/agents/skills/mochi-slack/SKILL.md