Agricultural Output Forecasting

Before installing or running this skill: - Do not set or expose any real billing or API keys until you audit the code. The registry metadata says 'no env vars' but the scripts expect billing keys (SKILLPAY_API_KEY / SKILLPAY_SKILL_ID) — the README and other docs use different names; this inconsistency can cause accidental credential leaks. - Inspect the code paths that access ~/.openclaw/. Trial data is written as JSON keyed by user_id (raw), contrary to claims that user IDs are hashed. If you care about privacy, either run the skill in a sandboxed account or modify TrialManager to hash/avoid storing raw identifiers. - The package includes auto-evolve-daemon.sh (an infinite loop that runs self_evolve.py). Do not run that daemon unless you understand and trust the self-evolution logic. If you don't need persistent background behavior, avoid running the shell script and remove it from the skill directory. - Verify the billing endpoint (https://skillpay.me) independently before supplying credentials. Consider testing in demo mode only (python scripts/forecast.py --demo ...) and confirm network calls using a network monitor or run inside an isolated environment/container. - Address documentation mismatches (trial counts, versions, env var names). If you plan to use this in production, request the maintainer to fix docs and provide a minimal surface (clear required env vars) and to change trial storage to not record raw user IDs. If you're unsure, run the skill in a disposable VM or container and/or ask the publisher for an authoritative manifest (which env vars are required and why) before granting any sensitive permissions.