Systems Lab

Agent skill

follow-up

Debrief a meeting and draft the follow-up.

activeSelf-containedInstructions only133 words

Filed under Outbound email.

From etrebels/claude-code-growth-os · 20 skill entries · 21 · pushed 2026-10-03

What it does when it runs

Debrief a meeting and draft the follow-up. Trigger when the user asks to debrief a call, follow up, or "what do I send after that meeting".

Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
None found.
Hosts it reaches
No third-party host appears in the skill or its bundled files.
Tool permissions it declares
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about follow-up

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah

Install it

View source on GitHub ↗
git clone --depth 1 --filter=blob:none --sparse https://github.com/etrebels/claude-code-growth-os.git /tmp/claude-code-growth-os
git -C /tmp/claude-code-growth-os sparse-checkout set ".claude/skills/follow-up"
mkdir -p ~/.claude/skills/follow-up
cp -R "/tmp/claude-code-growth-os/.claude/skills/follow-up/." ~/.claude/skills/follow-up/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

The skill

Source on GitHub ↗

Reproduced in full from etrebels/claude-code-growth-os/blob/3e0c2d7d1fc545d35073011208d8da3f845183fb/.claude/skills/follow-up/SKILL.md, which is licensed MIT (repository). 133 words, 2 headings.

Debrief & Follow-up

From a meeting note (point me at one in ops/ or demo/meetings/) or a pasted recap:

  1. Debrief (for you): decisions made, commitments — yours and theirs — and any new risk or signal. Offer to append it to ops/daily-log.md.
  2. Follow-up (for them): lead with the commitment you made or the decision they owe — not "just checking in". One clear next step with a date. Keep it short; a follow-up that needs scrolling doesn't get read.

Don't invent facts the note doesn't contain. Bring your own voice; this drafts the structure.

Depth

  • quick: the follow-up message only.
  • standard: debrief notes + the message + a subject line.
  • deep: + a second nudge for if they go quiet, with the date to send it.

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what follow-up does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.