webpilot

分类: 工具与效率 | 上传者: hugopalma17 | 下载: 0 | 版本: v1.0（最新）

Skill for LLM agents to drive a real browser through the Webpilot CLI and shared WebSocket runtime.

更新日志: Source: GitHub https://github.com/hugopalma17/webpilot

目录结构

当前层级: 根目录

📁 .github/
- 📁 workflows/
  - 📄 npm-publish.yml 857 B
📁 bin/
- 📄 cli.js 42.5 KB
- 📄 server-daemon.js 3.6 KB
📁 client/
- 📄 cursor.js 814 B
- 📄 element.js 3.3 KB
- 📄 index.js 404 B
- 📄 keyboard.js 486 B
- 📄 page.js 8.5 KB
📁 extension/
- 📁 icons/
  - 📄 icon-128.png 28.5 KB
  - 📄 icon-16.png 2.2 KB
  - 📄 icon-48.png 6.0 KB
- 📄 content-script.js 69.0 KB
- 📄 manifest.json 718 B
- 📄 service-worker.js 22.6 KB
📁 lib/
- 📄 first-run.js 6.2 KB
- 📄 launcher.js 9.9 KB
- 📄 server.js 13.3 KB
📁 mcp-server/
- 📁 lib/
  - 📄 ws-bridge.js 2.7 KB
- 📄 index.js 19.6 KB
- 📄 package-lock.json 40.0 KB
- 📄 package.json 852 B
📁 protocol/
- 📄 PROTOCOL.md 10.3 KB
📁 test/
- 📄 all-commands.js 12.8 KB
- 📄 browse-site.js 7.7 KB
- 📄 debug-evaluate.js 2.4 KB
- 📄 fixtures.html 5.0 KB
- 📄 fixtures.js 871 B
- 📄 github_button.html 515 B
- 📄 google-search.js 5.0 KB
- 📄 integration.js 5.9 KB
- 📄 raw-dispatch-failures.js 14.4 KB
- 📄 raw-fixtures.html 5.3 KB
- 📄 server.js 3.6 KB
- 📄 server.test.js 11.5 KB
📄 .gitignore 1.0 KB
📄 gemini-extension.json 327 B
📄 human-browser.config.example.js 4.1 KB
📄 index.js 16.9 KB
📄 LICENSE 10.5 KB
📄 package-lock.json 1.6 KB
📄 package.json 1.3 KB
📄 README.md 6.6 KB
📄 SKILL.md 4.4 KB

SKILL.md

---
name: webpilot
description: Skill for LLM agents to drive a real browser through the Webpilot CLI and shared WebSocket runtime.
---

# Webpilot Skill

Use Webpilot as a browser tool.

It gives you a local browser runtime, a CLI, and a WebSocket command surface. Your job is not to guess. Your job is to inspect page state, choose a safe action, run it, and verify the result.

**Do not default to screenshots.** Webpilot exposes the live DOM directly. Screenshots are slow, expensive, and unnecessary for most tasks. Use `html`, `discover`, and `q` to read page state. Reserve `ss` for cases where layout or visual rendering is the actual question.

## Setup

Verify the package is installed before doing anything else:

```bash
webpilot --help
```

If `webpilot` is not found, install it first:

```bash
npm install -g h17-webpilot
```

Then run `.help` to list all available commands:

```bash
webpilot -c '.help'
```

## Runtime

```bash
webpilot start
webpilot start -d
```

If the runtime is already running, use `webpilot -c '...'` directly.

Use `webpilot start -d` when you want an append-only session log.

- default path: `~/h17-webpilot/webpilot.log`
- config override: `framework.debug.sessionLogPath`

## Operating Loop

Use this order every time:

1. Inspect.
2. Act.
3. Verify.

Do not skip the inspect step unless you already have fresh page state from the immediately preceding command.

## Inspect

Use these first:

- `webpilot -c 'html'`: read the current page DOM, title, and URL
- `webpilot -c 'discover'`: list interactive elements and their handles
- `webpilot -c 'q <selector>'`: query specific elements
- `webpilot -c 'wait <selector>'`: wait for a known state change
- `webpilot -c 'ss'`: last resort — only when layout or visual rendering is the actual question, not DOM structure

## Act

Use the safest matching action:

- `webpilot -c 'click <selector|handleId>'`
- `webpilot -c 'type [selector] <text>'`
- `webpilot -c 'clear <selector>'`
- `webpilot -c 'key <name>'`
- `webpilot -c 'sd [px] [selector]'`
- `webpilot -c 'su [px] [selector]'`
- `webpilot -c 'go <url>'`
- `webpilot -c 'cookies load ./cookies.json'` when the task requires restoring an existing session

`click` goes through the human action pipeline. If the runtime refuses the action, respect the refusal and re-inspect the page.

## Verify

After navigation or interaction, confirm the new state:

- `webpilot -c 'wait <selector>'`
- `webpilot -c 'url'`
- `webpilot -c 'title'`
- `webpilot -c 'html'`
- `webpilot -c 'q <selector>'`

## Safe Usage Rules

- Never guess selectors when `html` or `discover` can tell you the real ones.
- Never assume a click worked. Verify it.
- Never treat `{ "clicked": false }` as something to brute-force through.
- Never confuse DOM reading with interaction. Read first, then act.
- Re-query stale handles instead of reusing them blindly.

## Raw Protocol

If you need a protocol action that the shorthand CLI does not expose directly, send it through raw mode:

```bash
webpilot -c 'dom.queryAllInfo {"selector": "a[href]"}'
webpilot -c 'human.scroll {"selector": ".feed", "direction": "down"}'
webpilot -c 'framework.getConfig {}'
```

You can also send a full JSON message:

```bash
webpilot -c '{"action": "tabs.navigate", "params": {"url": "https://example.com"}}'
```

## Strategy Notes

- Prefer `html`, `discover`, and `q` over `eval` when DOM inspection is enough.
- Use `wait` after page-changing actions.
- Use handle IDs when you already have a fresh element from `discover` or `q`.
- Use screenshots when layout or visibility is the uncertainty, not HTML structure.
- If the task needs a preloaded authenticated session, load cookies first or use config boot commands.

## MCP Server

An MCP adapter is available for environments that support the Model Context Protocol (e.g. Claude Desktop, Cursor, Windsurf).

Claude Desktop config (`~/Library/Application Support/Claude/claude_desktop_config.json`):

```json
{
  "mcpServers": {
    "webpilot": {
      "command": "npx",
      "args": ["webpilot-mcp"]
    }
  }
}
```

The MCP server connects to the same WebSocket runtime (`ws://localhost:7331`). Start the runtime first with `webpilot start`, then the MCP tools become available in the host application automatically.

## Limits

- Public defaults are generic and uncalibrated.
- This tool does not give you task strategy, retries, route doctrine, or tuned behavior profiles.
- Advanced outcomes depend on how well you choose selectors, waits, verification steps, and configuration.

登录后下载/点赞/收藏 ❤ 2 | ★ 0

webpilot

目录结构

SKILL.md

举报内容

提示