Openclaw Skill

What to consider before installing/using this skill: - Try Native Mode first (do not set HALAOS_API_KEY) to evaluate the built-in Q&A and calculation features without sending data to the cloud. - If you enable cloud mode (set HALAOS_API_KEY), assume the key grants the vendor access to company HR data and agent-driven operations (payroll generation, attendance, org intelligence). Confirm with the vendor: which API endpoints does the key talk to, what scopes/data are accessible, and the retention/authorization model. - The SKILL.md mentions storing local HR data and integrating with Notion/Google Sheets/Obsidian. Ask how credentials for those services are provided and stored (are you asked to paste tokens? does the skill store them in cleartext in config.json?), and verify file permissions for ~/.openclaw/skills/halaos-hr/config.json. - For sensitive HR data (payroll, personal identifiers), verify vendor identity (halaos.com), read their privacy/security documentation, and consider testing with dummy data first. - If you need stricter controls, request least-privilege API keys/scopes from the vendor and an audit/logging policy that shows what the cloud agents do with your data. If you want, I can produce a checklist of questions to ask the vendor (endpoints/scopes, retention, encryption at rest/in transit, where 3rd-party storage credentials are kept) or a template config.json permission recommendation.