Discovers Threads user accounts by keyword, extracting profile data including username, display name, verification status, biography, and follower count.
Install the "threads-profile-search" agent skill from https://github.com/browser-act/skills/tree/main/solutions/social-listening/threads-profile-search into .claude/skills/threads-profile-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threads-profile-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.
Type 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.
skills CLI
$ npx skills add browser-act/skills --skill threads-profile-search -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "threads-profile-search" agent skill from https://github.com/browser-act/skills/tree/main/solutions/social-listening/threads-profile-search into .agents/skills/threads-profile-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threads-profile-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.
skills CLI
$ npx skills add browser-act/skills --skill threads-profile-search -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "threads-profile-search" agent skill from https://github.com/browser-act/skills/tree/main/solutions/social-listening/threads-profile-search into .cursor/skills/threads-profile-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threads-profile-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.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add browser-act/skills --skill threads-profile-search -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "threads-profile-search" agent skill from https://github.com/browser-act/skills/tree/main/solutions/social-listening/threads-profile-search into .gemini/skills/threads-profile-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threads-profile-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.
Installs 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).
skills CLI
$ npx skills add browser-act/skills --skill threads-profile-search -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "threads-profile-search" agent skill from https://github.com/browser-act/skills/tree/main/solutions/social-listening/threads-profile-search into .github/skills/threads-profile-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threads-profile-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.
skills CLI
$ npx skills add browser-act/skills --skill threads-profile-search -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "threads-profile-search" agent skill from https://github.com/browser-act/skills/tree/main/solutions/social-listening/threads-profile-search into .opencode/skills/threads-profile-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threads-profile-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.
Facts
Skill name
threads-profile-search
GitHub stars
6.1k
Token cost
~1.8k tokens
SKILL.md length
671 words
Files
3 (incl. scripts)
Skills in repo
87
Repo updated
First seen
Licence
MIT
At a glance
Discovers Threads user accounts by keyword, extracting profile data including username, display name, verification status, biography, and follower count.
Works in 3 steps: navigate… → wait stable → eval "$(python…
User asks to find Threads accounts
SKILL.md covers Language, Objective, Prerequisites and Pre-execution Checks, plus 6 more sections
Runs Python scripts from its folder; calls python; reaches threads.com
What it does
Threads Profile Search is an agent skill from browser-act/skills. Discovers Threads user accounts by keyword, extracting profile data including username, display name, verification status, biography, and follower count. Use when user asks to find Threads accounts, search Threads profiles, discover Threads users by keyword, look up Threads creators, find influencers on Threads, search for people on Threads, get Threads user details, collect Threads profile information, find accounts related to a topic on Threads, search Threads for accounts by name or keyword, or enumerate…
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including scripts (for example `scripts/extract-profile-search.py` and `scripts/get-profile-details.py`).
It sits in Marketing & SEO, covering Influencer and creator marketing 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.
When your agent uses it
User asks to find Threads accounts
Search Threads profiles
Discover Threads users by keyword
Look up Threads creators
Example prompts
“Use the threads-profile-search skill to discover Threads user accounts by keyword, extracting profile data including username, display name…”
“/threads-profile-search”
Requirements
Python 3
Workflow steps
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.
Tool permissions
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.
Runs code
Ships 2 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
threads.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Threads Profile Search loads about 1.8k tokens when it runs. Until then it costs about 143 tokens; SKILL.md has 671 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~143
When it runs· the whole SKILL.md, loaded when a task matches
~1.8k
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.
Safety
Auto-check passed
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.
Download SKILL.mdSave it as .claude/skills/threads-profile-search/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
threads-profile-search
description
Discovers Threads user accounts by keyword, extracting profile data including username, display name, verification status, biography, and follower count. Use when user asks to find Threads accounts, search Threads profiles, discover Threads users by keyword, look up Threads creators, find influencers on Threads, search for people on Threads, get Threads user details, collect Threads profile information, find accounts related to a topic on Threads, search Threads for accounts by name or keyword, or enumerate Threads users matching a search term.
Threads — Profile Search
keyword → list of matching user profiles with optional enrichment (bio, follower count)
Language
All process output to user (progress updates, process notifications) follows the user's language.
Objective
Search Threads for user accounts matching a keyword and extract profile information, with optional per-user enrichment to retrieve biography and follower count via the profile API.
Prerequisites
A browser is open and connected via browser-act
No login required for profile search (unauthenticated: up to 16 profiles 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 execution.
SSR: Extract profile search results (basic info)
Navigate to the profile search page, then extract user accounts from the SSR-embedded JSON:
{
"keyword": "zuck",
"profiles": [
{
"pk": "14803522782", // Instagram-based user ID
"username": "ceozuck162", // Threads username (without @)
"full_name": "ceo,zuck", // display name
"is_verified": false, // blue checkmark verification status
"is_private": false, // true if account is private
"profile_pic_url": "https://...", // profile picture URL
"profile_url": "https://www.threads.com/@ceozuck162"
}
],
"count": 16,
"page_info": {
"end_cursor": null,
"has_next_page": false,
"has_previous_page": false,
"start_cursor": null
}
}
Error handling: If error: true is returned, verify the page URL ends with &type=profiles. If searchResults not found, retry navigate and wait stable once. If count: 0, no accounts matched the keyword.
API: Get full profile details (biography + follower count)
Enrich a single username with full profile data including biography and follower count. The browser must be on any Threads page (authentication state is shared across the session):
{
"pk": "314216", // Instagram user ID
"username": "zuck",
"full_name": "Mark Zuckerberg",
"biography": "I build stuff", // profile bio text, null if empty
"follower_count": 16944740, // number of followers, null if unavailable
"following_count": 464, // number of accounts followed
"is_verified": true,
"is_private": false,
"profile_pic_url": "https://...",
"profile_url": "https://www.threads.com/@zuck",
"external_url": null // website URL from profile, null if not set
}
Error handling: If error: true with a 429 status, the profile API is rate-limited — wait 10-30 seconds before retrying. If User not found, the username may be invalid or the account may be deleted.
Composite: Search profiles + enrich each with full details
To collect profiles with biography and follower count for all results:
eval "$(python scripts/extract-profile-search.py '{keyword}')" → collect profiles list
For each username in profiles:
a. eval "$(python scripts/get-profile-details.py '{username}')" → merge biography, follower_count, following_count, external_url into profile record
Output merged list with all fields
Note: Profile API calls are made in the browser context and share the same session cookies. Add 1-2 second intervals between per-user calls to avoid rate limiting.
Show full SKILL.md (261 more words)Show less
Pagination
Pagination is not available for unauthenticated access on profile search (has_next_page: false). Results are limited to approximately 16 profiles per keyword without login.
Success Criteria
result.count >= 1 and result.profiles[0].username != null
For enriched flow: profiles[0].follower_count != null and profiles[0].biography != null
Known Limitations
Unauthenticated access: no pagination; approximately 16 profiles per query
Basic profile search does not include biography or follower count — enrichment step required
Profile API (get-profile-details.py) may be rate-limited; add intervals in batch loops
Private accounts appear in search results but their post data is inaccessible
pk from SSR profile search is the Instagram-based ID, which differs from the Threads-specific ID in post data
Execution Efficiency
Batch orchestration: Run extract-profile-search.py once per keyword, then loop through the returned usernames for enrichment. Do not call get-profile-details.py in parallel within the same session — rate limit applies.
Test before batch execution: Test with 1-2 keywords first before running full enrichment batch.
Reduce redundant pre-operations: After the search page load, all subsequent get-profile-details.py calls use fetch() in the current browser context — no additional navigation needed.
Error resumption: Save results per username; on failure, resume enrichment from the breakpoint.
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.
Threads Profile 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.
Threads Profile Search compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Threads Profile Search this skillbrowser-act/skills
A skill your agent uses when the user asks to "amplify influencer content with paid media", "set up whitelisting or Spark Ads", "decide which posts to boost", "repurpose influencer content", "turn…
A skill your agent uses when the user asks to "find trending topics", "what trends should my brand jump on", or "time a campaign around a cultural moment"; produces a ranked trend report with…
Extracts structured Amazon product data for a keyword and marketplace through the BrowserAct API, including titles, prices, ratings, reviews, sales volume and promotions.
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.
Pulls structured Amazon search results (titles, ASINs, prices, ratings, specifications) for a keyword and brand through BrowserAct's Amazon Product API template.
Collects structured product data from Amazon search results for a keyword and optional brand, using a BrowserAct script, for market and competitor research.
Discovers Threads user accounts by keyword, extracting profile data including username, display name, verification status, biography, and follower count. Threads Profile Search is an agent skill from browser-act/skills. Discovers Threads user accounts by keyword, extracting profile data including username, display name, verification status, biography, and follower count.
When should I use Threads Profile Search?
Threads Profile Search fits situations like: user asks to find Threads accounts; search Threads profiles; discover Threads users by keyword; look up Threads creators.
How do I install Threads Profile Search in Claude Code?
Run `npx skills add browser-act/skills --skill threads-profile-search -a claude-code`. Or copy the skill folder (solutions/social-listening/threads-profile-search in browser-act/skills) into .claude/skills/threads-profile-search in your project. Claude Code loads it when a task matches its description.
How do I install Threads Profile Search in Codex?
Run `npx skills add browser-act/skills --skill threads-profile-search -a codex`. Or copy the skill folder (solutions/social-listening/threads-profile-search in browser-act/skills) into .agents/skills/threads-profile-search in your project. Codex loads it when a task matches its description.
Can I use Threads Profile Search in Cursor, Gemini CLI or GitHub Copilot?
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-profile-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-profile-search, .gemini/skills/threads-profile-search, .github/skills/threads-profile-search and .opencode/skills/threads-profile-search in your project.
What does Threads Profile Search need to run?
Going by SKILL.md and its folder, Threads Profile Search needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Threads Profile Search access the network?
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.
Is Threads Profile Search safe to install?
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.
What licence does Threads Profile Search use?
Threads Profile Search is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Threads Profile Search use?
About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Threads Profile Search?
Skills that share tags, products or a category with Threads Profile Search: Content Amplifier (aaron-he-zhu/aaron-marketing-skills, 2.9k stars), Trend Spotter (aaron-he-zhu/aaron-marketing-skills, 2.9k stars), Ecommerce Social Media Marketing (nexscope-ai/eCommerce-Skills, 1.1k stars) and Paw Mkt Social (pawbytes/skill-suites, 110 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Threads Profile Search?
browser-act (a GitHub organization) maintains it in browser-act/skills, which has 6,114 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.