ryanilanoryanilano/ilano-skills/skills/socials-mirror/SKILL.md

socials-mirror

Skill0 starsChanged 49 days agoMITView on GitHub

Snapshot a public figure's public profiles (GitHub, Bluesky, any RSS/Atom feed, Reddit .rss, X posts and threads via embeds and Thread Reader) to local markdown in one command. Use when asked what someone has been posting, building, or writing, or when given an X, Twitter, tweet or thread link to read. Twitter means X: any twitter.com or x.com link, tweet, or thread goes through the X flags. Public data only; no login. Not for a private individual.

In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/humanizer/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- cherrypickerSkill
- copyable-markdownSkill
- deltamaxxSkill
- docs-mirrorSkill
- ffmpegSkill
- humanizerSkill
- prompt-packSkill
- spamcheckSkill
- tool-call-repairSkill
- writing-beatsSkill
- writing-for-agentsSkill
- writing-fragmentsSkill
- writing-shapeSkill
- yt-ccSkill

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Every flag takes a handle or a URL and normalises it.
line 29
Distinctive:
Public only: No login, no cookies, no auth circumvention, no logged-in content.
line 57
Distinctive:
If NetNewsWire is already subscribed to a feed and refreshing it, the full post text is in a local SQLite cache — read that instead of …
line 70

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

socials-mirror

Public figures, public data, one friendly snapshot. Not a stalker tool.

python3 scripts/socials_mirror.py "Ahmad Awais" \
    --github ahmadawais \
    --bsky ahmadawais.com \
    --rss https://www.reddit.com/user/MrAhmadAwais/.rss \
    --x https://x.com/MrAhmadAwais \
    --x-post https://x.com/MrAhmadAwais/status/1234567890123456789 \
    --linkedin https://www.linkedin.com/in/mrahmadawais \
    --out ./socials --json

Then read the files it wrote (last stdout line is the directory): one .md per platform plus index.md, and .json with --json.

Twitter is X. A request that says Twitter, tweet, or twitter.com means the X flags below; --twitter, --tweet and --twitter-thread are accepted as aliases of --x, --x-post and --x-thread, and twitter.com links are rewritten to x.com.

Every flag takes a handle or a URL and normalises it. Share and tracking parameters (utm_*, trk=, s=, fbclid) are stripped from every input, so a sharer's click never lands in a note. --selftest checks this without touching the network.

Flag	Accepts	Becomes
`--github`	`octocat`, `@octocat`, any `github.com/octocat/...` URL	`octocat`
`--bsky`	`alice.com`, `alice` or `@alice` (bsky.social appended), a `bsky.app/profile/...` URL, a DID	handle or DID
`--x`	`@jack`, `jack`, any x.com or twitter.com URL	`https://x.com/jack`, then the author's threads from Thread Reader (`--x-threads N` pulls N in full, default 5, 0 lists only) and any `--x-rss-mirror` that answers
`--x-rss-mirror`	a Nitter-style template, `https://mirror.example/{handle}/rss` (repeatable; `SOCIALS_X_RSS` comma list)	tried in order, first real feed wins. None built in: every public mirror checked 2026-09-23 was down or suspended (xcancel.com: HTTP 451)
`--x-post`	`20`, `x.com/jack/status/20?s=21`, `twitter.com/i/web/status/20` (repeatable)	the post id, then its full text in `x.md`
`--x-thread`	the root post URL or id	every post in the thread, in order, in `x-thread.md`, from Thread Reader's public cache. Not cached there: the root post alone, and stderr says so
`--linkedin`	`jane`, `in/jane`, `company/acme`, any linkedin.com URL	`https://www.linkedin.com/in/jane`
`--rss`	`u/spez`, `r/selfhosted`, a Reddit profile or subreddit URL (`.rss` appended), any feed URL	a feed URL with no tracking

What pulls cleanly, and what doesn't

Source	How	Notes
GitHub	public REST (unauth)	profile + up to 100 repos, sorted by last update
BlueSky	public AppView XRPC (unauth)	profile + ~50 recent posts, full text
RSS/Atom	plain fetch + parse	the clean path for Reddit: `https://www.reddit.com/user/<u>/.rss` or `/r/<sub>/.rss` carries full posts. Also blogs and RSS bridges
X / Twitter	profile: Thread Reader's public author page, plus an RSS mirror if you name one. Named posts: public embed endpoint (unauth)	the timeline is not served without a login (syndication answers 429, public Nitter mirrors are down, RSSHub needs an account cookie). Thread Reader's `threadreaderapp.com/user/<handle>` lists the ~15 most recent threads anyone unrolled there, and each thread is pulled from its public cache. Name posts with `--x-post <url-or-id>` (repeatable) and each is mirrored in full: text, date, author, quoted post, media and links. `--x-thread <root>` pulls a whole thread from threadreaderapp.com's public cache when someone has unrolled it there. A public RSS bridge via `--rss` still works as a feed
LinkedIn	guest view (unauth)	the logged-out profile or company page (the copy search engines index): name, headline, about, location, followers from its JSON-LD, plus the handful of recent posts the page lists, each fetched from its public embed page for the full text. Capped at 8 posts, spaced, stops on a 999 or 429. The timeline beyond that is not public. If LinkedIn answers with its login wall, the link is recorded instead and stderr says so

Rules

Public only. No login, no cookies, no auth circumvention, no logged-in content. A guest page that a site serves to anyone (LinkedIn's logged-out profile, X's embed endpoint) counts as public. If a source needs auth, it becomes a recorded link, not a scrape.
Be friendly, not a stalker. One-shot snapshot of a public figure's public work. No monitoring loop, no aggregating private individuals.
RSS is the kindest and cleanest. One request, full posts. Reddit's own .rss carries the full post, so the OAuth API is never needed for a profile read.
Rate-limit and identify. A User-Agent is set and calls are spaced; do not hammer someone's server for a profile read.

NetNewsWire cache (zero network)

If NetNewsWire is already subscribed to a feed and refreshing it, the full post text is in a local SQLite cache — read that instead of re-fetching.

python3 scripts/nnw_export.py --list                    # every feed + cached count
python3 scripts/nnw_export.py --feed engadget --since 2026-09-01 --out ./feeds --json
python3 scripts/nnw_export.py --all --out ./feeds       # everything (large)

Reads ~/Library/Containers/com.ranchero.NetNewsWire-Evergreen/.../Accounts/*/DB.sqlite3 read-only (safe while NNW is open), maps feed IDs to titles via the account OPML, prefers contentHTML→text. Redacts secrets (?key=/token=/… query params) from every feed URL in output, so a private feed key never leaks. Prefer this over live RSS for any feed you already subscribe to — it's free and offline.

LinkedIn jobs

python3 scripts/linkedin_jobs.py <job-url-or-id> [...]                 # full JD per posting
python3 scripts/linkedin_jobs.py --search "design engineer" --location "New York" -n 25
python3 scripts/linkedin_jobs.py --search "staff product designer" --location Remote -n 10 --full

Reads LinkedIn's logged-out jobs-guest endpoints: the guest job search (ten cards per request, paged to -n) and the guest copy of a posting, which carries the full description plus seniority, employment type, job function and industries. LinkedIn throttles guests after a burst — the run stops on the first HTTP 999 or 429 instead of digging in. Public-only, no login and no cookie, same rule as the rest of this skill. --selftest checks the job-id parser.

Requirements

python3, standard library only. macOS for the NetNewsWire reader (path is NNW's macOS container).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free