Skills browser-read-x

Name: browser-read-x
Author: openclaw

Extract the main X/Twitter post or article content from a page that is already open in the browser (using browser act evaluate).

install

source · Clone the upstream repo

git clone https://github.com/openclaw/skills

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/bill492/browser-read-x" ~/.claude/skills/openclaw-skills-browser-read-x && rm -rf "$T"

OpenClaw · Install into ~/.openclaw/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.openclaw/skills && cp -r "$T/skills/bill492/browser-read-x" ~/.openclaw/skills/openclaw-skills-browser-read-x && rm -rf "$T"

manifest: skills/bill492/browser-read-x/SKILL.md

browser-read-x

Site-specific extractor for X/Twitter. It is tuned to return the central post/article content while filtering UI chrome such as sidebars, trends, login/signup prompts, reaction metrics, and article footer/promotional blocks.

Use case

```
web_fetch
```
is noisy or blocked (auth-required/public X/X-protected pages).
You need tweet/article text from an already-open X page in browser.
You specifically want the main status/article body, not sidebar or CTAs.

How to use

Navigate to the URL with
```
browser navigate
```
(or ensure the page is already open).

Run

browser act

with

kind="evaluate"

and pass the contents of

skills/browser-read-x/extract.js

fn

The script returns:
- ```
title
```
- ```
content
```
  (plain markdown-ish text with reduced X UI noise)
- ```
excerpt
```
- ```
byline
```
- ```
siteName
```
- ```
length
```
- ```
url
```

Example

{
  "action": "act",
  "kind": "evaluate",
  "targetId": "...",
  "fn": "(() => { ... })()"
}

Notes

Self-contained and safe to pass directly as JS to
```
browser act
```
.
The script prefers the specific status/article node on X and falls back to generic article/main selection if that fails.
For non-X pages it still behaves similarly to the generic extractor (best-effort cleanup + markdownish text conversion).