OpenWeb

v0.1.5

Typed JSON access to 90+ real websites — Google, Amazon, Reddit, YouTube, GitHub, Instagram, Bloomberg, Zillow, and more — across search, shopping, travel, f...

⭐ 1· 148·0 current·0 all-time

by@imoonkey

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for imoonkey/openweb.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "OpenWeb" (imoonkey/openweb) from ClawHub.
Skill page: https://clawhub.ai/imoonkey/openweb
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: OPENWEB_HOME
Required binaries: openweb
Config paths to check: $OPENWEB_HOME/config.json
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install openweb

ClawHub CLI

Package manager switcher

npx clawhub@latest install openweb

Security Scan

Capability signals

CryptoRequires walletCan make purchasesRequires OAuth tokenRequires sensitive credentials

These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.

VirusTotal

Benign

View report →

OpenClaw

Benign

medium confidence

✓

Purpose & Capability

Name/description (typed JSON access to many websites) aligns with what the skill requests: a local 'openweb' CLI, an OPENWEB_HOME config, and per-site packages. The Node install spec (@openweb-org/openweb) and the CLI binary requirement are proportionate to the stated purpose.

ℹ

Instruction Scope

SKILL.md instructs the agent to control a managed browser (CDP), read browser state (cookies, localStorage, window globals), inject tokens into page.evaluate(fetch(...)), capture HARs, and run read/write operations. These behaviors are expected for a site automation/adapter tool, but they are sensitive: the instructions explicitly describe extracting auth tokens and performing write actions (likes, follows, posts). The doc does include safety guidance (permission tiers, prompting for writes), but the agent will have access to browser sessions and can perform actions as the logged-in user if allowed.

ℹ

Install Mechanism

Install is via npm package @openweb-org/openweb which produces the 'openweb' binary — a plausible and expected mechanism. NPM installs are a moderate risk compared to instruction-only skills because arbitrary code will be installed; verify the package source (repository, maintainer) before installing.

ℹ

Credentials

Requires OPENWEB_HOME and a config file $OPENWEB_HOME/config.json, which is reasonable for a tool that needs site configs and permission settings. However, the config and the runtime browser access are sensitive: config.json may contain permission flags/overrides and the runtime will access cookies/localStorage and possibly secrets in your browser profile. No unrelated cloud credentials are requested, which is good.

✓

Persistence & Privilege

The skill is not 'always:true' and is user-invocable; autonomous invocation is allowed by platform default but not flagged here. The skill's runtime behavior does not request to modify other skills or system-wide agent settings. Normal install behavior (writing binaries) is declared in the npm install spec.

Assessment

