Docx

What it does

The source separates creating a new Word file from changing an existing document. It covers document structure, package-level edits and tools for reading or rendering the result. This is useful when a task involves headings, numbering, tables or revision markup that plain extracted text cannot represent faithfully.

Best for

Reports, letters and templates that need an editable Word deliverable, or focused changes to an existing document whose structure should be preserved. Supply the original file, the intended page size and any accepted style reference before generating a replacement.

Tradeoffs and requirements

A structurally valid package can still have poor pagination or broken visual relationships. Fonts and rendering engines can change line wrapping. Editing revision markup also requires more care than replacing visible text. Dependencies described as available in the source may need separate setup in another agent environment.

Unknown; inspect source requirements and supporting scripts.

Install from the source

Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code. Catalog ingestion never executes skill instructions or install scripts.

npx skills add https://github.com/anthropics/skills/tree/ca45fc496a3436251f191354091d557da31c15b5/skills/docx --skill docx

Review pinned skill folder ↗ · CLI documentation ↗

After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.

Safety & review signals

Static review only. This is not a security audit or a guarantee of safety.

SKILL.md text only; scripts, dependencies and runtime behavior not audited.

• Shell Or Package Install — review the source context.

Allowed tools declaration: Unknown. Runtime permissions and network behavior: Unknown.

AI Craft Pad Skill Score

86/100 · Metadata coverage 100% · Model 1.0

Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.

Documentation

100/100

100

Maintenance

100/100

100

License Clarity

100/100

100

Repository Health

85/100

85

Compatibility Evidence

80/100

80

Popularity

95/100

95

Originality

80/100

80

Static Safety

60/100

60

Supporting-file static inspection

Bounded source inspection, not a runtime security audit. This inspection does not execute code.

16 text files inspected at this exact repository snapshot. 44 files outside the inspection budget or type allowlist. Dependencies were not installed or independently audited.

• Network Client: 11 files — inspect context before use.
• Process Launch: 3 files — inspect context before use.
• File Write Or Delete: 9 files — inspect context before use.
• Credential Handling: 1 file — inspect context before use.

Absence of a pattern is not proof of safety. Permission needs and runtime behavior remain Unknown.

Suggested workflow

Choose creation or preservation of an existing package, make the requested changes, validate the package and render it. Use the PDF skill for the final fixed-layout version rather than treating a PDF export as an editable Word source.

How to judge the result

Open or render every page, inspect tables and headers, and verify that intended edits appear in the accepted text or tracked-change view as appropriate. Check the bundled license before reusing supporting material.