Yutori research

Use Yutori’s Research API and Browsing API (cloud browser) to research topics, collect sources, and extract structured facts from the web. Use when the user asks to “research X”, “monitor/find papers”, or “navigate to a site and extract info” and you have access to YUTORI dev/prod endpoints via YUTORI_API_BASE and an API key in env (YUTORI_API_KEY or ~/.openclaw/openclaw.json env.YUTORI_API_KEY).

This skill appears to do what it says (call Yutori research/browsing APIs), but be cautious before installing/using it: 1) The registry metadata does NOT declare the YUTORI_API_KEY requirement even though SKILL.md and the script use it — treat that as a packaging/information error and prefer to see the credential declared explicitly in the registry. 2) The bundled script will attempt to read ~/.openclaw/openclaw.json as a fallback to obtain the API key; review that file and the runner script before running to ensure you’re not unintentionally exposing other secrets. 3) Prefer setting YUTORI_API_KEY in a controlled environment variable rather than relying on a shared config file. 4) Verify the API key’s permissions (Research vs Browsing) and the intended API_BASE (dev vs prod) before use. If you do not trust the skill source, do not run the script or provide your API key until the registry metadata and SKILL.md are consistent and you have audited the code.

Type: OpenClaw Skill Name: yutori-web-research Version: 1.0.1 The skill accesses the sensitive `~/.openclaw/openclaw.json` file to retrieve the `YUTORI_API_KEY` (as seen in `scripts/yutori-research.mjs`). It also makes external network calls to `api.dev.yutori.com` or `api.yutori.com` (via `scripts/yutori-research.mjs` and `SKILL.md`'s `curl` example). While these actions are aligned with the stated purpose of interacting with the Yutori API, accessing local sensitive files and performing external network communication are high-risk capabilities that warrant a 'suspicious' classification, as they could be misused if the skill's intent were different. There is no clear evidence of intentional malicious behavior like exfiltration to unrelated endpoints or persistence mechanisms.