Cron
shibing624/agentica
Schedule, list, pause, resume, edit, or run the user's agentica cron jobs with the cronjob tool.
Persistent task queue system. An agent skill from LeoYeAI/openclaw-master-skills.
$ npx skills add LeoYeAI/openclaw-master-skills --skill task-runner -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills task-runner --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/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/autonomous-task-runner .claude/skills/task-runner && 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 "task-runner" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/autonomous-task-runner into .claude/skills/task-runner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "task-runner", 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/LeoYeAI/openclaw-master-skills/tree/main/skills/autonomous-task-runnerType 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 LeoYeAI/openclaw-master-skills --skill task-runner -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills task-runner --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/autonomous-task-runner .agents/skills/task-runner && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "task-runner" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/autonomous-task-runner into .agents/skills/task-runner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "task-runner", 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 LeoYeAI/openclaw-master-skills --skill task-runner -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills task-runner --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/autonomous-task-runner .cursor/skills/task-runner && 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 "task-runner" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/autonomous-task-runner into .cursor/skills/task-runner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "task-runner", 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/LeoYeAI/openclaw-master-skills.git --path skills/autonomous-task-runner--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 LeoYeAI/openclaw-master-skills --skill task-runner -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills task-runner --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/autonomous-task-runner .gemini/skills/task-runner && 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 "task-runner" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/autonomous-task-runner into .gemini/skills/task-runner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "task-runner", 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 LeoYeAI/openclaw-master-skills task-runnerInstalls 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 LeoYeAI/openclaw-master-skills --skill task-runner -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/autonomous-task-runner .github/skills/task-runner && 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 "task-runner" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/autonomous-task-runner into .github/skills/task-runner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "task-runner", 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 LeoYeAI/openclaw-master-skills --skill task-runner -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills task-runner --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/autonomous-task-runner .opencode/skills/task-runner && 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 "task-runner" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/autonomous-task-runner into .opencode/skills/task-runner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "task-runner", 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.
task-runnerPersistent task queue system. An agent skill from LeoYeAI/openclaw-master-skills.
Task Runner is an agent skill from LeoYeAI/openclaw-master-skills. Persistent task queue system. Users add tasks at any time via natural language; tasks are stored in a single persistent queue file and executed asynchronously via subagents. A heartbeat/cron dispatcher wakes periodically to check pending tasks, spawn workers, and report completions. The system never "finishes" — it always remains ready for the next task.
Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files (for example `CHANGELOG.md`, `README.md` and `STATUS.json`).
It sits in Productivity & Automation, covering Scheduled and recurring tasks, Background jobs and Subagents. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.
12 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Task Runner loads about 4.1k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 92 tokens; SKILL.md has 1,295 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.
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.
The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,295 words, ~4,072 tokens.
.claude/skills/task-runner/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.A persistent, daemon-style task queue. Users add tasks at any time. A dispatcher runs on every heartbeat to check the queue and execute pending work via subagents. Tasks accumulate, complete, and are archived — the queue itself never closes.
This skill has two distinct modes with different triggers and behaviors:
| Mode | Trigger | Purpose |
|---|---|---|
| INTAKE | User message containing task intent | Parse message → add tasks to queue → confirm → immediately run DISPATCHER |
| DISPATCHER | After INTAKE (primary) · Heartbeat/cron (backup) | Read queue → dispatch pending tasks → report completions |
Both modes read and write the same persistent queue file.
Activate INTAKE mode when the user's message matches any of the following patterns:
| Pattern | Examples |
|---|---|
| Explicit task add | "add task", "add these tasks", "task:", "new task" |
| Delegation | "do this for me", "do these for me", "handle these", "can you do X" |
| Framing | "I need you to", "help me with", "I need", "I want you to" |
| List framing | "task list", "my tasks", "queue these", "work on these" |
| Control commands | "skip T-03", "retry T-02", "mark T-01 done", "cancel T-04" |
| Status check | "show tasks", "task status", "what's in the queue", "what are my pending tasks" |
| Compound ask | Any message with 2+ distinct action items (bullets, numbers, "and also", "then") |
Do NOT activate INTAKE for:
Activate DISPATCHER mode when triggered by:
HEARTBEAT.md check during a heartbeat poll (backup: catches retries and completions)"TASK_RUNNER_DISPATCH: check queue and run pending tasks" (backup)| Variable | Location | Default | Description |
|---|---|---|---|
TASK_RUNNER_DIR | TOOLS.md | ~/.openclaw/tasks/ | Directory for queue file and deliverables |
TASK_RUNNER_MAX_CONCURRENT | TOOLS.md | 2 | Max tasks running simultaneously |
TASK_RUNNER_MAX_RETRIES | TOOLS.md or env | 3 | Max retry attempts before marking blocked |
TASK_RUNNER_ARCHIVE_DAYS | TOOLS.md | 7 | Days after which done/blocked tasks are archived |
How to configure — add to TOOLS.md:
## Task Runner
TASK_RUNNER_DIR=~/.openclaw/tasks/
TASK_RUNNER_MAX_CONCURRENT=2
TASK_RUNNER_MAX_RETRIES=3
TASK_RUNNER_ARCHIVE_DAYS=7Queue file path: ${TASK_RUNNER_DIR}/task-queue.json
(single persistent file, NOT dated — accumulates all tasks over time)
| Output | Path / Channel | Description |
|---|---|---|
| Queue file | ${TASK_RUNNER_DIR}/task-queue.json | Single persistent queue; all tasks |
| Per-task completion message | Chat notification | Sent immediately when a task finishes (done or blocked) |
| Deliverable files | Task-specific paths | Files produced by tasks (when applicable) |
| INTAKE confirmation | Chat | Sent after adding tasks to queue |
Goal: Convert user message into structured task objects, append to queue, confirm.
Run this check before anything else, every INTAKE invocation:
CHECK whether ${TASK_RUNNER_DIR}/task-queue.json exists
IF file does NOT exist:
→ This is the first run. Auto-configure everything silently before proceeding.
[1] Create directory:
exec: mkdir -p ${TASK_RUNNER_DIR}
[2] Initialize queue file:
WRITE ${TASK_RUNNER_DIR}/task-queue.json with default structure:
{ "lastId": null, "tasks": [], "archivedCount": 0 }
[3] Register heartbeat entry:
READ HEARTBEAT.md (create it if missing)
IF "Task Runner Dispatcher" is NOT already in the file:
APPEND the following block (with a blank line before it):
## Task Runner Dispatcher
Every heartbeat: check ${TASK_RUNNER_DIR}/task-queue.json
- If pending or running tasks exist → run DISPATCHER mode (task-runner skill)
- If nothing pending → HEARTBEAT_OK (skip)
WRITE the updated HEARTBEAT.md
[4] Register backup cron job:
CALL cron tool with:
action: "add"
job:
name: "Task Runner Dispatcher"
schedule: { kind: "every", everyMs: 900000 }
payload: { kind: "systemEvent", text: "TASK_RUNNER_DISPATCH: check queue and run pending tasks" }
sessionTarget: "main"
enabled: true
[5] Notify user:
"⚙️ Task Runner initialized.
Heartbeat dispatcher registered in HEARTBEAT.md.
Backup cron job registered (runs every 15 minutes).
Your tasks will execute automatically."
→ THEN continue with normal INTAKE steps below.
IF file already exists:
→ Skip Step 0 entirely. Proceed directly to Step 1.Idempotency rule: Step 0 only fires on true first run (queue file absent). It will never double-register the heartbeat entry or create duplicate cron jobs.
READ ${TASK_RUNNER_DIR}/task-queue.json
IF file does not exist:
Initialize with default structure (see references/queue-schema.md)
Set lastId = nullSplit user message into individual tasks using these cues:
Continue from lastId in the queue file:
lastId = "T-05", next task is T-06lastId = null, start at T-01T-NN (zero-padded, minimum 2 digits; expand to 3 when N > 99)For each parsed task, create a JSON object (schema in references/queue-schema.md):
id, description, goal, status = "pending", added_atretries = 0, maxRetries from configAPPEND new task objects to queue.tasks[]
UPDATE queue.lastId to the last assigned ID
WRITE updated queue file to diskAdded T-06: [description]. Starting now...For multiple tasks:
📋 Added 3 tasks to queue:
• T-06: [description]
• T-07: [description]
• T-08: [description]
Starting dispatcher now...Then immediately run DISPATCHER mode (Steps 1–5 below) in the same turn. Do not exit and wait for the next heartbeat. Tasks must start executing immediately. The heartbeat/cron dispatcher is a backup for retries and completion checks — not the primary execution path.
| Command | Action |
|---|---|
skip T-NN | Set status = "skipped"; save; confirm |
retry T-NN | Reset status = "pending", retries = 0; save; confirm |
cancel T-NN | Set status = "skipped", blocked_reason = "cancelled by user"; save; confirm |
mark T-NN done | Set status = "done", completed_at = now; save; confirm |
show tasks / task status | Read queue; render status table (see A5 templates) |
Goal: Check queue, dispatch pending tasks, track running tasks, report completions.
READ ${TASK_RUNNER_DIR}/task-queue.json
IF file does not exist OR tasks array is empty:
→ HEARTBEAT_OK (silent, nothing to do)
→ EXITpending_tasks = tasks where status = "pending"
running_tasks = tasks where status = "running"
IF pending_tasks is empty AND running_tasks is empty:
→ HEARTBEAT_OK (silent)
→ EXITFor each task with status = "running":
IF subagent_session is set:
CHECK subagent session status
IF session is DONE:
READ deliverable from session output
RUN verification (see references/verification-guide.md)
IF verification passes:
SET status = "done"
SET deliverable, deliverable_path, completed_at
NOTIFY user: ✅ T-NN done — [summary]
ELSE (verification failed):
TREAT as failure (see retry logic below)
IF session is FAILED or ERROR:
IF retries < maxRetries:
INCREMENT retries
ADD to strategies_tried
SET status = "pending" ← will be re-dispatched this cycle
ELSE:
SET status = "blocked"
SET blocked_reason, user_action_required, completed_at
NOTIFY user: 🚫 T-NN blocked — [reason + unblock steps]
IF session is STILL RUNNING:
Leave as-is (will check again next heartbeat)currently_running = count of tasks with status = "running"
slots_available = maxConcurrent - currently_running
FOR EACH pending task (in order of added_at), up to slots_available:
PICK execution strategy (see references/task-types.md)
SPAWN subagent with task description and strategy
SET status = "running"
SET subagent_session = spawned session ID
SET started_at = nowSubagent instructions template:
You are executing task [T-NN] for the task-runner skill.
Task: [description]
Goal: [goal]
Type: [task_type]
Strategy: [selected strategy from task-types.md]
Execute the task. When complete:
1. Report the result clearly
2. Note any deliverable file path if a file was created
3. If blocked, explain exactly why and what the user needs to do
Do not start any other tasks. Focus only on this one.WRITE updated queue file (status changes, subagent_session IDs)If any notifications were sent (done/blocked), this is an active heartbeat response. If only silent dispatching occurred, this is still a heartbeat response (not HEARTBEAT_OK). Only return HEARTBEAT_OK when there was truly nothing to do (no pending, no running tasks).
Added T-06: [description]. Queue now has N pending tasks.📋 Added N tasks to queue:
• T-06: [description]
• T-07: [description]
Starting now...📋 Task Queue — [N total, N pending, N running, N done, N blocked]
ID Status Description
T-01 ✅ done [description] → [deliverable summary]
T-02 🔄 running [description] (started [time ago])
T-03 ⏳ pending [description]
T-04 🚫 blocked [description] — [blocked_reason short]
T-05 ⏭️ skipped [description]✅ T-NN done — [one-sentence summary of what was accomplished]
[deliverable: link or file path, if applicable]🚫 T-NN blocked after [N] attempts
What was tried:
- [Strategy 1]: [result]
- [Strategy 2]: [result]
Why it's blocked:
[Clear plain-English explanation]
To unblock:
1. [Concrete step #1]
2. [Concrete step #2 if needed]
Reply "retry T-NN" once ready.⏭️ T-NN skipped — as requested.Heartbeat and cron setup is automatic. Step 0 of INTAKE mode handles this on first use — no manual configuration required.
Tasks are dispatched immediately after INTAKE — heartbeat and cron are backups only.
The backup dispatcher handles:
Users should never need to wait for a heartbeat for a freshly added task.
HEARTBEAT.md entry (injected on first INTAKE):
## Task Runner Dispatcher
Every heartbeat: check ${TASK_RUNNER_DIR}/task-queue.json
- If pending or running tasks exist → run DISPATCHER mode (task-runner skill)
- If nothing pending → HEARTBEAT_OK (skip)Backup cron job (registered on first INTAKE):
every 15 min → systemEvent: "TASK_RUNNER_DISPATCH: check queue and run pending tasks"
sessionTarget: mainIf for any reason auto-setup did not run (e.g., queue file was pre-created externally),
delete ${TASK_RUNNER_DIR}/task-queue.json and send any task — Step 0 will fire.
maxConcurrent slotsarchiveDays days with terminal status are archived/removedlastId always increments (no ID reuse)maxRetries respected before any task is marked blocked| Situation | Behavior |
|---|---|
| Queue file missing (first run) | Run Step 0 auto-setup: create dir, init queue, register heartbeat + cron; notify user |
| Queue file missing (manually deleted) | Step 0 re-fires: re-initializes queue; does NOT re-register heartbeat/cron (idempotent check) |
| Queue file corrupt/invalid JSON | Log error, notify user, do not overwrite; ask user to inspect |
| Task description is ambiguous | Assign unknown type; dispatcher will attempt classification + fallback |
maxConcurrent already reached | Dispatcher skips dispatching; checks again next heartbeat |
| User adds task while dispatcher is running | Race-safe: dispatcher reads, processes, writes atomically per cycle |
| Task depends on another task's output | Set blocked_reason = "depends on T-NN-1 which is pending/blocked" |
| User says "retry T-NN" | Reset to pending, retries = 0, strategies_tried = [] |
| All tasks blocked | Notify user: "All tasks are blocked. Review unblock instructions above." |
| 20+ tasks added at once | Dispatcher dispatches in batches of maxConcurrent; all tasks eventually run |
| Subagent session ID lost | Mark task as pending again; will re-dispatch next cycle |
| Archive: done tasks > archiveDays old | Move to ${TASK_RUNNER_DIR}/archive/YYYY-MM.json; remove from main queue |
${TASK_RUNNER_DIR}/
task-queue.json ← single persistent queue (all active tasks)
archive/
2026-01.json ← archived tasks (done/blocked, older than archiveDays)
2026-02.jsonQueue file schema is documented in references/queue-schema.md.
references/queue-schema.md — Queue JSON format (complete field reference)references/task-types.md — Task type catalog and strategy selectionreferences/verification-guide.md — Verification logic per task typetests/test-triggers.json — Trigger test cases (positive and negative)© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 9 other files (references) in skills/autonomous-task-runner of LeoYeAI/openclaw-master-skills.
Open the folder on GitHubat commit e5199b5
Task Runner 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 |
|---|---|---|---|---|---|---|
| Task Runner this skillLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.1k | Automated safety check: Pass | MIT | |
| Cronshibing624/agentica | 352 | — | ~317 | Automated safety check: Pass | Apache-2.0 | |
| Worker DevelopmentChatbotXIO/ChatbotX | 878 | — | ~2.7k | Automated safety check: Notes | Custom licence | |
| Convex Cronsopenclaw/clawhub | 9.5k | 1 repos | ~189 | Automated safety check: Pass | MIT | |
| Frappe Impl SchedulerImpertio-Studio/Frappe_Claude_Skill_Package | 187 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Autopilothanamizuki/solopreneur | 152 | — | ~6.8k | Automated safety check: Pass | MIT |
shibing624/agentica
Schedule, list, pause, resume, edit, or run the user's agentica cron jobs with the cronjob tool.
ChatbotXIO/ChatbotX
Create and manage background workers, BullMQ queues, and scheduled jobs.
openclaw/clawhub
Add recurring scheduled jobs (crons) to the Convex app. An agent skill from openclaw/clawhub.
Impertio-Studio/Frappe_Claude_Skill_Package
A skill your agent uses when implementing scheduled tasks and background jobs in Frappe v14/v15/v16.
hanamizuki/solopreneur
PR orchestration planner. An agent skill from hanamizuki/solopreneur.
NeverSight/learn-skills.dev
Build automated AI workflows combining multiple models and services.
LeoYeAI/openclaw-master-skills
Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.
LeoYeAI/openclaw-master-skills
Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.
LeoYeAI/openclaw-master-skills
Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.
LeoYeAI/openclaw-master-skills
Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.
LeoYeAI/openclaw-master-skills
Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.
LeoYeAI/openclaw-master-skills
Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.
Categories
Persistent task queue system. An agent skill from LeoYeAI/openclaw-master-skills. Task Runner is an agent skill from LeoYeAI/openclaw-master-skills. Persistent task queue system.
Task Runner fits situations like: tasks that involve Scheduled and recurring tasks; tasks that involve Background jobs; tasks that involve Subagents.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill task-runner -a claude-code`. Or copy the skill folder (skills/autonomous-task-runner in LeoYeAI/openclaw-master-skills) into .claude/skills/task-runner in your project. Claude Code loads it when a task matches its description.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill task-runner -a codex`. Or copy the skill folder (skills/autonomous-task-runner in LeoYeAI/openclaw-master-skills) into .agents/skills/task-runner in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill task-runner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/task-runner, .gemini/skills/task-runner, .github/skills/task-runner and .opencode/skills/task-runner in your project.
SKILL.md names no scripts, command-line tools or credentials: Task Runner is instructions for the agent only.
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.
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.
Task Runner is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.1k tokens (SKILL.md is roughly 16k 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 7.7k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Task Runner: Cron (shibing624/agentica, 352 stars), Worker Development (ChatbotXIO/ChatbotX, 878 stars), Convex Crons (openclaw/clawhub, 9.5k stars) and Frappe Impl Scheduler (Impertio-Studio/Frappe_Claude_Skill_Package, 187 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,158 GitHub stars. The repository holds 1,215 skills in this directory. The repository was last updated on July 20, 2026.
Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.