flight-monitor

What to know before installing: - Behavior: The skill queries public flight APIs (Ctrip) and, when necessary, suggests a single web_search for the AI to run. It stores monitor configurations and price history in your home directory under ~/.workbuddy/flight-monitor and ~/.workbuddy/automations. - Credentials: No credentials are required by default. If you want push notifications you must supply a push service key (Bark/Server酱/PushDeer); these keys are saved to ~/.workbuddy/flight-monitor/notify_config.json. The search tool also supports an optional third-party zbape API key saved to ~/.workbuddy/flight-monitor/api_config.json. Treat those files like any other sensitive config (permission them appropriately). - Network: The scripts make outbound HTTPS requests to booking/OTA endpoints (e.g., flights.ctrip.com) and to push-service APIs. If you have network or privacy concerns, review the code and consider running it in a restricted environment. - Safety checks: The code uses input validation and path boundary checks to mitigate path traversal and unsafe filenames. monitor_manager.py intentionally avoids subprocess/os.system calls; monitor 'run' prints prompts rather than executing shell commands. - Minor note: SKILL.md's claim 'no API keys required' is true for the main Ctrip flow, but an optional zbape key is supported — only supply keys you trust. If you want higher assurance, inspect the bundled scripts (they are included) and confirm you are comfortable with local config files and outbound network connections before enabling automatic monitoring.