docx
An AI agent skill from eigent-ai/eigent, scored 81 out of 100 by code and Verified.
Code score by group
It loses the most points in Done criteria (7), the group that checks whether there is a checklist and a step that verifies the work.
What the author says it does
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of "Word doc", "word document", ".docx", or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing 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 "report", "memo", "lett…
This is the description in the skill's own SKILL.md, written by its author, not by SkillCheatSheet.
- Repository
- eigent-ai/eigent
- Folder
- resources/example-skills/docx
- License
- Apache-2.0
- GitHub stars
- 15,808
- SKILL.md lines
- 482
- Other files
- 60
Add docx to your agent
npx skills add eigent-ai/eigent --skill docx
The command uses the open skills CLI. A skill is instructions and scripts your agent will follow, so read it first: open the folder on GitHub at the commit that was scored.
Labelled for
More skills from eigent-ai/eigent
-
pptx
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or e…
79B -
skill-security-auditor
Security auditing for code, configs, and infrastructure. Use when the user wants to audit or improve security: scan for vulnerabilities (SQL injection, XSS, command injection, pat…
70B -
skill-creator
Guide for creating effective skills. Use when creating a new skill or updating an existing skill that extends agent capabilities with specialized knowledge, workflows, or tool int…
65C
All skills in eigent-ai/eigent
Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.