Menu
Use PilotDeck's browser-use plugin for browser automation, screenshots, form filling, and web UI checks.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Run safe PowerShell commands on Windows, translate Bash snippets, and troubleshoot native Windows setup.
Intelligent meeting recording and transcription assistant with automated minutes generation, action item extraction, and sentiment analysis. Supports audio transcription, speaker diarization, meeting summarization, and task extraction. Use when users need to record meetings, transcribe audio, generate meeting minutes, extract action items, or analyze meeting content.
Set up and use 1Password CLI for sign-in, desktop integration, and reading or injecting secrets.
Create, view, edit, delete, search, move, or export Apple Notes via the memo CLI on macOS.
List, add, edit, complete, or delete Apple Reminders and reminder lists via remindctl.
Create, search, and manage Bear notes via grizzly CLI.
| name | browser-use |
| description | Use PilotDeck's browser-use plugin for browser automation, screenshots, form filling, and web UI checks. |
Use this skill when a task needs browser automation through PilotDeck's built-in browser-use plugin, especially for local Web UI smoke tests, screenshots, navigation, clicking, typing, and DOM inspection.
PilotDeck ships the browser-use plugin, which runs @playwright/mcp with Chromium. The plugin needs Chrome for Testing to be installed on the machine before browser automation can launch reliably.
Check whether the browser is already installed:
if ls "$HOME/Library/Caches/ms-playwright"/mcp-chrome-for-testing-* >/dev/null 2>&1 || \
ls "$HOME/.cache/ms-playwright"/mcp-chrome-for-testing-* >/dev/null 2>&1; then
echo "Chrome for Testing is already installed; no reinstall needed."
else
echo "Chrome for Testing is not installed yet."
fi
The one-line installer uses the same check. If Chrome for Testing is already present, it prints Chrome for Testing already installed and does not download it again.
Install it from a PilotDeck source checkout or installed app directory:
cd /path/to/PilotDeck
corepack pnpm install --frozen-lockfile
corepack pnpm run install:browser
For an installed one-line setup, use the app directory shown by pilotdeck status:
pilotdeck status
cd ~/.pilotdeck/app
corepack pnpm run install:browser
To let the one-line installer install it during setup, opt in explicitly:
PILOTDECK_SKIP_BROWSER_INSTALL=0 bash install.sh
Repeated installs are safe: check first, skip when present, install only when missing.
If the download is slow or blocked, configure your network proxy first and rerun the install command. Browser automation is optional; PilotDeck core chat, files, skills, and settings work without it.
pilotdeck status, usually http://localhost:3001.Open http://localhost:3001
Verify the page shows LLM Provider Setup when no real provider config exists
Open Settings and verify provider/API key controls are visible
Take a screenshot only when visual evidence is useful