This skill is coherent with its stated purpose (a CLI that drives a browser to read and interact with many websites), but it operates at a high privilege level: it expects to control a managed Chrome session, read cookies/localStorage/window globals, and can perform write actions on sites as your logged-in user. Before installing or enabling: - Inspect the npm package and upstream repository (https://github.com/openweb-org/openweb and https://getopenweb.com). Confirm the publisher and review recent code or package contents if possible. - Review $OPENWEB_HOME/config.json after installation before running: check for any surprising settings or embedded secrets, and keep this directory isolated (use a directory dedicated to openweb). - Consider running the CLI in a disposable environment or with an isolated browser profile (not your primary browser or profile) so captures and token reads don't touch your main sessions. - Treat write operations with caution: the docs say writes should prompt; keep an eye out for prompts and audit any agent actions that perform mutations. Avoid giving the agent blanket consent to run writes autonomously. - If you cannot audit the npm package source, avoid installing it on sensitive systems or provide it only to low-privilege test environments. If you want, I can: (1) list concrete checks to run on the npm package before install, (2) suggest a safe runtime setup (isolated Chrome profile, limited OPENWEB_HOME), or (3) help craft a minimal config.json template that avoids storing secrets.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

Binsopenweb

EnvOPENWEB_HOME

Config$OPENWEB_HOME/config.json

Install

Node

Bins: openweb

npm i -g @openweb-org/openweb

Links

Homepagehttps://getopenweb.com

Repositoryhttps://github.com/openweb-org/openweb

latestvk971ygecahtny7h2tm8c9th0qd85b3r4

148downloads

1stars

4versions

Updated 4d ago

v0.1.5

MIT-0

OpenWeb

Agent-native way to access any website. Bridging agent CLI and web GUI through API.

Load Discipline

Do not read every file in this folder.
Start with SKILL.md. Follow one route at a time.

Use Existing Site

1. Find the site

openweb sites                        # list all available sites

If the site has no package, do NOT say "unsupported." Route to add-site/guide.md.

2. Check readiness

openweb <site>                       # transport, auth, operations list

Requires browser: yes — browser auto-starts when needed; no manual setup required
Requires login: yes — user must be logged in via their browser session

3. Read site notes

Prefer site docs when they exist in your workspace:

Source repo: read src/sites/<site>/SKILL.md for workflows and intent mapping, then src/sites/<site>/DOC.md for internals.
Shipped/runtime package: only DOC.md, specs, manifest, examples, and adapters are guaranteed. Per-site SKILL.md and PROGRESS.md are source-tree docs and are not shipped into $OPENWEB_HOME/sites/<site>/.

If only the shipped package is available, rely on openweb <site>, openweb <site> <op>, examples, and DOC.md.

4. Inspect the operation

openweb <site> <op>                  # params, response shape, permission tier
openweb <site> <op> --example        # real example params from fixtures

Check the operation's permission tier before executing:

Tier	Default	Behavior
`read`	allow	GET-like operations — execute freely
`write`	prompt	Creates/updates — ask user before executing
`delete`	prompt	Destructive — ask user before executing
`transact`	deny	Financial/irreversible — always skip

5. Execute

openweb <site> <op> '{"key":"value"}'    # stdout=JSON, stderr=JSON error

Auto-spill: responses over 4096 bytes write to a temp file.

openweb <site> exec <op> '{...}' is equivalent — exec can be omitted when the third arg is JSON.

6. On failure

Errors on stderr include failureClass:

failureClass	Action
`needs_browser`	Browser auto-starts; if it fails, check Chrome installation. Fallback: `openweb browser start`
`needs_login`	`openweb login <site>` then `openweb browser restart`
`needs_page`	Open a tab to the site URL
`bot_blocked`	`openweb browser restart --no-headless`, user solves CAPTCHA in visible browser, then retry. For persistent sites, set `"browser": {"headless": false}` in config
`permission_denied`	Update `permissions` in `$OPENWEB_HOME/config.json`
`permission_required`	Ask user for confirmation, then retry
`retriable`	Wait a few seconds, retry (max 2)
`fatal`	Don't retry — fix params or check site name

If the table above doesn't resolve it, read references/troubleshooting.md.

7. Missing site or coverage

Site doesn't exist or lacks needed operations? Read add-site/guide.md.

Add / Expand / Upgrade Site

Read add-site/guide.md

Fix a Problem

Read references/troubleshooting.md

File Map

All paths relative to skills/openweb/.

add-site/ (workflow — load in sequence)

File	Load when
`add-site/guide.md`	Entry point for add/expand workflow
`add-site/probe.md`	Probe step: CDP browser-side discovery
`add-site/capture.md`	Capture step: recording browser traffic
`add-site/review.md`	Review step: reading analysis-summary.json
`add-site/curate-operations.md`	Curate: naming, noise, params, permissions
`add-site/curate-runtime.md`	Curate: auth, transport, extraction
`add-site/curate-schemas.md`	Curate: response schemas, examples, PII
`add-site/verify.md`	Verify: runtime + spec + doc loop
`add-site/document.md`	Document: per-site SKILL.md + DOC.md + PROGRESS.md, knowledge updates

references/ (lookup — load independently)

File	Load when
`references/cli.md`	CLI command syntax, flags, stdout/stderr
`references/x-openweb.md`	Full x-openweb field schema
`references/troubleshooting.md`	Something broke — classify, diagnose, fix

knowledge/ (patterns — load at decision points)

File	Load when
`knowledge/archetypes.md`	Expected operations by site category
`knowledge/auth-routing.md`	Auth type unknown — signal-to-family lookup
`knowledge/auth-primitives.md`	Configuring auth — config and gotchas
`knowledge/bot-detection.md`	Transport/capture decisions
`knowledge/extraction.md`	Extraction signals — SSR/DOM patterns
`knowledge/graphql.md`	GraphQL — persisted queries, batching
`knowledge/ws.md`	WebSocket — message/connection patterns
`knowledge/adapter-recipes.md`	Adapter patterns, code templates, pitfalls
`knowledge/transport-upgrade.md`	Transport tier decisions, node feasibility, API discovery

Comments

Loading comments...