Skip to content
Skills Library
Management & product · Tool integration

messenger

/messenger

Keeps the console's messenger for whoever holds its role: connects the workspace's Slack through an app the plugin makes, says which plugin events go to which channel, matches people to their Slack accounts by email, and reads what was sent and why something was not. Use when a person asks to connect Slack, to send approved leave to a channel, to find out why someone gets no messages, or why a message did not go out.

Licence
MIT
Last repository change
10.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Keeps the console's messenger for whoever holds its role: connects the workspace's Slack through an app the plugin makes, says which plugin events go to which channel, matches people to their Slack accounts by email, and reads what was sent and why something was not. Use when a person asks to connect Slack, to send approved leave to a channel, to find out why someone gets no messages, or why a message did not go out.

Original author description

Keeps the console's messenger for whoever holds its role: connects the workspace's Slack through an app the plugin makes, says which plugin events go to which channel, matches people to their Slack accounts by email, and reads what was sent and why something was not. Use when a person asks to connect Slack, to send approved leave to a channel, to find out why someone gets no messages, or why a message did not go out.

How it works

  1. Commands
  2. Connecting Slack, in order
  3. When a message did not go out
  4. Rules
Original SKILL.md headings · 48 lines, 1,210 words
SKILL.md preview
---
name: messenger
description: "Keeps the console's messenger for whoever holds its role: connects the workspace's Slack through an app the plugin makes, says which plugin events go to which channel, matches people to their Slack accounts by email, and reads what was sent and why something was not. Use when a person asks to connect Slack, to send approved leave to a channel, to find out why someone gets no messages, or why a message did not go out."
license: MIT
metadata:
  author: skillcdn
skillcdn:
  translations:
    ko:
      title: "메신저 관리"
      description: "메신저 담당을 위해 콘솔의 메신저를 관리합니다. 플러그인이 만드는 앱으로 워크스페이스의 Slack을 연결하고, 어떤 플러그인 알림을 어느 채널로 보낼지 정하고, 이메일로 사람을 Slack 계정과 맞추고, 무엇을 보냈고 무엇이 왜 안 갔는지 봅니다. Slack을 연결해 달라거나, 승인된 휴가를 채널에 올려 달라거나, 누가 왜 메시지를 못 받는지, 메시지가 왜 안 나갔는지 물을 때 쓰세요."
---
# Keeping the messenger

The messenger carries what the console's plugins have for people to the organization's Slack, and brings back what people do there: for HR, one shortcut, 휴가 in Korean and Time off in English, whose form requests leave and cancels one's upcoming leave, and each approval threaded with the person and whoever decides. Whoever holds the role `messenger` keeps it: the connection, the routes, the matching. Everyone else meets it in Slack alone.

## Commands

| Do | Command |
|---|---|
| See how the connection stands, and the next thing to do to set it up (`next`, `text`) | `console plugin messenger status` |
| Make the Slack app, or bring it up to date, and get the address that installs it | `console plugin messenger connect [--language en|ko] [--app-name <name>] [--bot-name <name>] [--icon <https address>]` |
| Send a test message to yourself, or to a channel | `console plugin messenger test [--channel <id>]` |
| Uninstall the app from the workspace and delete it, to start again in this workspace or another | `console plugin messenger disconnect` |
| Match people to their Slack accounts by email now: everyone, or one person | `console plugin messenger match [--person <login>]` |
| See who is matched, and why the others are not | `console plugin messenger people [--state no_email|no_account|not_checked|matched] [--limit <n>]` |
| List the channels a route may name | `console plugin messenger channels [--search <words>]` |
| Send a kind of event to a channel | `console plugin messenger route <channel> [--kind hr:leave-approved] [--language en|ko] [--as person|app]` |
| List the routes | `console plugin messenger routes` |
| Take a route away | `console plugin messenger unroute <id>` |
| Read what was sent, passed over or failed | `console plugin messenger activity [--outcome sent|skipped|failed] [--limit <n>]` |

## Connecting Slack, in order

`status` says which of these steps is next, as `next` and in a line of the caller's language as `text`, and says `ready` once they are done: read it first, and again after each step.

