What is slack-workflow-profiles?

A saved Slack catch-up profile that records which channels and people matter, how far back to read, and what kind of summary to produce. Slack is a team messaging service.

It helps prepare repeatable summaries and handoffs from selected Slack conversations, with output shaped for the intended audience.

Repeated catch-ups otherwise require choosing the same channels and priorities each time. A profile makes those instructions reusable for incidents, support, leadership updates, or launches.

slack-workflow-profiles — Skill for Claude Code and Codex by jtalk22

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add jtalk22/slack-mcp-server --skill slack-workflow-profiles

Clone the repo

git clone --depth 1 https://github.com/jtalk22/slack-mcp-server

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jtalk22/slack-mcp-server/slack-workflow-profiles/github.svg)](https://agentmods.dev/skills/jtalk22/slack-mcp-server/slack-workflow-profiles)

Your own site

<a href="https://agentmods.dev/skills/jtalk22/slack-mcp-server/slack-workflow-profiles"><img src="https://agentmods.dev/badge/skills/jtalk22/slack-mcp-server/slack-workflow-profiles/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jtalk22/slack-mcp-server/slack-workflow-profiles"><img src="https://agentmods.dev/badge/skills/jtalk22/slack-mcp-server/slack-workflow-profiles.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 79 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 936 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00079	$0.00936
Opus 5.5	$0.00032	$0.00374
Sonnet 5.5	$0.00016	$0.00187
Haiku 4.5	$0.00008	$0.00094

Measured 2d ago against content hash bf83759da1ba, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

slack-workflow-profiles scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/slack-workflow-profiles/SKILL.md · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Workflow profiles

A profile is a saved scope for slack_catch_me_up. It records which channels to read, whose messages count most, how far back to look, and which output keys the catch-up asks for. Profiles are stored on this machine in ~/.slack-mcp-workflows.json. Saving one sends nothing to Slack.

Choose the kind

The kind decides which keys slack_catch_me_up asks you to write.

`workflow_kind`	Use it for	Keys the catch-up asks for
`incident_room`	an incident channel, an on-call handoff	`incident_summary`, `timeline`, `open_risks`, `owner_gaps`, `next_actions`
`support_inbox`	customer or internal support queues	`open_threads`, `ack_lag`, `owner_gaps`, `escalations`, `next_actions`
`exec_brief`	a leadership digest across several channels	`summary`, `decisions`, `risks`, `asks`, `action_items`
`product_launch_watch`	a launch, a release cycle, a feedback stream	`launch_signals`, `feedback_themes`, `blockers`, `metrics`, `next_actions`
`custom`	anything else	`summary`, `highlights`, `open_questions`, `next_actions`

Build it

Ask what the catch-up is for and who reads it, then pick the kind.
Channels: call slack_list_conversations and use channel IDs. Names also match when the catch-up runs, but IDs survive a rename. Without that tool, ask the user for the channel names. If you leave channels empty, every catch-up reads whatever is unread at that moment.
Priority people: call slack_users_search with a name or email and put the user IDs in priority_people. Without that tool, ask the user for the IDs. Their messages and their mentions get their own lists in the catch-up.
summary_cadence sets the default look-back: 24 hours for on_demand and daily_8am, 7 days for weekly_monday. It schedules nothing. Something still has to call slack_catch_me_up.
retention_mode (ephemeral by default, or persistent) is recorded on the profile. This server does not act on it.
Call slack_workflow_save with profile_name, workflow_kind and the fields above. Saving an existing profile_name replaces the profile, and a field you leave out returns to its default, so send every field to change one. Confirm with slack_workflows, then run slack_catch_me_up once so the user sees what the profile returns.

Read the full file on GitHub · 66 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 66 lines · 79 tokens per session scan A bf83759da1ba

Subscribe to this mod's changes

slack-workflow-profiles is a skill published in the GitHub repository jtalk22/slack-mcp-server (32 stars, last pushed 3d ago), licensed MIT. It adds 79 tokens to every session and 936 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-11-04.

Productivity Project management ai-agents claude cursor mcp mcp-server model-context-protocol

slack-workflow-profiles next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
slack-workflow-profilesjtalk22/slack-mcp-server	Skill	32	3d ago	MIT	A	79	Claude Code, Codex
help-flowgriddynamics/rosetta	Skill	370	today	Apache-2.0	A	13	Claude Code, Codex
deja-reflectvshulcz/deja-vu	Skill	1.4k	today	MIT	A	49	Claude Code
modernization-flowgriddynamics/rosetta	Skill	370	today	Apache-2.0	A	36	Claude Code, Codex
external-lib-flowgriddynamics/rosetta	Skill	370	today	Apache-2.0	A	20	Claude Code, Codex
coding-flowgriddynamics/rosetta	Skill	370	today	Apache-2.0	A	24	Claude Code, Codex
coding-agents-prompting-flowgriddynamics/rosetta	Skill	370	today	Apache-2.0	A	28	Claude Code, Codex