ERP Tax Filler

This skill appears to do what it claims (XML-editing of .xlsx to preserve formulas/styles), but take these precautions before using it or installing it into an agent: - Do not run it on production/original templates — always test on copies and keep backups. - The SKILL.md recommends converting .xls via Excel COM. Opening files in Excel via COM can execute macros (Workbook_Open, Auto_Open). If you need to use Excel automation, ensure macros are disabled (e.g., set Application.AutomationSecurity = msoAutomationSecurityForceDisable) or otherwise ensure templates are trusted and free of malicious VBA. - The unpack/pack/edit flow will remove xl/calcChain.xml and repack the archive; if the workbook contains VBA (vbaProject.bin) or is macro-enabled (.xlsm), converting/saving as .xlsx or repacking may strip or break macros. The unpacker warns about vbaProject.bin — heed that. - The scripts assume presence of Python packages (xlrd, xlutils). The bundle includes no installer; confirm these dependencies and test in a controlled environment. - There are hardcoded fallback numeric values in the profit-table mapping — if ERP data for those lines is missing the script will insert those defaults; review and adjust if that is unacceptable. - Minor doc/code mismatch: SKILL.md strongly warns against using xlutils/openpyxl in some places but erp_fill.py imports xlutils.copy (though it doesn't appear to actually use it). Treat this as a small maintainability/quality issue and review the code before running. If you intend to use this in an automated/agent context, require user confirmation before running and ensure the environment disallows unintended macro execution. If you cannot review the templates and code yourself, consider this skill suspicious and avoid running it on sensitive data.