
Pp Slack
- 341 installs
- 1.9k repo stars
- Updated August 4, 2026
- mvanhorn/printing-press-library
pp-slack is a Printing Press agent skill that exposes a terminal Slack workspace CLI for posting messages, searching channels and DMs, and analyzing channel health using standardized webhook and bot integration patterns
About
pp-slack is a Printing Press library agent skill that turns Slack into a terminal-first workspace CLI for coding agents. The skill guides agents to send channel messages, reply to slash commands, deliver team notifications, search channels and direct messages, list conversations, and retrieve user, bot, and emoji metadata through standardized Printing Press webhook and bot integration patterns. Authentication spans two token types: SLACK_BOT_TOKEN (xoxb-) for workspace-wide read and post actions, and SLACK_USER_TOKEN (xoxp-) for user-scoped operations like DM history and search. Beyond messaging, pp-slack supports channel health analysis, stale thread detection, pinned-item and reminder listing, digest summarization, and local workspace sync for offline-capable queries. Developers reach for pp-slack when automating release announcements, incident updates, or workspace audits without leaving the agent session or writing one-off Slack API scripts.
- Slack messaging
- Printing Press
- channel posts
- team notifications
- workflow bots
Pp Slack by the numbers
- 341 all-time installs (skills.sh)
- +14 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #473 of 2,715 Automation & Workflows skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/mvanhorn/printing-press-library --skill pp-slackAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 341 |
|---|---|
| repo stars | ★ 1.9k |
| Last updated | August 4, 2026 |
| Repository | mvanhorn/printing-press-library ↗ |
How do you automate Slack messages from a coding agent?
Post channel updates, slash-command replies, and team notifications to Slack using Printing Press standardized webhook and bot integration patterns.
Who is it for?
Developers wiring Slack bots, webhooks, or agent workflows who need terminal-driven messaging, search, and channel analytics without custom API glue.
Skip if: Teams that only need occasional manual Slack posts or already manage Slack exclusively through a dedicated MCP server with full UI coverage.
When should I use this skill?
User asks to send a Slack message, search channels or DMs, check channel health, find stale threads, list users or emoji, or sync Slack for offline queries.
What you get
Posted Slack messages, channel search results, health reports, stale-thread lists, and locally synced workspace data
- Slack channel messages
- channel health reports
- locally synced workspace cache
By the numbers
- Uses two Slack token types: SLACK_BOT_TOKEN (xoxb-) and SLACK_USER_TOKEN (xoxp-)
Files
<!-- GENERATED FILE — DO NOT EDIT. This file is a verbatim mirror of library/productivity/slack/SKILL.md, regenerated post-merge by tools/generate-skills/. Hand-edits here are silently overwritten on the next regen. Edit the library/ source instead. See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->
Slack - Printing Press CLI
Prerequisites: Install the CLI
This skill drives the slack-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:
1. Install via the Printing Press installer. It defaults binaries to $HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:
npx -y @mvanhorn/printing-press-library install slack --cli-only2. Verify: slack-pp-cli --version 3. Ensure the reported install directory is on $PATH for the agent/runtime that will invoke this skill.
If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.4 or newer):
go install github.com/mvanhorn/printing-press-library/library/productivity/slack/cmd/slack-pp-cli@latestIf --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.
When to Use This CLI
Reach for this when the user wants:
- send a Slack message to a channel or DM
- search Slack across channels, DMs, and threads (live or synced)
- list users, channels, usergroups, custom emoji, pinned items, or reminders
- understand channel health (quiet channels, activity trends, response times, digest)
- find stale or unanswered threads across the workspace
- pull an activity summary for a user or channel
- export channel history to JSONL for archival or migration
- discover the funniest messages in public channels (local-sync-powered novelty query)
Skip it when the user wants to create Slack apps, workflows, or manage admin-only team settings beyond team access logs. Those surfaces are better served by the Slack web admin.
Two Auth Surfaces
Slack has two parallel token types and this CLI supports both:
| Token | Scopes | When to use |
|---|---|---|
SLACK_BOT_TOKEN (xoxb-) | workspace-scoped bot permissions | Default for post-message, read-channel, list-users, etc. |
SLACK_USER_TOKEN (xoxp-) | user-scoped | DM history, search on behalf of a user, stars, reminders |
Set whichever the workspace permits. If both are set, user-token wins for user-scoped endpoints and bot-token otherwise. Get a token at https://api.slack.com/apps -> your app -> OAuth & Permissions.
Argument Parsing
Parse $ARGUMENTS:
1. Empty, `help`, or `--help` -> show slack-pp-cli --help 2. Starts with `install` -> ends with mcp -> MCP installation; otherwise -> CLI installation 3. Anything else -> Direct Use (map to the best command and run it)
MCP Server Installation
The CLI also ships an MCP server at slack-pp-mcp. Install and register:
go install github.com/mvanhorn/printing-press-library/library/productivity/slack/cmd/slack-pp-mcp@latest
claude mcp add -e SLACK_BOT_TOKEN=xoxb-... slack-pp-mcp -- slack-pp-mcpAsk the user for the actual token value before running.
Direct Use
1. Check installed: which slack-pp-cli. If missing, offer CLI installation. 2. Discover commands: slack-pp-cli --help; drill into slack-pp-cli <cmd> --help. 3. Match the user query to the best command (see Notable Commands below). 4. Execute with --agent for structured output:
slack-pp-cli <command> [args] --agent5. The --agent flag sets --json --compact --no-input --no-color --yes.
Source routing (local vs live) is controlled by --data-source: auto (default) prefers local-synced data with live fallback; live always hits the API; local runs fully offline against the SQLite snapshot. Run slack-pp-cli sync first to populate the local store for analytics queries.
Notable Commands
| Command | What it does |
|---|---|
conversations | List channels and DMs in the workspace |
users | List all users in the workspace |
search <query> | Full-text search across synced messages (or live API with --data-source live) |
digest | Daily/weekly activity digest from locally synced data |
health | Channel health report (activity, engagement, stagnation) |
quiet | Find dead or low-activity channels |
response-times | Average first-response time in threads |
threads-stale | Unanswered or stale threads |
activity <user-or-channel> | Activity summary across channels from local sync |
trends | Week-over-week channel activity trends |
sync | Populate the local SQLite store for offline analytics |
emoji / reminders / pins / stars | Workspace directory queries |
team | Access logs (requires admin token) |
Run any command with --help for full flag documentation.
Agent Mode
Add --agent to any command. Expands to: --json --compact --no-input --no-color --yes.
- Pipeable — JSON on stdout, errors on stderr
- Filterable —
--selectkeeps a subset of fields, with dotted-path support (see below) - Previewable —
--dry-runshows the request without sending - Cacheable — GET responses cached for 5 minutes, bypass with
--no-cache - Non-interactive — never prompts, every input is a flag
Filtering output
--select accepts dotted paths to descend into nested responses; arrays traverse element-wise:
slack-pp-cli <command> --agent --select id,name
slack-pp-cli <command> --agent --select items.id,items.owner.nameUse this to narrow huge payloads to the fields you actually need — critical for deeply nested API responses.
Response envelope
Data-layer commands wrap output in {"meta": {...}, "results": <data>}. Parse .results for data and .meta.source to know whether it's live or local. The N results (live) summary is printed to stderr only when stdout is a TTY; piped/agent consumers see pure JSON on stdout.
Exit Codes
| Code | Meaning |
|---|---|
| 0 | Success |
| 2 | Usage error (wrong arguments) |
| 3 | Resource not found (channel, user, message) |
| 4 | Authentication required (token missing or invalid) |
| 5 | API error (Slack upstream, including not_in_channel, channel_not_found) |
| 7 | Rate limited (Slack 429; CLI honors Retry-After) |
Related skills
How it compares
Pick pp-slack over generic HTTP skills when you need Printing Press-standardized Slack bot, webhook, and terminal CLI patterns with dual-token auth and offline workspace sync.
FAQ
What Slack tokens does pp-slack use?
pp-slack supports two Slack auth surfaces. SLACK_BOT_TOKEN (xoxb-) enables workspace-wide read and post actions. SLACK_USER_TOKEN (xoxp-) covers user-scoped tasks like DM history and search.
Can pp-slack search Slack without live API calls?
pp-slack can sync a Slack workspace locally for offline-capable queries, letting agents search channels and conversations from cached data when repeated live API access is slow or costly.
When should a developer use pp-slack?
pp-slack fits developers automating channel updates, slash-command replies, digest summaries, or channel health audits from coding agents using Printing Press standardized webhook and bot patterns.