docx

DOCX creation, editing, and analysis

Overview

A .docx file is a ZIP archive containing XML files.

Generating Reports (Recommended for research reports)

For structured reports with cover page, TOC, tables, images, and references, use the pre-built template. The DOCX generator accepts the same JSON schema as the PDF generator, so one report_data.json can produce both formats.

Step 1: Copy the generator script

cp /builtin-skills/docx/scripts/generate_report.js ./generate_report.js

Step 2: Build report_data.json

Two phases: write section text files, then assemble into JSON.

Phase 1 — Write each section as a plain text file using write_file:

For each major section, read_file the relevant research data, then write_file the section content directly:

read_file("research_data/literature.md")           # refresh data in context
write_file("sections/sec_01_intro.txt", "...")      # write section content
write_file("sections/sec_02_mutations.txt", "...")   # next section
...

Each section file should be 1,000-2,000+ words with specific data, citations, and analysis.

NEVER write a Python script that contains section text as string literals. The section content goes directly into .txt files via write_file, not into Python code. Do NOT write scripts named "generate_sections", "create_content", "build_report" etc. that embed text in Python strings. If a sandbox script fails twice, switch to direct write_file calls.

Writing style — academic research report (CRITICAL):

• Write continuous flowing prose. Each paragraph: 8–10 sentences following the pattern: topic sentence → supporting evidence with specific data → analysis/comparison → transition to next point.
• Use in-text citations [1], [2] when referencing data. These render as blue superscript in the DOCX. Do NOT add a "References" list at the end of each chapter — all references go in ONE final references section.
• Synthesize across sources: "Study A [1] reported X, while Study B [2] found Y, suggesting that Z."
• Use academic connectives: "Furthermore", "In contrast", "These findings indicate", "Notably", "Taken together".
• NEVER use numbered-point structure (e.g. "1. Topic Title\n\nParagraph. 2. Topic Title\n\nParagraph."). Instead, use ## subheadings for structure and prose paragraphs for content. The template's renderText correctly renders ##/### as formatted subheadings.
• Bullet lists: max 5% of section, only for short enumerations (e.g. 4-5 drug names).