slack-standup-digest
Skill167 starsChanged 16 days agoMITView on GitHub
Create an automation that generates an async standup digest from Slack. Searches selected channels for messages since the previous workday, groups updates by project, highlights blockers and decisions, and posts a summary to a target channel.
- Reads credentials
- Sends data out
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Slack MCP: must be installed in Settings → MCP.
- Distinctive: line 27
Ask the user for:
- Distinctive: line 47
If it fails, tell the user to install the Slack MCP integration first.
- Distinctive: line 71
Use the prompt preset endpoint:
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Slack Standup Digest Automation
Set up a recurring automation that summarizes Slack activity into an async standup digest.
Prerequisites
Required integration
- Slack MCP must be installed in Settings → MCP.
Information to collect
Ask the user for:
- Source channels — which Slack channels to scan for updates (e.g.
#engineering,#frontend,#backend) - Target channel — where the digest should be posted (e.g.
#standup,#team-updates) - Schedule — when should the digest run? Default: weekday mornings at 9 AM
- Timezone — user's timezone (e.g.
America/New_York,Europe/London) - Auto-post or draft — should the digest post automatically, or be saved for the user to review and approve first?
- Grouping — how should updates be organized? Default: by project/channel, with sections for shipped work, active work, blockers, and decisions
Setup Workflow
Step 1 — Verify Slack MCP access
Confirm the Slack MCP integration is working:
Use the Slack MCP to search for recent messages in one of the source channels.If it fails, tell the user to install the Slack MCP integration first.
Step 2 — Configure the schedule
Build a cron schedule from the user's preferences:
- Weekday mornings at 9 AM ET:
0 9 * * 1-5with timezoneAmerica/New_York - Daily at 8 AM UTC:
0 8 * * *
Step 3 — Build the digest prompt
Construct a prompt that includes:
- Source channels to scan
- Target channel for posting
- Lookback window (typically "since previous workday" — Friday→Monday for Monday digests)
- Grouping structure (by project, by channel, etc.)
- Whether to auto-post or draft
- What to highlight: blockers, decisions, shipped items, unanswered questions
Step 4 — Create the automation
Set OPENHANDS_HOST and AUTH_HEADER for the request below:
- OpenHands Cloud or Enterprise - a
<HOST>value is in your system prompt: use it asOPENHANDS_HOST, withAUTH_HEADER="Authorization: Bearer $OPENHANDS_API_KEY" - Local Agent Canvas - an Automation backend is listed in
<RUNTIME_SERVICES>: use itsurl_from_agentasOPENHANDS_HOST, withAUTH_HEADER="X-Session-API-Key: $OPENHANDS_AUTOMATION_API_KEY"
Use the prompt preset endpoint:
curl -s -X POST "${OPENHANDS_HOST}/api/automation/v1/preset/prompt" \
-H "$AUTH_HEADER" \
-H "Content-Type: application/json" \
-d '{
"name": "Slack Standup Digest",
"prompt": "<constructed digest prompt>",
"trigger": {"type": "cron", "schedule": "<schedule>", "timezone": "<tz>"}
}'PowerShell note: use curl.exe for this exact flag syntax, and replace ${OPENHANDS_HOST} / $AUTH_HEADER with $env:OPENHANDS_HOST / $env:AUTH_HEADER if running it natively.
Step 5 — Confirm
Tell the user:
✅ Slack Standup Digest is running!
- Automation ID:
{id}- Source channels:
{channel list}- Target channel:
{target}- Schedule:
{cron description}- Mode:
{auto-post or draft}
In this repository68 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-javadocSkill
- add-skillSkill
- agent-canvas-environmentSkill
- agent-creatorSkill
- agent-memorySkill
- agent-sdk-builderSkill
- azure-devopsSkill
- bitbucket-cloudSkill
- bitbucket-data-centerSkill
- bitbucketSkill
- canvas-extension-apiSkill
- code-reviewSkill
- code-simplifierSkill
- datadogSkill
- denoSkill
- discordSkill
- dockerSkill
- evidence-based-citationsSkill
- flarglebargleSkill
- frontend-designSkill
- github-actionsSkill
- github-agents-md-maintainerSkill
- github-delivery-watchdogSkill
- github-issue-to-prSkill
- github-issue-triageSkill
- github-pr-reviewerSkill
- github-pr-reviewSkill
- github-repo-monitorSkill
- githubSkill
- github-stale-ci-pr-closerSkill
- gitlab-issue-to-mrSkill
- gitlabSkill
- incident-retrospectiveSkill
- iterateSkill
- jira-issue-to-prSkill
- jupyterSkill
- kubernetesSkill
- learn-from-code-reviewSkill
- linearSkill
- linear-triageSkill
- news-digestSkill
- notionSkill
- npmSkill
- openhands-apiSkill
- openhands-automationSkill
- openhands-enterprise-troubleshootingSkill
- openhands-sdkSkill
- pdflatexSkill
- plain-english-contentSkill
- prdSkill
- qa-changesSkill
- release-notesSkill
- research-briefSkill
- securitySkill
- simplified-technical-englishSkill
- skill-creatorSkill
- slack-channel-monitorSkill
- spark-version-upgradeSkill
- sshSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

