skills/x-scan/SKILL.md
Scan X (Twitter) for posts from a user, search results, or single-tweet fetches. Uses FXTwitter (no auth) for single tweets. Returns findings without vault persistence. Sibling to llm-wiki/ingest-tweet.
npx skillsauth add RonanCodes/ronan-skills x-scanInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Pull posts from X / Twitter and return distilled findings. No file writes.
/ro:x-scan https://x.com/user/status/1234567890 # one tweet, full text
/ro:x-scan @karpathy --limit 20 # recent posts by user
/ro:x-scan "search:agent observability" # topic search
FXTwitter — free, no auth, returns full text including long "note tweets":
curl -s "https://api.fxtwitter.com/{user}/status/{id}"
Return: tweet.text, author (name @screen_name), created_at, likes/retweets/replies, quoted tweet if any, media URLs if any.
Strip ?s=46&t=... tracking params from the input URL before parsing.
@user)FXTwitter doesn't expose timelines without auth. Options in order of preference:
https://nitter.net/{user}/rsshttps://nitter.poast.org/{user}/rsshttps://nitter.privacyredirect.com/{user}/rsscurl ... | xmllint --xpath '//item' or a simple sed pipeline. Extract title (= tweet text preview), pubDate, and the tweet URL from <link>./ro:x-scan can fall back to the single-tweet fetch if the caller wants full content.If all mirrors fail, report that clearly and suggest the caller either paste specific tweet URLs or switch to /ro:hn-scan / /ro:linkedin-scan.
search:<topic>)Same Nitter fallback as above with /search?q={encoded-topic}&f=tweets — again, mirrors are flaky. If the caller has access to the paid X API, prefer that (check for X_API_BEARER env var and use https://api.x.com/2/tweets/search/recent if set).
# X scan: <target> (<N> results)
1. @<screen_name> (<likes>♥ <retweets>↻ · <time ago>)
<tweet text, stripped of t.co links>
https://x.com/<user>/status/<id>
2. ...
For single-tweet mode include the full text, not a truncation.
If Nitter is all down AND the caller needs timeline/search, the firefox-cookies skill can extract X session cookies for authenticated scraping. This is brittle (layout-dependent) — only fall back to it when the free paths are exhausted and the caller has explicitly opted in.
curl — alwaysxmllint (from libxml2) — for RSS parsing, optionalfirefox-cookies skill — optional last-resort fallbackllm-wiki/.claude/skills/ingest-tweet — persists single tweets into a vault. Use when you want to keep a tweet long-term./ro:trend-scan — orchestrator running x-scan alongside hn-scan, linkedin-scan, reddit-scan./ro:hn-scan, /ro:linkedin-scan, /ro:reddit-scan.testing
--- name: linear-pipeline description: The Fable orchestrator for a single dispatched Linear ticket. Holds almost no context itself; it receives `--issue <ID> --detached`, decides the stage sequence, and fans out a sub-agent per stage, passing forward only each stage's artifact (never re-derived, never inlined into its own context). Step zero, before any planning or stage routing, is a boundary triage against `canon/security-boundary.md` (#199): a match tags Ronan Connolly and stops the run, no
development
--- name: in-your-face description: Capture a chat-only answer into a durable artifact (markdown + HTML, PDF when cheap) and launch it automatically so the user cannot miss it. Use when user says "in your face", "don't let me lose this", "save that answer", "make that durable", or right after answering a substantive side question (a recipe, comparison, how-to, or generated prompt) that would otherwise die with the context. category: workflow argument-hint: [--no-open] [--vault <short>] [hint of
tools
One-shot headless OpenAI Codex CLI calls for background/admin AI tasks — summaries, classification, extraction, admin glue. The default engine for anything that runs AI constantly in the background (daemon-driven, per-event), because it bills the flat ChatGPT subscription instead of Claude usage or per-token API spend, and it keeps working while Claude is rate-limited. NEVER for coding — coding stays Claude. Use when a skill or daemon needs a cheap always-on AI call, when the user says "use codex", "ask codex", "codex as backup", or when building a background summarizer/classifier into a listener or loop. Reads auth from ~/.codex/auth.json (ChatGPT account, no API key).
research
Turn a warranty rejection, repair quote, or RMA email into a cited decision brief — legal read (NL/EU consumer law), is the part user-serviceable, live part and new-unit prices, repair-vs-DIY-vs-new economics, before-you-send-it checklist, deadlines. Use when the user pastes or screenshots a repair quote, warranty rejection, "not covered" email, onderzoekskosten fee, or asks "should I repair or replace this".