queue

Schedule deferred Claude Code commands via one-shot cron jobs.

89|7|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/nikhilsitaram/claude-caliper --skill queue-nikhilsitaram
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: queue
Source: https://github.com/nikhilsitaram/claude-caliper/tree/main/skills/queue
Command: npx skills add https://github.com/nikhilsitaram/claude-caliper --skill queue-nikhilsitaram

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, git, and includes scripts (resource) components.

What problem does it solve?

This Skill removes the friction of deferring Claude Code work until the right moment, especially when you want to wait for a fresh usage window or a specific future time.

Core Features & Use Cases

  • Reset-aware scheduling: Queue commands to run after the current 5-hour usage window resets, or target the weekly reset when needed.
  • Explicit future timing: Schedule work for a duration or local clock time such as later today, tomorrow morning, or a named hour.
  • Reliable session execution: Uses a one-shot cron job, validates the computed fire time, detects stale usage-state data, and supports the statusline capture workflow required for reset-based scheduling.

Quick Start

Ask the queue skill to schedule the following work to run in this same session after the current Claude usage window resets: review the changes, run the tests, and open the pull request.

Frequently Asked Questions about queue

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

FAQPage Schema
How do I schedule Claude Code commands to run after my usage window resets?

You can defer Claude Code commands to run after a usage window resets by scheduling a one-shot cron job within the same session. This requires statusline-captured usage state to detect the 5-hour or 7-day reset timing accurately.

Can I queue deferred Claude Code execution for a specific local clock time?

Yes, you can queue deferred Claude Code execution for a specific local clock time. The mechanism resolves local-time epochs and generates minute-granular cron jobs to fire commands at explicit future times like tomorrow morning.

Do I need statusline data to schedule work for the next fresh usage window?

Yes, statusline-captured usage state is required for reset-aware scheduling. The system relies on this data to calculate the next 5-hour or 7-day window and includes stale-data detection to ensure scheduling accuracy.

What's the best way to automate delayed execution of Claude Code tasks in the same session?

The best way to automate delayed execution is creating a one-shot cron job that fires within the same Claude Code session. It performs explicit validation before scheduling and applies minute-granular cron generation for precise timing control.

Why does deferred Claude Code scheduling require explicit validation before running?

Explicit validation before scheduling prevents errors from stale usage-state data. The system detects stale data and validates the computed fire time to ensure the one-shot cron job executes reliably at the correct moment.