Schedule

**Quick judgement:** A solid, well-scoped scheduling skill that behaves like a user-space cron for OpenClaw agents. It is best used as an orchestration layer for time-based workflows rather than a full automation system. **Strengths & suitable scenarios:** - Works well whenever you need recurring or one-off tasks driven by time (e.g., “every weekday at 9am, summarize my email”), while keeping the actual work delegated to other skills. - Good fit for users or agents that want persistent schedules with explicit permissions and an audit trail, without touching system-level cron or external services. - Particularly useful in multi-skill workflows where clear separation between *when* and *what* improves clarity and safety. **Key risks / limitations:** - Relies on the broader agent/runtime being active and correctly invoking the scheduler; missed or duplicated runs are possible if the environment is unstable. - Users unfamiliar with cron-like timing may still run into configuration mistakes, especially for more complex schedules. - Because it can repeatedly trigger other, more powerful skills, misconfigured jobs (e.g., too frequent, overly broad actions) can amplify downstream risks, even though this skill itself is conservative. **Recommended use:** Employ this skill as the central timing mechanism for personal or team automations—reminders, daily summaries, regular maintenance—while keeping a careful eye on job definitions, timezones, and the permissions granted in the requires field. This balances utility with safety and makes schedules easier to inspect, adjust, and audit over time.