How do I install the Buddy Followup skill?

Run npx skillmds@latest add knownasnaffy/buddy-followup-5 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Buddy Followup safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Buddy Followup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Buddy Followup free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Buddy Followup?

knownasnaffy (@knownasnaffy) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Buddy Followup by knownasnaffy — Agent Skill

Name: Buddy Followup
Rating: 4.2 (5 reviews)
Author: knownasnaffy

Buddy Followup

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.

knownasnaffy Updated Sep 22, 2026 0 repo stars

File contents

Permission Setup Review

python scripts/_perms_marker.py is an optional setup helper for the buddy-followup skill. It may apply broad filesystem permissions for compatibility. Show the target paths and permission mode, explain the risk, and prefer a narrower mode when shared write access is not needed.

buddy-followup

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.

Installation

Via ClawHub (recommended):

npx clawhub install buddy-followup

When to Use

You launch a sub-agent, script, build, download, or API call that takes time
You tell the user "I'll update you when it's done" or "give me a few minutes"
You need to check back on something after a delay

How It Works

You estimate how long the task will take and call the script with that delay
Cron jobs fire at the given time on every configured channel (Telegram, WhatsApp, etc.)
You wake up with the task context, check status, and reply to the user
Still pending? Set another timer and keep the loop going
Done? Report results and close the loop

No hardcoded IDs — channels and targets are read dynamically from openclaw config get at runtime.

Usage

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.

When the Follow-Up Fires

On receiving ⏰ FOLLOW-UP (<delay>): <task>:

Check the task status
Reply directly — routes to all configured channels automatically
Done → confirm results to the user

Still running → tell the user, reset the timer:

bash ~/clawd/skills/buddy-followup/scripts/followup.sh 2m "still waiting for X, checking again"

Requirements

OpenClaw gateway running
At least one channel configured (Telegram with channels.telegram.defaultTo, or WhatsApp with channels.whatsapp.allowFrom)
openclaw CLI available in PATH

Notes

Channels are discovered at runtime — adding a new channel automatically includes it
Each timer creates one cron job per channel, deleted after firing
The agent decides the delay — base it on realistic task completion time

---name: buddy-followup-5description: 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.---### Permission Setup Review`python scripts/_perms_marker.py` is an optional setup helper for the `buddy-followup` skill. It may apply broad filesystem permissions for compatibility. Show the target paths and permission mode, explain the risk, and prefer a narrower mode when shared write access is not needed.# buddy-followup**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.## InstallationVia ClawHub (recommended):```bashnpx clawhub install buddy-followup```## When to Use- You launch a sub-agent, script, build, download, or API call that takes time- You tell the user "I'll update you when it's done" or "give me a few minutes"- You need to check back on something after a delay## How It Works1. **You estimate** how long the task will take and call the script with that delay2. **Cron jobs fire** at the given time on every configured channel (Telegram, WhatsApp, etc.)3. **You wake up** with the task context, check status, and reply to the user4. **Still pending?** Set another timer and keep the loop going5. **Done?** Report results and close the loopNo hardcoded IDs — channels and targets are read dynamically from `openclaw config get` at runtime.## Usage```bashbash ~/clawd/skills/buddy-followup/scripts/followup.sh <delay> "task context"```**Delay formats:** `30s`, `5m`, `2h`**Examples:**```bashbash ~/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.## When the Follow-Up FiresOn receiving `⏰ FOLLOW-UP (<delay>): <task>`:1. Check the task status2. Reply directly — routes to all configured channels automatically3. **Done** → confirm results to the user4. **Still running** → tell the user, reset the timer: ```bash bash ~/clawd/skills/buddy-followup/scripts/followup.sh 2m "still waiting for X, checking again" ```## Requirements- OpenClaw gateway running- At least one channel configured (Telegram with `channels.telegram.defaultTo`, or WhatsApp with `channels.whatsapp.allowFrom`)- `openclaw` CLI available in PATH## Notes- Channels are discovered at runtime — adding a new channel automatically includes it- Each timer creates one cron job per channel, deleted after firing- The agent decides the delay — base it on realistic task completion time

Frequently asked questions