Programming · Automation
schedules
/schedules
MUST use when configuring schedules.
For whom
- Author
- windmill-labs ↗
- Repository
- windmill ↗
- Licence
- Apache-2.0
- Last repository change
- 25.10.2026
Assessment and security
92/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability17 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
Deprecation
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
Licence
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
MUST use when configuring schedules.
Original author description
MUST use when configuring schedules.
How it works
- File Naming
- Cron Expression Format
- CLI Commands
Original SKILL.md headings · 50 lines, 290 words
SKILL.md preview
---
name: schedules
description: MUST use when configuring schedules.
---
# Windmill Schedules
Schedules run scripts and flows automatically on a cron schedule.
## File Naming
Schedule files use the pattern: `{path}.schedule.yaml`
Example: `f/folder/daily_sync.schedule.yaml`
Note: The path is derived from the filename, not stored in the file content.
## Cron Expression Format
Windmill uses 6-field cron expressions (includes seconds):
```
┌───────────── second (0-59)
│ ┌───────────── minute (0-59)
│ │ ┌───────────── hour (0-23)
│ │ │ ┌───────────── day of month (1-31)
│ │ │ │ ┌───────────── month (1-12 or jan-dec)
│ │ │ │ │ ┌───────────── day of week (0-6, 0=Sunday, or sun-sat)
│ │ │ │ │ │
* * * * * *
```
**Common Examples:**
- `0 0 0 * * *` - Daily at midnight
- `0 0 12 * * *` - Daily at noon
- `0 */5 * * * *` - Every 5 minutes
- `0 0 9 * * 1-5` - Weekdays at 9 AM
- `0 0 0 1 * *` - First day of each month
## CLI Commands
Deploying local changes to the workspace can be destructive to remote state — only suggest/run a deploy when the user explicitly asks to deploy/publish/push, not when they say "run", "try", or "test". Deploy via `git push` or `wmill sync push` depending on how the repo is wired (see the **Deploying** section in `AGENTS.wmill.md`). The commands below never mutate remote state, so they're safe to run yourself — note that `sync pull` does overwrite local files to match the remote (use `sync pull --dry-run` to only preview), while `schedule` just lists.
```bash
# Push schedules to Windmill — only when the user explicitly asks to deploy
wmill sync push
# Pull schedules from Windmill
wmill sync pull
# List schedules
wmill schedule
```
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · windmill-labs/windmill | 92 | Apache-2.0 |
| durabullhq/durabull | 86 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 3b64de87a40d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 1 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 92triggers
MUST use when configuring triggers. - 92resources
MUST use when managing resources. - 90testing-automation-schedules
Use when testing automation schedules is required during automation product work, especially when the result must be traceable, independently reviewable, and safe to hand to another agent. - 90depreciation-schedules
Prepare depreciation schedules under the firm's chosen accounting and tax policies. TRIGGERS - Use when user needs help with depreciation schedules related tasks. - 100vercel-schedules
Vercel Schedules guidance — run a private function, route, or Vercel Queues topic on a cron cadence or once at a set time. Covers static schedules in vercel.json, dynamic per-user schedules with @vercel/schedules, handleSchedule, the vercel schedules CLI, environments, jitter,…