Menu
Pause execution for a requested number of minutes by sleeping one-minute increments to avoid exceeding shell timeouts.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Interview the user, inspect this template repo, run the interactive onboarding CLI, and prune unused systems so a new Python project gets running quickly.
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear or thermonuclear code quality review, deep code-quality audit, or especially harsh maintainability review.
Use whenever creating, editing, renaming, or deleting any file under .claude/skills/, .claude/agents/, .agents/skills/, or .codex/agents/. Teaches the dual-tool Claude/Codex layout and reminds to run `make sync-agent-config`.
Instructions for managing and running git hooks using `prek`. Use this skill for any mention of pre-commit hooks, as `prek` overrides pre-commit hooks.
Git branch hygiene - delete merged/closed branch, prune stale refs, sync dependencies
Instructions for running code quality checks and maintaining standards in the Python-Template project.
| name | wait |
| description | Pause execution for a requested number of minutes by sleeping one-minute increments to avoid exceeding shell timeouts. |
| user_invocable | true |
| triggers | ["/wait","wait"] |
Use this skill whenever the user asks the assistant to pause or wait for a few minutes during a task. Instead of issuing a single long sleep command (which often hits the 2-minute shell timeout), run one-minute sleeps repeatedly for the requested duration.
Determine the wait time. Parse the user’s request for a duration expressed in minutes. If the request is vague, ask a clarifying question (e.g., “How many minutes should I wait?”) before running commands.
Enforce sane limits. If the user requests a very large number of minutes, warn them and offer to break the wait into smaller chunks or confirm before proceeding.
Execute sequential Bash sleeps. For each of the requested N minutes, issue a separate bash tool call with sleep 60. Before each call, report the upcoming iteration as executing sleep: i/N: bash sleep 60 so observers know how many sleeps will run. Avoid bundling the sleeps into a single script; the goal is to keep every sleeping command under the 2-minute timeout.
Report completion. Once the loop finishes, notify the user that the wait is over and resume the primary task.
sleep unavailable), report the failure and stop waiting.