JPeetz/agent-skills / skills/documentation-content/read-x-articles
read-x-articles
VerifiedUse this skill when a user drops an x.com or twitter.com URL (especially an X Article like /i/article/ID) and expects it read, or says "read this X post/article/thread" in any AI coding agent. Resolves the canonical /i/article/ID URL (which serves plain text) instead of giving up on the login/JS wall that hits profile and /status/ pages. Includes browser-tool and API fallbacks.
| File | Kind | Size |
|---|---|---|
| CHANGELOG.md | markdown | 742 B |
| LICENSE | other | 1.0 KB |
| SKILL.md | skill md | 5.2 KB |
| evals/evals.json | config | 1.9 KB |
| references/url-forms.md | markdown | 1.9 KB |
| scripts/read_x_article.py | script | 2.5 KB |
references/url-forms.md
View on GitHub# Reading X Articles — reference
## URL forms and what they give you
| URL form | Render-capable extractor | Bare `curl`/`urllib` | Note |
|---|---|---|---|
| `https://x.com/i/article/<ID>` | ✅ FULL body | ⚠️ often login shell | **Use this URL + a render tool.** |
| `https://x.com/<handle>/status/<id>` | ❌ wall | ❌ wall | Post page; not the article body. |
| `https://x.com/<handle>` | ⚠️ recent-post list only | ❌ wall | Profile page; discovery only. |
| `twitter.com/...` (legacy) | Same as x.com | Same | Redirects; treat identically. |
> **Key nuance (learned 2026-08-12):** the canonical `/i/article/<ID>` URL is
> necessary but a *plain* HTTP fetch (urllib/curl) can still return a
> login/JS shell. Use a JS-executing extractor (agent-grade `web_extract`) or a
> browser render to get the real body. Do not conclude the article is
> unreadable because a bare curl returned a shell.
## How to find the article ID from a status/share
- When a post IS an X Article, the author's "share" or article card points at
`/i/article/<article_id>`.
- The status URL for an article-share post may carry the article link in its
quote/attachment; fetch the status with a browser, or find the author's
article card on their profile.
- If you only have a `/status/` post, prefer asking the user for the article
link, or resolve it via a browser render.
## Fallback order (when plain `fetch`/`web_extract` fails)
1. Straight `web_extract`/fetch on `/i/article/<ID>` (works for the vast majority).
2. Browser tool to render the JS page, then read the DOM/rendered text.
3. X API (e.g. `xurl`): query the article tweet and read
`data.article.plain_text`.
## Validation checklist
- [ ] Returned text contains the article's real thesis and body paragraphs
(not just a title + "Log in or sign up for X").
- [ ] Paper length is plausible (essays return 1,000+ words of prose).
- [ ] The exact URL read is reported so the user can verify.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |