Chain repeated 10-minute background intervals to schedule deferred tasks and poll conditions.
npx skills add https://github.com/archibate/archibate-skills --skill long-waits
Please help me install this Agent Skill. Skill: long-waits Source: https://github.com/archibate/archibate-skills/tree/main/skills/long-waits Command: npx skills add https://github.com/archibate/archibate-skills --skill long-waits
Many automation tasks must wait for long delays or for external conditions to become true, but shells and simple timers hit limits and block progress or the agent. This Skill provides a safe, observable pattern to schedule deferred actions and poll conditions without hitting single-sleep timeouts or blocking the agent.
Ask the agent to check the target condition every 10 minutes and run the specified task when the condition becomes true.
High-intent search queries and answers about installing and using this skill.
To schedule long-duration waits without hitting shell timeout limits, you can chain repeated 10-minute background sleep intervals. This approach breaks extended delays into manageable chunks, verifying system time and polling conditions to remain event-driven while providing progress tracking.
Condition polling for deferred task execution works by periodically checking for specific triggers like file presence, CI completion, or log changes. The mechanism chains background sleep intervals to verify system state, triggering actions only when the target condition becomes true.
The best way to wait for a staging build to succeed is using chained interval waiting. It checks the build condition every 10 minutes, bypassing shell timeout limits, then automatically triggers integration tests and deployment when the condition is met while reporting progress.
Yes, you can execute calendar-triggered runs by computing time differences and verifying system wall-clock time. The mechanism converts target datetimes into interval counts, ensuring reliable execution of deferred actions at specific scheduled times.
Long-duration sleep blocks the agent because simple timers hit single-sleep timeout limits. Using chained background intervals bypasses these limits, keeping the agent unblocked while providing observable progress tracking throughout the wait period.
You should not use chained interval polling if your environment lacks Unix-based shell support or if your tasks require sub-10-minute immediate execution. This approach is specifically designed for extended delays and deferred task execution rather than real-time event processing.
filipexyzManage cron, interval, and one-shot job scheduling in the Ravi runtime.
zenobi-usReplace arbitrary timeouts with waitFor polling for state changes in tests.
c-dalyPoll a tool at fixed intervals until a condition is met.
clonable-edenManage recurring tasks via launchd and crontab with cron expressions.
