Read, Search & Extract Web Pages by Dokobot

Read and extract content from any web page using a real Chrome browser — including SPAs, JavaScript-rendered sites, and complex dynamic pages. Use when fetch...

Security Scan

The skill's requirements and runtime instructions are coherent with its stated purpose (driving a local or cloud Dokobot Chrome session); nothing requested or instructed appears unrelated or excessive, though the functionality inherently involves sensitive browser data and extension permissions that you should review before use.

Purpose & Capability

Name and description match the declared runtime needs: the skill requires the dokobot CLI and (optionally) a DOKO_API_KEY for remote mode. No unrelated binaries or credentials are requested.

Instruction Scope

SKILL.md consistently instructs the agent to run dokobot CLI commands and to use a browser extension/bridge. It does not ask the agent to read unrelated system files or secrets. Important caveat: the skill's purpose is to read pages from your real browser, including pages behind authenticated sessions — that implies the extension/bridge will have access to cookies/page content; this is expected but sensitive.

Install Mechanism

This is an instruction-only skill (no install spec). The doc tells users to run npm install -g @dokobot/cli and to install a Chrome extension/bridge. Nothing is automatically downloaded or executed by the skill itself.

Credentials

The skill declares no required env vars and only an optional DOKO_API_KEY for remote mode, which is proportional. However, functionality requires browser-session access (cookies/auth) via the extension, which is sensitive even though it's not an environment variable.

Persistence & Privilege

always:false and normal agent invocation settings. The skill does not request permanent inclusion or make claims about modifying other skills or system-wide settings.

Assessment

This skill appears internally consistent, but review these points before installing: (1) Dokobot works by accessing your real Chrome session — the extension/bridge can read page content and authenticated sessions, so avoid using it with accounts or pages you don't want exposed. (2) Prefer local mode (dokobot install-bridge and --local) if you want to avoid sending data to the cloud. (3) If using remote mode, inspect the CLI and extension source on the linked GitHub to verify encryption claims and scope of data sent; limit the DOKO_API_KEY scope if possible. (4) Be cautious when installing global npm packages and browser extensions; check permissions and reviews. (5) If you need stronger assurance, ask the publisher for a cryptographic proof of the CLI/extension build or a security whitepaper, or run the CLI in an isolated environment first.

Dokobot — Read Web Pages with a Real Browser

Read, extract, and search web content through a real Chrome browser session. Unlike headless scrapers, Dokobot uses your actual browser with full JavaScript rendering — so it works on SPAs, dynamic sites, and complex web applications.

Also useful for multilingual tasks: translate web pages (网页翻译), summarize articles (文章总结), and extract content (内容提取) in any language. Supports web search (联网搜索) and reading from social platforms like Twitter/X, Reddit, YouTube, GitHub, LinkedIn, Facebook, Instagram, WeChat articles (微信公众号), Weibo (微博), Zhihu (知乎), Xiaohongshu (小红书), and Bilibili (B站).

Supports two modes: local (free, unlimited, via local bridge) and remote (via cloud API with DOKO_API_KEY).

Prerequisites

• @dokobot/cli installed globally (npm install -g @dokobot/cli)
• Chrome browser with Dokobot extension installed
• For local mode: bridge installed (dokobot install-bridge)
• For remote mode: DOKO_API_KEY set via dokobot config, Remote Control enabled in extension
• If no API Key is set, ask the user to create one at the Dokobot dashboard: https://dokobot.ai/dashboard/api-keys, then run dokobot config

Discovering commands

Run dokobot doko --help to list available commands. Run dokobot doko <command> --help to see full usage, flags, and defaults for any command.

dokobot doko --help
dokobot doko read --help
dokobot doko search --help

Always refer to --help output for the authoritative list of parameters and defaults. Do NOT assume flags or defaults from memory.

Core commands

Command	Description	Example
read <url>	Read a web page and return text	dokobot doko read 'https://example.com'
search <query>	Web search	dokobot doko search 'latest news'
list	List connected devices	dokobot doko list
close-session <id>	Close an active read session	dokobot doko close-session <SESSION_ID>

Behavioral guidance

These are things --help does not cover:

Local vs Remote mode

• --local: Free and unlimited. Reads through the local bridge without any server. Requires dokobot install-bridge and Chrome with the extension.
• Remote (default): Reads through the cloud API. Requires DOKO_API_KEY and Remote Control enabled in the extension.
• Prefer --local when the user has Chrome open locally. Use remote when accessing browsers on other machines.

Session continuity

When a read result includes canContinue and sessionId, pass the session ID to continue reading from where it stopped:

dokobot doko read '<URL>' --session-id <SESSION_ID> --screens 5

Close a session explicitly with:

dokobot doko close-session <SESSION_ID>

Concurrency

Multiple read requests can run in parallel (each opens a separate browser tab). Recommended maximum: 5 concurrent calls.

Error handling

• 401: Invalid API Key — ask user to check DOKO_API_KEY
• 403: API Key scope insufficient
• 422: Operation failed or was cancelled by user (read only)
• 503: No extension connected (read only) — check read command requirements
• 504: Timed out — retry with a longer --timeout

Troubleshooting

If a command fails unexpectedly, check the CLI version and update if needed:

dokobot --version
dokobot update

Security & Permissions

• Local-first architecture: In local mode (--local), all data flows directly between the CLI and your browser via a local Unix socket. No data leaves your machine.
• End-to-end encryption: In remote mode, page content is encrypted on the browser before transmission and decrypted only on the CLI. The server never sees plaintext page content.
• Open source CLI: The @dokobot/cli package is fully open source at https://github.com/nicepkg/dokobot. Inspect the code to verify data handling.
• User-provisioned credentials: DOKO_API_KEY is created and managed by the user. The skill never generates, stores, or exfiltrates credentials.
• Explicit opt-in: Remote Control must be manually enabled in the browser extension by the user. Local mode requires no API key or server.
• Read-only by default: the read and search commands only extract content. They do not modify pages, submit forms, or execute scripts.