1. **The console's address.** Slack reaches the console over https at a public address. `status` says whether it can; a console on this machine, or on http, cannot be connected, and the deployment fixes that, not the agent.
2. **The configuration token.** At api.slack.com/apps, under "Your App Configuration Tokens", someone who administers the Slack workspace generates a token for it; an administrator of the console pastes the access token as `slackConfigToken` and the refresh token as `slackConfigRefreshToken`, on the plugin's settings page or at their own terminal with `console plugin messenger secret slackConfigToken` and `console plugin messenger secret slackConfigRefreshToken`, which take the value typed unseen. A token never goes on a command line, through `echo`, or through the agent: the agent says which command to run and waits. The plugin renews them itself from then on.
3. **The app.** `connect` makes it from the plugin's manifest; the console seals its secrets from Slack's answer. `--language` sets the language of the names the app shows in Slack, the leave shortcut's among them; unless said, the workspace's language where an administrator set one (`console workspace edit --language ko`), else the caller's own, so that an agent working in English says `--language ko` for a Korean workspace that has none set. A route's `--language` falls back the same way. `--app-name` names the app in Slack, up to 35 characters in any script; `--bot-name` names its bot, in Latin letters, digits, spaces, `.`, `_` and `-` alone, since Slack makes the bot's handle (@) from it: "Acme" gives `@acme`, a number added where it is taken. Both are kept until said again, an empty value bringing back the language's own, and `status` says the handle Slack made. Ask the person for the names before the app is made: a bot renamed after it is installed may keep its handle, and the sure way to a new one is `disconnect` then `connect`, while nobody uses the app. `--icon` gives the address of a square image of 512 to 2000 pixels that anyone can open over https; Slack fetches it. Where the configuration token may not set icons, `connect` says so and where to upload it by hand on Slack's page.
4. **The installation.** `connect` answers an address on slack.com. A person who may install apps in the workspace opens it in their browser while signed in to the console, and approves; Slack sends them back to the console, which keeps the bot's token. An agent cannot do this step for them: say the address and wait.
5. **The people.** Within the hour the plugin matches everyone by email, and every day after; `match` does it now. `people --state no_email` lists those the console knows no address for, which an administrator writes on the console's People page.
6. **HR.** For the leave shortcut and the threads, an administrator turns on `plugins:hr` among the plugin's optional capabilities and grants it HR's role `hr` on the plugin's settings page; `status` says what is missing.
7. **The routes.** `channels` lists the channels; `route <channel>` sends approved leave there. A private channel takes posts only once someone invites the app to it in Slack.

To move to another workspace, as from a workspace kept for trying the plugin to the organization's own: `disconnect`, paste the other workspace's configuration tokens, then `connect` and install there. The routes and the matched accounts of the last workspace go when the new one is installed; in the same workspace they stay.

## When a message did not go out

- `activity --outcome failed` says what Slack or the console answered, and `activity --outcome skipped` why an event was passed over: Slack not connected, HR's api off, the role not granted, nobody in Slack to tell.
- Someone gets nothing: `people` says whether they are matched; a person with no email in the console, or with another address in Slack, is not.
- The shortcut is missing in Slack: `status` says whether HR is on for the messenger; the plugin puts the shortcut in the app within the hour once it is. People find it by typing its name after `/` in a message box, or in the shortcuts menu.
- Someone sees no leave to cancel in the form: the form lists only what HR 0.3.0 or later says they may cancel themselves; leave whose first day has gone by, or that their kind leaves to HR, is HR's to cancel on the console.

## Rules

- Never ask for a token in chat, never repeat one, never put one in a report: an administrator pastes it into the console, and the plugin never reads it.
- A route carries what everyone in a channel may read: who is out and when, never a reason. The reason stays in the thread of the person and whoever decides.
- People decide: the plugin answers a decision only for the person who pressed its button in Slack, as theirs, and only one on their plate. An agent answers a decision only as its person tells it, with `console answer`.
- `test` is the one message an agent sends; everything else the messenger sends follows from what happened on the console.

Versions

The database has no other skills named messenger.

Database snapshot: 13.11.2026 · package version 47dc55287373 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 86slack-connect
    Set up Slack as a notification channel for your Egregore — creates the workspace app, invites the bot, and binds a channel. Use for /slack-connect, ''connect slack'', or ''set up slack notifications''.
  • 100slack-connect
    Set up Slack as a notification channel for your Egregore — creates the workspace app, invites the bot, and binds a channel. Use for /slack-connect, 'connect slack', or 'set up slack notifications'.
  • 100okhp3-slack-channel-message
    Draft a new Slack channel message for a supplied workspace destination. Use when the user needs a clear announcement, update, question, or handoff for a named Slack channel. It returns formatted draft text only and does not send, schedule, direct-message, mention broadly, attach…
  • 100slack-messaging
    Slack channel and thread messaging skill with context-aware session management. Reads messages, sends replies, searches channels and users, drafts and schedules messages -- all via Slack MCP tools. Use this skill whenever the user wants to read Slack messages, reply in Slack,…
  • 100slack-channel
    Slack for a Pots bot. How to connect a Slack workspace yourself (the Slack app, its tokens, bot.json), send and edit messages, call Slack's Web API, files and limits, and how to post buttons, menus, tables and forms with Block Kit, get clicks and mark a question answered. Use…
  • 100tmn-slack
    (tmn) Draft and send a Slack message that a busy teammate reads once and acts on - outcome or ask in the first line, five sentences max, threaded correctly, no AI slop - and lint it before sending. Use whenever asked to post, send, reply or announce something in Slack, update a…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.