NaviOffice Skill

NaviOffice OA 办公系统 MCP 集成技能 - 覆盖系统管理、人力资源、考勤、财务、CRM、销售、采购、库存、项目、生产、计量检测 11 大模块，支持数据查询与业务操作。

This skill appears to be a genuine NaviOffice API client, but there are important red flags you should consider before installing or using it: - Secrets required: The SKILL.md and the included scripts require NAVI_OFFICE_API_TOKEN (and optionally NAVI_OFFICE_API_URL and NAVI_OFFICE_ALLOW_CUSTOM_DOMAIN), but the registry metadata lists no required env vars. Treat this as a transparency/packaging mistake — assume you must provide an API token for the skill to work. - Broken domain validation: Both the JS and Python scripts have a bug that compares the parsed hostname to the full URL string 'https://oa.teredy.com/api'. As written, the scripts will reject the official domain and terminate unless NAVI_OFFICE_ALLOW_CUSTOM_DOMAIN=true is set. That effectively forces users to enable "allow custom domain" to proceed, which is risky because it relaxes the whitelist and could allow the token to be sent to an arbitrary endpoint. - Before using the skill, do one or more of the following: - Inspect the scripts (navioffice.js / navioffice.py) yourself or ask the author to fix the domain-check bug so the allowed host is compared correctly (should compare hostname to 'oa.teredy.com' or compare the full URL string consistently). A safe fix: validate that the parsed hostname === 'oa.teredy.com' (or if you want to allow subdomains, check suffix). - If you must test, use a non-production API token with minimal privileges and run the tool in an isolated environment/network where you can monitor outbound requests. - Do not set NAVI_OFFICE_ALLOW_CUSTOM_DOMAIN=true unless you fully trust the endpoint. If you do set it, ensure NAVI_OFFICE_API_URL points to a vetted, internal, or otherwise trusted host. - Ask the publisher to update registry metadata to declare NAVI_OFFICE_API_TOKEN as a required env var so the platform can surface the requirement. - Prefer the Python/Node shells only after verifying they send traffic to the intended hostname and not to unknown third parties. Given the missing metadata and the domain-validation bug (which has a direct security impact), treat this package as suspicious until the author corrects the issues or you perform an independent code/network audit.