← Back to Skills Marketplace
Quick Reminders
by
Nikita Shkoda
· GitHub ↗
· v1.1.4
5100
Downloads
9
Stars
0
Active Installs
6
Versions
Install in OpenClaw
/install quick-reminders
Description
Zero-LLM one-shot reminders (<48h) via nohup sleep + openclaw message send, operated via {baseDir}/scripts/nohup-reminder.sh.
Usage Guidance
Install only if you are comfortable with this skill starting short-lived background processes that later send messages using your existing OpenClaw setup. Keep reminder text low-sensitivity, review or protect `reminders.json`, and be cautious using `remove` if that state file could have been edited by something else.
Capability Analysis
Type: OpenClaw Skill
Name: quick-reminders
Version: 1.1.4
The 'quick-reminders' skill is designed for one-shot reminders and appears benign. The `SKILL.md` provides clear instructions for the agent, including guardrails and message composition guidelines, without any evidence of prompt injection attempts to subvert the agent. The `nohup-reminder.sh` script uses `nohup` and `sleep` to schedule reminders, leveraging `jq` for JSON management and `openclaw message send` for delivery. It employs robust shell scripting practices, such as `set -euo pipefail`, file-based locking, atomic JSON updates, and careful argument handling for the `nohup bash -c` command to mitigate shell injection risks. Temporary message files are created with `umask 077` for security, and PIDs are validated before `kill` operations. The `README.md` provides transparent documentation on data access, security considerations, and limitations, confirming no credential handling or unauthorized data exfiltration. All operations align with the stated purpose of a reminder skill.
Capability Assessment
Purpose & Capability
The purpose is coherent: short-horizon reminders delivered later through `openclaw message send`. The background process and message delivery are disclosed and align with that purpose.
Instruction Scope
The skill says reminders are for under 48 hours and tells agents to use a calendar for 2+ days, but the script does not enforce that limit and accepts longer relative or absolute times.
Install Mechanism
No hidden installer or package installation behavior was found. The skill declares `jq` and `openclaw` as required binaries.
Credentials
The file and process access is mostly proportionate, but `remove` deletes the `.msg_file` path loaded from mutable `reminders.json` without validating that it is one of the skill's own temp files.
Persistence & Privilege
Detached `nohup`/`disown` workers are central to the feature and are documented, but they can outlive the session and use existing OpenClaw messaging credentials later; cancellation exists, but runtime duration is not technically bounded.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install quick-reminders - After installation, invoke the skill by name or use
/quick-reminders - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.1.4
- No user-visible changes;
- README updated.
v1.1.3
- Removed the _meta.json file from the skill.
- No changes to user experience or skill functionality.
v1.1.2
- Added _meta.json file for enhanced metadata support.
- Updated SKILL.md: "openclaw" is now a required binary dependency in metadata.
v1.1.1
Version 1.1.1
- Minor edit to Rule 4 for clearer instructions: "remove old → add new" changed to "remove old, then add new".
- No functional or command changes; behavior remains the same.
v1.1.0
Version 1.1.0
- Replaced unsafe bash -c string interpolation with argument-based detached runner execution (fixes injection/broken quoting risks for --channel, --target, paths)
- Added per-workspace temp message file naming using WORKSPACE_KEY (oclaw-rem-<workspace-key>-<id>.msg) to prevent cross-workspace collisions
- Added lock-based state protection (LOCK_DIR, acquire_lock, release_lock) around add, list, and remove to avoid concurrent JSON races
- Added atomic JSON writer (write_json with unique mktemp temp files) and replaced fixed .tmp writes
- Stored msg_file in each reminder record and updated removal logic to delete recorded file path reliably (with fallback cleanup for old filename format)
- Added pre-ID prune under lock so max(id)+1 runs on cleaned, synchronized state
- Hardened process/file handling:
- reminder message file now written with restricted perms via umask 077
- kill now guarded to numeric PIDs only
v1.0.0
- Initial release of quick-reminders: set human-friendly, one-shot reminders for up to 48 hours, delivered via openclaw CLI.
- Composes reminder messages at creation time (no LLM used at delivery).
- Strict <2 days guardrail — longer reminders are redirected to calendar with an explanation.
- Supports multiple channels (Telegram default; WhatsApp, Discord, Signal, iMessage via flag).
- CLI-only operation with easy commands for add, list, and remove.
- Reminder messages use a casual, friendly tone, never robotic.
- Confirmation responses are concise and future-tense (e.g., "Will do", "Got it").
Metadata
Frequently Asked Questions
What is Quick Reminders?
Zero-LLM one-shot reminders (<48h) via nohup sleep + openclaw message send, operated via {baseDir}/scripts/nohup-reminder.sh. It is an AI Agent Skill for Claude Code / OpenClaw, with 5100 downloads so far.
How do I install Quick Reminders?
Run "/install quick-reminders" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Quick Reminders free?
Yes, Quick Reminders is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Quick Reminders support?
Quick Reminders is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Quick Reminders?
It is built and maintained by Nikita Shkoda (@lstpsche); the current version is v1.1.4.
More Skills