threads-search
Skill2 starsChanged 29 days agoMITView on GitHub
Search Threads posts and comments. Use for Threads recommendations, reviews, warnings, or travel experiences.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- lloyd3126/chenchungnien-skillstheir own version, first seen Aug 25, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- lloyd3126/chenchungnien-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- discordSkill
- google-mapSkill
- human-reviewSkill
- linear-cliSkill
- reclaim-code-entropySkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 32
Stop and report on: Session rejected or expired (user must refresh THREADS_SID), Rate limited (stop all calls), Search query expired, …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Threads Search
CLI: <dir of this SKILL.md>/scripts/threads_cli.py
python3 "<CLI_PATH>" search --query "<keywords>" --max-pages 0 # 0-2; start at 0, prefer a new query over more pages
python3 "<CLI_PATH>" get --url "<results[].url>" # post + top ~10 direct comments; no paginationstdout: {"schemaVersion":"1","command":"search|get","data":{...}}
stderr on failure (exit 1): {"schemaVersion":"1","error":{"code":"INVALID_ARGUMENT|COMMAND_FAILED","message":"..."}}
data:
- search:
results[]{id,url,text,timestamp,likeCount,replyCount,images,videos,links},hasMoreResults - get:
post{same fields},comments[]{same fields without replyCount},hasMoreComments(not fetchable)
Use
- Cite only
urlvalues from the output; never fabricate URLs. - Deduplicate by
id. Reposts or several mentions in one thread are one source. getonly posts whose comments add evidence.
Failures
Stop and report on: Session rejected or expired (user must refresh THREADS_SID), Rate limited (stop all calls), Search query expired, Request forbidden (HTTP 403) (do not assume expiry). Fix INVALID_ARGUMENT once. did not contain the requested post / redirected away: skip that URL. Never retry auth or rate-limit failures; never touch cookies or GraphQL config.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.