Agent skill

Cron Management

by grandamenium in grandamenium/cortextos

Manage scheduled tasks (crons). An agent skill from grandamenium/cortextos.

MITAuto-check passedProductivity & Automation

Install Cron Management

skills CLI

$ npx skills add grandamenium/cortextos --skill cron-management -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install grandamenium/cortextos cron-management --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/grandamenium/cortextos.git skills-src && mkdir -p .claude/skills && cp -r skills-src/community/agents/research-agent/.claude/skills/cron-management .claude/skills/cron-management && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "cron-management" agent skill from https://github.com/grandamenium/cortextos/tree/main/community/agents/research-agent/.claude/skills/cron-management into .claude/skills/cron-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cron-management", 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

$skill-installer install https://github.com/grandamenium/cortextos/tree/main/community/agents/research-agent/.claude/skills/cron-management

Type 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.

skills CLI

$ npx skills add grandamenium/cortextos --skill cron-management -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install grandamenium/cortextos cron-management --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/grandamenium/cortextos.git skills-src && mkdir -p .agents/skills && cp -r skills-src/community/agents/research-agent/.claude/skills/cron-management .agents/skills/cron-management && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "cron-management" agent skill from https://github.com/grandamenium/cortextos/tree/main/community/agents/research-agent/.claude/skills/cron-management into .agents/skills/cron-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cron-management", 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.

skills CLI

$ npx skills add grandamenium/cortextos --skill cron-management -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install grandamenium/cortextos cron-management --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/grandamenium/cortextos.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/community/agents/research-agent/.claude/skills/cron-management .cursor/skills/cron-management && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "cron-management" agent skill from https://github.com/grandamenium/cortextos/tree/main/community/agents/research-agent/.claude/skills/cron-management into .cursor/skills/cron-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cron-management", 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

$ gemini skills install https://github.com/grandamenium/cortextos.git --path community/agents/research-agent/.claude/skills/cron-management

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add grandamenium/cortextos --skill cron-management -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install grandamenium/cortextos cron-management --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/grandamenium/cortextos.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/community/agents/research-agent/.claude/skills/cron-management .gemini/skills/cron-management && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "cron-management" agent skill from https://github.com/grandamenium/cortextos/tree/main/community/agents/research-agent/.claude/skills/cron-management into .gemini/skills/cron-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cron-management", 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.

GitHub CLI

$ gh skill install grandamenium/cortextos cron-management

Installs 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).

skills CLI

$ npx skills add grandamenium/cortextos --skill cron-management -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/grandamenium/cortextos.git skills-src && mkdir -p .github/skills && cp -r skills-src/community/agents/research-agent/.claude/skills/cron-management .github/skills/cron-management && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "cron-management" agent skill from https://github.com/grandamenium/cortextos/tree/main/community/agents/research-agent/.claude/skills/cron-management into .github/skills/cron-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cron-management", 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.

skills CLI

$ npx skills add grandamenium/cortextos --skill cron-management -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install grandamenium/cortextos cron-management --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/grandamenium/cortextos.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/community/agents/research-agent/.claude/skills/cron-management .opencode/skills/cron-management && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "cron-management" agent skill from https://github.com/grandamenium/cortextos/tree/main/community/agents/research-agent/.claude/skills/cron-management into .opencode/skills/cron-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cron-management", 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-management
GitHub stars: 101
Token cost: ~1.1k tokens
SKILL.md length: 329 words
Files: 1
Skills in repo: 55
Repo updated: Sep 23, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Manage scheduled tasks (crons). An agent skill from grandamenium/cortextos.

Works in 3 steps: cortextos bus list-crons $CTX_AGENT_NAME… → cortextos bus get-cron-log… → Check daemon log:…
: verifying crons on session start
SKILL.md covers On Session Start, Handling a Cron Fire, Adding a Recurring Cron and Updating a Cron, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Cron Management is an agent skill from grandamenium/cortextos. Manage scheduled tasks (crons). Crons are daemon-managed and stored in crons.json — they survive restarts automatically. Use when: verifying crons on session start, creating new recurring tasks, updating or removing crons, troubleshooting scheduled tasks, or using the dashboard test-fire button.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Productivity & Automation, covering Scheduled and recurring tasks. The licence is MIT.

