Menú
Use when a user requests a task to be done later or on a schedule.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when the user wants to customize Shelley by injecting behavior at lifecycle events. It documents Shelley's hooks.
Use when the user asks for a diagram, sketch, flowchart, architecture diagram, sequence diagram, mind map, or other visual explanation. Renders hand-drawn-style diagrams from Excalidraw JSON via the output_iframe tool.
Use to discover external services and APIs available on this exe.dev VM via network-edge-injected credentials and to discover VM metadata like owner email, VM tags, and default port.
Use when the user needs Node.js or npm installed, or is running a JS framework dev server (Next.js, Vite, webpack, etc.) on an exe.dev VM — especially if the browser logs 'WebSocket ... failed', or the dev server complains about cross-origin requests, allowedDevOrigins, or allowedHosts.
Use when the user references a previous conversation, asks you to continue earlier work, or you need to look up what was discussed before.
| 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.