remind-me

sundial-org/awesome-openclaw-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/sundial-org/awesome-openclaw-skills --skill remind-me
0 commentsdiscussion
summary

Natural language reminders that schedule cron jobs and log to markdown.

  • Parses relative times (\"in 2 hours\", \"later today\"), absolute times (\"tomorrow at 3pm\"), and dates (\"January 15\", \"2026-01-15 14:30\")
  • Supports both one-time reminders (via --at ) and recurring schedules (hourly, daily, weekly, or custom intervals)
  • Automatically logs all reminders to a markdown file with status tracking (scheduled, recurring, sent) and job IDs for manual removal
  • Requires bash and the
skill.md

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
how to use remind-me

How to use remind-me on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add remind-me
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/sundial-org/awesome-openclaw-skills --skill remind-me

The skills CLI fetches remind-me from GitHub repository sundial-org/awesome-openclaw-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/remind-me

Reload or restart Cursor to activate remind-me. Access the skill through slash commands (e.g., /remind-me) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.847 reviews
  • Ren Dixit· Dec 16, 2024

    remind-me has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Fatima Bhatia· Dec 8, 2024

    remind-me reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Pratham Ware· Dec 4, 2024

    remind-me fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Ren Desai· Dec 4, 2024

    We added remind-me from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Aanya Bansal· Nov 27, 2024

    I recommend remind-me for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Fatima Choi· Nov 11, 2024

    remind-me fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Amina Desai· Nov 7, 2024

    Keeps context tight: remind-me is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Ren Lopez· Oct 26, 2024

    remind-me is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Fatima Martinez· Oct 18, 2024

    Useful defaults in remind-me — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Fatima Bansal· Oct 2, 2024

    We added remind-me from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

showing 1-10 of 47

1 / 5