quick-reminders

What This Skill Does

The quick-reminders skill provides a high-performance, low-overhead mechanism for scheduling one-shot notifications within the OpenClaw ecosystem. By leveraging background Unix processes (specifically nohup and sleep), this skill avoids the latency and resource consumption associated with spawning full Large Language Model chains at the moment of delivery. When a user requests a reminder for a task occurring less than 48 hours in the future, the agent drafts a conversational, human-like message immediately and schedules it to be dispatched via the openclaw message send utility.

Installation

To integrate quick-reminders into your OpenClaw environment, ensure your workspace has the necessary dependencies. Execute the following command within your terminal:

clawhub install openclaw/skills/skills/lstpsche/quick-reminders

This will pull the script into your project structure. Once installed, ensure that your TOOLS.md file contains the appropriate delivery targets (such as Telegram chat IDs or WhatsApp numbers) to allow the CLI script to route messages effectively. If your target is missing, the skill will attempt to resolve it using the session_status tool.

Use Cases

This skill is designed for transient, short-term task management. Ideal use cases include:

• Timing the removal of laundry from the dryer.
• Setting a quick prompt to step away from a meeting in 30 minutes.
• Scheduling a follow-up text for a friend later in the evening.
• Creating a "nudge" to check on a long-running background process.

Example Prompts

1. "Remind me to check the oven in 45 minutes."
2. "Can you ping me in 1 hour and 30 minutes to start drafting that email?"
3. "Hey, remind me to leave for the airport in 3 hours."

Tips & Limitations

• The 48-Hour Guardrail: This skill is strictly for near-term reminders. If a user requests a reminder for a date two or more days in the future, the agent must defer to the system's Calendar skill. This ensures long-term tasks are indexed correctly in a persistent store rather than relying on ephemeral background processes.
• Tone is Key: Because the delivery is automated, the agent should craft the message to sound like a human peer. Avoid robotic or system-generated phrasing. Use casual, empathetic, and concise language to ensure the reminder is helpful rather than intrusive.
• Resolution: If the script cannot locate {baseDir}, always fallback to the relative path ./skills/quick-reminders/scripts/nohup-reminder.sh to ensure consistent execution regardless of the current working directory.