Agent skill

Schedule

by TinyAGI in TinyAGI/tinyagi

Create, list, and delete scheduled tasks (recurring or one-time) that send messages to agents.

MITAuto-check passedProductivity & Automation

Install Schedule

skills CLI
$ npx skills add TinyAGI/tinyagi --skill schedule -a claude-code

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

GitHub CLI
$ gh skill install TinyAGI/tinyagi schedule --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/TinyAGI/tinyagi.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/schedule .claude/skills/schedule && 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/

Facts

Skill name
schedule
GitHub stars
3.6k
Token cost
~1.4k tokens
SKILL.md length
488 words
Files
3 (incl. scripts, references)
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Create, list, and delete scheduled tasks (recurring or one-time) that send messages to agents.

  • Works in 5 steps: Confirm the target agent ID exists… → Determine recurring vs one-time → Compose a clear task message — this is… → …
  • The user wants to: schedule a recurring task for an agent
  • SKILL.md covers API Endpoints, Shell CLI, Workflow and Cron expression quick reference, plus 3 more sections
  • Runs Shell scripts from its folder; calls curl

What it does

Schedule is an agent skill from TinyAGI/tinyagi. Create, list, and delete scheduled tasks (recurring or one-time) that send messages to agents. Use when the user wants to: schedule a recurring task for an agent, set up a one-time future task, list existing scheduled tasks, delete or remove a scheduled task, or automate periodic agent work (reports, checks, reminders, syncs).

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts and reference files (for example `references/queue-format.md` and `scripts/schedule.sh`).

It sits in Productivity & Automation, covering Scheduled and recurring tasks and Task breakdown. The repository describes itself as: TinyAGI is the agent teams orchestrator for One Person Company. (fka TinyClaw). The licence is MIT.

When your agent uses it

  • The user wants to: schedule a recurring task for an agent
  • Set up a one-time future task
  • List existing scheduled tasks
  • Remove a scheduled task

Example prompts

  • “/schedule”

Requirements

  • A Bash shell

Workflow steps

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

  1. Confirm the target agent ID exists (check settings.json or ask the user).
  2. Determine recurring vs one-time
  3. Compose a clear task message — this is the prompt the agent will receive.
  4. Run scripts/schedule.sh create (recurring) or use the API (one-time) with the parameters.
  5. Verify with scripts/schedule.sh list.

What it can do on your machine

Read from SKILL.md and the folder at commit 2db3a03. 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

    Ships 1 file in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use curl, 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

Schedule loads about 1.4k tokens when it runs, and up to ~1.8k if it reads all its reference files. Until then it costs about 84 tokens; SKILL.md has 488 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~84
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.8k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from TinyAGI/tinyagi at commit 2db3a03, republished under its MIT licence (© TinyAGI). 488 words, ~1,438 tokens.

Download SKILL.mdSave it as .claude/skills/schedule/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
schedule
description
Create, list, and delete scheduled tasks (recurring or one-time) that send messages to agents. Use when the user wants to: schedule a recurring task for an agent, set up a one-time future task, list existing scheduled tasks, delete or remove a scheduled task, or automate periodic agent work (reports, checks, reminders, syncs).

Schedule Skill

Manage scheduled tasks that deliver messages to agents via the tinyagi API. Schedules can be recurring (cron-based) or one-time (fire once at a specific date/time). Each schedule enqueues a routed message (@agent_id <task>) that the queue processor picks up and invokes.

Schedules are persisted to ~/.tinyagi/schedules.json and run in-process via the croner library — no system crontab required.

API Endpoints

Schedules are managed via REST endpoints on the API server:

  • GET /api/schedules[?agent=ID] — list schedules
  • POST /api/schedules — create a schedule
  • PUT /api/schedules/:id — update a schedule
  • DELETE /api/schedules/:id — delete a schedule

Shell CLI

Use the bundled CLI scripts/schedule.sh for shell-based operations.

Create a recurring schedule
bash
scripts/schedule.sh create \
  --cron "EXPR" \
  --agent AGENT_ID \
  --message "Task context for the agent" \
  [--channel CHANNEL] \
  [--sender SENDER] \
  [--label LABEL]
  • --cron — 5-field cron expression (required for recurring). Examples: "0 9 * * *" (daily 9am), "*/30 * * * *" (every 30 min), "0 0 * * 1" (weekly Monday midnight).
  • --agent — Target agent ID (required). Must match an agent configured in settings.json.
  • --message — The task context / prompt sent to the agent (required).
  • --channel — Channel name in the queue message (default: schedule).
  • --sender — Sender name in the queue message (default: Scheduler).
  • --label — Unique label to identify this schedule (default: auto-generated).
