Schedule
TinyAGI/tinyagi
Create, list, and delete scheduled tasks (recurring or one-time) that send messages to agents.
Choose and use GSV delegation, subprocess, IPC, scheduling, and cron workflows.
$ npx skills add deathbyknowledge/gsv --skill process-orchestration -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install deathbyknowledge/gsv process-orchestration --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/deathbyknowledge/gsv.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/process-orchestration .claude/skills/process-orchestration && 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 "process-orchestration" agent skill from https://github.com/deathbyknowledge/gsv/tree/main/skills/process-orchestration into .claude/skills/process-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "process-orchestration", 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/deathbyknowledge/gsv/tree/main/skills/process-orchestrationType 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 deathbyknowledge/gsv --skill process-orchestration -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install deathbyknowledge/gsv process-orchestration --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deathbyknowledge/gsv.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/process-orchestration .agents/skills/process-orchestration && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "process-orchestration" agent skill from https://github.com/deathbyknowledge/gsv/tree/main/skills/process-orchestration into .agents/skills/process-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "process-orchestration", 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 deathbyknowledge/gsv --skill process-orchestration -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install deathbyknowledge/gsv process-orchestration --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deathbyknowledge/gsv.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/process-orchestration .cursor/skills/process-orchestration && 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 "process-orchestration" agent skill from https://github.com/deathbyknowledge/gsv/tree/main/skills/process-orchestration into .cursor/skills/process-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "process-orchestration", 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/deathbyknowledge/gsv.git --path skills/process-orchestration--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 deathbyknowledge/gsv --skill process-orchestration -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install deathbyknowledge/gsv process-orchestration --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deathbyknowledge/gsv.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/process-orchestration .gemini/skills/process-orchestration && 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 "process-orchestration" agent skill from https://github.com/deathbyknowledge/gsv/tree/main/skills/process-orchestration into .gemini/skills/process-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "process-orchestration", 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 deathbyknowledge/gsv process-orchestrationInstalls 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 deathbyknowledge/gsv --skill process-orchestration -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/deathbyknowledge/gsv.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/process-orchestration .github/skills/process-orchestration && 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 "process-orchestration" agent skill from https://github.com/deathbyknowledge/gsv/tree/main/skills/process-orchestration into .github/skills/process-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "process-orchestration", 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 deathbyknowledge/gsv --skill process-orchestration -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install deathbyknowledge/gsv process-orchestration --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deathbyknowledge/gsv.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/process-orchestration .opencode/skills/process-orchestration && 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 "process-orchestration" agent skill from https://github.com/deathbyknowledge/gsv/tree/main/skills/process-orchestration into .opencode/skills/process-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "process-orchestration", 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.
process-orchestrationChoose and use GSV delegation, subprocess, IPC, scheduling, and cron workflows.
Process Orchestration is an agent skill from deathbyknowledge/gsv. Choose and use GSV delegation, subprocess, IPC, scheduling, and cron workflows. Use when work should run in another process or at a later or recurring time.
Its SKILL.md is about 1.2k 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 Scheduled and recurring tasks. The repository describes itself as: Personal AI computer / distributed OS across all your devices. The licence is MIT.
Read from SKILL.md and the folder at commit d9c5746. 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 bash and cron).
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.
Process Orchestration loads about 1.2k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 508 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 deathbyknowledge/gsv at commit d9c5746, republished under its MIT licence (© deathbyknowledge). 508 words, ~1,173 tokens.
.claude/skills/process-orchestration/SKILL.md (or your agent's skills folder).Run every command in this guide through Shell on target gsv. Keep CodeMode for scripted tool workflows inside the current process; it is not the delegation mechanism.
proc delegate for bounded work in a new child process when its result must return to the current process.proc call for bounded work in an existing process.proc send to send an asynchronous message to an existing process when no reply is required.proc spawn to start a new fire-and-forget process. Its answer remains in the child process history.sched add --here when a future or recurring prompt should re-enter the current process conversation.sched add --to for future or recurring direct text delivery that must not run an agent.crontab for recurring shell commands or true fire-and-forget background automation.Name the work so the user can recognize its subject and purpose without opening the process. Use ordinary words and spaces.
Ship selects the Crew account named in ~/context.d/10-delegation.md for general delegated work. Replace ACCOUNT with that name or another owned account suited to the task:
proc delegate --as ACCOUNT --label 'Compare backup options' --check-after 10m 'Compare backup options and recommend one.'Delegation creates a non-interactive child, returns an in-progress task handle immediately, and sends its result back as a process event. The check interval is a supervision checkpoint, not a work deadline. It requires a process-backed caller, so never put proc delegate in a crontab or top-level scheduled shell command.
Without --as, a child inherits the parent's identity and account context. List the accounts available for running processes when choosing a different identity:
proc agents
proc delegate --as ACCOUNT --label 'Review hosting costs' 'Review hosting costs and identify savings.'Use the other process commands according to their reply contract:
proc spawn --label "Check last night's backup" "Verify that last night's backup completed successfully."
proc call <pid> --timeout 60s 'Complete this bounded task.'
proc send <pid> 'Handle this without replying.'Pass --non-interactive to proc spawn for scheduled background work. Inspect a child process when necessary:
proc history --pid <pid> --tail --limit 20Add --full or --json only when untruncated content is needed.
Use --here when each firing should run the current process:
sched add --here --name <name> \
(--every <duration> | --cron <expr> [--timezone <zone>] | --after <duration> | --at <timestamp>) \
--message <prompt> [--conversation <id>]When created during an adapter run, --here preserves the current authorized reply destination so the future final answer returns there. Otherwise, the answer remains in the GSV process conversation. The schedule stays bound to that process id; recreate it after killing the process.
Use --to for direct delivery without an agent run:
sched add --to <destination> --name <name> \
(--every <duration> | --cron <expr> [--timezone <zone>] | --after <duration> | --at <timestamp>) \
--message <text>Choose exactly one time expression. An --at value must be a future ISO timestamp with Z or an explicit numeric UTC offset.
Inspect and control schedules with:
sched list
sched list --all
sched run <id> [--force]
sched enable <id>
sched disable <id>
sched remove <id>sched list --all includes disabled schedules, not other users' schedules. A successful process-event firing means the event was admitted, not that the model turn or reply completed.
Use crontab -l to inspect the current table and crontab FILE to install one. A per-user table is also available at /var/spool/cron/<username>. Each job is a five-field cron expression followed by a shell command:
0 9 * * * proc spawn --non-interactive --label 'Refresh search index' "Refresh the search index."The crontab file is desired state, so reinstalling it regenerates its Kernel schedule ids. A schedule status of ok for proc spawn means dispatch and spawn acceptance, not child completion or delivery. The answer remains in the child process history.
Use man proc, man sched, man crontab, or each command's --help output for exact syntax.
© deathbyknowledge, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/process-orchestration of deathbyknowledge/gsv.
Open the folder on GitHubat commit d9c5746
Process Orchestration 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 |
|---|---|---|---|---|---|---|
| Process Orchestration this skilldeathbyknowledge/gsv | 125 | — | ~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 | |
| Wp Wpcli And OpsAutomattic/agent-skills | 211 | 2 repos | ~988 | Automated safety check: Pass | None | |
| Ohdearohdearapp/ohdear-cli | 141 | — | ~1.1k | Automated safety check: Pass | MIT |
TinyAGI/tinyagi
Create, list, and delete scheduled tasks (recurring or one-time) that send messages to agents.
TinyAGI/tinyagi
Send a proactive message to a paired user via their channel (Discord, Telegram, or WhatsApp).
czl9707/build-your-own-openclaw
Create, list, and delete scheduled cron jobs. An agent skill from czl9707/build-your-own-openclaw.
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…
ohdearapp/ohdear-cli
Manage Oh Dear website monitoring using the ohdear CLI. An agent skill from ohdearapp/ohdear-cli.
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.
deathbyknowledge/gsv
Retrieve and maintain the memory. An agent skill from deathbyknowledge/gsv.
deathbyknowledge/gsv
Create or revise reusable GSV agent workflows under skills.d.
deathbyknowledge/gsv
Consult the GSV Manual before saying GSV cannot do something, and for questions about its operating model, workflows, settings, devices, agents, automation, integrations, filesystem, desktop, shell…
deathbyknowledge/gsv
Use a paired browser: the user's signed-in profile, reaching any site they are logged into (calendar, mail, dashboards) with no integration.
deathbyknowledge/gsv
Read and analyze images on GSV or connected targets with img2txt.
Categories
Choose and use GSV delegation, subprocess, IPC, scheduling, and cron workflows. Process Orchestration is an agent skill from deathbyknowledge/gsv. Choose and use GSV delegation, subprocess, IPC, scheduling, and cron workflows.
Process Orchestration fits situations like: work should run in another process; tasks that involve Scheduled and recurring tasks.
Run `npx skills add deathbyknowledge/gsv --skill process-orchestration -a claude-code`. Or copy the skill folder (skills/process-orchestration in deathbyknowledge/gsv) into .claude/skills/process-orchestration in your project. Claude Code loads it when a task matches its description.
Run `npx skills add deathbyknowledge/gsv --skill process-orchestration -a codex`. Or copy the skill folder (skills/process-orchestration in deathbyknowledge/gsv) into .agents/skills/process-orchestration 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 deathbyknowledge/gsv --skill process-orchestration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/process-orchestration, .gemini/skills/process-orchestration, .github/skills/process-orchestration and .opencode/skills/process-orchestration in your project.
SKILL.md names no scripts, command-line tools or credentials: Process Orchestration 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.
Process Orchestration is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Process Orchestration: 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 Wp Wpcli And Ops (Automattic/agent-skills, 211 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
deathbyknowledge (a GitHub user) maintains it in deathbyknowledge/gsv, which has 125 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 6, 2026.
Source: deathbyknowledge/gsv on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.