Skip to content
Back to skills

Docx

ASecurity

Create, read, edit, and review Word .docx documents

  • 147 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 3, 2026
ai-agentspython

Security analysis

A92/100
  • mediumInstalls packages at runtime which could introduce malicious dependencies

Pro shows the line behind each finding and how to fix it

Scanned September 3, 2026

npx -y skills add prapaa-ai/agav --skill docx --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Docx?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Docx
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/prapaa-ai-docx/badge)](https://www.skillsdirectory.com/skills/prapaa-ai-docx)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: docx
description: Create, read, edit, and review Word .docx documents
version: 1.0.0
invocation: both
allowed-tools: read_file write_file run_command find_files list_directory
tags:
  - documents
  - writing
  - office
---

# Word Documents (docx)

Create, read, edit, and review Microsoft Word .docx files.

## Instructions

1. Check that the `python-docx` library is available: run `python -c "import docx"`. If it fails, install it with `pip install python-docx` (requires user approval) and tell the user if installation is not possible.
2. Determine the task:
   - **Create**: a new document from provided content or an outline.
   - **Edit/Review**: an existing document the user pointed to.
   - **Read/Extract**: pull text out of a document into plain text or Markdown.
3. For new documents, build a sensible structure: Title style for the title, Heading 1 for sections, Heading 2 for subsections, body text for paragraphs, list styles for bullets/numbered items, and tables where tabular data fits better than prose.
4. For edits, preserve the document's existing styles and formatting. Modify only the paragraphs or runs the user asked about; do not reformat untouched content.
5. Never overwrite the original file when creating a revised copy — write to a new file (e.g. `report-v2.docx`) unless the user explicitly asks to modify in place.
6. After writing, verify the result by reopening the file and checking it parses, then report: file path, paragraph/table counts, and any content you could not represent (e.g. complex page layouts, headers/footers beyond basics).
7. If the source content is a PDF or scan, note that text extraction from PDFs is handled by the pdf skill instead.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…