Doc Xls2docx Xlsx
v1.0.0Skill for batch converting legacy Office files (.doc, .xls) to modern formats (.docx, .xlsx). Use when user asks to convert .doc/.xls files, migrate Office d...
⭐ 0· 13·0 current·0 all-time
byjuanfenglong@longjf25
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, SKILL.md, and included scripts align: doc_to_docx_com.py uses Word COM for .doc→.docx (Windows+Word required) and xls_to_xlsx.py uses xlrd/openpyxl for .xls→.xlsx. No unrelated binaries, env vars, or config paths are requested.
Instruction Scope
Runtime instructions are narrowly scoped to running the two scripts and installing the indicated Python packages. The doc conversion uses local Word COM automation which will open the provided .doc files — this is expected for the stated purpose but can expose the host to risks inherent in opening untrusted Word documents (macros, external links, embedded content). SKILL.md does not mention disabling macros or using protected/sandboxed view; consider adding guidance to avoid processing untrusted files on production systems.
Install Mechanism
This is an instruction-only skill with no install spec that pulls code from arbitrary URLs. All code is included in the bundle and there are no network fetches or archive extracts in the install phase.
Credentials
No environment variables, credentials, or config paths are requested. Requiring Microsoft Word and Python packages is proportionate to the conversion tasks.
Persistence & Privilege
The skill does not request always:true, does not modify other skills or system configuration, and contains no persistence mechanisms. It runs locally and acts only on user-specified files/directories.
Assessment
This skill appears to do what it claims and has no network calls or secret requirements, but take these precautions before using it:
- Run conversions on copies of files, not originals, so you can recover if something goes wrong.
- Be cautious with untrusted .doc files: opening them with Word can execute macros or fetch external content. Prefer converting on an isolated or sandboxed Windows machine, enable Protected View, or disable macros before batch conversion.
- Review the included scripts yourself (they are short and local) or run them in a Python virtual environment after installing xlrd/openpyxl/pywin32 as recommended.
- Test with a small sample set first to confirm formatting/encoding behavior; the xls→xlsx script has noncritical date-handling code paths that may behave differently on some inputs.
- If you need enterprise deployment, consider adding logging, input validation, and explicit safeguards around macro handling and temp file locations.Like a lobster shell, security has layers — review code before you run it.
latestvk979k69t5s5gzjxn8b7vhrbv5h848ga1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
