agentleFS
Sign inStart free
DeiblerDeibler/edmund-harness/skills/reminders/SKILL.md

reminders

Skill24 starsChanged 2 months agoMITView on GitHub

Schedule future events that wake you up in the same iMessage conversation.

17 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use calendar.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • jacobraskSkill

    calendar

    Interact with Apple Calendar via AppleScript. Use when the user asks to check calendar, view events, create events, manage schedule, find free time, or list calendars. Triggers include "my calendar", "my schedule", "calendar events", "create event", "add to calendar", "what's on my calendar", "free time", "available slots", "upcoming events", "today's events". Requires macOS with Calendar.app.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the schedule_reminder MCP tool (from the edmund-harness server) to queue a future event.

    line 8

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

reminders

Use the schedule_reminder MCP tool (from the edmund-harness server) to queue a future event. When the time arrives, this same session resumes and the event text is delivered as if the user just sent it — so write event as what you want to see.

When to use

  • User asks for a reminder: "remind me to call mom at 4pm"
  • User asks for recurring check-ins: "every morning at 9, ask me my top priority"
  • You need to follow up later: "I'll check back in an hour"

Examples

schedule_reminder(when="in 10 minutes", event="Remind the user to drink water")
schedule_reminder(when="at 2026-04-20T16:00:00-05:00", event="Time to call mom — draft a quick reminder message")
schedule_reminder(when="0 9 * * *", event="Morning check-in — ask what the top priority is today")

Managing

  • list_reminders() to see what's queued for this conversation.
  • cancel_reminder(id) to remove one.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free