reminders

Persist reminder text and due times to a SQLite database with cron-backed delivery.

2|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/eddmann/jeeves --skill reminders-eddmann
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reminders
Source: https://github.com/eddmann/jeeves/tree/main/skills/reminders
Command: npx skills add https://github.com/eddmann/jeeves --skill reminders-eddmann

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manage reminders — one-off and recurring — by persisting them with historical context and a simple interface, so you never miss important tasks.

Core Features & Use Cases

  • One-off and recurring reminders: Create reminders that fire at a specific time or on a repeating schedule.
  • Classification and history: Organize reminders by category and review past reminders in history.
  • Integrated scheduling: Uses a cron-backed system and SQLite to store metadata, delivery, and status.
  • Use Case: Example: set a morning reminder to take meds, and track when it fired and the next due time.

Quick Start

Tell Jeeves to remind you about something at a specific time, and Jeeves will create the reminder and schedule it.

Frequently Asked Questions about reminders

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I schedule recurring reminders that persist across sessions?

Schedule recurring reminders by persisting text and due times to a SQLite database for reliable delivery. The storage ensures reminders survive across sessions and fire accurately based on their configured repeating schedule.

Can I organize reminders by category and review past history?

Yes, reminders support classification by category and maintain a full history. The SQLite database stores metadata, delivery records, and status, allowing you to audit past reminders and re-use them as needed.

What's the best way to track one-off alerts and recurring nudges?

Track one-off alerts and recurring nudges by creating reminders that fire at specific times or on repeating schedules. The cron-backed delivery system ensures timely execution while logging the history of when each reminder fired.

How does cron-backed scheduling work for time-based notifications?

Cron-backed scheduling works by triggering stored reminders at their specified due times. The system queries the SQLite database for pending notifications and executes delivery, then updates the status and calculates the next due time for recurring reminders.

Do I need a database to manage reminders with historical context?

A SQLite database is required to persist reminder text, due times, and historical context. This storage mechanism guarantees reliable delivery and allows auditing of past reminders, their delivery status, and next scheduled times.

What are the limitations of using SQLite for reminder scheduling?

Using SQLite for reminder scheduling relies on a cron-backed system for delivery, meaning reminders depend on the cron daemon running consistently. While it handles one-off and recurring alerts, complex scheduling rules may require manual configuration within the database.