New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Scheduler

by warpdotdev in warpdotdev/oz-skills

Schedule on-device reminders and local actions only. An agent skill from warpdotdev/oz-skills.

MITAuto-check passed

Install Scheduler

skills CLI
$ npx skills add warpdotdev/oz-skills --skill scheduler -a claude-code

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

GitHub CLI
$ gh skill install warpdotdev/oz-skills scheduler --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/warpdotdev/oz-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/scheduler .claude/skills/scheduler && 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
scheduler
GitHub stars
825
Token cost
~1.9k tokens
SKILL.md length
956 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

Schedule on-device reminders and local actions only. An agent skill from warpdotdev/oz-skills.

  • Works in 2 steps: Reminder → Task
  • Set personal reminders
  • SKILL.md covers What this Skill can schedule, Step 1: Parse the request, Step 2: Determine delivery or… and Step 3: Normalize the schedule, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Scheduler is an agent skill from warpdotdev/oz-skills. Schedule on-device reminders and local actions only. Use this skill to set personal reminders or run lightweight, local tasks at a specific time or interval (e.g., notifications, local scripts), on the user's computer or with platforms like Slack. Do NOT use for scheduling cloud agents, background agentic jobs, or Oz-managed workflows.

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

It works with Slack. The licence is MIT.

When your agent uses it

  • Set personal reminders
  • Run lightweight
  • Local tasks at a specific time
  • On the users computer

Example prompts

  • “/scheduler”

Workflow steps

2 steps, taken from the step headings in SKILL.md.

  1. Reminder
  2. Task

What it can do on your machine

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

    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

Scheduler loads about 1.9k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 956 words of instructions outside code blocks.

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

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 warpdotdev/oz-skills at commit 6c08c49, republished under its MIT licence (© warpdotdev). 956 words, ~1,948 tokens.

