← Back to Skills Marketplace
juanpin

Yutori research

by juanpin · GitHub ↗ · v1.0.1
cross-platform ⚠ suspicious
2165
Downloads
0
Stars
1
Active Installs
2
Versions
Install in OpenClaw
/install yutori-web-research
Description
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).
Usage Guidance
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.
Capability Analysis
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.
Capability Assessment
Purpose & Capability
Name/description => calling Yutori Research and Browsing APIs; the included Node runner and SKILL.md implement exactly that. Required functionality (POST /v1/research/tasks and /v1/browsing/tasks) aligns with the stated purpose.
Instruction Scope
SKILL.md instructs the agent to create and poll research/browsing tasks and to return structured results. The included script only performs API calls, polling, and prints results. However both SKILL.md and the script reference reading ~/.openclaw/openclaw.json as a fallback for the API key — this means the skill will read a local config file in the user's home directory, which can contain other environment settings or secrets.
Install Mechanism
No install spec; this is an instruction-only skill with a small runner script bundled. No downloads, no archive extraction, and no package installs — low install risk.
Credentials
SKILL.md and the script require a YUTORI_API_KEY and suggest a YUTORI_API_BASE, but the registry metadata lists no required env vars or primary credential. That mismatch is an incoherence. The script will read the file ~/.openclaw/openclaw.json to extract env.YUTORI_API_KEY as a fallback — reading that file may expose other saved env values if the script is modified or extended.
Persistence & Privilege
always: false and no install hooks. The skill does not request persistent system presence or modify other skills' configs. It runs network calls to the declared API base (default dev/prod yutori endpoints).
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install yutori-web-research
  3. After installation, invoke the skill by name or use /yutori-web-research
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
- No functional or documentation changes detected in this release. - Version bump recorded without modification to code or documentation files.
v1.0.0
Initial release of yutori-web-research. - Integrates Yutori’s Research API for web research (with citation sources). - Supports cloud browser automation for web navigation and structured data extraction. - Requires API key and endpoint setup via environment variables. - Comes with a Node runner script for research task automation and result formatting. - Provides guidance for both research and web browsing workflows with clean bullet-point outputs. - Outputs clear, source-linked, human-friendly text summaries and lists.
Metadata
Slug yutori-web-research
Version 1.0.1
License
All-time Installs 1
Active Installs 1
Total Versions 2
Frequently Asked Questions

What is 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). It is an AI Agent Skill for Claude Code / OpenClaw, with 2165 downloads so far.

How do I install Yutori research?

Run "/install yutori-web-research" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Yutori research free?

Yes, Yutori research is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Yutori research support?

Yutori research is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Yutori research?

It is built and maintained by juanpin (@juanpin); the current version is v1.0.1.

💬 Comments