Agent skill · Content & Marketing

threads-keyword-search

Searches Threads posts by keyword or hashtag and returns matching posts with engagement metrics, extracted from SSR-embedded JSON. Use when user asks to search Threads posts, find Threads content by topic, scrape Threads search results, collect Threads posts about a keyword, monitor Threads hashtag activity, pull Threads posts mentioning a term, gather Threads content by hashtag, search for posts on Threads, extract Threads search feed, get trending posts on Threads, find Threads discussions about a subject, or fetch recent or top Threads posts by keyword.

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

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

Facts
Files in the skill folder: 2
SKILL.md size: 6 KB
Bundled scripts: yes
Path: solutions/social-listening/threads-keyword-search/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 — Keyword & Hashtag Search > keyword + sort filter → list of matching posts with engagement metrics ## Language All process output to user (progress updates, process notifications) follows the user's language. ## Objective Search Threads for posts matching a keyword or hashtag and extract the results from SSR-embedded JSON, with support for top/recent sort ordering. ## Prerequisites - A browser is open and connected via browser-act - No login required for public search results (unauthenticated: typically 17-18 results per query, no pagination) ## 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. ## Capability Components > This Skill's operational boundary = what the user can manually do in their browser. It only reads data already displayed to the user on the page. JS code is encapsulated in Python files under the `scripts/` directory, invoked via `eval "$(python scripts/xxx.py {params})"`. `$(...)` is bash syntax; it is recommended to use the bash tool for

What's inside
Steps it walks through
  1. Language
  2. Objective
  3. Prerequisites
  4. Pre-execution Checks
  5. 1. Tool Readiness
  6. Capability Components
  7. SSR: Extract keyword search results
  8. SSR: Hashtag search
  9. Enum Parameters
  10. Pagination
  11. Success Criteria
  12. Known Limitations
  13. Execution Efficiency
  14. Experience Notes
Ships with 1 file
  • scripts/extract-search-results.py
More from skills
All skills →
About this skill
What does the threads-keyword-search skill do?

Searches Threads posts by keyword or hashtag and returns matching posts with engagement metrics, extracted from SSR-embedded JSON. Use when user asks to search Threads posts, find Threads content by topic, scrape Threads search results, collect Threads posts about a keyword, monitor Threads hashtag activity, pull Threads posts mentioning a term, gather Threads content by hashtag, search for posts on Threads, extract Threads search feed, get trending posts on Threads, find Threads discussions about a subject, or fetch recent or top Threads posts by keyword.

How do I install it?

Run `npx skills add browser-act/skills --skill threads-keyword-search --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