Shuke Document Formatting

What to consider before installing or running this skill: - The code appears to do what the description says (format DOCX → PDF and install/verify fonts), but it performs system-level changes: install_shuke_fonts.py requires root and will copy TTF files into /usr/share/fonts/数科文印字体 and run fc-cache. Only proceed if you trust the font files and the author. - Missing declared dependencies: the SKILL.md lists python-docx but does not list system binaries and Python packages actually used (pandoc, weasyprint, pdffonts/pdfinfo, fc-list/fc-cache, reportlab, PyPDF2). Install those in a controlled environment first (or inspect code) rather than elevating privileges to install them on the system blindly. - Inspect font files before installing: the installer will scan and copy any matching TTFs from the provided directory. Verify that the TTF files are legitimate and licensed for your use; do not install unknown or untrusted fonts as root. - Hard-coded paths: some tools default to /root/.openclaw/workspace paths if no arguments are given. Run the scripts with explicit input/output paths to avoid accidental operations on unexpected files. - Test in an isolated environment: if possible, run the tool in a disposable VM or container first (or in a non-root user account) and avoid running install_shuke_fonts.py as root until you’ve verified the font files and the script behavior. - Backup system fonts: if you decide to install, backup existing font directories first so you can recover if something goes wrong. - If you only need formatting/PDF conversion and not system-wide font installation, try running the conversion tools with local font files or use the generate_proper_example/doc_generator utilities to see behavior without modifying /usr/share. If you want, I can highlight the exact lines that (a) copy files into /usr/share, (b) require root checks, and (c) reference the hard-coded /root workspace paths so you can inspect them directly.