Agent skill

Process Orchestration

by deathbyknowledge in deathbyknowledge/gsv

Choose and use GSV delegation, subprocess, IPC, scheduling, and cron workflows.

MITAuto-check passedProductivity & Automation

Install Process Orchestration

skills CLI
$ npx skills add deathbyknowledge/gsv --skill process-orchestration -a claude-code

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

GitHub CLI
$ gh skill install deathbyknowledge/gsv process-orchestration --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/deathbyknowledge/gsv.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/process-orchestration .claude/skills/process-orchestration && 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
process-orchestration
GitHub stars
125
Token cost
~1.2k tokens
SKILL.md length
508 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Choose and use GSV delegation, subprocess, IPC, scheduling, and cron workflows.

  • Work should run in another process
  • SKILL.md covers Choose the Mechanism, Delegate or Start a Process, Schedule Work and Schedule Shell Commands
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tasks that involve Scheduled and recurring tasks

What it does

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.

When your agent uses it

  • Work should run in another process
  • Tasks that involve Scheduled and recurring tasks

Example prompts

  • “/process-orchestration”

What it can do on your machine

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

    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

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.

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

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 deathbyknowledge/gsv at commit d9c5746, republished under its MIT licence (© deathbyknowledge). 508 words, ~1,173 tokens.

Download SKILL.mdSave it as .claude/skills/process-orchestration/SKILL.md (or your agent's skills folder).
name
process-orchestration
description
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.

Process Orchestration

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.

Choose the Mechanism

  • Use proc delegate for bounded work in a new child process when its result must return to the current process.
  • Use proc call for bounded work in an existing process.
  • Use proc send to send an asynchronous message to an existing process when no reply is required.
  • Use proc spawn to start a new fire-and-forget process. Its answer remains in the child process history.
  • Use sched add --here when a future or recurring prompt should re-enter the current process conversation.
  • Use sched add --to for future or recurring direct text delivery that must not run an agent.
  • Use crontab for recurring shell commands or true fire-and-forget background automation.

Delegate or Start a Process

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:

bash
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:

bash
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:

bash
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:

bash
proc history --pid <pid> --tail --limit 20

Add --full or --json only when untruncated content is needed.

Show full SKILL.md (210 more words)Show less

Schedule Work

Use --here when each firing should run the current process:

bash
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:

bash
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:

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

Schedule Shell Commands

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:

cron
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

Files

Just SKILL.md in skills/process-orchestration of deathbyknowledge/gsv.

Open the folder on GitHubat commit d9c5746

Compare with similar skills

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.

Process Orchestration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Process Orchestration this skilldeathbyknowledge/gsv125—~1.2kAutomated safety check: PassMIT
ScheduleTinyAGI/tinyagi3.6k—~1.4kAutomated safety check: PassMIT
Send User MessageTinyAGI/tinyagi3.6k—~829Automated 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

Similar skills

  • Schedule

    TinyAGI/tinyagi

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

    3.6k GitHub stars~1.4k tokensUpdated 6 mo ago
    Productivity & AutomationAuto-check passed
  • 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
    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

More from deathbyknowledge/gsv

  • Memory

    deathbyknowledge/gsv

    Retrieve and maintain the memory. An agent skill from deathbyknowledge/gsv.

    125 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed
  • Skill Authoring

    deathbyknowledge/gsv

    Create or revise reusable GSV agent workflows under skills.d.

    125 GitHub stars~508 tokensUpdated yesterday
    Auto-check passed
  • Gsv Manual

    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…

    125 GitHub stars~243 tokensUpdated yesterday
    Auto-check passed
  • Browser Target

    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.

    125 GitHub stars~3.1k tokensUpdated yesterday
    Auto-check: warnings
  • Image Reading

    deathbyknowledge/gsv

    Read and analyze images on GSV or connected targets with img2txt.

    125 GitHub stars~343 tokensUpdated yesterday
    Auto-check passed

Questions about Process Orchestration

What does Process Orchestration do?

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.

When should I use Process Orchestration?

Process Orchestration fits situations like: work should run in another process; tasks that involve Scheduled and recurring tasks.

How do I install Process Orchestration in Claude Code?

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.

How do I install Process Orchestration in Codex?

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.

Can I use Process Orchestration 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 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.

What does Process Orchestration need to run?

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

Does Process Orchestration 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 Process Orchestration 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 Process Orchestration use?

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.

How many tokens does Process Orchestration use?

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.

What are the alternatives to Process Orchestration?

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.

Who maintains Process Orchestration?

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.