Agent skill · Data & Analytics

threads-user-posts

Fetches public posts from a Threads user's profile page, extracting post text, engagement metrics, and media info from SSR-embedded JSON. Use when user asks to scrape Threads posts, get someone's Threads feed, pull posts from a Threads account, collect Threads content by username, download Threads user posts, extract Threads profile posts, monitor a Threads user's activity, retrieve recent posts from a Threads handle, gather Threads post data for a creator, or fetch all posts from a specific Threads profile.

browser-actgithub.com/browser-actGitHub ↗
claude-codecodexcursorships scriptsMIT
Install
npx skills add browser-act/skills --skill threads-user-posts --agent claude-code

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

Facts
Files in the skill folder: 3
SKILL.md size: 9 KB
Bundled scripts: yes
Path: solutions/social-listening/threads-user-posts/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 5,160
Language: Python
Read our review of the source →

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

From the SKILL.md

# Threads — User Posts > username → list of public posts with engagement metrics (SSR + scroll pagination) ## Language All process output to user (progress updates, process notifications) follows the user's language. ## Objective Extract public posts from a given Threads user's profile page using SSR-embedded JSON data, with optional scroll-triggered pagination to load more posts. ## Prerequisites - A browser is open and connected via browser-act - **Login recommended**: Threads enforces a login wall on profile pages in most regions as of mid-2026. A logged-in browser session is required for reliable access. Unauthenticated access via US-based proxies may work in some configurations but is not guaranteed. ## Pre-execution Checks ### 1. Tool Readiness If browser-act has been confirmed available in the current session → skip this step. Invoke `browser-act` via Skill tool to load usage. If installation or configuration issues arise, follow its guidance to resolve then retry. ### 2. Login Verification If login status for Threads has been confirmed in the current session → skip this step. Otherwise: `navigate https://www.threads.com` and check page state: - User avatar or username visib

What's inside
Steps it walks through
  1. Language
  2. Objective
  3. Prerequisites
  4. Pre-execution Checks
  5. 1. Tool Readiness
  6. 2. Login Verification
  7. Capability Components
  8. SSR: Extract posts from profile page (initial load)
  9. DOM: Scroll to trigger more posts
  10. Composite: Full profile post collection (SSR + scroll pagination)
  11. Pagination
  12. Success Criteria
  13. Known Limitations
  14. Execution Efficiency
Ships with 2 files
  • scripts/extract-posts.py
  • scripts/scroll-load-more.py
More from skills
All skills →
About this skill
What does the threads-user-posts skill do?

Fetches public posts from a Threads user's profile page, extracting post text, engagement metrics, and media info from SSR-embedded JSON. Use when user asks to scrape Threads posts, get someone's Threads feed, pull posts from a Threads account, collect Threads content by username, download Threads user posts, extract Threads profile posts, monitor a Threads user's activity, retrieve recent posts from a Threads handle, gather Threads post data for a creator, or fetch all posts from a specific Threads profile.

How do I install it?

Run `npx skills add browser-act/skills --skill threads-user-posts --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 browser-act/skills, a repository with 5,160 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