// Use when the user asks to schedule recurring tasks, one-off reminders, timers, or cron-style jobs through the OpenSquilla cron tool.
Delegate coding tasks to Codex, Claude Code, or Pi agents via background process. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn in temp dir), (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit), reading code (use read tool), thread-bound ACP harness requests in chat (for example spawn/run Codex or Claude Code in a Discord thread; use sessions_spawn with runtime:"acp"), or any work in ~/clawd workspace (never spawn agents here). Prefer non-interactive CLI modes such as codex exec, claude --print, opencode run, or pi -p.
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory/**/*.md.
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
Multi-round research with explicit methodology, evidence tracking, and citation-tagged synthesis. Trigger on 'deep dive', 'research report', 'literature review', 'investigate X across sources', 'multi-round investigation'. Distinct from the `summarize` skill, which is a single-pass condensation; this skill maintains a state file across iterations, tracks coverage, and produces a long-form report with per-claim citations. Three execution stages: plan (scope into sub-questions), iterate (record evidence per round), compile (synthesize report). The skill itself does not fetch the web â it tells the host agent which fetches to perform via OpenSquilla's existing web tools, and records what comes back.
Read, edit, or create Microsoft Word `.docx` files. Trigger this skill whenever the user mentions a Word document, .docx file, contract, report, brief, memo, or asks to extract text, modify an existing doc, generate one from a brief, or audit tracked changes. Three execution paths: text-and-structure extraction, in-place edit-by-run (preserves styles), and create-from-scratch with python-docx. Falls back to OOXML unzip-and-patch for layout work python-docx cannot reach.
Render HTML (with CSS) to a PDF file. Trigger when the user wants to export a styled report, invoice, label, or any HTML/Jinja-rendered page to PDF. Uses WeasyPrint, which supports a meaningful subset of CSS Paged Media (page size, margins, headers/footers, page-break-before/after). Optional dependency â install via `pip install opensquilla[document-extras]` or `uv add weasyprint` because WeasyPrint pulls in native libraries (Pango, Cairo, fontconfig) that need OS-level packages.
| name | cron |
| description | Use when the user asks to schedule recurring tasks, one-off reminders, timers, or cron-style jobs through the OpenSquilla cron tool. |
| always | false |
| triggers | ["schedule","recurring","timer","cron","every","reminder","remind","ćé","ćŻĺé","ćŻ5ĺé","ćŻĺ¤Š","ĺŽćś"] |
| provenance | {"origin":"openclaw-derived","license":"MIT","upstream_url":"https://github.com/openclaw/openclaw","maintained_by":"OpenSquilla"} |
| metadata | {"opensquilla":{"requires_tools":["cron"]}} |
When the user asks to schedule something, set up a recurring task, create a timer, or create a reminder, use the cron tool.
The schedule argument is a structured object, not a string. Choose one shape and translate any natural language yourself before calling the tool â the tool will not parse free-form text and will reject flat strings with a structured error.
Three accepted schedule shapes:
{"kind": "cron", "expr": "<5-field POSIX cron>", "tz": "<optional IANA timezone>"}
Recurring on a calendar pattern. Example: {"kind": "cron", "expr": "0 9 * * 1-5", "tz": "Asia/Shanghai"} for weekdays at 09:00 Shanghai wall time.{"kind": "every", "every_seconds": <integer ⼠1>}
Recurring on a fixed sub-minute or odd interval. Example: {"kind": "every", "every_seconds": 30} for every 30 seconds.{"kind": "at", "at": "<ISO-8601 with timezone>"}
One-shot at an absolute time. The timestamp must include a timezone offset.Translation examples (do this in your own reasoning before calling the tool):
cron(action="add", schedule={"kind": "cron", "expr": "*/5 * * * *"}, task="ĺć°´", job_kind="system_event", session_target="main")cron(action="add", schedule={"kind": "every", "every_seconds": 30}, task="...", job_kind="agent_turn", session_target="isolated")cron(action="add", schedule={"kind": "at", "at": "<that ISO-8601>"}, task="...", job_kind="system_event", session_target="main")cron(action="add", schedule={"kind": "cron", "expr": "0 9 * * 1-5", "tz": "America/Los_Angeles"}, task="...")Other actions:
cron(action="list").cron(action="run", job_id="<job id>").cron(action="remove", job_id="<job id>").Cron expression format: minute hour day month weekday (e.g. 0 9 * * 1-5 = weekdays at 9am).