Apify Content Analytics
sickn33/agentic-awesome-skills
Track engagement metrics, measure campaign ROI, and analyze content performance across Instagram, Facebook, YouTube, and TikTok.
Searches Threads posts by keyword or hashtag and returns matching posts with engagement metrics, extracted from SSR-embedded JSON.
$ npx skills add browser-act/skills --skill threads-keyword-search -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install browser-act/skills threads-keyword-search --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/browser-act/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/solutions/social-listening/threads-keyword-search .claude/skills/threads-keyword-search && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "threads-keyword-search" agent skill from https://github.com/browser-act/skills/tree/main/solutions/social-listening/threads-keyword-search into .claude/skills/threads-keyword-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threads-keyword-search", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/browser-act/skills/tree/main/solutions/social-listening/threads-keyword-searchType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add browser-act/skills --skill threads-keyword-search -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install browser-act/skills threads-keyword-search --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/browser-act/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/solutions/social-listening/threads-keyword-search .agents/skills/threads-keyword-search && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "threads-keyword-search" agent skill from https://github.com/browser-act/skills/tree/main/solutions/social-listening/threads-keyword-search into .agents/skills/threads-keyword-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threads-keyword-search", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add browser-act/skills --skill threads-keyword-search -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install browser-act/skills threads-keyword-search --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/browser-act/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/solutions/social-listening/threads-keyword-search .cursor/skills/threads-keyword-search && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "threads-keyword-search" agent skill from https://github.com/browser-act/skills/tree/main/solutions/social-listening/threads-keyword-search into .cursor/skills/threads-keyword-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threads-keyword-search", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/browser-act/skills.git --path solutions/social-listening/threads-keyword-search--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add browser-act/skills --skill threads-keyword-search -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install browser-act/skills threads-keyword-search --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/browser-act/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/solutions/social-listening/threads-keyword-search .gemini/skills/threads-keyword-search && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "threads-keyword-search" agent skill from https://github.com/browser-act/skills/tree/main/solutions/social-listening/threads-keyword-search into .gemini/skills/threads-keyword-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threads-keyword-search", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install browser-act/skills threads-keyword-searchInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add browser-act/skills --skill threads-keyword-search -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/browser-act/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/solutions/social-listening/threads-keyword-search .github/skills/threads-keyword-search && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "threads-keyword-search" agent skill from https://github.com/browser-act/skills/tree/main/solutions/social-listening/threads-keyword-search into .github/skills/threads-keyword-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threads-keyword-search", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add browser-act/skills --skill threads-keyword-search -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install browser-act/skills threads-keyword-search --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/browser-act/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/solutions/social-listening/threads-keyword-search .opencode/skills/threads-keyword-search && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "threads-keyword-search" agent skill from https://github.com/browser-act/skills/tree/main/solutions/social-listening/threads-keyword-search into .opencode/skills/threads-keyword-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threads-keyword-search", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
threads-keyword-searchSearches Threads posts by keyword or hashtag and returns matching posts with engagement metrics, extracted from SSR-embedded JSON.
Threads Keyword Search is an agent skill from browser-act/skills. 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…
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/extract-search-results.py`).
It sits in Data & Analytics, covering Product metrics, Web scraping and Social media marketing. It works with Python. The repository describes itself as: Browser automation CLI built for AI agents. Break through anti-bot walls, hand off to humans across platforms when stuck. Parallel multi-task execution, independent multi-session… The licence is MIT.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 11c057b. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
pythonFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
threads.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Threads Keyword Search loads about 1.7k tokens when it runs. Until then it costs about 146 tokens; SKILL.md has 615 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from browser-act/skills at commit 11c057b, republished under its MIT licence (© browser-act). 615 words, ~1,654 tokens.
.claude/skills/threads-keyword-search/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.keyword + sort filter → list of matching posts with engagement metrics
All process output to user (progress updates, process notifications) follows the user's language.
Search Threads for posts matching a keyword or hashtag and extract the results from SSR-embedded JSON, with support for top/recent sort ordering.
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.
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 viaeval "$(python scripts/xxx.py {params})".$(...)is bash syntax; it is recommended to use the bash tool for execution.
Navigate to the search page with the keyword and sort filter, then extract all results embedded in the initial HTML:
navigate https://www.threads.com/search/?q={keyword}&serp_type={filter}{keyword}: URL-encoded search term or hashtag (e.g., AI or %23AI for #AI){filter}: top (default, most relevant) or recent (chronologically newest)wait stableeval "$(python scripts/extract-search-results.py '{keyword}' --filter {filter})"Output example:
{
"keyword": "AI",
"filter": "top",
"posts": [
{
"id": "3936653356768062022", // post internal ID (pk)
"code": "DZyvcdEl-W1", // post short code for URL
"url": "https://www.threads.com/@flower_popy/post/DZyvcdEl-W1",
"text": "AI is changing everything...", // post text content, null if no caption
"taken_at": 1781926571, // Unix timestamp of post creation
"like_count": 34, // number of likes
"reply_count": 6, // number of direct replies
"repost_count": 0, // number of reposts
"quote_count": 0, // number of quote posts
"is_reply": false, // true if this post is a reply
"media_type": 19, // 1=photo, 2=video, 8=carousel, 19=text-only
"has_media": false, // true if post contains image/video/carousel
"user": {
"pk": "14803522782",
"username": "flower_popy",
"full_name": "Flower",
"is_verified": false
}
}
],
"count": 17,
"page_info": {
"end_cursor": null,
"has_next_page": false,
"has_previous_page": false,
"start_cursor": null
}
}Error handling: If error: true is returned, check that the search page loaded correctly by verifying the URL contains the query parameter. If searchResults not found, the page may have failed to render SSR data — retry navigate and wait stable once. If count: 0, no posts matched the keyword.
Hashtag search uses the same URL pattern. Prefix keyword with #:
navigate https://www.threads.com/search/?q=%23{hashtag}&serp_type={filter}%23AI for #AIwait stableeval "$(python scripts/extract-search-results.py '#AI' --filter top)"The # prefix in the keyword argument is for labeling only; the URL encoding %23 is what Threads uses to identify hashtag searches.
[DOM] filter — values: top (most relevant/popular posts), recent (newest posts first). Set via --filter argument and serp_type URL parameter.
Pagination is not available for unauthenticated access on the search endpoint (has_next_page: false is returned regardless of result volume). Results are limited to approximately 17-18 posts per query without login. For broader coverage, run multiple searches with related keywords.
result.count >= 1 and result.posts[0].id != null and result.posts[0].user.username != null
taken_at (Unix timestamp) client-side after extractionnavigate to the search URL — the search parameters are baked into the URL.Path: {working-directory}/browser-act-skill-forge-memories/threads-scraper-threads-keyword-search.memory.md
Before execution: If the file exists, read it first — it records unexpected situations encountered during past executions; adjust strategy order accordingly.
After execution: If an unexpected situation is encountered (strategy became ineffective, page redesigned, anti-scraping upgraded, better path discovered), append a line:
{YYYY-MM-DD}: {what happened} → {conclusion}
Normal execution does not write to the file. Do not record what keywords were used or how many results were returned — those are task outputs, not experience.
© browser-act, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file (scripts) in solutions/social-listening/threads-keyword-search of browser-act/skills.
Open the folder on GitHubat commit 11c057b
Threads Keyword Search next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Threads Keyword Search this skillbrowser-act/skills | 6.1k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Apify Content Analyticssickn33/agentic-awesome-skills | 47k | 2 repos | ~1.2k | Automated safety check: Notes | MIT | |
| Crawl4AI Web Scrapingsmallnest/goclaw | 599 | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Boss Zhipin Scrapereatmoreduck/boss-zhipin-scraper | 1.5k | — | ~2.6k | Automated safety check: Pass | MIT | |
| Axyusukebe/ax | 719 | 1 repos | ~918 | Automated safety check: Pass | MIT | |
| Google Maps ScraperMahanaicoach/google-maps-scraper-kit | 1.3k | — | ~2.8k | Automated safety check: Pass | MIT |
sickn33/agentic-awesome-skills
Track engagement metrics, measure campaign ROI, and analyze content performance across Instagram, Facebook, YouTube, and TikTok.
smallnest/goclaw
Scrapes sites, handles JavaScript-heavy pages and extracts structured data with Crawl4AI, through its crwl CLI or Python SDK, including schema-based extraction without an LLM.
eatmoreduck/boss-zhipin-scraper
Scrape BOSS直聘 (job listing site) via Chrome CDP. An agent skill from eatmoreduck/boss-zhipin-scraper.
yusukebe/ax
Use the ax CLI instead of curl + throwaway parsing scripts whenever you fetch a URL, explore an unknown web page, or extract structured data from HTML.
Mahanaicoach/google-maps-scraper-kit
Scrape Google Maps business listings (name, address, phone, website, rating, reviews, lat/lng, hours, emails) via the local gosom google-maps-scraper REST API.
cortega26/chile-hub
Execute Python code in a safe sandboxed environment via [inference.sh](https://inference.sh).
browser-act/skills
Fetches structured Amazon product details such as title, price, ratings and availability for a given ASIN through BrowserAct's lookup API template.
browser-act/skills
Extracts structured Amazon product data for a keyword and marketplace through the BrowserAct API, including titles, prices, ratings, reviews, sales volume and promotions.
browser-act/skills
Pulls Amazon product details, competing seller prices and seller ratings for a given ASIN through the BrowserAct API, without browser automation.
browser-act/skills
Analyzes a competitor's Amazon listing by ASIN with BrowserAct data extraction, then reports what it does well, where the market has gaps and opportunity points for your own listing.
browser-act/skills
Pulls structured Amazon search results (titles, ASINs, prices, ratings, specifications) for a keyword and brand through BrowserAct's Amazon Product API template.
browser-act/skills
Collects structured product data from Amazon search results for a keyword and optional brand, using a BrowserAct script, for market and competitor research.
Works with
Searches Threads posts by keyword or hashtag and returns matching posts with engagement metrics, extracted from SSR-embedded JSON. Threads Keyword Search is an agent skill from browser-act/skills. Searches Threads posts by keyword or hashtag and returns matching posts with engagement metrics, extracted from SSR-embedded JSON.
Threads Keyword Search fits situations like: user asks to search Threads posts; find Threads content by topic; scrape Threads search results; collect Threads posts about a keyword.
Run `npx skills add browser-act/skills --skill threads-keyword-search -a claude-code`. Or copy the skill folder (solutions/social-listening/threads-keyword-search in browser-act/skills) into .claude/skills/threads-keyword-search in your project. Claude Code loads it when a task matches its description.
Run `npx skills add browser-act/skills --skill threads-keyword-search -a codex`. Or copy the skill folder (solutions/social-listening/threads-keyword-search in browser-act/skills) into .agents/skills/threads-keyword-search in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add browser-act/skills --skill threads-keyword-search -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/threads-keyword-search, .gemini/skills/threads-keyword-search, .github/skills/threads-keyword-search and .opencode/skills/threads-keyword-search in your project.
Going by SKILL.md and its folder, Threads Keyword Search needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
SKILL.md names 1 domain. In commands or code: threads.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Threads Keyword Search is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.7k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Threads Keyword Search: Apify Content Analytics (sickn33/agentic-awesome-skills, 47k stars), Crawl4AI Web Scraping (smallnest/goclaw, 599 stars), Boss Zhipin Scraper (eatmoreduck/boss-zhipin-scraper, 1.5k stars) and Ax (yusukebe/ax, 719 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
browser-act (a GitHub organization) maintains it in browser-act/skills, which has 6,122 GitHub stars. The repository holds 87 skills in this directory. The repository was last updated on August 24, 2026.
Source: browser-act/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.