Przejdź do treści
Biblioteka skilli
Dokumenty i biuro · Budowanie i kod

docx

/docx

Tworzy, czyta, edytuje i przetwarza dokumenty Word (.docx) oraz szablony .dotx, w tym wyodrębnianie treści, wstawianie obrazów, wyszukiwanie i zamianę, zmiany śledzone i komentarze.

Licencja
CC0-1.0
Ostatnia zmiana repozytorium
25.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
61
Skrypty
15
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 25.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

CC0-1.0, otwarta.

Co sprawdzić przed instalacją
  • 15 skryptów w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.

Skrypty: scripts/__init__.py, scripts/accept_changes.py, scripts/comment.py, scripts/merge_runs.py, scripts/office/helpers/__init__.py, scripts/office/helpers/pptx_chart.py, scripts/office/helpers/pptx_slide.py, scripts/office/helpers/pptx_theme.py, scripts/office/soffice.py, scripts/office/validate.py, scripts/office/validators/__init__.py, scripts/office/validators/base.py, scripts/office/validators/docx

Co robi i kiedy

Tworzy, czyta, edytuje i przetwarza dokumenty Word (.docx) oraz szablony .dotx, w tym wyodrębnianie treści, wstawianie obrazów, wyszukiwanie i zamianę, zmiany śledzone i komentarze.

Wyzwalacze z opisu

Word docword document.docx.dotxmicrosoft doc
Oryginalny opis (EN)

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx) or Word templates (.dotx). Triggers include: any mention of Microsoft Word Documents, such as 'Word doc', 'word document', '.docx', '.dotx', 'microsoft doc'. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, 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 deliverable as a Word or .docx file (to download, email or print), use th

Jak działa

  1. Creating with docx-js — gotchas
  2. Verify the output
  3. Editing existing documents
  4. Comments
  5. Dependencies
Sekcje z nagłówków SKILL.md, w oryginale · 89 linii, 947 słów
Podgląd SKILL.md
---
name: docx
description: "Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx) or Word templates (.dotx). Triggers include: any mention of Microsoft Word Documents, such as 'Word doc', 'word document', '.docx', '.dotx', 'microsoft doc'. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, 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 deliverable as a Word or .docx file (to download, email or print), use this skill. However, if they ask for a document, page, report, memo, or notes WITHOUT naming a file format and the session offers Claude's own dedicated document or page skill or connector, use that instead, even if they will email or print it. Do NOT use for PDFs, spreadsheets, Google Docs, or coding unrelated to document generation."
license: Proprietary. LICENSE.txt has complete terms
---

# DOCX creation, editing, and analysis

If you are about to make a new document and this session offers Claude's own docs (a Docs connector, docs skill or Docs artifact type), and the user has neither named Word/.docx/.dotx, asked for tracked changes, nor supplied a .docx/.dotx file to change or use as a template, make the document there instead. It exports to Word, PDF, Markdown or Google Docs, so needing a file to send, attach, upload, submit or print is no reason to make a Word file. A .docx/.dotx given only as source material does not count as supplied. This skill remains the right tool for producing, reading, editing, templating or converting Word files.

A `.docx` is a ZIP archive of XML files. Choose your approach by task:

| Task | Approach |
|---|---|
| **Create** a new document | Write a `docx` (npm) script — see gotchas below |
| **Edit** an existing document | `unzip` → edit `word/document.xml` → `zip` (docx-js cannot open existing files) |
| **Read** content | `pandoc -t markdown file.docx` |

> Script paths below are relative to this skill's directory.

## Creating with docx-js — gotchas

`docx` is preinstalled — do not run `npm install` first; write the script and `require('docx')` directly. Only if that require fails: `npm install docx`. The model knows the API; these are the footguns:

