Follow up
Skill etrebels/claude-code-growth-os/.claude/skills/follow-up
Claude Code Growth Operating System (OS): Sales, Marketing, Product and Retention as one Revenue system
npx -y skills add etrebels/claude-code-growth-os --skill follow-upAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 17 stars17 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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".
SKILL.md
0.9 KB, as published. Nobody here has run it
Debrief & Follow-up
From a meeting note (point me at one in ops/ or demo/meetings/) or a pasted recap:
- Debrief (for you): decisions made, commitments — yours and theirs — and any new risk or signal. Offer to append it to
ops/daily-log.md. - 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.