MetaBot Scheduler
xvirobotics/metabot
Schedules persistent cron and one-shot tasks on the MetaBot server that survive Claude session restarts and can be managed by other bots.
Registers, lists and removes recurring agent tasks with five-field cron expressions, and sets safety rules so a schedule is created only when the user clearly asks.
Install Scheduled Tasks Cron
$ npx skills add KonghaYao/peri --skill cron -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install KonghaYao/peri cron --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/KonghaYao/peri.git skills-src && mkdir -p .claude/skills && cp -r skills-src/peri-middlewares/src/skills/builtin/skills/cron .claude/skills/cron && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cron" agent skill from https://github.com/KonghaYao/peri/tree/main/peri-middlewares/src/skills/builtin/skills/cron into .claude/skills/cron/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cron", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/KonghaYao/peri/tree/main/peri-middlewares/src/skills/builtin/skills/cronType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add KonghaYao/peri --skill cron -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install KonghaYao/peri cron --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/KonghaYao/peri.git skills-src && mkdir -p .agents/skills && cp -r skills-src/peri-middlewares/src/skills/builtin/skills/cron .agents/skills/cron && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cron" agent skill from https://github.com/KonghaYao/peri/tree/main/peri-middlewares/src/skills/builtin/skills/cron into .agents/skills/cron/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cron", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add KonghaYao/peri --skill cron -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install KonghaYao/peri cron --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/KonghaYao/peri.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/peri-middlewares/src/skills/builtin/skills/cron .cursor/skills/cron && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cron" agent skill from https://github.com/KonghaYao/peri/tree/main/peri-middlewares/src/skills/builtin/skills/cron into .cursor/skills/cron/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cron", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/KonghaYao/peri.git --path peri-middlewares/src/skills/builtin/skills/cron--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add KonghaYao/peri --skill cron -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install KonghaYao/peri cron --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/KonghaYao/peri.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/peri-middlewares/src/skills/builtin/skills/cron .gemini/skills/cron && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cron" agent skill from https://github.com/KonghaYao/peri/tree/main/peri-middlewares/src/skills/builtin/skills/cron into .gemini/skills/cron/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cron", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install KonghaYao/peri cronInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add KonghaYao/peri --skill cron -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/KonghaYao/peri.git skills-src && mkdir -p .github/skills && cp -r skills-src/peri-middlewares/src/skills/builtin/skills/cron .github/skills/cron && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cron" agent skill from https://github.com/KonghaYao/peri/tree/main/peri-middlewares/src/skills/builtin/skills/cron into .github/skills/cron/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cron", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add KonghaYao/peri --skill cron -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install KonghaYao/peri cron --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/KonghaYao/peri.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/peri-middlewares/src/skills/builtin/skills/cron .opencode/skills/cron && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cron" agent skill from https://github.com/KonghaYao/peri/tree/main/peri-middlewares/src/skills/builtin/skills/cron into .opencode/skills/cron/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cron", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
cron- GitHub stars
- 223
- Token cost
- ~683 tokens
- SKILL.md length
- 335 words
- Files
- 1
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Registers, lists and removes recurring agent tasks with five-field cron expressions, and sets safety rules so a schedule is created only when the user clearly asks.
- Works in 3 steps: Confirm the user wants a recurring task,… → Translate the schedule into a 5-field… → Call cron_register, then cron_list to…
- Setting up a daily or weekly report that runs without being asked
- SKILL.md covers When to Use, Tools, Cron Expression Format and Safety, plus 1 more section
- Calls git
What it does
The agent uses three tools: cron_register takes a cron expression plus the prompt that is submitted each time the task fires, cron_list shows every task with its status, next fire time and prompt, and cron_remove deletes one by ID. Schedules are written as minute, hour, day of month, month and day of week, and the skill gives examples such as every five minutes, daily at nine, weekdays at nine and the first of each month. After registering, the agent calls cron_list to confirm the next fire time.
Because a registered task starts future agent turns without further confirmation, the skill treats it as delegating execution authority. The agent registers only when the user explicitly wants repetition, not merely because a time was mentioned, prefers prompts that read or report over ones that write, delete or push, states the schedule and exact prompt before registering when anything is unclear, and avoids very tight intervals that burn tokens. In approval mode the user is prompted every time.
When your agent uses it
- Setting up a daily or weekly report that runs without being asked
- Creating a recurring reminder or status check
- Listing scheduled tasks and removing one that is no longer needed
- Converting a plain-language schedule into a cron expression
Example prompts
- “Every weekday at 9am, summarize new issues in this repo.”
- “List my scheduled tasks and remove the one that runs every five minutes.”
- “Remind me every Monday morning to review open pull requests.”
Requirements
- An agent runtime that provides the cron_register, cron_list and cron_remove tools
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Confirm the user wants a recurring task, and pin down the schedule + what the prompt should do.
- Translate the schedule into a 5-field cron expression.
- Call cron_register, then cron_list to confirm the task and its next fire time.
What it can do on your machine
Read from SKILL.md and the folder at commit d7ee444. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Scheduled Tasks Cron loads about 683 tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 335 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from KonghaYao/peri at commit d7ee444, republished under its Apache-2.0 licence (© KonghaYao). 335 words, ~683 tokens.
Download SKILL.mdSave it as
.claude/skills/cron/SKILL.md (or your agent's skills folder).- name
- cron
- description
- Scheduled tasks (cron). Use when the user asks for recurring, periodic, or scheduled tasks — reminders, periodic reports, or anything that should run at a fixed interval ("every day at 9am", "每 5 分钟", "every Monday"). Also use when managing existing scheduled tasks via cron_list / cron_remove.
- userInvocable
- true
Scheduled Tasks (Cron)
You have access to scheduled task tools (cron_register, cron_list, cron_remove) for registering recurring automated tasks using standard 5-field cron expressions (minute hour day_of_month month day_of_week).
When to Use
- The user asks for a recurring/periodic task: reminders, periodic reports, status checks, polling.
- The user asks to manage existing scheduled tasks (list, remove).
- The user's phrasing implies "every X", "每天/每周/每月", "at 9am daily", etc.
Do NOT register a cron task just because the user mentions a time — only when they explicitly want it to repeat automatically.
Tools
| Tool | Purpose |
|---|---|
cron_register(expression, prompt) | Register a new scheduled task. prompt is the user message submitted when the task fires. |
cron_list() | List all registered tasks with status, next fire time, and prompt. |
cron_remove(id) | Remove a task by its ID (shown by cron_list). |
Cron Expression Format
Standard 5-field cron expression:
minute hour day_of_month month day_of_weekExamples:
*/5 * * * *— every 5 minutes0 9 * * *— every day at 09:000 9 * * 1-5— weekdays at 09:0030 8 1 * *— the 1st of each month at 08:30
Use cron_list to verify the registered task and its next fire time after registering.
Safety
cron_register schedules future agent turns that fire without further user confirmation — treat it like delegating execution authority. Before registering:
- Confirm the user explicitly asked for a recurring task. Do not register cron tasks speculatively or "to be helpful."
- Prefer prompts that read or report over prompts that write, delete, commit, or run destructive commands. A cron that fires
git push --forceovernight is a footgun. - State the schedule and the exact prompt you are about to register, then wait for confirmation if there is any ambiguity.
- Avoid tight intervals (e.g.
* * * * *) unless the user asked for them — they burn tokens fast and can flood the session.
In approval mode, cron_register always prompts the user before registering.
Workflow
- Confirm the user wants a recurring task, and pin down the schedule + what the prompt should do.
- Translate the schedule into a 5-field cron expression.
- Call
cron_register, thencron_listto confirm the task and its next fire time.
© KonghaYao, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in peri-middlewares/src/skills/builtin/skills/cron of KonghaYao/peri.
Open the folder on GitHubat commit d7ee444
Compare with similar skills
Scheduled Tasks Cron next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Scheduled Tasks Cron this skillKonghaYao/peri | 223 | — | ~683 | Automated safety check: Pass | Apache-2.0 | |
| MetaBot Schedulerxvirobotics/metabot | 991 | — | ~1k | Automated safety check: Pass | MIT | |
| Superset Automatesuperset-sh/superset | 15k | — | ~1.4k | Automated safety check: Pass | Custom licence | |
| Aeon Agent Setup and Managementaeonfun/aeon | 767 | — | ~9k | Automated safety check: Warn | MIT | |
| n8n Workflow Patternsczlonkowski/n8n-skills | 6.4k | — | ~5.1k | Automated safety check: Pass | MIT | |
| AI Automation WorkflowsNeverSight/learn-skills.dev | 216 | 1 repos | ~2.6k | Automated safety check: Pass | None |
Similar skills
Superset Automate
superset-sh/superset
Turns a recurring chore into a scheduled or event-triggered Superset agent, drafting its prompt, picking a target and trigger, and reviewing the first run.
Aeon Agent Setup and Management
aeonfun/aeon
Sets up and manages an Aeon agent instance that runs skills on a schedule through GitHub Actions: starting, rescheduling, debugging, editing skills and mining chat history.
n8n Workflow Patterns
czlonkowski/n8n-skills
Architecture patterns for n8n workflows covering webhooks, HTTP APIs, databases, AI agents, scheduled jobs and batch processing, with advice on choosing between them.
AI Automation Workflows
NeverSight/learn-skills.dev
Build automated AI workflows combining multiple models and services.
N8n Workflows
vibeeval/vibecosystem
n8n otomasyon workflow'lari. An agent skill from vibeeval/vibecosystem.
More from KonghaYao/peri
All 19 skills in this repoLangfuse and LLM Gateway Logs
KonghaYao/peri
Queries Langfuse traces, prompts, datasets and sessions, and analyzes local LLM gateway logs for requests, context growth, token use and cache hits.
Learn From History Audit
KonghaYao/peri
Audits recent agent conversation history and turns repeated failures and successes into testable harness improvement proposals that later audits can check.
SSH Remote Command CLI
KonghaYao/peri
Runs commands, reads and edits files, and copies data on remote machines through a single-file Node script that wraps the system ssh and scp, in Chinese.
Advisor Consultation
KonghaYao/peri
Sends a compact, redacted decision packet to a tool-free Opus advisor subagent when a task has high-risk trade-offs or stalled investigations, then weighs the answer.
Heavy Verify Loop for Peri TUI
KonghaYao/peri
Verifies and repairs a feature by using the real Peri terminal UI as a user would, looping verify, decide, fix and review until a fresh round shows no blockers.
Ultracode
KonghaYao/peri
Multi-agent workflow orchestration. An agent skill from KonghaYao/peri.
Related
Categories
Questions about Scheduled Tasks Cron
What does Scheduled Tasks Cron do?
Registers, lists and removes recurring agent tasks with five-field cron expressions, and sets safety rules so a schedule is created only when the user clearly asks. The agent uses three tools: cron_register takes a cron expression plus the prompt that is submitted each time the task fires, cron_list shows every task with its status, next fire time and prompt, and cron_remove deletes one by ID. Schedules are written as minute, hour, day of month, month and day of week, and the skill gives examples such as every five minutes, daily at nine, weekdays at nine and the first of each month.
When should I use Scheduled Tasks Cron?
Scheduled Tasks Cron fits situations like: setting up a daily or weekly report that runs without being asked; creating a recurring reminder or status check; listing scheduled tasks and removing one that is no longer needed; converting a plain-language schedule into a cron expression.
How do I install Scheduled Tasks Cron in Claude Code?
Run `npx skills add KonghaYao/peri --skill cron -a claude-code`. Or copy the skill folder (peri-middlewares/src/skills/builtin/skills/cron in KonghaYao/peri) into .claude/skills/cron in your project. Claude Code loads it when a task matches its description.
How do I install Scheduled Tasks Cron in Codex?
Run `npx skills add KonghaYao/peri --skill cron -a codex`. Or copy the skill folder (peri-middlewares/src/skills/builtin/skills/cron in KonghaYao/peri) into .agents/skills/cron in your project. Codex loads it when a task matches its description.
Can I use Scheduled Tasks Cron in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add KonghaYao/peri --skill cron -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cron, .gemini/skills/cron, .github/skills/cron and .opencode/skills/cron in your project.
What does Scheduled Tasks Cron need to run?
Going by SKILL.md and its folder, Scheduled Tasks Cron needs the command-line tools its instructions call (git). Our summary lists: An agent runtime that provides the cron_register, cron_list and cron_remove tools.
Does Scheduled Tasks Cron access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Scheduled Tasks Cron safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Scheduled Tasks Cron use?
Scheduled Tasks Cron is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Scheduled Tasks Cron use?
About 683 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Scheduled Tasks Cron?
Skills that share tags, products or a category with Scheduled Tasks Cron: MetaBot Scheduler (xvirobotics/metabot, 991 stars), Superset Automate (superset-sh/superset, 15k stars), Aeon Agent Setup and Management (aeonfun/aeon, 767 stars) and n8n Workflow Patterns (czlonkowski/n8n-skills, 6.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Scheduled Tasks Cron?
KonghaYao (a GitHub user) maintains it in KonghaYao/peri, which has 223 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 8, 2026.
Source: KonghaYao/peri on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.