home / skills / bdambrosio / cognitive_workbench / mc-wait
This skill provides a fixed one-second wait to pace actions and synchronize steps in Python workflows.
npx playbooks add skill bdambrosio/cognitive_workbench --skill mc-waitReview the files below or copy the command above to add this skill to your agents.
---
name: mc-wait
type: python
description: "Synchronous wait for 1 second using time.sleep. Useful for timing delays or pacing actions"
---
# Minecraft Wait Tool
Synchronous wait for 1 second using time.sleep. Useful for timing delays or pacing actions.
## Purpose
Timing control for pacing actions, waiting for asynchronous operations, and coordinating multi-step sequences.
## Input
- `value`: Ignored
## Output
Returns uniform_return format with:
- `value`: Text summary (wait completion message)
- `data`: Structured data dict (machine-readable). Key fields:
- `success`: Boolean
- `wait_duration_seconds`: Float (currently fixed at `1.0`)
## Behavior & Performance
- Synchronous wait - blocks execution for 1 second
- Fixed duration of 1.0 seconds
- Useful for pacing rapid actions
## Guidelines
- Use to pace rapid action sequences
- Use after asynchronous operations to allow time for completion
- Fixed 1-second duration - cannot be customized
- Blocks execution during wait
## Usage Examples
Wait one second:
```json
{"type":"mc-wait","out":"$wait"}
```
This skill provides a synchronous 1-second wait using Python's time.sleep. It is designed to add deterministic pacing or simple delays into scripts and action sequences. The behavior is fixed and blocks execution for exactly one second.
When invoked the skill calls time.sleep(1.0) and then returns a uniform_return structure. The returned data includes a human-readable message and a machine-readable dict with success and wait_duration_seconds fields. The input value is ignored and duration cannot be changed.
Can I change the wait duration?
No. The skill is fixed to a 1.0 second synchronous wait and does not accept a duration parameter.
Does the wait run asynchronously?
No. The implementation uses time.sleep and blocks the executing thread for the duration.