plugins/ls-slack/skills/slack-message/SKILL.md
Use when asked to draft, write, or format a message for Slack. Produces raw text the user can copy into Slack, then format with Cmd+Shift+F.
npx skillsauth add LandonSchropp/agent-toolkit plugins/ls-slack/skills/slack-messageInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
The user will copy your output, paste it into Slack, and press Cmd+Shift+F to convert the pseudo-markdown into Slack's rich formatting.
Output the message directly — no preamble ("Here's the message:"), no trailing commentary, no wrapping code block. The message is the entire response.
REQUIRED: See references/slack-formatting.md for the exact pseudo-markdown Slack accepts, what passes through literally, and what is NOT supported.
| Thought | Reality |
| ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| "I'll use **bold** — that's standard markdown" | Slack requires single asterisks. Double asterisks render literally in Slack. |
| "I'll add a # Header for structure" | Cmd+Shift+F doesn't convert headers. Use a *bold line* instead. |
| "I'll add a short intro before the message" | The message IS the response. Any text outside it is noise the user has to skip past. |
| "I'll use • bullets for list items" | Bullets can't be copy-pasted into Slack's list format. Write list items as plain lines separated by a single newline — the user will apply the list style manually. |
tools
Use when a finished, reviewed branch is committed and needs to be merged into the default branch in a repo that integrates directly to `main` (not via pull request).
tools
Use when working with a stack of GitHub pull requests — creating branches, keeping the stack in sync, or merging in order. Covers Git Town setup, PR targeting, rebasing, and landing the stack.
tools
Use when writing or modifying tests in a Bun project
tools
Use when publishing or releasing a new version of an npm/pnpm/yarn/bun package to the registry. Covers package-manager detection, semver bump selection, tagging, pushing, scoped-package access, authentication, and one-time passwords (OTP).