Agent skill · Data & Analytics

social-fetch

When you or another skill needs to fetch the content of a social media post by URL — tweet, X thread, LinkedIn post, Instagram post, TikTok video, Bluesky post, Reddit thread, Mastodon status, Threads post, Hacker News thread. Returns normalized structured data (author, posted_at, text, engagement counts, media URLs, replies if requested) regardless of platform. Tries strategies in order: direct API (Bluesky, Mastodon, HN, Reddit), agent-browser with modal dismissal (LinkedIn, X preview), Wayback Machine (older posts), paid APIs (ScrapeCreators / Apify — only if env keys present). Triggers on

coreyhaines31github.com/coreyhaines31GitHub ↗
claude-codeMIT
Install
npx skills add coreyhaines31/makerskills --skill social-fetch --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 7 KB
Bundled scripts: none
Version: 0.1.1
Path: skills/social-fetch/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 500

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# /social-fetch — Pull any social post by URL Normalized fetcher for social posts across platforms. Detects platform from URL, tries strategies in order, returns the same JSON shape regardless of source. ## Step 1 — Detect platform | URL pattern | Platform | |---|---| | `x.com/<user>/status/<id>` or `twitter.com/<user>/status/<id>` | **x** (Twitter) | | `linkedin.com/posts/<slug>` or `linkedin.com/feed/update/urn:li:activity:<id>` | **linkedin** | | `linkedin.com/in/<handle>` (profile, recent activity) | **linkedin-profile** | | `instagram.com/p/<id>` or `instagram.com/reel/<id>` | **instagram** | | `tiktok.com/@<user>/video/<id>` | **tiktok** | | `bsky.app/profile/<handle>/post/<rkey>` | **bluesky** | | `reddit.com/r/<sub>/comments/<id>/...` | **reddit** | | `<mastodon-instance>/@<user>/<id>` (e.g. mastodon.social, hachyderm.io) | **mastodon** | | `threads.net/@<user>/post/<id>` | **threads** | | `news.ycombinator.com/item?id=<id>` | **hn** | | `youtube.com/watch?v=<id>` or `youtu.be/<id>` | → defer to `watch-video` | If the URL doesn't match any pattern, ask the user what platform it is. ## Step 2 — Pick strategy chain Read `references/strategies.md` for the per-platform strategy

What's inside
Steps it walks through
  1. Step 1 — Detect platform
  2. Step 2 — Pick strategy chain
  3. Step 3 — Execute strategy
  4. Step 4 — Normalize output
  5. Step 5 — Optional enrichments
  6. Step 6 — Cache (optional)
  7. Composes with
  8. Known limits
  9. Notes on quality
Ships with 3 files
  • references/auth-keys.md
  • references/output-schema.md
  • references/strategies.md
More from makerskills
All skills →
About this skill
What does the social-fetch skill do?

When you or another skill needs to fetch the content of a social media post by URL — tweet, X thread, LinkedIn post, Instagram post, TikTok video, Bluesky post, Reddit thread, Mastodon status, Threads post, Hacker News thread. Returns normalized structured data (author, posted_at, text, engagement counts, media URLs, replies if requested) regardless of platform. Tries strategies in order: direct API (Bluesky, Mastodon, HN, Reddit), agent-browser with modal dismissal (LinkedIn, X preview), Wayback Machine (older posts), paid APIs (ScrapeCreators / Apify — only if env keys present). Triggers on

How do I install it?

Run `npx skills add coreyhaines31/makerskills --skill social-fetch --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From coreyhaines31/makerskills, a repository with 500 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going