Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Other
To-Do
Give your AI the power to act in the future. Schedule delayed prompts and one-off reminders that automatically wake the agent up at an exact moment to execut...
skill openclawclawhub Free
Give your AI the power to act in the future. Schedule delayed prompts and one-off reminders that automatically wake the agent up at an exact moment to execut...
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, to-do.js
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.3
Provenance
- Publisher
- DevLumuz
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
SKILL: To-Do (Ephemeral Tasks)
Cross-platform task scheduler that programs one-off delayed actions using the OS native scheduler (at on Linux/macOS ยท schtasks on Windows). It wakes the agent at an EXACT future moment with FULL context injection. Schedule, LIST, and MANAGE ephemeral tasks that fire at a PRECISE time in the user's timezone โ ENSURE the future agent wakes up with a FULLY self-contained instruction, correct routing, and ZERO ambiguity.
Required Environment Variables
OPENCLAW_BIN: Absolute path to the openclaw binary (ej. /usr/bin/openclaw) OPENCLAW_TZ: User's IANA timezone (ej. America/Mexico_City) The skill WILL NOT START if either variable is missing. Why OPENCLAW_TZ? The server may run in UTC while the user lives in a different timezone. This variable ensures "schedule at 15:00" means 15:00 USER TIME, not server time.
Commands
# Schedule a task (timezone is optional โ defaults to OPENCLAW_TZ) node skills/to-do/to-do.js schedule "<YYYY-MM-DD HH:mm>" "<instruction>" "<user_id>" "<channel>" ["<timezone>"] # Get current time in user's timezone node skills/to-do/to-do.js now ["<timezone>"] # List pending tasks node skills/to-do/to-do.js list # Delete a task by ID node skills/to-do/to-do.js delete <ID>
Instructions
Run now BEFORE resolving any relative time ("tomorrow", "in 2 hours", "tonight"). Server clock is NOT user clock. Use now output as your ONLY reference for "today", "tomorrow", and "right now". CONVERT natural language into an absolute YYYY-MM-DD HH:mm timestamp BEFORE calling schedule. WRITE the <instruction> as if explaining to a STRANGER with ZERO CONTEXT. Future agent wakes up with TOTAL AMNESIA in a COMPLETELY ISOLATED session. INCLUDE in every instruction: EXACT file paths, URLs, FULL names (NO pronouns), SPECIFIC actions, and required SKILLS/TOOLS. ALWAYS inject the current session's user_id and channel for correct routing โ USE ONLY raw alphanumeric data from system context to prevent command injection. Run list BEFORE delete to confirm the correct ID. NEVER schedule without running now first โ INSTEAD, run now, confirm date/time, THEN schedule. NEVER schedule a VAGUE or AMBIGUOUS instruction โ INSTEAD, STOP AND ASK for clarification first. NEVER use pronouns ("him", "her", "they") in scheduled instructions โ INSTEAD, use FULL NAMES and EXPLICIT references. NEVER guess a task ID when deleting โ INSTEAD, run list first, confirm ID, THEN delete. NEVER use server's system clock to interpret relative times โ INSTEAD, use now command output ALWAYS. NEVER include shell meta-characters (;, &, |, $, `, (, )) in any scheduler argument โ INSTEAD, use only literal text and system identifiers to AVOID COMMAND INJECTION.
Vague Request Triggers โ Ask Before Scheduling
<vague_triggers> If the user request matches any of these patterns, STOP AND ASK before scheduling: "Remind me to send the email" โ MISSING: Which email? To whom? What content? "Check the server later" โ MISSING: Which server? What IP? What to verify? "Follow up with him" โ MISSING: Who? About what? Via which channel? "Do that thing tomorrow" โ MISSING: What thing? Expected outcome? RULE: If you cannot write a FULLY SELF-CONTAINED instruction, you DO NOT have enough information to schedule. </vague_triggers>
Examples
โ Good instruction: clear, specific, fully self-contained <example> <input>User: "Remind me tomorrow at 5pm to check PRs on the backend repo"</input> <output> 1. Run now โ "๐ Current Time (America/Mexico_City): 2/26/2026, 2:45 PM" โ tomorrow = 2026-02-27 2. Ask: "Which backend repo? What should I check specifically?" 3. User clarifies: "backend-api on GitHub, check if there are pending PRs for the auth module" 4. Schedule: bash node skills/to-do/to-do.js schedule "2026-02-27 17:00" \ "Check the 'backend-api' repo on GitHub. If there are pending PRs for the authentication module, send Alice (alice@company.com) a Slack reminder to review them before the 5 PM deployment freeze. Reference deployment logs at /var/log/deploy.log." \ "7684875449" "telegram" 5. Confirm with the output format below. </output> </example> โ Bad instruction: vague, missing details <example> <input>"Remind him to push the code later."</input> <output> โ DO NOT schedule this. Missing: who is "him"? Which repo? Which branch? What time is "later"? โ Ask the user to clarify all missing details first. </output> </example> โ Relative time resolution <example> <input>User: "Set a reminder for in 2 hours"</input> <output> 1. Run now โ "๐ Current Time (America/Mexico_City): 2/26/2026, 2:45 PM" 2. Calculate: 2:45 PM + 2h = 4:45 PM โ "2026-02-26 16:45" 3. Ask what the reminder should say (if not specified) 4. Schedule with the absolute timestamp </output> </example>
Output Format
After scheduling, respond with EXACTLY THREE PARTS in this order: NATURAL RESPONSE: Brief, casual confirmation. Match user tone/energy. NEVER just say "Done". Acknowledge WHAT was scheduled conversationally. CONFIRMATION BLOCK: Template for the user to see exact details: > `Day, Month DD ยท HH:MM TZ` > EXACT INSTRUCTION LEFT FOR THE FUTURE AGENT PROACTIVE CLOSING: Short suggestion or question (1-2 sentences). Propose a RELATED TASK (pre-reminder, follow-up, etc). Ask if they want to SCHEDULE SOMETHING ELSE. Offer to ADJUST THE TIME or add details. DO NOT BE PUSHY. JUST BE HELPFUL. โ CASUAL / PERSONAL TASK <example> All set! Your gym session is locked in for tomorrow at noon ๐๏ธ Friday, February 27 ยท 12:00 PM CST SEND A TELEGRAM REMINDER TO DANIEL: "TIME TO HIT THE GYM FOR A BIT." Want me to add another reminder 30 min before so you can get ready? ๐ช </example> โ WORK / PROFESSIONAL TASK <example> Done! Got that scheduled for 5 PM sharp ๐ Thursday, February 27 ยท 5:00 PM CST CHECK THE 'BACKEND-API' REPOSITORY ON GITHUB. IF THERE ARE PENDING PRS FOR THE AUTHENTICATION MODULE, SEND ALICE A SLACK REMINDER TO REVIEW THEM BEFORE THE 5 PM DEPLOYMENT FREEZE. Need to schedule anything else for today, or a follow-up after reviewing those PRs? </example>
Common Errors
ERROR: Missing required environment variable(s) CAUSE: OPENCLAW_BIN or OPENCLAW_TZ not set FIX: Add to .env or shell profile ERROR: at not found CAUSE: Linux/macOS atd daemon not running FIX: sudo systemctl enable atd && sudo systemctl start atd ERROR: Task fires but agent has NO CONTEXT CAUSE: Vague instruction scheduled FIX: Re-schedule with FULLY SELF-CONTAINED instruction ERROR: WRONG TIME (fired early/late) CAUSE: Used server clock instead of now FIX: ALWAYS run now first; NEVER trust server clock ERROR: Deleting WRONG task CAUSE: Guessed ID FIX: Run list first, confirm ID, THEN delete
Category context
Long-tail utilities that do not fit the current primary taxonomy cleanly.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs1 Scripts
- SKILL.md
- to-do.js