ODT File Manager & Editor
PassAudited by ClawScan on May 1, 2026.
Overview
This appears to be a coherent local ODT editing skill, but it can modify documents in place and depends on an unpinned Python package.
This skill is reasonable for local ODT work. Before installing or using it, make sure you are comfortable installing `odfdo`, run edits only on intended documents, keep backups for important files, and review any document before uploading it back to NextCloud or another shared location.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A mistaken file path or replacement pattern could alter the wrong document or change more text than intended.
The script saves changes back to the same user-supplied document path, including after find/replace operations.
doc.save(path, pretty=True)
print(f"OK replaced {count} occurrence(s) in: {path}")Inspect first, work on copies for important files, and require explicit confirmation before replace, style, metadata, or upload operations.
Users may install whatever version pip resolves at setup time, which can affect reproducibility and supply-chain assurance.
The required Python dependency is installed via an unpinned pip command, so the exact package version is not fixed by the skill artifacts.
pip install odfdo
Install from a trusted Python package source and consider pinning a known-good `odfdo` version in controlled environments.
A bad local edit could be propagated to a cloud document if the upload step is run.
The documented workflow can re-upload locally edited ODT files through a separate NextCloud skill.
python3 $NC/files_binary.py upload /tmp/MyDoc.odt "/Documents/MyDoc.odt"
Review the edited local file before uploading, and keep backups or version history enabled for cloud documents.