Create a one-time schedule (via API)

One-time schedules are created via the REST API by passing runAt (ISO 8601 datetime) instead of cron:

bash
curl -X POST http://localhost:3777/api/schedules \
  -H "Content-Type: application/json" \
  -d '{
    "runAt": "2026-03-20T09:00:00.000Z",
    "agentId": "coder",
    "message": "Deploy the staging build",
    "label": "staging-deploy"
  }'

One-time schedules automatically disable themselves after firing.

List schedules
bash
scripts/schedule.sh list [--agent AGENT_ID]

Lists all tinyagi schedules. Optionally filter by --agent to show only schedules targeting a specific agent.

Delete a schedule
bash
scripts/schedule.sh delete --label LABEL
scripts/schedule.sh delete --all

Delete a specific schedule by label, or delete all tinyagi schedules.

Workflow

  1. Confirm the target agent ID exists (check settings.json or ask the user).
  2. Determine recurring vs one-time:
    • Recurring: determine the cron expression from the user's description (e.g., "every morning" -> "0 9 * * *").
    • One-time: determine the target date/time and convert to ISO 8601 format.
  3. Compose a clear task message — this is the prompt the agent will receive.
  4. Run scripts/schedule.sh create (recurring) or use the API (one-time) with the parameters.
  5. Verify with scripts/schedule.sh list.
Show full SKILL.md (175 more words)Show less

Cron expression quick reference

┌───────────── minute (0-59)
│ ┌───────────── hour (0-23)
│ │ ┌───────────── day of month (1-31)
│ │ │ ┌───────────── month (1-12)
│ │ │ │ ┌───────────── day of week (0-7, 0 and 7 = Sunday)
│ │ │ │ │
* * * * *
PatternMeaning
0 9 * * *Daily at 9:00 AM
0 9 * * 1-5Weekdays at 9:00 AM
*/15 * * * *Every 15 minutes
0 */2 * * *Every 2 hours
0 0 * * 0Weekly on Sunday midnight
0 0 1 * *Monthly on the 1st
30 8 * * 1Monday at 8:30 AM

Examples

Daily report
bash
scripts/schedule.sh create \
  --cron "0 9 * * *" \
  --agent analyst \
  --message "Generate the daily metrics report and post a summary" \
  --label daily-report
Periodic health check
bash
scripts/schedule.sh create \
  --cron "*/30 * * * *" \
  --agent devops \
  --message "Run health checks on all services and report any issues" \
  --label health-check
One-time deployment task
bash
curl -X POST http://localhost:3777/api/schedules \
  -H "Content-Type: application/json" \
  -d '{"runAt":"2026-03-20T14:00:00.000Z","agentId":"devops","message":"Deploy v2.1 to production","label":"prod-deploy-v21"}'
List and clean up
bash
# See all schedules
scripts/schedule.sh list

# See only schedules for @coder
scripts/schedule.sh list --agent coder

# Remove one
scripts/schedule.sh delete --label health-check

# Remove all
scripts/schedule.sh delete --all

How it works

  • Schedules are persisted in ~/.tinyagi/schedules.json.
  • The server runs an in-process cron scheduler (using croner) — no system crontab needed.
  • When a schedule fires, it directly enqueues a message in the SQLite queue.
  • The queue processor picks up the message and invokes the target agent, exactly like a message from any channel.
  • One-time schedules (runAt) auto-disable after firing.
  • Responses are stored in the SQLite queue and delivered by channel clients.

TinyOffice UI

Schedules can also be managed via the Schedule tab on each agent's detail page in TinyOffice. The UI provides a calendar view showing upcoming scheduled events and a form to create new schedules (recurring or one-time) without writing cron expressions.

© TinyAGI, 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 2 other files (scripts, references) in .agents/skills/schedule of TinyAGI/tinyagi.

  • SKILL.md
  • references/queue-format.md
  • scripts/schedule.sh

Open the folder on GitHubat commit 2db3a03

Compare with similar skills

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

