time-bomb

Schedule payloads to execute at a future time or condition.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Hmbown/mmbnchips --skill time-bomb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: time-bomb
Source: https://github.com/Hmbown/mmbnchips/tree/main/generated/codex/time-bomb
Command: npx skills add https://github.com/Hmbown/mmbnchips --skill time-bomb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Time Bomb addresses the need to perform actions at a later, controlled moment by deferring execution of a payload until a defined trigger or time.

Core Features & Use Cases

  • Deferred execution: schedule payloads to run at a chosen time or condition.
  • Explicit control: define an owner and a cancel path to disarm the payload if needed.
  • Checks and reminders: trigger follow-up actions after delays or checkpoints.

Quick Start

Plant a delayed action by specifying a trigger time or condition, assign an owner and a cancel path, then arm the payload to execute when the trigger fires.

Frequently Asked Questions about time-bomb

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

FAQPage Schema
How do I schedule a delayed action to trigger a payload later?

To schedule a delayed action, you define a trigger time or condition, assign an owner, specify a cancel path, and arm the payload to execute automatically when the trigger fires.

What is deferred execution used for in automation workflows?

Deferred execution is used for triggering follow-up actions, reminders, or payloads after a defined pause or checkpoint, ensuring checks happen at a controlled future moment rather than immediately.

Can I cancel a scheduled payload after it has been armed?

Yes, you can cancel a scheduled payload by utilizing the explicit cancel path defined during setup, which provides a safe disarm mechanism to stop execution before the trigger fires.

Do I need an explicit owner to set up a delayed trigger?

Yes, an explicit owner is required to set up a delayed trigger, ensuring accountability and providing a clear path for controlling the scheduled payload's arming and disarming mechanisms.

What's the best way to handle deferred checks in an automated workflow?

The best way to handle deferred checks is using a safe scheduling mechanism that allows you to define a trigger, assign an owner, and set a cancel path to safely arm or disarm payloads.

When should I not use delayed payload scheduling?

Avoid using delayed payload scheduling for actions requiring immediate execution or when you cannot define a clear cancel path and owner, as the mechanism relies on deferred triggers and safe disarm controls.