Individual skill
cron-scheduler
Schedules recurring or delayed agent tasks. Use for: schedule this, run daily, cron job, set timer.
.grok/skills/cron-scheduler/SKILL.md
Source commit bf31cc83a43ed8069d0d5070c68df4250273eb29
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 14
- Repository last updated
- Oct 21, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- grok Repository topic
- prompt-engineering Repository topic
- workflow-automation Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,944 bytesreferences/scheduling.mddoc · 1,023 bytes
Read excerpt
# Cron Scheduler
## When to Use
- User says **schedule this** or task matches this capability
- User says **run daily** or task matches this capability
- User says **cron job** or task matches this capability
- User says **set timer** or task matches this capability
- User says **every morning** or task matches this capability
## Workflow
1. Parse the schedule expression (cron, interval, or natural language).
2. Present the proposed trigger, task scope, notification channel, and next three run times.
3. Obtain explicit user approval before writing or enabling any recurring schedule; otherwise provide an inactive copy-paste configuration only.
4. After approval, save only the named configuration and do not enable background execution, outbound notifications, or external actions beyond the approved scope.