schedule-followup

Parse requests to schedule aperiodic pulses or hour-aligned diary entries.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/reubenjohn/reeve-desk --skill schedule-followup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: schedule-followup
Source: https://github.com/reubenjohn/reeve-desk/tree/main/.claude/skills/schedule-followup-pulse
Command: npx skills add https://github.com/reubenjohn/reeve-desk --skill schedule-followup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Schedule follow-ups to ensure important tasks, responses, or events are reviewed on time, reducing missed actions.

Core Features & Use Cases

  • Distinguish aperiodic pulses from diary entries to avoid duplicate wake-ups.
  • Parse user requests to extract what, when, why, and priority for follow-ups.
  • Create and log follow-ups as pulses or diary entries with contextual notes.

Quick Start

Tell Reeve to schedule a follow-up reminder for a task or response at a specific time.

Frequently Asked Questions about schedule-followup

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

FAQPage Schema
How do I schedule a follow-up reminder for a specific task or response?

To schedule a follow-up reminder, provide the task details, timing, and priority. The system parses your request to extract what, when, and why, then logs it as a pulse or diary entry to trigger a wake-up at the specified time.

What is the difference between aperiodic pulses and diary entries for reminders?

Aperiodic pulses trigger wake-ups at irregular times for status checks, while diary entries are hour-aligned logs. Distinguishing between them prevents duplicate wake-ups and ensures follow-ups are scheduled in the correct format.

Can I set priority levels when scheduling follow-up reminders?

Yes, you can set priority levels. The system parses user requests to extract priority alongside what, when, and why, enforcing prioritization to ensure critical tasks, responses, or events are reviewed on time.

How do follow-up reminders handle context and confirmation logging?

Follow-up reminders log contextual notes and confirmations automatically. When a pulse or diary entry is created, the system records the associated context to maintain a clear history of scheduled tasks, responses, or events.

What is the best way to avoid duplicate wake-ups when scheduling status checks?

The best way to avoid duplicate wake-ups is to distinguish aperiodic pulses from hour-aligned diary entries. The system parses requests and categorizes them correctly to prevent overlapping reminder triggers.

Do I need to specify a reason when creating a follow-up pulse?

Yes, specifying a reason is part of the request parsing process. The system extracts what, when, why, and priority to create follow-ups with contextual notes, ensuring the reminder has clear purpose and context.