Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Program recurring or one-time tasks. User defines what to do, skill handles when.
Program recurring or one-time tasks. User defines what to do, skill handles when.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
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.
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.
~/schedule/ โโโ jobs.json # Job definitions โโโ preferences.json # Timezone, preferred times โโโ history/ # Execution logs โโโ YYYY-MM.jsonl Create on first use: mkdir -p ~/schedule/history
This skill: โ Stores scheduled job definitions in ~/schedule/ โ Triggers jobs at specified times โ Learns timezone and time preferences from user Execution model: User explicitly defines WHAT the job does User grants any permissions needed for the job Skill only handles WHEN, not WHAT This skill does NOT: โ Assume access to any external service โ Modify system crontab or launchd โ Execute jobs without user-defined instructions
TopicFileCron expression syntaxpatterns.mdCommon mistakestraps.mdJob formatjobs.md
When user requests a scheduled task: WHAT: User specifies the action (may require other skills/permissions) WHEN: This skill handles timing HOW: User grants any needed access explicitly Example flow: User: "Every morning, summarize my emails" Agent: "I'll schedule this for 8am. This will need email access โ do you want me to use the mail skill for this?" User: "Yes" โ Job stored with explicit reference to mail skill
RequestAction"Remind me to X at Y"Store job, confirm"Every morning do X"Ask time, store job"Cancel X"Remove from jobs.json
โ [what user requested] ๐ [when] ([timezone]) ๐ง [permissions/skills needed, if any] ๐ [id]
In ~/schedule/jobs.json: { "daily_review": { "cron": "0 9 * * 1-5", "task": "User-defined task description", "requires": ["mail"], "created": "2024-03-15", "timezone": "Europe/Madrid" } } The requires field explicitly lists any skills/access the job needs.
When scheduled time arrives: Agent executes the user-defined task Uses only permissions user explicitly granted Logs result to history/
After first job, store in preferences.json: Timezone Preferred "morning" / "evening" times Default notification style
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.