Agent skill

C Schedule

Smart scheduling — automate recurring Claude tasks with cost control.

MITAuto-check passedProductivity & Automation

Install C Schedule

skills CLI

$ npx skills add daxaur/openpaw --skill c-schedule -a claude-code

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

GitHub CLI

$ gh skill install daxaur/openpaw c-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/daxaur/openpaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/c-schedule .claude/skills/c-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/

Paste into Claude Code

Install the "c-schedule" agent skill from https://github.com/daxaur/openpaw/tree/main/skills/c-schedule into .claude/skills/c-schedule/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "c-schedule", 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/daxaur/openpaw/tree/main/skills/c-schedule

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 daxaur/openpaw --skill c-schedule -a codex

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

GitHub CLI

$ gh skill install daxaur/openpaw c-schedule --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/daxaur/openpaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/c-schedule .agents/skills/c-schedule && 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 "c-schedule" agent skill from https://github.com/daxaur/openpaw/tree/main/skills/c-schedule into .agents/skills/c-schedule/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "c-schedule", 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 daxaur/openpaw --skill c-schedule -a cursor

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

GitHub CLI

$ gh skill install daxaur/openpaw c-schedule --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/daxaur/openpaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/c-schedule .cursor/skills/c-schedule && 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 "c-schedule" agent skill from https://github.com/daxaur/openpaw/tree/main/skills/c-schedule into .cursor/skills/c-schedule/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "c-schedule", 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/daxaur/openpaw.git --path skills/c-schedule

--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 daxaur/openpaw --skill c-schedule -a gemini-cli

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

GitHub CLI

$ gh skill install daxaur/openpaw c-schedule --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/daxaur/openpaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/c-schedule .gemini/skills/c-schedule && 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 "c-schedule" agent skill from https://github.com/daxaur/openpaw/tree/main/skills/c-schedule into .gemini/skills/c-schedule/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "c-schedule", 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 daxaur/openpaw c-schedule

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 daxaur/openpaw --skill c-schedule -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/daxaur/openpaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/c-schedule .github/skills/c-schedule && 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 "c-schedule" agent skill from https://github.com/daxaur/openpaw/tree/main/skills/c-schedule into .github/skills/c-schedule/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "c-schedule", 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 daxaur/openpaw --skill c-schedule -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 daxaur/openpaw c-schedule --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/daxaur/openpaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/c-schedule .opencode/skills/c-schedule && 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 "c-schedule" agent skill from https://github.com/daxaur/openpaw/tree/main/skills/c-schedule into .opencode/skills/c-schedule/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "c-schedule", 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: c-schedule
GitHub stars: 174
Token cost: ~814 tokens
SKILL.md length: 240 words
Files: 1
Skills in repo: 42
Repo updated: May 23, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Smart scheduling — automate recurring Claude tasks with cost control.

Works in 6 steps: Jobs are stored in… → Each job registers as a system scheduler → When triggered, openpaw schedule run is… → …
Tasks that involve Budgeting and forecasting
SKILL.md covers Managing Schedules, Schedule Syntax, Cost Control and Delivery Methods, plus 3 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

C Schedule is an agent skill from daxaur/openpaw. Smart scheduling — automate recurring Claude tasks with cost control. Deliver results to Telegram, file, or notification. Built into OpenPaw.

Its SKILL.md is about 810 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 Budgeting and forecasting. It works with Telegram and macOS. The repository describes itself as: Personal Assistant Wizard for Claude Code — npx pawmode. The licence is MIT.

When your agent uses it

Tasks that involve Budgeting and forecasting

Example prompts

“/c-schedule”

Workflow steps

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

Jobs are stored in ~/.config/openpaw/schedules.json
Each job registers as a system scheduler
When triggered, openpaw schedule run is called
Claude runs with the job's prompt via the Agent SDK
Results are delivered to the configured channel
Cost is recorded

What it can do on your machine

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

C Schedule loads about 814 tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 240 words of instructions outside code blocks.

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

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 daxaur/openpaw at commit a2562d1, republished under its MIT licence (© daxaur). 240 words, ~814 tokens.

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

name: c-schedule
description: Smart scheduling — automate recurring Claude tasks with cost control. Deliver results to Telegram, file, or notification. Built into OpenPaw.
tags: schedule, automation, cron, recurring, proactive, cost-control

Smart Scheduling

Automate recurring tasks with Claude. Jobs run on a schedule via launchd (macOS) or cron (Linux), with built-in cost caps to prevent runaway spending.

Managing Schedules

bash

# Add a scheduled job (inline)
openpaw schedule add "weekdays 8am" --run "check email and summarize the important ones"
openpaw schedule add "daily 9pm" --run "review today's GitHub notifications"
openpaw schedule add "every 30 minutes" --run "check if any urgent emails arrived" --model haiku

# Interactive mode (prompts for all options)
openpaw schedule add

# List all jobs
openpaw schedule list

# Remove a job
openpaw schedule remove <id>

# Manually trigger a job
openpaw schedule run <id>

# Enable/disable without removing
openpaw schedule enable <id>
openpaw schedule disable <id>

# View cost usage
openpaw schedule costs

# Set daily cost cap
openpaw schedule set-cap 10.00

Schedule Syntax

Human-readable formats:

weekdays 8am or weekdays 08:00
daily 9pm or daily 21:00
weekends 10am
every 30 minutes
every 2 hours
monday 9am, friday 5pm, etc.
Raw cron: 0 8 * * 1-5

Cost Control

Daily cap: $5/day by default — jobs are skipped if the cap would be exceeded
Per-run budget: Each job has its own budget cap (default $1.00)
Cost tracking: All costs logged to ~/.config/openpaw/schedule-costs.json
30-day history: Old entries auto-pruned
View anytime: openpaw schedule costs

