Schedules commands to run later in the same Claude session — by default after the 5-hour usage window resets, or at a specified time/duration. Useful for deferring work onto fresh quota or specific deadlines.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-caliper-tooling:queueThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The user wants a set of commands to run later, **in this same session**, via a
The user wants a set of commands to run later, in this same session, via a
one-shot CronCreate job. The default trigger is the moment their current
5-hour usage window resets (so the work lands on fresh quota); they can instead
name an explicit time or duration.
/queue [<when>] <commands> — <when> is optional; everything else is the
QUEUED PAYLOAD.
Requires the statusline tap for reset-mode (the default): the wrapper
./skills/queue/scripts/statusline-wrapper.shmust be wired in as yourstatusLinecommand so it can capture the 5-hour reset time to the state file — see this skill'sREADME.md. Without it, reset-mode has no data, but explicit<when>targets still work. (macOS/BSDdateonly.)
Inspect the start of the invocation for an optional <when>. Times are local —
cron fires in the machine's local timezone, so no conversion is needed; let
date resolve it (if the user names a different zone, convert to local).
No time given → 5h-window-reset mode. Run the helper with no args:
./skills/queue/scripts/compute-fire.sh
(Invoke it directly — it's executable. Do NOT prefix with bash.)
For the weekly reset instead (e.g. "queue this for next week's reset"), add
--window 7d so it fires after the 7-day window resets.
A duration ("in 2h", "in 90m", "2h30m") or clock time ("3pm", "15:00", "3:30pm") or natural language ("10am tomorrow", "tomorrow at 9", "friday 5pm") → resolve it yourself to an absolute Unix epoch, then:
date '+%s | %Y-%m-%d %H:%M:%S %Z'.
Let date own the timezone — compute the epoch for the intended
wall-clock in the machine's local zone (don't hand-apply a Central offset).date -r <epoch> and check the
printed wall-clock matches what the user meant. Don't skip this../skills/queue/scripts/compute-fire.sh --epoch <epoch>Cron is minute-granular — sub-minute durations ("in 30s") can't be honored
exactly; the helper bumps them to the next whole minute. The helper floors to
the minute and honors explicit times; if the named time lands on :00/:30,
mention it may fire up to ~90s early (CronCreate one-shot jitter) and offer to
nudge a minute.
The helper prints CRON=, FIRE_HUMAN=, MINUTES_AWAY=, and either
RESET_HUMAN= (reset mode) or TARGET_HUMAN= (explicit). In reset mode it also
prints STALE=yes|no. On non-zero exit, relay the stderr message and do not
schedule — exit 1/2 = no reset time captured (keep terminal focused ~10-15s and
retry); 3 = target in the past; 4 = bad --epoch. If a WARNING: is printed
(stale state, or a DST-gap fire time), surface it: for STALE=yes, refresh the
statusline (focus terminal ~10s, re-run) before trusting the reset time.
With the helper's output, call CronCreate:
cron: the CRON value, verbatim.recurring: falsedurable: false — session-only, matches keep-this-session-open. Only true
if the user explicitly wants it to survive a restart.prompt: re-state the payload and instruct execution now. Template:
Your queued task is due. Execute the following queued work now, in order. If a step is a slash command, run it; otherwise treat it as an instruction.
If the user passed no commands, ask what to queue — don't schedule an empty job.
State: fire time (FIRE_HUMAN), the basis (RESET_HUMAN/TARGET_HUMAN),
minutes away, the returned job ID, and the two caveats:
In reset mode, the fire time is keyed to the last observed window reset; if the real reset drifts slightly, the +90s/round-up cushion absorbs it.
CronList — show what's scheduled this session.CronDelete <id> — cancel a queued job./queue adds another one-shot; they don't replace each other.npx claudepluginhub nikhilsitaram/claude-caliper --plugin claude-caliper-workflowSchedules one-shot delayed instructions to run once later in the session via natural language or /delay. Use for reminders, scheduled tasks, or delayed actions. Not for recurring intervals or persistent schedules.
Schedules a future Claude Code session to resume GSD project work at a specified time. Useful for overnight processing, token cap recovery, or queuing commands.