GEDCOM Explorer

What to consider before installing or running this skill: - Source verification: The homepage/source is unknown. Prefer skills with a known author and repository. Ask the publisher for a public repo or release tarball so you can audit the full code. - Inspect the full script: The provided build_explorer.py was truncated in the package listing. Before running, open the entire file and search for any network or subprocess activity (look for imports or strings: requests, urllib, http, socket, subprocess, os.system, popen, ftplib, smtplib, telnet, ssh, eval, exec). If you see any outbound endpoints (URLs, IPs) or hidden obfuscated strings, do not run it until you understand them. - Remove/inspect hidden characters: The pre-scan found unicode-control-chars in SKILL.md. View the file in a hex editor or use a utility to show non-printable characters and remove them if they are not intended. - Run in isolation: If you choose to run the script, do so on a disposable VM or sandbox with no sensitive network access and with a test GEDCOM file first. Verify the produced HTML contains no calls to remote resources (open it while offline) and that no unexpected outbound connections occur while generating the file. - Privacy: GEDCOM files contain personal data. Be aware the tool embeds all data into a single HTML file — treat that file like the original GEDCOM with respect to privacy and sharing. - Cron/notification note: SKILL.md mentions Telegram/cron integration as an extension. Do not enable or wire any notification integrations until you review the implementation and approve the destination endpoints and credentials. If you can provide the complete build_explorer.py (full file) or a public repository URL, I can re-evaluate and raise the confidence level.