← Back to Skills Marketplace
1025
Downloads
0
Stars
11
Active Installs
3
Versions
Install in OpenClaw
/install web-tools-guide
Description
MANDATORY before calling web_search, web_fetch, browser, or opencli. Contains required error-handling procedures (web_search failure → must guide user to con...
Usage Guidance
This skill appears to do what it claims (guide web tools and fallbacks) but performs intrusive operations: it asks you to run a bundled setup script that will install an npm package, download and extract a browser extension, and kill/restart your Chrome process; it also instructs writing user-provided API keys into the agent's openclaw config and restarting the gateway. Before installing or running it: 1) review the setup script and extension contents locally; verify the GitHub release and the npm package (@jackwener/opencli) are legitimate; 2) back up your browser profile—the script will terminate and restart Chrome; 3) do not paste secrets into chat unless you trust the operator and understand where they will be stored; consider entering API keys only via a secure secret store rather than plain chat if possible; 4) prefer to run installation steps in an isolated environment (VM/container) first; and 5) require explicit, per-action confirmation (especially before browser restarts, gateway restarts, or any write operations) rather than allowing the skill to perform them automatically. If you cannot verify the upstream sources or are uncomfortable with process/config changes, treat this skill as potentially risky and avoid running the setup script or providing API keys.
Capability Tags
Capability Assessment
Purpose & Capability
Name/description (guidance for web_search/web_fetch/opencli/browser) matches the included files and instructions: fallback logic, site URL index, opencli usage, and web_search configuration steps. The included install script and references are consistent with enabling opencli/Browser Bridge functionality that the SKILL.md promises.
Instruction Scope
SKILL.md directs the agent to read local reference files, to run a bundled setup script, to request API keys from users and then to write them into openclaw config and restart the gateway. These actions go beyond read-only guidance: they perform system changes, accept user secrets, and perform process control. While coherent with enabling the described tooling, this scope is high-impact and requires explicit user consent at each step (the SKILL.md asks for some confirmations but also instructs running the install script without prompting about browser restart).
Install Mechanism
No formal install spec, but the included scripts install an npm package (@jackwener/opencli) and download a browser extension from a GitHub releases URL (github.com/jackwener/opencli/releases). Using npm + GitHub releases is typical and traceable, but the script will extract archive contents to a user directory and then attempt to restart Chrome to load the extension. This is moderate-risk (network downloads + file extraction + execution) and should be inspected before running.
Credentials
The skill does not declare required env vars, but its web-search config flow asks the user to provide API keys (tvly-*, sk-*) and then programs them into openclaw config. Requesting an API key for a web search provider is proportionate to the feature. However the skill's insistence on verbatim copying and automatic configuration + gateway restart increases the risk of accidental key disclosure or unintended persistence of credentials in agent config.
Persistence & Privilege
The setup script attempts to find a running Chrome process, kill it, and relaunch it with extension parameters; web-search-config steps instruct writing API keys into openclaw.json and restarting the gateway (or using docker pkill). Those are system-level changes (process control + persistent config changes). The skill is not marked always:true, but its runtime instructions request significant privileges and persistent modifications — users should not allow these actions without explicit, informed consent and review.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install web-tools-guide - After installation, invoke the skill by name or use
/web-tools-guide - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.2
- Added OpenCLI integration as a fallback tool (covering 70+ sites) between web_fetch and browser, with setup script and user guidance.
- Updated decision process: tools are now parallel branches—not a strict escalation—to choose the most efficient path based on scenario.
- Enhanced error handling: failures in web_search or web_fetch now require explicit configuration guidance and OpenCLI fallback before using the browser.
- Expanded documentation: included references to opencli usage guide and setup instructions for smoother onboarding.
- Modified skill to be MANDATORY before using web_search, web_fetch, browser, or opencli, emphasizing correct fallback and error procedures.
v1.0.1
- No user-facing or internal changes in this version.
- All documentation and logic remain unchanged.
v1.0.0
Web 工具策略指南上线，分级选用 web_search, web_fetch, browser 工具：
- 明确三层工具选择：先搜索（web_search），再抓取（web_fetch），最后必要时使用浏览器自动化（browser）
- 每次升级工具层级时须向用户解释原因，严禁静默切换
- 登录、敏感和不可逆操作需用户授权或二次确认
- 明确 web_search 失败后的用户引导与降级方案
- 强调科学元素等待、保持浏览器状态、对验证码问题告知用户
Metadata
Frequently Asked Questions
What is web-tools-guide?
MANDATORY before calling web_search, web_fetch, browser, or opencli. Contains required error-handling procedures (web_search failure → must guide user to con... It is an AI Agent Skill for Claude Code / OpenClaw, with 1025 downloads so far.
How do I install web-tools-guide?
Run "/install web-tools-guide" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is web-tools-guide free?
Yes, web-tools-guide is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does web-tools-guide support?
web-tools-guide is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created web-tools-guide?
It is built and maintained by FMLS (@fmls); the current version is v1.0.2.
More Skills