Reminder Engine

Create, list, cancel, and snooze reminders using OpenClaw cron jobs (one-shot or recurring). Use when a user asks things like: 'remind me in 20 minutes', 're...

Security Scan

The skill's requirements and runtime instructions are consistent with a reminder/cron scheduling helper and do not request unrelated credentials or install code — it appears to be what it says it is.

Purpose & Capability

Name/description match the instructions: the SKILL.md only describes parsing reminder intents, confirming schedules, and creating/listing/cancelling cron jobs. There are no unrelated env vars, binaries, or install steps requested.

Instruction Scope

Instructions stay within reminder management (create/list/remove/snooze) and explicitly forbid including secrets and spammy broadcasts. A small caveat: it tells the agent to include light conversational context and to use payload.kind="systemEvent" and sessionTarget="main" — these are platform-specific fields that could affect where and how reminders are delivered, so the operator should confirm what "systemEvent" and sessionTarget imply on your platform (delivery channel, visibility, privileges).

Install Mechanism

Instruction-only skill with no install spec and no code files; nothing is written to disk and no external packages are pulled. This minimizes install-time risk.

Credentials

The skill declares no required environment variables, credentials, or config paths. The SKILL.md does not instruct reading unrelated secrets or system files; it even warns to avoid secrets in reminder payloads.

Persistence & Privilege

always is false and there are no install side-effects. The skill can be invoked autonomously (platform default) but that is not, by itself, a red flag. If you are concerned about autonomous scheduling, verify platform controls for when the agent can create cron jobs and whether user confirmation prompts are enforced at runtime.

Assessment

This skill is internally coherent for creating and managing reminders. Before installing, verify: (1) your platform's "cron" tool and what payload.kind="systemEvent" and sessionTarget="main" actually do (delivery behavior, visibility, and any side effects); (2) that the agent will always show the confirmation prompt the skill requires before creating recurring jobs; and (3) that reminder payloads will not leak sensitive info (the skill warns about secrets, but you should still avoid including tokens/passwords in reminder text). If you need higher assurance, ask the publisher for a link to platform docs or an implementation example showing the cron API calls this SKILL.md expects.

Turn natural-language reminders into OpenClaw cron jobs.

Workflow

1) Parse intent

Classify the request:

• One-shot: “in 20 minutes”, “tomorrow at 9”, “on March 1st at 10:00”
• Recurring: “every day at 9”, “every weekday at 10:30”, “every Monday”, “every 2 hours”
• Management: “list reminders”, “cancel X”, “disable/enable”, “snooze X”

Extract:

• reminder text (what should be said when it fires)
• delivery channel context (current chat unless user specifies otherwise)
• timezone (default to the runtime timezone unless user specifies)

2) Confirm schedule (always)

Before creating/updating/removing jobs, echo back:

• the computed schedule in human form (and timezone)
• whether it’s one-shot or recurring
• the exact reminder message text

If the user’s wording is ambiguous (“next Friday”, “in the morning”), ask a single clarifying question.

3) Create the cron job (reminders)

Use the cron tool.

Rules:

• Prefer schedule.kind="at" for one-shots.
• Prefer schedule.kind="cron" for recurring reminders (use tz when possible).
• Use sessionTarget="main" and payload.kind="systemEvent".
• Write payload text like a reminder: start with “Reminder:” (especially if the reminder is set far in advance).
• Include light context if it helps (“Reminder: submit the invoice (you said you need this for the client call)”).

4) List / cancel / snooze

• List: use cron.list, show jobId + next run + name/summary.
• Cancel: cron.remove(jobId) (prefer cancelling by exact jobId; if user provides text, search list and confirm).
• Snooze: implement as cancel+recreate (one-shot) or a one-shot override reminder.

Reminder text quality

• Keep it short and action-oriented.
• Avoid secrets.
• If the reminder is for a public channel, warn the user.

Safety

• Never create spammy recurring reminders without explicit confirmation.
• Never “broadcast” reminders to multiple targets unless explicitly requested.
• Never include access keys/tokens in reminder payloads.

Examples (what good looks like)

User: “remind me in 20 minutes to stretch”

• Create one-shot at job.
• Payload text: Reminder: stretch.

User: “every weekday at 10:30 remind me to stand up”

• Create recurring cron job in local timezone.
• Payload text: Reminder: stand up (weekday standup alarm).

User: “list my reminders”

• List jobs; show ids so the user can say “cancel <id>”.

User: “cancel the stand up reminder”

• List matching jobs, ask which one if multiple, then remove.