Blog to Kindle

What to consider before installing and running this skill: - Missing runtime requirements: The scripts expect a macOS Mail.app/osascript environment and external tools (pandoc) and Python libraries (httpx, BeautifulSoup). Don’t run blindly — install and audit dependencies (pip install httpx bs4 or use a venv) and ensure pandoc is from a trusted source. - Replace the default Kindle address: The scripts and docs include a hard-coded Kindle email (simonpilkington74_8oVjpj@kindle.com). Change it before sending anything — otherwise you may accidentally send content to someone else. - Keychain/API usage is implicit: The manual workflow shows retrieving GEMINI_API_KEY from the macOS keychain to drive a cover-generation skill. If you follow that path, inspect the nano-banana-pro skill and confirm how it uses any API keys before allowing it access to your keychain or secrets. - macOS-specific behavior: Sending relies on Mail.app via AppleScript. If you’re not on macOS or prefer not to use your Mail.app account, modify send_to_kindle.py to use an alternative (SMTP with explicit credentials that you control) or test via a local sandbox first. - Test safely: Run fetch/compile steps on a small site or a local HTML snapshot first. Inspect ~/.clawdbot/state/blog-kindle/ for what the skill writes. Avoid enabling any autonomous invocation or automation until you’re comfortable with behavior. - Provenance and audit: The skill's source/homepage is unknown. If you don’t know or trust the owner, review the included scripts line-by-line (they’re short) before use. Consider running in an isolated VM/container and not granting any keychain/API access until you verify the other skills it depends on. If you want, I can: (a) list the exact dependencies and commands to set up a safe environment to run this skill, (b) suggest a patched send_to_kindle.py that prompts for the Kindle address instead of using the hard-coded default, or (c) scan the scripts for specific strings/hosts to look for potential exfiltration points.