When your agent uses it

: verifying crons on session start
Creating new recurring tasks
Troubleshooting scheduled tasks
Using the dashboard test-fire button

Example prompts

“/cron-management”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

cortextos bus list-crons $CTX_AGENT_NAME — confirm it is registered and not disabled.
cortextos bus get-cron-log $CTX_AGENT_NAME — check for status: failed entries.
Check daemon log: ~/.cortextos/$CTX_INSTANCE_ID/logs/$CTX_AGENT_NAME/

What it can do on your machine

Read from SKILL.md and the folder at commit 6f93838. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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

Cron Management loads about 1.1k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 329 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~78
When it runs · the whole SKILL.md, loaded when a task matches: ~1.1k

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 grandamenium/cortextos at commit 6f93838, republished under its MIT licence (© grandamenium). 329 words, ~1,134 tokens.

Download SKILL.mdSave it as .claude/skills/cron-management/SKILL.md (or your agent's skills folder).

name: cron-management
description: Manage scheduled tasks (crons). Crons are daemon-managed and stored in crons.json — they survive restarts automatically. Use when: verifying crons on session start, creating new recurring tasks, updating or removing crons, troubleshooting scheduled tasks, or using the dashboard test-fire button.
triggers: remind me, every day, every hour, every week, schedule, recurring, daily, weekly, cron, loop, check regularly, monitor, keep an eye on, set up a reminder…

Cron Management

Crons are daemon-managed. They are stored in ${CTX_ROOT}/state/$CTX_AGENT_NAME/crons.json and dispatched by the cortextOS daemon. Crons survive agent restarts, context compactions, and daemon restarts automatically. You do NOT need to recreate them on session start.

Never use /loop or CronCreate for persistent recurring work — those are session-local and die on agent restart.

On Session Start

Check that your crons are registered. Do not recreate them unless they are missing.

bash

cortextos bus list-crons $CTX_AGENT_NAME

If a cron is missing from the list, add it:

bash

cortextos bus add-cron $CTX_AGENT_NAME <name> <interval|cron-expr> "<prompt>"

Handling a Cron Fire

When a cron prompt is injected into your session, complete the requested work and then record the fire. Use the cron's schedule as the --interval value, whether it is shorthand (4h) or a 5-field cron expression ("0 9 * * *").

bash

cortextos bus update-cron-fire <cron-name> --interval <interval-or-cron-expr>

This is the daemon's audit trail. Without it, the dashboard may think the cron is stuck even if the work completed.

Adding a Recurring Cron

Interval shorthand (s/m/h/d/w):

bash

cortextos bus add-cron $CTX_AGENT_NAME heartbeat 6h "Read HEARTBEAT.md and follow its instructions."
cortextos bus add-cron $CTX_AGENT_NAME health-check 30m "Check system health and report anomalies."

5-field cron expression (minute hour dom month dow):

bash

cortextos bus add-cron $CTX_AGENT_NAME morning-report "0 9 * * 1-5" "Generate and send the daily analytics report."
cortextos bus add-cron $CTX_AGENT_NAME weekly-summary "0 17 * * 5" "Compile and deliver the weekly summary."

The daemon reloads automatically after add-cron. Confirm with list-crons.

Updating a Cron

bash

# Change the schedule
cortextos bus update-cron $CTX_AGENT_NAME heartbeat --interval 4h

# Update the prompt
cortextos bus update-cron $CTX_AGENT_NAME heartbeat --prompt "New prompt text."

# Disable (stops firing without removing it)
cortextos bus update-cron $CTX_AGENT_NAME heartbeat --enabled false

# Re-enable
cortextos bus update-cron $CTX_AGENT_NAME heartbeat --enabled true

Removing a Cron

bash

cortextos bus remove-cron $CTX_AGENT_NAME <name>

Testing a Cron Immediately

From the dashboard (/workflows/$CTX_AGENT_NAME/<name>), click Test Fire to inject the cron's prompt immediately. A 30-second cooldown prevents accidental rapid-fires.

Set manualFireDisabled: true on a cron definition to block dashboard test-fires (e.g. for crons that must only fire on schedule).

Checking Execution History

bash

# All crons for this agent
cortextos bus get-cron-log $CTX_AGENT_NAME

# Filter to a specific cron
cortextos bus get-cron-log $CTX_AGENT_NAME <name>

Each log entry: ts, cron, status (fired/retried/failed), attempt, duration_ms, error.

Troubleshooting

Cron not firing:

cortextos bus list-crons $CTX_AGENT_NAME — confirm it is registered and not disabled.
cortextos bus get-cron-log $CTX_AGENT_NAME <name> — check for status: failed entries.
Check daemon log: ~/.cortextos/$CTX_INSTANCE_ID/logs/$CTX_AGENT_NAME/

crons.json corrupted:

readCrons automatically falls back to crons.json.bak on parse failure. Usually self-healing.
If both files are bad, re-add crons via add-cron or force re-migration: cortextos bus migrate-crons $CTX_AGENT_NAME --force

Scheduler retained stale schedule after reload:

If a reload produces an empty schedule (transient corruption), the daemon keeps the last-good schedule in memory (lastGoodSchedule). Crons keep firing. Repair crons.json and the scheduler recovers automatically on the next reload.

Files

Just SKILL.md in community/agents/research-agent/.claude/skills/cron-management of grandamenium/cortextos.

Open the folder on GitHubat commit 6f93838

Compare with similar skills

Cron Management 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.

Cron Management compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Cron Management this skillgrandamenium/cortextos	101	—	~1.1k	Automated safety check: Pass	MIT	18 days ago
ScheduleTinyAGI/tinyagi	3.6k	—	~1.4k	Automated safety check: Pass	MIT	6 mo ago
Send User MessageTinyAGI/tinyagi	3.6k	—	~829	Automated safety check: Pass	MIT	6 mo ago
Cron Opsczl9707/build-your-own-openclaw	1.9k	—	~593	Automated safety check: Pass	MIT	3 mo ago
X Bookmarkssharbelxyz/x-bookmarks	289	—	~2k	Automated safety check: Notes	None	7 mo ago
Wp Wpcli And OpsAutomattic/agent-skills	211	2 repos	~988	Automated safety check: Pass	None	8 mo ago

Similar skills

Schedule
TinyAGI/tinyagi
Create, list, and delete scheduled tasks (recurring or one-time) that send messages to agents.
3.6k GitHub stars~1.4k tokensUpdated 6 mo ago
Productivity & AutomationAuto-check passed
Send User Message
TinyAGI/tinyagi
Send a proactive message to a paired user via their channel (Discord, Telegram, or WhatsApp).
3.6k GitHub stars~829 tokensUpdated 6 mo ago
Productivity & AutomationAuto-check passed
Cron Ops
czl9707/build-your-own-openclaw
Create, list, and delete scheduled cron jobs. An agent skill from czl9707/build-your-own-openclaw.
1.9k GitHub stars~593 tokensUpdated 3 mo ago
Productivity & AutomationAuto-check passed
X Bookmarks
sharbelxyz/x-bookmarks
Fetch, summarize, and manage X/Twitter bookmarks via bird CLI or X API v2.
289 GitHub stars~2k tokensUpdated 7 mo ago
Productivity & AutomationAuto-check: notes
Wp Wpcli And Ops
Automattic/agent-skills
A skill your agent uses when working with WP-CLI (wp) for WordPress operations: safe search-replace, db export/import, plugin/theme/user/content management, cron, cache flushing, multisite, and…
211 GitHub starsUsed in 2 repos~988 tokens
Productivity & AutomationAuto-check passed
Ohdear
ohdearapp/ohdear-cli
Manage Oh Dear website monitoring using the ohdear CLI. An agent skill from ohdearapp/ohdear-cli.
141 GitHub stars~1.1k tokensUpdated 1 mo ago
Productivity & AutomationAuto-check passed

More from grandamenium/cortextos

All 55 skills in this repo

Cortext Self Diagnosis
grandamenium/cortextos
Diagnose cortextOS itself when the framework misbehaves — an agent has gone silent or wedged, agents are crash-looping, Telegram or agent-to-agent messages are not arriving, crons did not fire, an…
101 GitHub stars~3.7k tokensUpdated 18 days ago
Auto-check passed
Activity Channel
grandamenium/cortextos
You have completed something significant and want the whole org — all agents and the user — to know about it.
101 GitHub stars~624 tokensUpdated 18 days ago
Auto-check passed
Agentcard Purchase
grandamenium/cortextos
You need to make a purchase on behalf of the user — buy a SaaS subscription, pay for an API, purchase a domain, or any transaction requiring a credit card.
101 GitHub stars~1.1k tokensUpdated 18 days ago
Auto-check passed
Claude To Codex Migration
grandamenium/cortextos
Migrate ANY cortextOS agent from the claude-code runtime to the live codex-app-server runtime.
101 GitHub stars~12k tokensUpdated 18 days ago
Auto-check: warnings
Bus Reference
grandamenium/cortextos
Complete cortextos bus CLI reference - all available commands with examples.
101 GitHub stars~3.8k tokensUpdated 18 days ago
Auto-check passed
Business News Monitor
grandamenium/cortextos
Daily cron-driven scan of news/forums/social in a domain to surface market shifts, new competitors, regulatory changes, and net-new opportunities.
101 GitHub stars~1.3k tokensUpdated 18 days ago
Auto-check passed

Questions about Cron Management

What does Cron Management do?

Manage scheduled tasks (crons). An agent skill from grandamenium/cortextos. Cron Management is an agent skill from grandamenium/cortextos. Manage scheduled tasks (crons).

When should I use Cron Management?

Cron Management fits situations like: : verifying crons on session start; creating new recurring tasks; troubleshooting scheduled tasks; using the dashboard test-fire button.

How do I install Cron Management in Claude Code?

Run `npx skills add grandamenium/cortextos --skill cron-management -a claude-code`. Or copy the skill folder (community/agents/research-agent/.claude/skills/cron-management in grandamenium/cortextos) into .claude/skills/cron-management in your project. Claude Code loads it when a task matches its description.

How do I install Cron Management in Codex?

Run `npx skills add grandamenium/cortextos --skill cron-management -a codex`. Or copy the skill folder (community/agents/research-agent/.claude/skills/cron-management in grandamenium/cortextos) into .agents/skills/cron-management in your project. Codex loads it when a task matches its description.

Can I use Cron Management 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 grandamenium/cortextos --skill cron-management -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-management, .gemini/skills/cron-management, .github/skills/cron-management and .opencode/skills/cron-management in your project.

What does Cron Management need to run?

SKILL.md names no scripts, command-line tools or credentials: Cron Management is instructions for the agent only.

Does Cron Management access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Cron Management 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 Cron Management use?

Cron Management is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cron Management use?

About 1.1k tokens (SKILL.md is roughly 4.5k 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 Cron Management?

Skills that share tags, products or a category with Cron Management: Schedule (TinyAGI/tinyagi, 3.6k stars), Send User Message (TinyAGI/tinyagi, 3.6k stars), Cron Ops (czl9707/build-your-own-openclaw, 1.9k stars) and X Bookmarks (sharbelxyz/x-bookmarks, 289 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cron Management?

grandamenium (a GitHub user) maintains it in grandamenium/cortextos, which has 101 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on September 23, 2026.

Source: grandamenium/cortextos on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Cron Management

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Cron Management

On Session Start

Handling a Cron Fire

Adding a Recurring Cron

Updating a Cron

Removing a Cron

Testing a Cron Immediately

Checking Execution History

Troubleshooting

Files

Compare with similar skills

Similar skills

More from grandamenium/cortextos

Related

Questions about Cron Management