// 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.
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.
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.
Retrieves papers the user browsed today, downloads PDFs, generates summaries, and returns an enriched list. Use when the user asks what papers they read today, wants a summary of today's papers, or asks about their recent reading activity.
| name | preserve-meaning |
| description | 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. |
Use this skill during and after rewriting.
Its purpose is simple: improve the writing without changing what the text actually says.
Use this skill whenever you rewrite user text, especially when the text contains:
You may change:
You may not change:
Before finalizing, ask:
If any answer is risky, revise again.
Rewrite for naturalness and stronger authorship, but preserve the original meaning exactly.
Do not add facts, examples, arguments, or stronger conclusions.
Keep names, numbers, constraints, and technical content intact.
After rewriting, compare the new version against the original for meaning drift.