Menu
Schedule and manage recurring or one-time jobs for main/project agents.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | cron |
| description | Schedule and manage recurring or one-time jobs for main/project agents. |
Use the cron tool to create, list, remove, enable/disable, and run scheduled jobs.
add: create a joblist: show jobsremove: delete a job by idenable: enable or disable by idrun: run a job nowDaily at 8:00:
cron(action="add", message="Report yesterday's progress", cron_expr="0 8 * * *")
Every 30 minutes:
cron(action="add", message="Check project status", every_seconds=1800)
Target a student/project agent:
cron(action="add", target="proj:project-id", message="Summarize blockers", cron_expr="0 9 * * 1-5")
One-time reminder:
cron(action="add", message="Prepare meeting notes", at="2026-03-10T14:00:00")
target is omitted, default is main.add, provide exactly one of: every_seconds, cron_expr, at.tz can be used only with cron_expr.Use the ACPX CLI through DrClaw's existing exec/long_exec tools to run Codex in the current project workspace.
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
Convert a user style request into concrete rewrite constraints and apply that style during de-flavoring. Use when the user specifies a target tone, audience, or writing persona.
Diagnose formulaic writing patterns and authorial gaps before rewriting. Use when text feels generic, over-smoothed, abstract, or structurally mechanical and you need a targeted edit plan.
Guard against meaning drift during de-flavor rewrites. Use when rewriting text to sound more natural without adding facts, changing claims, or losing important constraints.
Rebuild specificity, texture, and authorial judgment in a rewrite without inventing facts. Use when text feels abstract, generic, over-smoothed, or full of empty framing.