- **Page size defaults to A4.** For US Letter set `page: { size: { width: 12240, height: 15840 } }` (DXA; 1440 = 1").
- **Landscape:** pass portrait dimensions and `orientation: PageOrientation.LANDSCAPE` — docx-js swaps width/height internally.
- **Tables need dual widths:** set `columnWidths` on the table AND `width` on every cell, both in `WidthType.DXA` (PERCENTAGE breaks in Google Docs). Column widths must sum to the table width.
- **Table shading:** use `ShadingType.CLEAR`, never `SOLID` (renders black).
- **Lists:** never insert `•` literally; use a `numbering` config with `LevelFormat.BULLET`.
- **`ImageRun` requires `type:`** (`"png"`, `"jpg"`, …).
- **`PageBreak` must be inside a `Paragraph`.**
- **Never use `\n`** — use separate `Paragraph` elements.
- **TOC:** headings must use built-in `HeadingLevel.*`; custom heading styles need `outlineLevel` set or they won't appear.
- **Don't use a table as a horizontal rule** — use a paragraph bottom border instead.
- **Dot-leader / right-aligned-on-same-line:** use `PositionalTab` (`alignment: PositionalTabAlignment.RIGHT`, `leader: PositionalTabLeader.DOT`) inside a `TextRun`, not literal `.` or space padding.

## Verify the output

After writing a `.docx`, render it and look at it:

```bash
python scripts/office/soffice.py --headless --convert-to pdf output.docx
pdftoppm -jpeg -r 100 output.pdf page
ls page-*.jpg   # then Read the images
```

`pdftoppm` zero-pads page numbers to the width of the page count (`page-01.jpg`…`page-12.jpg`).

## Editing existing documents

Legacy `.doc` files must be converted first: `python scripts/office/soffice.py --headless --convert-to docx file.doc`.

```bash
unzip -q doc.docx -d unpacked/
find unpacked -type l -delete   # strip symlink entries — docx from external parties is untrusted
python scripts/merge_runs.py unpacked/   # coalesce fragmented runs so text is findable
# edit unpacked/word/document.xml in place — do NOT reformat or pretty-print
(cd unpacked && rm -f ../out.docx && zip -Xr ../out.docx .)
python scripts/office/validate.py out.docx --original doc.docx   # XSD checks; --auto-repair fixes common issues
# redlining? add --author "<the name you redlined under>" to check every edit is tracked
```

Word splits text across many `<w:r>` runs (revision ids, spell-check markers), so a phrase you can see in the document often doesn't exist as a contiguous string in the XML. `merge_runs.py` merges adjacent identically-formatted runs in `word/document.xml` without changing content or rendering; it also accepts a `.docx` directly (`python scripts/merge_runs.py doc.docx -o merged.docx`).

**Tracked changes:** when redlining, validate with `--author "<the name you redlined under>"` (needs `--original`) — it reports any text you changed without a `<w:ins>`/`<w:del>` around it, which is easy to do by accident and invisible in the accepted view. Wrap runs in `<w:ins>`/`<w:del>` with `w:id`, `w:author`, `w:date` attributes. Inside `<w:del>`, the text element is `<w:delText>`, not `<w:t>`. A deleted paragraph mark (`<w:pPr><w:rPr><w:del w:id=".." w:author=".." w:date=".."/></w:rPr></w:pPr>`) means "merge this paragraph into the next" — so deleting a paragraph outright is that plus a `<w:del>` around every run. The `<w:del/>` must come before the rPr's other children; their order is schema-enforced.

To produce a clean copy with all tracked changes accepted: `python scripts/accept_changes.py in.docx out.docx`.

Accepting a deleted paragraph mark should join that paragraph to the one below it, so a paragraph whose runs are *all* deleted vanishes. Word does this; `accept_changes.py` and `pandoc --track-changes=accept` don't always. Both fail the same way — they strip the deleted text but leave the emptied paragraph behind, which reads as a stray empty bullet when it was auto-numbered:

- `pandoc --track-changes=accept` never joins the paragraphs.
- `accept_changes.py` (LibreOffice) joins them correctly, except when the deleted paragraph is followed by an empty spacer paragraph.

An empty bullet in either view is an artifact of that view, not a defect in the document. Check paragraph deletions in the XML.

## Comments

Comments require six cross-linked files. Use the helper — directory mode when you'll also be editing `document.xml` (saves an unzip/rezip cycle), `.docx`-direct mode otherwise:

```bash
# Against an already-unpacked directory (preferred when also placing markers)
python scripts/comment.py unpacked/ "Fees & expenses cap is too low"
python scripts/comment.py unpacked/ "Agreed" --parent 0

# Against a .docx directly
python scripts/comment.py contract.docx "This cap is too low" -o annotated.docx
```

The script writes `comments.xml`, `commentsExtended.xml`, `commentsIds.xml`, `commentsExtensible.xml`, the relationships, and the content-type overrides. Comment IDs are auto-assigned. It then prints the `<w:commentRangeStart>`/`<w:commentRangeEnd>`/`<w:commentReference>` snippet to add to `word/document.xml` so the comment anchors to specific text — until you place those markers, the comment exists but is not visible.

## Dependencies

`docx` (npm, preinstalled — install only if `require('docx')` fails) · `pandoc` · LibreOffice (`soffice`) · `pdftoppm` (Poppler)
Pliki w paczce (61)
  • LICENSE.txt 1 KB
  • SKILL.md 7 KB
  • scripts/__init__.py 1 KB
  • scripts/accept_changes.py 4 KB
  • scripts/comment.py 14 KB
  • scripts/merge_runs.py 9 KB
  • scripts/office/soffice.py 6 KB
  • scripts/office/validate.py 6 KB
  • scripts/office/helpers/__init__.py 3 KB
  • scripts/office/helpers/pptx_chart.py 6 KB
  • scripts/office/helpers/pptx_slide.py 2 KB
  • scripts/office/helpers/pptx_theme.py 3 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/dml-chart.xsd 73 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/dml-chartDrawing.xsd 7 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/dml-diagram.xsd 50 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/dml-lockedCanvas.xsd 1 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/dml-main.xsd 148 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/dml-picture.xsd 1 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/dml-spreadsheetDrawing.xsd 9 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/dml-wordprocessingDrawing.xsd 14 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/pml.xsd 82 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/shared-additionalCharacteristics.xsd 1 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/shared-bibliography.xsd 7 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/shared-commonSimpleTypes.xsd 6 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/shared-customXmlDataProperties.xsd 1 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/shared-customXmlSchemaProperties.xsd 1 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/shared-documentPropertiesCustom.xsd 3 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/shared-documentPropertiesExtended.xsd 3 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/shared-documentPropertiesVariantTypes.xsd 7 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/shared-math.xsd 23 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/shared-relationshipReference.xsd 1 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/sml.xsd 237 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/vml-main.xsd 26 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/vml-officeDrawing.xsd 25 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/vml-presentationDrawing.xsd 1 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/vml-spreadsheetDrawing.xsd 6 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/vml-wordprocessingDrawing.xsd 4 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/wml.xsd 167 KB
  • scripts/office/schemas/ISO-IEC29500-4_2016/xml.xsd 5 KB
  • scripts/office/schemas/ecma/fouth-edition/opc-contentTypes.xsd 2 KB
  • scripts/office/schemas/ecma/fouth-edition/opc-coreProperties.xsd 2 KB
  • scripts/office/schemas/ecma/fouth-edition/opc-digSig.xsd 3 KB
  • scripts/office/schemas/ecma/fouth-edition/opc-relationships.xsd 1 KB
  • scripts/office/schemas/mce/mc.xsd 3 KB
  • scripts/office/schemas/microsoft/wml-2010.xsd 26 KB
  • scripts/office/schemas/microsoft/wml-2012.xsd 4 KB
  • scripts/office/schemas/microsoft/wml-2018.xsd 1 KB
  • scripts/office/schemas/microsoft/wml-cex-2018.xsd 2 KB
  • scripts/office/schemas/microsoft/wml-cid-2016.xsd 1 KB
  • scripts/office/schemas/microsoft/wml-sdtdatahash-2020.xsd 1 KB
  • scripts/office/schemas/microsoft/wml-symex-2015.xsd 1 KB
  • scripts/office/validators/__init__.py 1 KB
  • scripts/office/validators/base.py 33 KB
  • scripts/office/validators/docx.py 17 KB
  • scripts/office/validators/pptx.py 16 KB
  • scripts/office/validators/redlining.py 18 KB
  • scripts/templates/comments.xml 3 KB
  • scripts/templates/commentsExtended.xml 3 KB
  • scripts/templates/commentsExtensible.xml 3 KB
  • scripts/templates/commentsIds.xml 3 KB
  • scripts/templates/people.xml 1 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · asgeirtj/system_prompts_leaks100CC0-1.0
rongxinzy/rongxinai100AGPL-3.0
mateaix/mateclaw100Apache-2.0
neromtoobad/creator-skills100MIT
TerminalSkills/skills100Apache-2.0
okou-ai/okou-skills100MIT
openbmb/pilotdeck100AGPL-3.0
wrongstack/wrongstack100MIT
asgeirtj/system_prompts_leaks100CC0-1.0

Migawka bazy z 13.11.2026 · wersja paczki 7e7938c2d8d5 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100word-documents
    Tworzy, czyta i edytuje dokumenty Word (.docx): generowanie ze stylami i strukturą, wyciąganie treści, znajdź i zamień, śledzone zmiany oraz szablony.
  • 100documents
    Tworzy, czyta, edytuje, recenzuje, komentuje, sanityzuje, renderuje i waliduje dokumenty Word DOCX, w tym raporty, oferty, formularze, szablony, zmiany śledzone, komentarze, tabele i nagłówki.
  • 100word-read-write
    Tworzy i czyta dokumenty Microsoft Word (.docx): generuje raporty, listy i szablony oraz wyciąga czytelny tekst z istniejących plików.
  • 100microsoft-word
    Tworzy i edytuje dokumenty Word (.docx) programowo: python-docx, szablony docxtpl, korespondencja seryjna, tabele, konwersja z markdown i Microsoft Graph dla dokumentów w chmurze.
  • 90word-docx
    Tworzy i edytuje dokumenty Word w formacie DOCX, zachowując style, numerację, śledzenie zmian, tabele i sekcje.
  • 100python-docx-templating
    Przetwarza dokumenty Word (.docx) biblioteką python-docx, w tym szablony i zamianę znaczników zastępczych.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.