Flyai Travelmapify

Key points to consider before installing/running: - Missing declared requirements: The registry shows no required env vars, but the skill needs an Amap Web API key (and the recommended local Amap proxy) and the FlyAI CLI. Ask the author to explicitly declare these requirements and what env names are expected. - Filesystem probing: scripts/config.py actively searches your filesystem for OpenClaw workspace files and for the flyai executable (runs 'which flyai', queries npm global bin, and rglob-searches common node paths). If you are uncomfortable with a skill scanning your home directories, run it in a sandbox or container. - Local servers: The tool auto-starts HTTP and hotel-search servers (default ports 9000 and 8770). Ensure those ports are allowed and that running local servers is acceptable in your environment. Confirm the hotel-search-server's behavior and whether it calls external network services. - Amap proxy & API keys: The skill expects a local proxy to avoid exposing API keys client-side. Only provide an Amap API key to a proxy you trust; do not paste keys into untrusted remote services. Verify the proxy implementation you run. - Inspect and test before trusting: Because the skill ships many scripts, review the hotel-search-server and main scripts for any outbound network requests or unexpected behavior. Run the skill in an isolated environment (VM/container) first if you cannot fully audit the code. - What would change this assessment: if the publisher supplies a verified homepage/source repo, documents exact env var names/credentials in the registry, or provides minimal code that clearly documents all external calls (and you can audit the hotel-search-server), the assessment would move toward benign. Conversely, any hidden remote endpoints, undisclosed credentials use, or attempts to transmit data off-host would worsen the verdict.