unbrowse
Analyze any website's network traffic and turn it into reusable API skills backed by a shared marketplace. Skills discovered by any agent are published, scored, and reusable by all agents. Capture network traffic, discover API endpoints, learn patterns, execute learned skills, and manage auth for gated sites. Use when someone wants to extract structured data from a website, discover API endpoints, automate web interactions, or work without official API documentation.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/cnm-byd/unbrowse-openclawUnbrowse — Drop-in Browser Replacement for Agents
Browse once, cache the APIs, reuse them instantly. First call discovers and learns the site's APIs (~20-80s). Every subsequent call uses cached skills (<200ms for server-fetch, ~2s for sites requiring browser execution).
IMPORTANT: Always use the CLI (bun src/cli.ts). NEVER pipe output to node -e, python -c, or jq — this causes shell escaping failures. Use --path, --extract, and --limit flags instead.
Server Startup
cd ~/.agents/skills/unbrowse && bun src/cli.ts health
If not running, the CLI auto-starts the server. First time requires ToS acceptance — ask the user:
Unbrowse needs you to accept its Terms of Service:
- Discovered API structures may be shared in the collective registry
- You will not use Unbrowse to attack, overload, or abuse any target site Full terms: https://unbrowse.ai/terms
After consent, the CLI handles startup automatically. First run also needs the browser engine:
cd ~/.agents/skills/unbrowse && npx agent-browser install
Core Workflow
Step 1: Resolve an intent
cd ~/.agents/skills/unbrowse && bun src/cli.ts resolve \
--intent "get feed posts" \
--url "https://www.linkedin.com/feed/" \
--pretty
This returns available_endpoints — a ranked list of discovered API endpoints. Pick the right one by URL pattern (e.g., MainFeed for feed, HomeTimeline for tweets).
Step 2: Execute with extraction
cd ~/.agents/skills/unbrowse && bun src/cli.ts execute \
--skill {skill_id} \
--endpoint {endpoint_id} \
--path "data.included[]" \
--extract "author:actor.name.text,text:commentary.text.text,posted:actor.subDescription.text" \
--limit 20 \
--pretty
This is the key pattern — --path + --extract + --limit replace ALL piping to jq/node/python.
Step 3: Submit feedback (MANDATORY)
cd ~/.agents/skills/unbrowse && bun src/cli.ts feedback \
--skill {skill_id} \
--endpoint {endpoint_id} \
--rating 5 \
--outcome success
Rating: 5=right+fast, 4=right+slow(>5s), 3=incomplete, 2=wrong endpoint, 1=useless.
Data Extraction Flags
These flags eliminate the need to pipe output to any external parser:
| Flag | Example | What it does |
|---|---|---|
--path | "data.home.timeline.instructions[].entries[]" | Drill into nested response using dot-paths with [] array expansion |
--extract | "user:core.user.name,text:legacy.full_text" | Pick specific fields with alias:path mapping |
--limit | 10 | Cap array output to N items |
--pretty | (boolean) | Indented JSON output |
--raw | (boolean) | Skip extraction recipes, return unprocessed data |
When these flags are used, trace metadata is slimmed automatically (1MB raw -> 1.5KB output typical).
Examples
# X timeline — extract tweets with user, text, likes
b...
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-cnm-byd-unbrowse-openclaw": {
"enabled": true,
"auto_update": true
}
}
}