Post a daily standup to slack
Slack standup automation is an Agent Skill: a written method your AI applies on demand, in Zealos or in any client that reads SKILL.md.
Slack standup automation is an Agent Skill: a written method your AI applies on demand, in Zealos or in any client that reads SKILL.md.
An automated standup is only read if it is short and specific: what moved, what is blocked, and what nobody has touched — with the last category being the one that justifies posting at all.
| name | call-recap-format |
|---|---|
| description | The structure of a good call recap: commitments, owners, dates, risks. Use when summarising a recorded call or meeting, or writing a follow-up that has to survive being forwarded. |
| allowed-tools | none — this skill adds judgement, not reach |
| compatibility | Zealos, Claude Code, Cursor, Codex and any client that reads SKILL.md |
| license | Free to use and edit |
--- name: call-recap-format description: The structure of a good call recap: commitments, owners, dates, risks. Use when summarising a recorded call or meeting, or writing a follow-up that has to survive being forwarded. --- # Call recap format A recap is read by someone who was not on the call. Write for them. ## Structure **One line up top:** what was decided, or that nothing was. **Commitments** — the only section that always matters. Each line: *who* · *what* · *by when*. Both sides. If a date was not said, write "no date agreed" rather than inventing one. **What we learned** — new facts only. Not a transcript. Three bullets is plenty. **Risks and open questions** — what could kill this, and what we still do not know. If a concern was raised and not resolved, it goes here even if the tone was friendly. **Next step** — one action, one owner, one date. ## Rules - Quote the customer where the exact words matter (pricing, scope, timing). - Separate what they said from what you concluded. Mark inferences as inferences. - Do not soften bad news. A recap that reads better than the call did is worse than useless. - If the call had no commitments, say that. It is the most important thing on the page. ## Length Under 200 words. If it is longer, the call did not have that much in it and you are padding.
The team channel gets a short, honest picture every morning without anyone spending the first fifteen minutes assembling it.
You can tell what is actually moving across a small team without a meeting that costs six people half an hour.
Stalled work becomes visible on the day it stalls rather than at the next weekly review.
Any channel the connected Slack bot has been invited to. The skill decides what is worth saying; the agent decides where.
Write the restraint into the skill. The most valuable line in a digest skill is the list of things not worth posting.
Only the ones the connected bot has been invited to, and inviting it is a deliberate act by someone in that channel. A skill decides what to do with what an agent can already see; it never widens access.
It replaces the reporting half — the part where six people take turns describing what they did. What it cannot replace is the conversation that happens when two of them realise they are blocked on each other.
Post-call automation turns a recorded conversation into the three things that outlive it: the commitments each side made, the fields that changed, and the follow-up that has to go out today.
/call-recap-formatA pre-call brief is worth writing only if it changes what you ask: who is in the room, what they are measured on, what happened last time, and the one question you cannot afford to leave without answering.
/discovery-questionsA follow-up gets a reply when it opens with the specific commitment made on the call, stays under 120 words, and asks for exactly one thing the recipient can answer in a sentence.
/email-rulesAutomatic call scoring is only fair if the rubric is visible: score the observable things — whether a next step was agreed, whether questions were about the past — and leave judgement to a human.
/discovery-questionsAfter-call work is the twenty minutes nobody books: the CRM update, the recap, the follow-up, the task for the thing you promised — and it is the first work to disappear on a busy day.
/call-recap-formatA useful Zoom summary is not a compression of the transcript: it is the commitments, the decisions and the unresolved risks, written for someone who was not on the call.
/call-recap-format