CLI and agent skill
The CLI manages schedules through the Space API. The orpheus-space skill tells the agent how to identify the requester, select their schedules and clarify the repeat rule.
Installation
Installation in a Linux Codex sandbox. For arm64, replace arch=amd64 with arch=arm64. For another agent, use its skills directory. The commands download the CLI and skill from one Space release, verify SHA256 and preserve references/.
set -eu
version=v0.13.0
arch=amd64
release="https://github.com/orpheus-agents/orpheus-space/releases/download/$version"
for file in "orpheus-space_${version}_linux_${arch}.tar.gz" "orpheus-space_${version}_skill.tar.gz" checksums.txt; do
curl -fsSLO "$release/$file"
done
sha256sum --check --ignore-missing checksums.txt
mkdir -p "$HOME/.local/bin" "$HOME/.agents/skills"
tar -xzf "orpheus-space_${version}_linux_${arch}.tar.gz" -C "$HOME/.local/bin"
tar -xzf "orpheus-space_${version}_skill.tar.gz" -C "$HOME/.agents/skills"
export PATH="$HOME/.local/bin:$PATH"
orpheus-space --versionInclude them in the sandbox template so new sessions can use them. Supply the CLI environment variables to the agent:
ORPHEUS_SPACE_HOST=https://space.example.com
ORPHEUS_SPACE_API_KEY=<space-api-key>Use a key from Space's PUBLIC_API_KEYS. The host has no /api/v1 suffix. Define a service with both ENV names, supply their values to the Orpheus worker and select the service in the workflow or session. This grants the agent the API key's full schedule permissions. Select it only when the task needs to manage schedules.
Verify
orpheus-space services --json
orpheus-space profiles --json
orpheus-space templates --json
orpheus-space schedule list --owner-email alice@example.com --jsonThe skill identifies the requester from verified connector metadata and handles only their schedules. Without verified email, it must not guess the owner. These are agent instructions, not restrictions on the shared API. See commands, retries and schedule selection.
Inside a scheduled run, Space supplies the owner identity for managing only that originating schedule. See scheduled-run identity. Shared schedules provide no owner identity for this skill workflow.