用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/boldsoftware/shelley --skill schedule命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when the user wants to change Shelley itself — its code, UI, tools, or behavior beyond what hooks allow — or asks to rebase/upgrade a customized Shelley build.
Use when a task needs an external service credential (API key, database, OAuth service) this exe.dev VM doesn't have attached. Emits a clickable exe.dev connect link the user clicks to grant it. NEVER ask the user to paste a secret into chat.
Use when the user wants to customize Shelley by injecting behavior at lifecycle events. It documents Shelley's hooks.
基于 SOC 职业分类
正在显示 SKILL.md
| name | schedule |
| description | Use when a user requests a task to be done later or on a schedule. |
Use systemd user timer units. Unless the user explicitly asked to schedule something, have the user confirm.
If the task is obvious and straightforward, such as a bash command, you might schedule just the command. Otherwise, schedule a future Shelley conversation by calling shelley client chat.
Name shelley-calling units shelley-<name>.{service,timer}. The service ExecStart should invoke:
shelley client chat -p '<prompt>' -cwd '<working_directory>'
Each timer firing always creates a new conversation so that no conversation grows without bound.
The prompt baked into the service unit should concisely convey the overarching goals and context from the user, preferably in their own words, as well as the specific task being achieved by this scheduled invocation. The prompt must always include the originating conversation ID (from $SHELLEY_CONVERSATION_ID), so that new agent can refer to the originating conversation for additional context if needed.
You are responsible for ensuring that one-shot units will be cleaned up.