wait
Skill1 starsChanged 5 months agoMITView on GitHub
Pause execution for a requested number of minutes by sleeping one-minute increments to avoid exceeding shell timeouts.
3 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- wenxueru/wait-skilltheir own version, first seen Nov 8, 2026
- OHOKAYYEAH/claude-skillstheir own version, first seen Oct 13, 2026
- elie222/inbox-zeroedited, first seen Oct 8, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- elie222/inbox-zero★ 13k12% same
Wrote their own version · 2
- OHOKAYYEAH/claude-skills★ 1same name
- wenxueru/wait-skill★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository28 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/agent.mdcCursor rule
- .cursor/rules/coding_style.mdcCursor rule
- .cursor/rules/commit_msg.mdcCursor rule
- .cursor/rules/common.mdcCursor rule
- .cursor/rules/deprecated.mdcCursor rule
- .cursor/rules/github_actions.mdcCursor rule
- .cursor/rules/langfuse.mdcCursor rule
- .cursor/rules/llm.mdcCursor rule
- .cursor/rules/long_run_code.mdcCursor rule
- .cursor/rules/makefile-commands.mdCursor rule
- .cursor/rules/package-management.mdCursor rule
- .cursor/rules/tests.mdcCursor rule
- .cursor/rules/typing.mdcCursor rule
- .cursor/rules/uv.mdcCursor rule
- frontend-design-principlesSkill
- goose-gui-e2eSkill
- local-sandboxSkill
- manage-agent-configSkill
- new-agent-ruleSkill
- onboardingSkill
- push-releaseSkill
- cleanupSkill
- code-qualitySkill
- prek-precommit-hookSkill
- thermo-nuclear-code-quality-reviewSkill
- usageSkill
- gmail-mcpSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Use this skill whenever the user asks the assistant to pause or wait for a few minutes during a task.
- Distinctive: line 17
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 …
- Very specific: line 24
If the shell command fails (e.g., sleep unavailable), report the failure and stop waiting.
- Distinctive: line 25
If the user changes their mind mid-wait, cancel the remaining iterations and explain how much time was actually spent waiting.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Wait Skill
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.
Workflow
- 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
bashtool call withsleep 60. Before each call, report the upcoming iteration asexecuting sleep: i/N: bash sleep 60so 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.
Error handling
- If the shell command fails (e.g.,
sleepunavailable), report the failure and stop waiting. - If the user changes their mind mid-wait, cancel the remaining iterations and explain how much time was actually spent waiting.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.