Schedule
TinyAGI/tinyagi
Create, list, and delete scheduled tasks (recurring or one-time) that send messages to agents.
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
Install Agent Self Scheduling
$ npx skills add majiayu000/claude-skill-registry --skill agent-self-scheduling -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install majiayu000/claude-skill-registry agent-self-scheduling --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/majiayu000/claude-skill-registry.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ai-llm/agent-self-scheduling .claude/skills/agent-self-scheduling && 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 "agent-self-scheduling" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/ai-llm/agent-self-scheduling into .claude/skills/agent-self-scheduling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-self-scheduling", 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/majiayu000/claude-skill-registry/tree/main/skills/ai-llm/agent-self-schedulingType 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 majiayu000/claude-skill-registry --skill agent-self-scheduling -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install majiayu000/claude-skill-registry agent-self-scheduling --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/ai-llm/agent-self-scheduling .agents/skills/agent-self-scheduling && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "agent-self-scheduling" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/ai-llm/agent-self-scheduling into .agents/skills/agent-self-scheduling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-self-scheduling", 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 majiayu000/claude-skill-registry --skill agent-self-scheduling -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install majiayu000/claude-skill-registry agent-self-scheduling --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/ai-llm/agent-self-scheduling .cursor/skills/agent-self-scheduling && 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 "agent-self-scheduling" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/ai-llm/agent-self-scheduling into .cursor/skills/agent-self-scheduling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-self-scheduling", 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/majiayu000/claude-skill-registry.git --path skills/ai-llm/agent-self-scheduling--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 majiayu000/claude-skill-registry --skill agent-self-scheduling -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install majiayu000/claude-skill-registry agent-self-scheduling --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/ai-llm/agent-self-scheduling .gemini/skills/agent-self-scheduling && 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 "agent-self-scheduling" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/ai-llm/agent-self-scheduling into .gemini/skills/agent-self-scheduling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-self-scheduling", 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 majiayu000/claude-skill-registry agent-self-schedulingInstalls 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 majiayu000/claude-skill-registry --skill agent-self-scheduling -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/ai-llm/agent-self-scheduling .github/skills/agent-self-scheduling && 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 "agent-self-scheduling" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/ai-llm/agent-self-scheduling into .github/skills/agent-self-scheduling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-self-scheduling", 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 majiayu000/claude-skill-registry --skill agent-self-scheduling -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install majiayu000/claude-skill-registry agent-self-scheduling --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/ai-llm/agent-self-scheduling .opencode/skills/agent-self-scheduling && 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 "agent-self-scheduling" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/ai-llm/agent-self-scheduling into .opencode/skills/agent-self-scheduling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-self-scheduling", 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
agent-self-scheduling- GitHub stars
- 666
- Used in
- 2 other repos
- Token cost
- ~1.2k tokens
- SKILL.md length
- 507 words
- Files
- 2
- Skills in repo
- 1,273
- Repo updated
- First seen
- Licence
- MIT
At a glance
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
- Works in 4 steps: Camp A: log file grows after one… → Camp B: hermes cron list shows the job +… → Confirm permission/sandbox flags are… → …
- Tasks that involve Scheduled and recurring tasks
- SKILL.md covers When to Use, Camp A — one-shot agents, you…, Camp B — Hermes built-in… and Heartbeat pattern, plus 2 more sections
- Calls codex and claude
What it does
Agent Self Scheduling is an agent skill from majiayu000/claude-skill-registry. Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `metadata.json`).
It sits in Productivity & Automation, covering Scheduled and recurring tasks. The repository describes itself as: Searchable Claude Code skills catalog with source-linked guides and generated registry artifacts. The licence is MIT.
When your agent uses it
- Tasks that involve Scheduled and recurring tasks
Example prompts
- “/agent-self-scheduling”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Camp A: log file grows after one interval, or run the wrapped command once by hand → clean JSON, exit 0.
- Camp B: hermes cron list shows the job + sane next_run; trigger a run-now to confirm delivery.
- Confirm permission/sandbox flags are present — the #1 silent failure is a hung permission prompt.
- Heartbeats: confirm a nothing-due tick stays silent.
What it can do on your machine
Read from SKILL.md and the folder at commit 2d14a69. 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:
codexclaude
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
Agent Self Scheduling loads about 1.2k tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 507 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 majiayu000/claude-skill-registry at commit 2d14a69, republished under its MIT licence (© majiayu000). 507 words, ~1,190 tokens.
Download SKILL.mdSave it as
.claude/skills/agent-self-scheduling/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- agent-self-scheduling
- description
- Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
- category
- agent-orchestration
- risk
- critical
- source
- community
- source_repo
- davidondrej/skills
- source_type
- community
- date_added
- 2026-07-07
- author
- davidondrej
- tags
- agents, scheduling, automation, cron
- tools
- claude, codex
- license
- MIT
Agent Self-Scheduling
When to Use
- Use when the user asks for recurring, scheduled, heartbeat, or looped agent work.
- Use when you need to choose between cron, external schedulers, hooks, or built-in agent scheduling.
First question: does the agent have a built-in scheduler (Hermes → Camp B), or do you own the clock (everything else → Camp A)?
Universal floor: cron is 1 minute minimum (5-field expr, no seconds) — every camp. For sub-minute you MUST use a while ...; sleep N; done loop, a TS extension, or an event hook. Never put an LLM on a tight timer.
Camp A — one-shot agents, you own the clock
These run once and exit (amnesiac unless resumed). Schedule them externally.
claude -p "PROMPT" --output-format json --allowedTools "Read,Edit,Bash" # Claude Code
codex exec --json "PROMPT" # Codex
pi run "PROMPT" # PiWrap in a clock:
# 1. cron (>= 1 min floor)
*/10 * * * * cd /path/to/project && pi run "check X and report" >> ~/agent.log 2>&1
# 2. systemd timer (Linux, survives reboot, better logging) — OnUnitActiveSec=10min
# 3. dumb loop (sub-minute, or no cron available)
while true; do pi run "check X"; sleep 30; doneGotchas (each breaks unattended runs if ignored):
- Permissions hang forever. Pass
--allowedTools(Claude) or sandbox/auto-approve flags (Codex), or the run blocks on a prompt. - Use JSON output (
--output-format json/--json) so the wrapper parses results deterministically. - Runs are amnesiac. Resume (
codex exec resume --last) or persist state to a file the next run reads.
Pi has NO built-in scheduler/loop/heartbeat by design — external clock only (or a TS extension for agent-side timers).
cmux — orchestration only, NO scheduler
cmux has no timer/watch/cron. Three ways to loop it: orchestrator-driven (send → sleep → read-screen on your own clock), a dumb while-sleep wrapper, or — preferred — event-driven via cmux notify + OSC terminal hooks, which is cheaper and more responsive than polling. read-screen is non-interruptive, safe to poll.
If a loop checks another agent, send the user a one-line status each check: what the agent is doing, on track or not. (Claude Code may prefill a predicted next user message after finishing — that's Claude, not the user.)
Show full SKILL.md (231 more words)Show less
Camp B — Hermes built-in scheduler
Hermes' gateway ticks every 60s and runs due jobs in fresh isolated sessions. State-check first:
hermes gateway install # user-level ( --system to survive reboot)
hermes cron create "every 1h" "summarize new emails and report" --skill himalaya
hermes cron create "0 9 * * *" "post daily standup" # cron expr
hermes cron create "30m" "one-shot reminder in 30 min" # one-shot delayHermes-unique: zero-token mode (run a script, deliver stdout verbatim — use for watchdogs), chaining (context_from pipes one job's output into the next), self-terminating loops, and loop safety (scheduled sessions cannot create more cron jobs — don't schedule from inside a scheduled job). Each run is a fresh session: the prompt must carry all context.
Heartbeat pattern
One fast recurring tick gates many slower per-task checks: the tick reads a task list + per-task last_run timestamps and only acts on tasks that are due. In Hermes use a recurring job (zero-token mode when nothing's due); in Camp A use a while-sleep loop. Define active-hours, and stay silent when nothing is due — no empty noise.
Verify it fires (before reporting success)
- Camp A: log file grows after one interval, or run the wrapped command once by hand → clean JSON, exit 0.
- Camp B:
hermes cron listshows the job + sanenext_run; trigger a run-now to confirm delivery. - Confirm permission/sandbox flags are present — the #1 silent failure is a hung permission prompt.
- Heartbeats: confirm a nothing-due tick stays silent.
Limitations
- Adapted from
davidondrej/skills; verify local paths, tools, credentials, and agent features before acting. - For commands, remote access, scheduling, browser automation, or file-changing workflows, get explicit user approval and confirm the target environment first.
© majiayu000, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/ai-llm/agent-self-scheduling of majiayu000/claude-skill-registry.
- SKILL.md
- metadata.json
Open the folder on GitHubat commit 2d14a69
Used in 2 other repositories
We found 6 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in majiayu000/claude-skill-registry, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Agent Self Scheduling 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 |
|---|---|---|---|---|---|---|
| Agent Self Scheduling this skillmajiayu000/claude-skill-registry | 666 | 2 repos | ~1.2k | Automated safety check: Pass | MIT | |
| ScheduleTinyAGI/tinyagi | 3.6k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Send User MessageTinyAGI/tinyagi | 3.6k | — | ~829 | Automated safety check: Pass | MIT | |
| Cron Opsczl9707/build-your-own-openclaw | 1.9k | — | ~593 | Automated safety check: Pass | MIT | |
| X Bookmarkssharbelxyz/x-bookmarks | 289 | — | ~2k | Automated safety check: Notes | None | |
| Jobsphysiclaw/PhysiClaw | 386 | 1 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Send User Message
TinyAGI/tinyagi
Send a proactive message to a paired user via their channel (Discord, Telegram, or WhatsApp).
Cron Ops
czl9707/build-your-own-openclaw
Create, list, and delete scheduled cron jobs. An agent skill from czl9707/build-your-own-openclaw.
X Bookmarks
sharbelxyz/x-bookmarks
Fetch, summarize, and manage X/Twitter bookmarks via bird CLI or X API v2.
Jobs
physiclaw/PhysiClaw
A skill your agent uses when the task involves scheduling future work — any "remind me at …", "every weekday …", "check again in 30 min", or closing a fired cron job.
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…
More from majiayu000/claude-skill-registry
All 1,273 skills in this repoDeep Research
majiayu000/claude-skill-registry
Multi-source deep research using firecrawl and exa MCPs. An agent skill from majiayu000/claude-skill-registry.
Exa Search
majiayu000/claude-skill-registry
Neural search via Exa MCP for web, code, and company research.
Fal AI Media
majiayu000/claude-skill-registry
Unified media generation via fal.ai MCP — image, video, and audio.
Pyzotero
majiayu000/claude-skill-registry
Interact with Zotero reference management libraries using the pyzotero Python client.
Bgpt Paper Search
majiayu000/claude-skill-registry
Search scientific papers and retrieve structured experimental data extracted from full-text studies via the BGPT MCP server.
Bio Alignment Pairwise
majiayu000/claude-skill-registry
Perform pairwise sequence alignment using Biopython Bio.Align.PairwiseAligner.
Related
Categories
Questions about Agent Self Scheduling
What does Agent Self Scheduling do?
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers. Agent Self Scheduling is an agent skill from majiayu000/claude-skill-registry. Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
When should I use Agent Self Scheduling?
Agent Self Scheduling fits situations like: tasks that involve Scheduled and recurring tasks.
How do I install Agent Self Scheduling in Claude Code?
Run `npx skills add majiayu000/claude-skill-registry --skill agent-self-scheduling -a claude-code`. Or copy the skill folder (skills/ai-llm/agent-self-scheduling in majiayu000/claude-skill-registry) into .claude/skills/agent-self-scheduling in your project. Claude Code loads it when a task matches its description.
How do I install Agent Self Scheduling in Codex?
Run `npx skills add majiayu000/claude-skill-registry --skill agent-self-scheduling -a codex`. Or copy the skill folder (skills/ai-llm/agent-self-scheduling in majiayu000/claude-skill-registry) into .agents/skills/agent-self-scheduling in your project. Codex loads it when a task matches its description.
Can I use Agent Self Scheduling 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 majiayu000/claude-skill-registry --skill agent-self-scheduling -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agent-self-scheduling, .gemini/skills/agent-self-scheduling, .github/skills/agent-self-scheduling and .opencode/skills/agent-self-scheduling in your project.
What does Agent Self Scheduling need to run?
Going by SKILL.md and its folder, Agent Self Scheduling needs the command-line tools its instructions call (codex and claude).
Does Agent Self Scheduling 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 Agent Self Scheduling 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 Agent Self Scheduling use?
Agent Self Scheduling is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Agent Self Scheduling use?
About 1.2k tokens (SKILL.md is roughly 4.8k 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 Agent Self Scheduling?
Skills that share tags, products or a category with Agent Self Scheduling: 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 Agent Self Scheduling?
majiayu000 (a GitHub user) maintains it in majiayu000/claude-skill-registry, which has 666 GitHub stars. The repository holds 1,273 skills in this directory. The repository was last updated on October 7, 2026.
Source: majiayu000/claude-skill-registry on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.