Delivery Methods

telegram — results sent directly to your Telegram (requires Telegram bridge setup)
file — saved to ~/.config/openpaw/schedule-results/ (always saved as backup)
notify — macOS notification via terminal-notifier

How It Works

Jobs are stored in ~/.config/openpaw/schedules.json
Each job registers as a system scheduler:
- macOS: launchd plist in ~/Library/LaunchAgents/
- Linux: crontab entry
When triggered, openpaw schedule run <id> is called
Claude runs with the job's prompt via the Agent SDK
Results are delivered to the configured channel
Cost is recorded

Guidelines

Use haiku for simple, frequent checks (cheapest)
Use sonnet for routine tasks like email summaries
Use opus only for complex analysis (expensive)
Test jobs manually first: openpaw schedule run <id>
Start with a higher per-run budget and reduce once you know typical costs
Check openpaw schedule costs to monitor spending

Common Recipes

bash

# Morning briefing to Telegram
openpaw schedule add "weekdays 8am" --run "give me a morning briefing: check email, calendar, and any GitHub notifications" --delivery telegram

# Evening project summary
openpaw schedule add "daily 6pm" --run "summarize what I worked on today based on git commits and recent files" --delivery file

# Urgent email monitor
openpaw schedule add "every 30 minutes" --run "check for urgent emails and notify me if any" --model haiku --budget 0.25 --delivery notify

Files

Just SKILL.md in skills/c-schedule of daxaur/openpaw.

Open the folder on GitHubat commit a2562d1

Compare with similar skills

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

C Schedule compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
C Schedule this skilldaxaur/openpaw	174	—	~814	Automated safety check: Pass	MIT	4 mo ago
Vercel Token Setupvellum-ai/vellum-assistant	1.4k	—	~2.4k	Automated safety check: Pass	MIT	today
Date NightLeoYeAI/openclaw-master-skills	2.2k	—	~4.8k	Automated safety check: Pass	MIT	2 mo ago
Process Inboxtelegramdesktop/tdesktop	33k	2 repos	~4.5k	Automated safety check: Pass	GPL-3.0	today
Perform Tasktelegramdesktop/tdesktop	33k	2 repos	~3k	Automated safety check: Pass	GPL-3.0	today
Continuetelegramdesktop/tdesktop	33k	2 repos	~9.4k	Automated safety check: Pass	GPL-3.0	today

Similar skills

Vercel Token Setup
vellum-ai/vellum-assistant
Set up a Vercel API token for publishing apps using browser automation
1.4k GitHub stars~2.4k tokensUpdated today
Productivity & AutomationAuto-check passed
Date Night
LeoYeAI/openclaw-master-skills
Your AI date night concierge — plans, books, and coordinates an entire evening out through browser automation.
2.2k GitHub stars~4.8k tokensUpdated 2 mo ago
Productivity & AutomationAuto-check passed
Process Inbox
telegramdesktop/tdesktop
Process the local ignored ai-tdesktop inbox into durable, independently testable Telegram Desktop task records while task execution worktrees remain active.
33k GitHub starsUsed in 2 repos~4.5k tokens
Productivity & AutomationAuto-check passed
Perform Task
telegramdesktop/tdesktop
Resolve, start or resume, implement, review, test, and publish exactly one existing ai-tdesktop task by short slug or full dated id, including rare blocked retries and split-required results.
33k GitHub starsUsed in 2 repos~3k tokens
Productivity & AutomationAuto-check passed
Continue
telegramdesktop/tdesktop
Continue autonomous Telegram Desktop development from the shared ai-tdesktop repository.
33k GitHub starsUsed in 2 repos~9.4k tokens
Productivity & AutomationAuto-check passed
Mac Computer Use
To3akaRin/mac-computer-use
操作 macOS 桌面应用，探测窗口和自动化接口、截图、读取或修改辅助功能元素、执行鼠标键盘动作，以及通过 CDP 操作内嵌 Chromium 页面。适用于桌面应用自动化与界面验收；普通网页任务优先使用已有浏览器工具。
1.1k GitHub starsUsed in 1 repo~495 tokens
Productivity & AutomationAuto-check passed

Questions about C Schedule

What does C Schedule do?

Smart scheduling — automate recurring Claude tasks with cost control. C Schedule is an agent skill from daxaur/openpaw. Smart scheduling — automate recurring Claude tasks with cost control.

When should I use C Schedule?

C Schedule fits situations like: tasks that involve Budgeting and forecasting.

How do I install C Schedule in Claude Code?

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

How do I install C Schedule in Codex?

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

Can I use C 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 daxaur/openpaw --skill c-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/c-schedule, .gemini/skills/c-schedule, .github/skills/c-schedule and .opencode/skills/c-schedule in your project.

What does C Schedule need to run?

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

Does C Schedule 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 C 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. Review the folder before installing.

What licence does C Schedule use?

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

About 814 tokens (SKILL.md is roughly 3.3k 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 C Schedule?

Skills that share tags, products or a category with C Schedule: Vercel Token Setup (vellum-ai/vellum-assistant, 1.4k stars), Date Night (LeoYeAI/openclaw-master-skills, 2.2k stars), Process Inbox (telegramdesktop/tdesktop, 33k stars) and Perform Task (telegramdesktop/tdesktop, 33k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains C Schedule?

daxaur (a GitHub user) maintains it in daxaur/openpaw, which has 174 GitHub stars. The repository holds 42 skills in this directory. The repository was last updated on May 23, 2026.

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

Install C Schedule

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

Smart Scheduling

Managing Schedules

Schedule Syntax

Cost Control

Delivery Methods

How It Works

Guidelines

Common Recipes

Files

Compare with similar skills

Similar skills

More from daxaur/openpaw

Related

Questions about C Schedule