Schedule compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Schedule this skillTinyAGI/tinyagi3.6k—~1.4kAutomated safety check: PassMIT
Daily Task PrepTheCraigHewitt/hermes-chief-of-staff104—~632Automated safety check: PassMIT
Cron Opsczl9707/build-your-own-openclaw1.9k—~593Automated safety check: PassMIT
Wp Wpcli And OpsAutomattic/agent-skills2112 repos~988Automated safety check: PassNone
Ohdearohdearapp/ohdear-cli141—~1.1kAutomated safety check: PassMIT
Jobsphysiclaw/PhysiClaw386—~1.1kAutomated safety check: PassMIT

Similar skills

  • Daily Task Prep

    TheCraigHewitt/hermes-chief-of-staff

    Nightly task preparation — enriches tomorrow's task list with recurring items, due-date promotions, and calendar events.

    104 GitHub stars~632 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
  • 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
  • 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.

    386 GitHub stars~1.1k tokensUpdated 2 days ago
    Productivity & AutomationAuto-check passed
  • 21 Day Self Interview

    Forlives/21-day-self-interview

    夜间自我访谈引导(21 天)。扮演资深存在主义心理咨询师,每晚提三个有意义的问题,记录回答并在节点回映,帮助用户看清自己。Use when running a nightly self-inquiry / journaling ritual driven by a scheduled task.

    101 GitHub stars~2k tokensUpdated 4 mo ago
    Productivity & AutomationAuto-check passed

More from TinyAGI/tinyagi

  • 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
    Auto-check passed
  • Skills Manager

    TinyAGI/tinyagi

    Search for and install skills from the skills registry to agent workspaces.

    3.6k GitHub stars~528 tokensUpdated 6 mo ago
    Auto-check passed
  • Tasks

    TinyAGI/tinyagi

    Manage your assigned tasks on the TinyAGI kanban board — list tasks, update task status, create new tasks, and add or view comments.

    3.6k GitHub stars~721 tokensUpdated 6 mo ago
    Auto-check passed
  • Tinyagi Admin

    TinyAGI/tinyagi

    Manage and operate the TinyAGI system itself — agents, teams, settings, queue, tasks, daemon lifecycle, and source code.

    3.6k GitHub stars~2.5k tokensUpdated 6 mo ago
    Auto-check passed
  • Memory

    TinyAGI/tinyagi

    Manage your persistent hierarchical memory — save, update, search, and organize knowledge as markdown files in the memory/ folder.

    3.6k GitHub stars~1.1k tokensUpdated 6 mo ago
    Auto-check passed

Questions about Schedule

What does Schedule do?

Create, list, and delete scheduled tasks (recurring or one-time) that send messages to agents. Schedule is an agent skill from TinyAGI/tinyagi. Create, list, and delete scheduled tasks (recurring or one-time) that send messages to agents.

When should I use Schedule?

Schedule fits situations like: the user wants to: schedule a recurring task for an agent; set up a one-time future task; list existing scheduled tasks; remove a scheduled task.

How do I install Schedule in Claude Code?

Run `npx skills add TinyAGI/tinyagi --skill schedule -a claude-code`. Or copy the skill folder (.agents/skills/schedule in TinyAGI/tinyagi) into .claude/skills/schedule in your project. Claude Code loads it when a task matches its description.

How do I install Schedule in Codex?

Run `npx skills add TinyAGI/tinyagi --skill schedule -a codex`. Or copy the skill folder (.agents/skills/schedule in TinyAGI/tinyagi) into .agents/skills/schedule in your project. Codex loads it when a task matches its description.

Can I use Schedule 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 TinyAGI/tinyagi --skill schedule -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/schedule, .gemini/skills/schedule, .github/skills/schedule and .opencode/skills/schedule in your project.

What does Schedule need to run?

Going by SKILL.md and its folder, Schedule needs a shell for the scripts in its folder and the command-line tools its instructions call (curl). Our summary lists: A Bash shell.

Does Schedule access the network?

SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Schedule 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Schedule use?

Schedule 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 Schedule use?

About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 354 tokens, read only when the agent opens those files.

What are the alternatives to Schedule?

Skills that share tags, products or a category with Schedule: Daily Task Prep (TheCraigHewitt/hermes-chief-of-staff, 104 stars), Cron Ops (czl9707/build-your-own-openclaw, 1.9k stars), Wp Wpcli And Ops (Automattic/agent-skills, 211 stars) and Ohdear (ohdearapp/ohdear-cli, 141 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Schedule?

TinyAGI (a GitHub organization) maintains it in TinyAGI/tinyagi, which has 3,620 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on March 30, 2026.

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