Word DOCX by Xiaomolong
v1.0.0Create, inspect, and edit Microsoft Word documents and DOCX files with reliable styles, numbering, tracked changes, tables, sections, and compatibility check...
⭐ 0· 125·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name, description, and SKILL.md consistently describe DOCX/Word handling and the skill requires no binaries, installs, or credentials, which is proportionate. Minor metadata inconsistencies exist: the registry metadata lists version 1.0.0 while SKILL.md shows 1.0.2, and the ownerId in _meta.json differs from the registry ownerId—these look like bookkeeping/mismatch issues rather than functional problems, but they reduce provenance confidence.
Instruction Scope
SKILL.md is a detailed, OOXML-aware playbook for reading, editing, and preserving DOCX structure. It does not contain shell commands, network endpoints, or instructions to read unrelated system files or environment variables. The guidance is narrowly scoped to DOCX internals (styles, numbering, sections, tracked changes), which is appropriate for the stated purpose.
Install Mechanism
There is no install spec and no code files; this is instruction-only, so nothing is written to disk or fetched during installation. This is the lowest-risk install pattern.
Credentials
The skill declares no required environment variables, no primary credential, and no config paths. That aligns with an instruction-only authoring skill.
Persistence & Privilege
always is false and the skill is user-invocable; autonomous invocation is allowed (the platform default). The skill does not request persistent presence, nor does it include install steps that would modify agent/system configuration.
Assessment
This skill is an instruction-only DOCX/Word editing guide and appears internally consistent and low-risk. Before enabling: (1) note the metadata mismatches (version/ownerId) — they don't prove malice but reduce provenance; (2) only supply document files the agent legitimately needs (it may read whole .docx packages to follow its rules); (3) treat macro-enabled files (.docm) as higher risk and avoid providing sensitive documents until you test behavior on non-sensitive samples; (4) if you need stronger guarantees, ask the publisher for a signed/consistent release or prefer a skill from a known author.Like a lobster shell, security has layers — review code before you run it.
documentvk972zawppe7nxxx504qj3bc23d83hdrwdocxvk972zawppe7nxxx504qj3bc23d83hdrwlatestvk972zawppe7nxxx504qj3bc23d83hdrwofficevk972zawppe7nxxx504qj3bc23d83hdrwwordvk972zawppe7nxxx504qj3bc23d83hdrw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📘 Clawdis
OSLinux · macOS · Windows