Remind Me 2.1.0

Set reminders using natural language. Automatically creates one-time cron jobs and logs to markdown.

Security Scan

The skill's files and instructions partially match a reminder tool, but there are multiple mismatches and undeclared external behaviors (hardcoded paths, undeclared dependencies, and sending messages to a fixed Telegram recipient) that deserve caution.

Purpose & Capability

The description says it creates cron jobs and logs to markdown, which aligns with some files, but the scripts depend on a local project (cd /home/julian/clawdbot) and run 'npx tsx src/index.ts cron add' to create jobs and deliver messages via Telegram to a hardcoded recipient. The manifest declared only 'bash' and 'date' as required binaries; 'npx', 'tsx', and 'jq' are required by the scripts but not declared. Requiring a local Clawdbot repo and an external delivery channel is beyond the simple "cron + markdown" description and is not justified in the metadata.

Instruction Scope

SKILL.md instructs the agent to run the included scripts which read/write /home/julian/clawd/reminders.md and invoke the Clawdbot CLI (via npx) to deliver messages over Telegram to a fixed id (6636746252). The check-reminders.sh script expects unchecked items formatted as '- [ ] ...' and marks them '[x]', but create-reminder.sh and create-recurring.sh log entries as '- [scheduled]' and '- [recurring]', so the check script will not detect or mark those entries—an operational inconsistency. The scripts thus (a) modify user files in a hardcoded home path, (b) invoke a local JS tool with network/external-delivery side effects, and (c) will likely not work as intended due to inconsistent log formats.

Install Mechanism

There is no declared install spec (instruction-only), which is lower risk in isolation. However, the bundled scripts assume a node/npm environment ('npx', 'tsx') and 'jq' are available and that a local project exists at /home/julian/clawdbot. Those implicit dependencies increase runtime risk because arbitrary JavaScript code will be executed via npx from that repo (or will fail if absent).

Credentials

The skill declares no required environment variables or credentials but calls into a local Clawdbot command that delivers messages to Telegram (--channel telegram --to 6636746252). That implies the Clawdbot project must have credentials/config for delivery; those secrets are not declared. The hardcoded recipient ID means reminder content will be sent to a fixed external target (possible data leakage). No justification is provided for these credentials/targets in the SKILL.md.

Persistence & Privilege

always:false (normal) and the skill does not request system-wide privileges or modify other skills. It does, however, write to and edit a hardcoded file path (/home/julian/clawd/reminders.md) and assumes a particular user's directory layout; this limit of scope reduces broad privilege but makes the skill brittle and user-specific.

What to consider before installing

Do not install blindly. Key concerns: (1) The scripts call 'npx tsx' in /home/julian/clawdbot and will execute code from that repo (or fail) — ensure you control and inspect that project. (2) Reminders are delivered via Telegram to a hardcoded recipient (6636746252) — this will send reminder text externally and could leak sensitive info; confirm the recipient is intended. (3) The code requires undeclared tools ('npx', 'tsx', 'jq') and uses a hardcoded home path (/home/julian) making it user-specific. (4) There is an inconsistency: check-reminders.sh looks for '- [ ]' items, but create-* scripts log '- [scheduled]'/'- [recurring]', so automatic delivery may not work as written. Actions to consider before proceeding: ask the publisher to explain the Telegram target and provide required environment/dependency documentation; run the scripts in a safe isolated test user account after installing and inspect the local /home/julian/clawdbot code; or reject the skill until these inconsistencies and undeclared external deliveries are resolved.

Remind Me

Natural language reminders that fire automatically. Uses cron for scheduling, markdown for logging.

Usage

One-Time Reminders

Just ask naturally:

• "Remind me to pay for Gumroad later today"
• "Remind me to call mom tomorrow at 3pm"
• "Remind me in 2 hours to check the oven"
• "Remind me next Monday at 9am about the meeting"

Recurring Reminders

For repeating reminders:

• "Remind me every hour to stretch"
• "Remind me every day at 9am to check email"
• "Remind me every Monday at 2pm about the meeting"
• "Remind me weekly to submit timesheet"

How It Works

1. Parse the time from your message
2. Create a one-time cron job with --at
3. Log to /home/julian/clawd/reminders.md for history
4. At the scheduled time, you get a message

Time Parsing

One-Time Reminders

Relative:

• "in 5 minutes" / "in 2 hours" / "in 3 days"
• "later today" → 17:00 today
• "this afternoon" → 15:00 today
• "tonight" → 20:00 today

Absolute:

• "tomorrow" → tomorrow 9am
• "tomorrow at 3pm" → tomorrow 15:00
• "next Monday" → next Monday 9am
• "next Monday at 2pm" → next Monday 14:00

Dates:

• "January 15" → Jan 15 at 9am
• "Jan 15 at 3pm" → Jan 15 at 15:00
• "2026-01-15" → Jan 15 at 9am
• "2026-01-15 14:30" → Jan 15 at 14:30

Recurring Reminders

Intervals:

• "every 30 minutes"
• "every 2 hours"

Daily:

• "daily at 9am"
• "every day at 3pm"

Weekly:

• "weekly" → every Monday at 9am
• "every Monday at 2pm"
• "every Friday at 5pm"

Reminder Log

All reminders are logged to /home/julian/clawd/reminders.md:

- [scheduled] 2026-01-06 17:00 | Pay for Gumroad (id: abc123)
- [recurring] every 2h | Stand up and stretch (id: def456)
- [recurring] cron: 0 9 * * 1 | Weekly meeting (id: ghi789)

Status:

• [scheduled] — one-time reminder waiting to fire
• [recurring] — repeating reminder (active)
• [sent] — one-time reminder already delivered

Manual Commands

# List pending reminders
cron list

# View reminder log
cat /home/julian/clawd/reminders.md

# Remove a scheduled reminder
cron rm <job-id>

Agent Implementation

One-Time Reminders

When the user says "remind me to X at Y":

bash /home/julian/clawd/skills/remind-me/create-reminder.sh "X" "Y"

Examples:

bash /home/julian/clawd/skills/remind-me/create-reminder.sh "Pay for Gumroad" "later today"
bash /home/julian/clawd/skills/remind-me/create-reminder.sh "Call dentist" "tomorrow at 3pm"
bash /home/julian/clawd/skills/remind-me/create-reminder.sh "Check email" "in 2 hours"

Recurring Reminders

When the user says "remind me every X to Y":

bash /home/julian/clawd/skills/remind-me/create-recurring.sh "Y" "every X"

Examples:

bash /home/julian/clawd/skills/remind-me/create-recurring.sh "Stand up and stretch" "every 2 hours"
bash /home/julian/clawd/skills/remind-me/create-recurring.sh "Check email" "daily at 9am"
bash /home/julian/clawd/skills/remind-me/create-recurring.sh "Weekly team meeting" "every Monday at 2pm"

Both scripts automatically:

1. Parse the time/schedule
2. Create a cron job (one-time with --at or recurring with --every/--cron)
3. Log to /home/julian/clawd/reminders.md
4. Return confirmation with job ID