メニュー
浏览器环境配置技能 - 自动检测系统已安装的 Chrome/Chromium，或提供下载安装指引。支持 Linux/macOS/Windows 跨平台检测。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of "Word doc", "word document", ".docx", or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a "report", "memo", "letter", "template", or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
使用 Bun.fetch 进行 HTTP API 调用。支持 GET/POST/PUT/DELETE、JSON 处理、请求头设置、超时控制。当用户需要调用 API、获取网络数据、测试 API 接口时使用。
测试 Bun 运行时功能。当用户要求测试 Bun、验证 Bun 安装、或执行 JavaScript 代码时使用。
| name | browser_setup |
| description | 浏览器环境配置技能 - 自动检测系统已安装的 Chrome/Chromium，或提供下载安装指引。支持 Linux/macOS/Windows 跨平台检测。 |
| version | 1.0 |
| author | GopherPaw |
当用户需要配置浏览器环境、检测系统浏览器、解决浏览器找不到的问题时，使用本技能。
本技能帮助用户解决 browser_use 工具报告 "executable file not found" 的问题：
CHROME_BIN 环境变量用户询问类似问题时进行检测：
使用以下命令检测系统浏览器：
# Linux/macOS
which google-chrome google-chrome-stable chromium chromium-browser
# 或使用 ls 检查常见路径
ls /usr/bin/google-chrome* /usr/bin/chromium* /snap/bin/chromium
# macOS
ls "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome"
# Windows
where chrome.exe
可调用 shell_tool 运行检测脚本：
# 运行检测脚本
bash configs/active_skills/browser_setup/scripts/detect.sh
/usr/bin/google-chrome/usr/bin/google-chrome-stable/usr/bin/chromium/usr/bin/chromium-browser/usr/lib/chromium/chromium/snap/bin/chromium/Applications/Google Chrome.app/Contents/MacOS/Google Chrome/Applications/Chromium.app/Contents/MacOS/ChromiumC:\Program Files\Google\Chrome\Application\chrome.exeC:\Program Files (x86)\Google\Chrome\Application\chrome.exe# 临时设置（当前会话）
export CHROME_BIN="/usr/bin/google-chrome-stable"
# 永久设置（添加到 ~/.bashrc 或 ~/.zshrc）
echo 'export CHROME_BIN="/usr/bin/google-chrome-stable"' >> ~/.bashrc
source ~/.bashrc
创建 ~/.gopherpaw/browser.json：
{
"chrome_path": "/usr/bin/google-chrome-stable",
"last_updated": "2025-03-08T10:30:00Z",
"auto_installed": false
}
在 Docker 容器中运行时，需要特殊处理：
/.dockerenv 文件或 /proc/1/cgroup--no-sandbox 和 --disable-setuid-sandbox可通过环境变量显式指定：
export GOPHERPAW_RUNNING_IN_CONTAINER=1
# Ubuntu/Debian
sudo apt-get update
sudo apt-get install -y chromium-browser
# 或安装 Chrome
wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
sudo dpkg -i google-chrome-stable_current_amd64.deb
sudo apt-get install -f -y
# CentOS/RHEL
sudo yum install -y chromium
# 使用 Homebrew
brew install --cask chromium
apk add --no-cache chromium
从官网下载安装：
运行验证脚本检查浏览器是否可用：
bash configs/active_skills/browser_setup/scripts/verify.sh
或手动验证：
# 检查环境变量
echo $CHROME_BIN
# 检查可执行文件
$CHROME_BIN --version
# 或直接调用
google-chrome --version
chromium --version
配置完成后，测试 browser_use 工具：
// 启动浏览器
{"action": "start", "headed": true}
// 打开网页
{"action": "open", "url": "https://example.com"}
// 截图测试
{"action": "screenshot", "path": "/tmp/test.png"}
A: 按优先级尝试：
CHROME_BIN 环境变量指向浏览器路径A: 确保设置了：
GOPHERPAW_RUNNING_IN_CONTAINER=1/.dockerenv 文件存在--no-sandbox 参数A: 检查浏览器可执行文件权限：
chmod +x /usr/bin/chromium