// 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.
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.
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.
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 | align-target-style |
| description | 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. |
Use this skill after diagnosis and before final rewriting when the user provides an explicit style requirement.
This skill turns vague style requests into usable editing constraints.
Use this skill when the user says things like:
Convert the requested style into a small style card.
The style card should capture:
Do not use this skill when no style is given.
The agent default remains:
Translate the user's style request into a compact style card for rewriting.
Specify tone, formality, rhythm, directness, and audience fit.
Then apply that style while making the prose sound authored and natural.
Preserve meaning and avoid exaggerated mimicry.