# Create and Format Word Documents

Manual DOCX formatting is slow and easy to break. This skill provides OpenXML workflows for creating, editing, validating, and templating Word documents.

## Install

```bash
npx skillstore add fokkyp/docx-toolkit
```

## Metadata

- Status: approved
- Slug: fokkyp-docx-toolkit
- Version: 1.0.0
- Author version: 1.0.0
- Skillstore revision: r1
- Version status: valid
- Tree hash: 0177063790e26cddb1514055b304c0ea04a2823dc260137fbb26c08b367f35f2
- Author: Fokkyp
- GitHub username: Fokkyp
- License: MIT
- Repository: https://github.com/Fokkyp/SoftwareCopyright-Skill/tree/main/software-copyright-materials/vendor/docx-toolkit
- Ref: 30c73eac2afe762f6aa9c4553158769369d47351
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network, external\_commands, filesystem
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/fokkyp-docx-toolkit
- Manifest: https://skillstore.pages.dev/api/skills/fokkyp-docx-toolkit/manifest

## Capabilities

- Creates new DOCX documents such as reports, letters, memos, and academic documents.
- Edits existing DOCX files through text replacement, placeholder filling, table updates, and metadata changes.
- Applies template styles, numbering, themes, section properties, headers, and footers to source documents.
- Runs OpenXML validation, business-rule checks, run merging, order repair, and document diffs.
- Previews DOCX text and converts legacy DOC files when optional tools are installed.
- Provides detailed OpenXML samples for tables, images, lists, fields, comments, track changes, and typography.

## Use Cases

- Generate Client Documents: Create polished reports, proposals, letters, and memos with consistent Word structure and page settings.
- Fill Existing Templates: Replace placeholders, update tables, and modify metadata in supplied DOCX files without rebuilding the document manually.
- Standardize Document Formatting: Apply approved styles, headers, footers, numbering, and validation checks to documents that must match a template.

## Prompt Templates

### Create a Basic Report

```
Create a DOCX report titled "Quarterly Project Update" with sections for summary, milestones, risks, and next steps. Use a professional report style.
```

### Fill a Form Document

```
Fill the placeholders in this DOCX template using the supplied client details. Preserve the original layout and show a brief summary of changes.
```

### Apply a Formatting Template

```
Reformat the source DOCX to match the attached template. Preserve all source content, apply template styles, then validate the result.
```

### Build a Complex Word Package

```
Create a multi-section DOCX with a cover page, table of contents placeholder, styled headings, tables, images, headers, footers, and validation checks.
```

## Limitations

- Requires .NET SDK 8 or newer, and optional tools such as pandoc or LibreOffice for some workflows.
- Setup scripts may install packages, download dependencies, and change local configuration.
- Some Word fields, such as table of contents entries, may still need refresh in Microsoft Word.
- Complex templates can require custom C\# work and careful validation before delivery.

## Best Practices

- Run environment checks before document work, and review any setup script before allowing installation changes.
- Validate every generated or modified DOCX before delivering it to the user.
- Use the closest sample or scenario guide instead of inventing OpenXML element order or formatting values.

## Anti Patterns

- Do not run setup scripts automatically in a sensitive environment without reviewing package installs and configuration changes.
- Do not edit raw DOCX XML manually when the OpenXML SDK helpers can preserve schema order.
- Do not apply a template without checking that source content, section breaks, headers, and footers were preserved.

## Security Audit

- Audited at: 2026-07-21T07:31:57.216\+00:00
- Summary: Most static matches are false positives caused by OpenXML markup, documentation, and ordinary shell syntax. Confirmed risks are concentrated in the agent-directed setup workflow: it runs elevated package installations, downloads and executes an installer from /tmp without integrity verification, and persists user configuration changes. The documented advanced path also permits generated custom C\# execution. Static review was capped at 400/806 representative findings; omitted static matches are unconfirmed, so automatic publishing stays disabled until manual review.

## Stats

- Views: 127
- Downloads: 6
- Favorites: 0
- Popularity score: 0