Agents say "I'll follow up" — and then forget. This skill fixes that. When you kick off a long-running task (sub-agent, build, API call, script), set a timer before you move on. When it fires, you wake up with the original context on every configured channel and actually deliver the update you promised. If the task isn't done yet, set another timer and keep going. No hardcoded IDs — channels are read dynamically from OpenClaw config.
Agents say "I'll follow up" — and then forget. This skill fixes that.
When you kick off a long-running task and tell the user "I'll get back to you", use this to actually follow through — automatically, on every configured channel.
Via ClawHub (recommended):
npx clawhub install buddy-followup
No hardcoded IDs — channels and targets are read dynamically from openclaw config get at runtime.
bash ~/clawd/skills/buddy-followup/scripts/followup.sh <delay> "task context"
Delay formats: 30s, 5m, 2h
Examples:
bash ~/clawd/skills/buddy-followup/scripts/followup.sh 2m "check if sub-agent finished building the API"
bash ~/clawd/skills/buddy-followup/scripts/followup.sh 10m "check if deployment completed"
bash ~/clawd/skills/buddy-followup/scripts/followup.sh 30s "verify test results are ready"
Run via exec tool — the script exits immediately after scheduling. No background flag needed.
On receiving ⏰ FOLLOW-UP (<delay>): <task>:
bash ~/clawd/skills/buddy-followup/scripts/followup.sh 2m "still waiting for X, checking again"
channels.telegram.defaultTo, or WhatsApp with channels.whatsapp.allowFrom)openclaw CLI available in PATH