Download SKILL.mdSave it as .claude/skills/scheduler/SKILL.md (or your agent's skills folder).
name
scheduler
description
Schedule on-device reminders and local actions only. Use this skill to set personal reminders or run lightweight, local tasks at a specific time or interval (e.g., notifications, local scripts), on the user's computer or with platforms like Slack. Do NOT use for scheduling cloud agents, background agentic jobs, or Oz-managed workflows.
license
MIT

Scheduler Skill

You are a scheduling assistant. Your role is to help users schedule future actions, including reminders and automated tasks.

This Skill supports:

  • One-time schedules (“tomorrow at 9am”, “in 30 minutes”)
  • Recurring schedules (“every weekday”, “every Monday at 10”)
  • Multiple delivery types (notifications, messages, task execution)
  • Multiple backends (OS-native schedulers, Slack, or other configured systems)

This Skill does not assume a default delivery mechanism.
If the user does not specify how the scheduled action should run or be delivered, ask a clarifying question.

What this Skill can schedule

A scheduled item may be one of the following:

1. Reminder

A human-facing message delivered at a scheduled time.

Examples:

  • Notification
  • Terminal message
  • Slack message
2. Task

An automated action that runs at a scheduled time.

Examples:

  • Running a script or command
  • Triggering a workflow
  • Performing a recurring check

If the user does not clearly indicate whether they want a reminder or a task, assume a reminder and confirm.

Step 1: Parse the request

Extract:

  • Intent
    • Reminder vs task
  • Action
    • Message to display (for reminders), or
    • Command / operation to run (for tasks)
  • Schedule
    • One-time time
    • Relative delay
    • Recurring pattern
  • Delivery / execution method, if specified
    • Notification
    • Slack
    • Background task
    • Command execution

If any of these are unclear, ask a follow-up question before scheduling.

Ask clarifying questions if the schedule is ambiguous (e.g. “tomorrow morning”) or if the timezone is unclear.

Step 2: Determine delivery or execution method

Supported categories:

Local / OS-based execution options

When using local scheduling or delivery, select mechanisms appropriate to the user’s operating system and the requested action. The exact implementation may vary by environment and available tools.

macOS

macOS provides several native primitives that can be combined for scheduling, notifications, and automation:

  • Scheduling

    • launchd (native system scheduler)
      • Supports one-time and recurring schedules
      • Reliable across reboots and sleep
    • User-level scheduled jobs (no admin privileges required)

  • Notifications

    • AppleScript via osascript
      • Native Notification Center alerts
      • Can include title, subtitle, and message
    • Can also display dialogs if explicitly requested

  • Automation / Tasks

    • AppleScript or JavaScript for Automation (JXA)
    • Shell scripts or binaries
    • Can trigger other applications or workflows
Linux

Linux environments vary widely, so choose tools that are commonly available and degrade gracefully:

  • Scheduling

    • cron
      • Widely available and suitable for recurring schedules
    • systemd timers (if available)
      • Better reliability and richer semantics than cron
    • User-level scheduling preferred over system-wide jobs

  • Notifications

    • notify-send (freedesktop.org notification spec)
      • May not be available on all systems
    • Terminal output if no notification system is present

  • Automation / Tasks

    • Shell scripts
    • Executable binaries
    • Language runtimes available on the system

If desktop notifications are unavailable, fall back to terminal output or ask the user how they want the result delivered.

Windows

Windows provides built-in scheduling and notification capabilities through system services:

  • Scheduling

    • Windows Task Scheduler
      • Supports one-time and recurring tasks
      • Can run tasks in the background or at login
      • User-level tasks preferred unless elevated permissions are required

  • Notifications

    • Windows Toast notifications
      • Native system notifications
      • May require helper scripts or APIs depending on environment

  • Automation / Tasks

    • PowerShell scripts
    • Batch files
    • Executable programs

When creating scheduled tasks, ensure actions are scoped to the user context unless explicitly requested otherwise.

Fallback behavior

If a requested capability is not available on the user’s system:

  • Explain the limitation clearly
  • Offer an alternative (e.g. terminal output instead of notifications)
  • Ask the user how they would like to proceed

Never silently downgrade behavior without informing the user.

Show full SKILL.md (398 more words)Show less
External / Messaging
  • Slack (requires user configuration)
  • Other messaging systems if available

If no delivery method is specified, ask the user something like:

“Should this be a notification, a background task, or a message (for example, Slack)?”

Do not assume notifications or Slack by default.

Step 3: Normalize the schedule

Normalize the schedule into a structured form:

  • Absolute timestamp
  • Relative delay
  • Recurring rule

Guidelines:

  • Interpret times in the user’s local timezone unless they explicitly specify otherwise.
  • Preserve the user’s original intent when converting formats.
  • If a backend requires a specific format (e.g. cron), convert internally.

Step 4: Generate a stable name

Generate a short, kebab-case name based on the scheduled action.

Examples:

  • “review PRs” → review-prs
  • “weekly backup” → weekly-backup

If a name collision occurs, append a numeric suffix.

Step 5: Create the scheduled item

Create the scheduled reminder or task using the chosen backend.

You may:

  • Create scheduler entries
  • Write small helper scripts
  • Store metadata needed for later management

Do not assume:

  • A specific repository
  • Version control
  • Preconfigured secrets
  • Network access

Step 6: Confirm with the user

Always confirm with a clear summary:

  • Name
  • What will happen
  • When it will happen (human-readable, local time)
  • How it will be delivered or executed

Example:

✅ Scheduled
review-prs
Every weekday at 10:00 AM (local time)
Action: reminder message via notification

Listing scheduled items

When the user asks to see scheduled items:

  • List all items created via this Skill
  • Include:
    • Name
    • Type (reminder / task)
    • Schedule
    • Delivery / execution method
    • Status (active / paused)

Managing scheduled items

Support:

  • Pause
  • Unpause
  • Delete (confirm before deleting)
  • Update schedule
  • Update message or task action

If the user refers to an item ambiguously, ask for clarification.

Slack support (optional)

Slack delivery is optional and must be explicitly requested by the user.

If Slack is requested but not configured:

  • Explain what configuration is required. Look up Slack docs as needed.
  • Offer an alternative (local execution or notification)

Slack messages should be concise and clearly automated.

Safety and constraints

  • Do not schedule destructive actions without explicit confirmation
  • Avoid modifying unrelated system schedules
  • Keep scheduled items isolated and inspectable
  • Treat scheduling like installing automation on the user’s system

Examples

  • “Remind me in 30 minutes to stretch”
  • “Every weekday at 10am schedule a reminder to review PRs”
  • “Run this script every Sunday at midnight”
  • “Slack me every Friday at 4pm to send the weekly update”
  • “Pause my weekly-backup task”
  • “Delete the stand-up reminder”

End of Skill.

© warpdotdev, MIT. 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 .agents/skills/scheduler of warpdotdev/oz-skills.

Open the folder on GitHubat commit 6c08c49

Compare with similar skills

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

Scheduler compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Scheduler this skillwarpdotdev/oz-skills825—~1.9kAutomated safety check: PassMIT
Agent Browser CLIvercel-labs/agent-browser44k24 repos~864Automated safety check: PassApache-2.0
Slack GIF Creatoranthropics/skills180k28 repos~2kAutomated safety check: PassApache-2.0
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
Electron App Automationvercel-labs/agent-browser44k5 repos~1.7kAutomated safety check: PassApache-2.0
Slack Browser Automationvercel-labs/agent-browser44k1 repos~2.1kAutomated safety check: PassApache-2.0

Similar skills

  • Agent Browser CLI

    vercel-labs/agent-browser

    Official

    Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking…

    44k GitHub starsUsed in 24 repos~864 tokens
    Productivity & AutomationAuto-check passed

  • Slack GIF Creator

    anthropics/skills

    Official

    Provides Slack size and frame limits, Python animation helpers and validators for building animated GIFs sized for emoji and messages.

    180k GitHub starsUsed in 28 repos~2k tokens
    Media & CreativeAuto-check passed

  • Code Design Rationale Investigator

    cursor/plugins

    Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed

  • Electron App Automation

    vercel-labs/agent-browser

    Official

    Automates Electron desktop apps such as VS Code, Slack or Discord by connecting agent-browser to their Chrome DevTools Protocol port.

    44k GitHub starsUsed in 5 repos~1.7k tokens
    Productivity & AutomationAuto-check passed

  • Slack Browser Automation

    vercel-labs/agent-browser

    Official

    Drives the Slack web app with the agent-browser CLI to check unread channels, search, read channel details and extract information, with screenshots as evidence.

    44k GitHub starsUsed in 1 repo~2.1k tokens
    Productivity & AutomationAuto-check passed

  • Composio

    ComposioHQ/composio

    Route and complete Composio work across Composio For You and Composio Platform.

    30k GitHub starsUsed in 1 repo~1.7k tokens
    Productivity & AutomationAuto-check passed

More from warpdotdev/oz-skills

All 13 skills in this repo

  • SEO Aeo Audit

    warpdotdev/oz-skills

    Optimize for search engine visibility, ranking, and AI citations.

    825 GitHub stars~4.9k tokensUpdated 1 mo ago
    Auto-check passed

  • Web Accessibility Audit

    warpdotdev/oz-skills

    Audit web applications for WCAG accessibility compliance. An agent skill from warpdotdev/oz-skills.

    825 GitHub stars~3.1k tokensUpdated 1 mo ago
    Auto-check passed

  • Webapp Testing

    warpdotdev/oz-skills

    Test local web applications with Playwright. An agent skill from warpdotdev/oz-skills.

    825 GitHub stars~914 tokensUpdated 1 mo ago
    Auto-check passed

  • GitHub Bug Report Triage

    warpdotdev/oz-skills

    Triage GitHub bug reports for actionability. An agent skill from warpdotdev/oz-skills.

    825 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed

  • Analysis Artifacts

    warpdotdev/oz-skills

    Generate reproducible analysis artifacts — SQL queries, Python visualizations, and summary tables — as you work through a BigQuery data analysis.

    825 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed

  • CI Fix

    warpdotdev/oz-skills

    Diagnose and fix GitHub Actions CI failures. An agent skill from warpdotdev/oz-skills.

    825 GitHub stars~790 tokensUpdated 1 mo ago
    Auto-check passed

Works with

Questions about Scheduler

What does Scheduler do?

Schedule on-device reminders and local actions only. An agent skill from warpdotdev/oz-skills. Scheduler is an agent skill from warpdotdev/oz-skills. Schedule on-device reminders and local actions only.

When should I use Scheduler?

Scheduler fits situations like: set personal reminders; run lightweight; local tasks at a specific time; on the users computer.

How do I install Scheduler in Claude Code?

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

How do I install Scheduler in Codex?

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

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

What does Scheduler need to run?

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

Does Scheduler 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 Scheduler 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 Scheduler use?

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

About 1.9k tokens (SKILL.md is roughly 7.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 Scheduler?

Skills that share tags, products or a category with Scheduler: Agent Browser CLI (vercel-labs/agent-browser, 44k stars), Slack GIF Creator (anthropics/skills, 180k stars), Code Design Rationale Investigator (cursor/plugins, 10k stars) and Electron App Automation (vercel-labs/agent-browser, 44k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Scheduler?

warpdotdev (a GitHub organization) maintains it in warpdotdev/oz-skills, which has 825 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on August 15, 2026.

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