DOCX TO HTML CONVERTER

Use this skill whenever the user has a DOCX file (.docx) and wants to convert, read, view, extract content from, or process it in any way — including summari...

Security Scan

The skill appears to implement a straightforward DOCX→HTML converter, but the package metadata and runtime requirements are inconsistent with the registry declarations (missing required binaries/install steps), so review and sandboxing are recommended before use.

Purpose & Capability

The code and SKILL.md match the stated purpose (using mammoth.js to convert .docx to HTML). However the registry metadata declares no required binaries or env vars while the SKILL.md explicitly requires Python 3 and Node.js; that mismatch is unexpected and should be corrected.

Instruction Scope

Runtime instructions are narrowly scoped to locating a .docx file, running the provided convert.py wrapper (which calls the included Node script), and verifying the HTML output. The instructions do not request or reference unrelated system files, credentials, or external endpoints.

Install Mechanism

There is no formal install spec in the registry; instead the SKILL.md instructs running 'npm install' in scripts/. That downloads packages from the public npm registry (package-lock.json is provided). This is a common pattern but increases risk compared with an explicit reviewed install spec; the lockfile points to known packages (mammoth and dependencies) and there are no download-from-arbitrary-URL steps.

Credentials

The skill does not request environment variables or credentials and the code does not access secrets or unrelated config paths. All file I/O is limited to the user-supplied input .docx and the specified output .html.

Persistence & Privilege

The skill is not 'always' enabled and does not attempt to modify other skills or global agent settings. It runs on-demand and does not request elevated or persistent privileges.

What to consider before installing

This skill's implementation (Python wrapper + Node/mammoth) is coherent with its stated purpose, but the registry metadata omits required binaries (Node.js and Python) — treat that as a packaging oversight. Before installing or running: (1) inspect package-lock.json for unfamiliar packages (already provided here; mammoth and common deps look normal); (2) run npm install in a sandbox or isolated environment, not on a production host; (3) ensure Node.js (v16+) and Python 3 are available; (4) if you will process sensitive documents, run the conversion in a secure/local environment since the code writes files to disk and npm packages will be downloaded; and (5) if you need a higher assurance, ask the publisher for corrected metadata and a signed release or a packaged install spec.

This skill provides a straightforward method to convert Microsoft Word (.docx) documents into clean, semantic HTML, making them suitable for various web-based and AI-driven applications.

Compatibility

• Python 3 (for the conversion wrapper)
• Node.js with mammoth installed (core conversion engine)

To install Node.js dependencies, run once from the scripts/ directory:

npm install

Use Cases

• Browser-Based Viewing: Convert DOCX documents for display in web browsers without requiring Microsoft Word.
• AI-Ready Content: Prepare DOCX content for LLMs for tasks like summarization, Q&A, and semantic search.
• Web Integration: Integrate Word document content into web applications, CMS, or online editors.
• Data Extraction: Extract structured data (tables, lists, headings) from DOCX files for automated reporting and analysis.
• Search and Indexing: Enable full-text and vector search by converting DOCX content into easily indexable HTML.

Workflow

1. Locate DOCX File: Identify the path to the .docx file to convert.

2. Run Conversion Script: Execute the Python wrapper from the skill's scripts/ directory:

   python3 <skill-dir>/scripts/convert.py <input_path.docx> <output_path.html>
   

   Replace <skill-dir> with the actual path where this skill is installed.

3. Verify Output: Open the generated .html file in a browser and check:

   • Headings (<h1>, <h2>, etc.) appear at the correct hierarchy levels
   • Tables render with the expected rows and columns
   • Lists appear as bullet or numbered items (not plain text)
   • Bold, italic, and inline formatting are preserved
   • Images are visible (embedded as base64 by default)

4. Process HTML: Use the resulting HTML for further tasks like summarization, indexing, or display.

Bundled Resources

• scripts/docx-converter.js: Core Node.js conversion logic using mammoth.js.
• scripts/convert.py: Python wrapper for invoking the Node.js converter.
• scripts/package.json: Node.js dependency manifest (includes mammoth).

Technical Details

The conversion leverages mammoth.js, which prioritizes semantic meaning over visual replication:

• Semantic Conversion: Document structure maps to proper HTML — headings become <h1>/<h2>, lists become <ul>/<ol>, etc.
• Basic Styling: Bold, italics, and common paragraph styles are preserved.
• Image Embedding: Images are extracted and embedded as base64 data URIs in the HTML output.

Troubleshooting

Problem	Likely Cause	Fix
node: command not found	Node.js not installed	Install Node.js (v16+)
Cannot find module 'mammoth'	npm deps missing	Run npm install in scripts/
Empty or garbled output	Corrupted or password-protected DOCX	Try re-saving the file from Microsoft Word
Missing images	Large embedded images	Check mammoth.js image size limits in docx-converter.js

Limitations

• Advanced or highly specific styling from the original DOCX may not be perfectly replicated in the HTML output.
• Features like tracked changes, comments, or complex layout elements may be simplified or omitted.