x-research
Skill1 starsChanged 3 months agoMITView on GitHub
Research and synthesize substantial live X evidence across one or multiple topics, labeled query angles, Top and Latest, relevant timelines, and post context. Use for open-ended research, comparisons, trend discovery, emerging accounts, current events, or technical discussion on X.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- prantikmedhi/crossbartheir own version, first seen Nov 8, 2026
- PostPlusAI/postplus-skillstheir own version, first seen Nov 5, 2026
- yologdev/yoyo-evolvetheir own version, first seen Oct 17, 2026
- r0undm1dn1ghty-star/ds_content-radartheir own version, first seen Oct 17, 2026
- laodao-ai/laodao-skillstheir own version, first seen Oct 13, 2026
- agentbody/skillstheir own version, first seen Oct 11, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- yologdev/yoyo-evolve★ 1.9ksame name
- rohunvora/x-research-skill★ 1.2ksame name
- bradautomates/head-of-content★ 227same name
- PostPlusAI/postplus-skills★ 27same name
- lleqsnoom/xskills★ 2same name
- prantikmedhi/crossbar★ 2same name
- agentbody/skills★ 1same name
- jpoindexter/theft-kit★ 1same name
- laodao-ai/laodao-skills★ 0same name
- r0undm1dn1ghty-star/ds_content-radar★ 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 repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- x-feed-and-threadSkill
- x-monitoringSkill
- x-setupSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Call x_status only when service, sign-in, or rate health is uncertain.
- Very specific: line 9
Use x_search_accounts when the task needs people, organizations, experts, emerging accounts, or an exact handle.
- Very specific: line 13
Use x_get_timeline for an exact Following, For You, user, bookmarks, list, or community source.
- Very specific: line 15
Create or change an x_monitor only when requested.
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
X research
- Call
x_statusonly when service, sign-in, or rate health is uncertain. - Use
x_search_accountswhen the task needs people, organizations, experts, emerging accounts, or an exact handle. Continue with its returned cursor only when the next account page is useful. - Plan enough distinct post-query angles to answer the actual question. For a broad single topic, usually combine Top and Latest with a few scoped or Media variants in one
x_search. For multiple topics, label each topic and lens in one consolidated call when practical. Choose useful per-leg limits andresponseLimitfrom the requested breadth; do not request 200 by habit or impose an arbitrary global result ceiling. - Let long research run when it is still gathering useful evidence. Poll with
x_get_runusingview: "summary"; pass the returnedrevisionasifRevisionon later polls so unchanged progress stays small. Read full evidence when it changes or completes. If a result isrunningwithretryAt, retain itsrunId, continue independent reasoning, and poll afterretryAt. Do not launch replacement searches or rapid status probes during the backoff window. - Inspect
totalPosts, the evidence-page cursor, per-leg requested/returned counts, continuation availability, query coverage, lenses, authors, clusters, warnings, and failed legs. Usex_get_evidenceto read more already-stored records without touching X. Usex_continue_searchon only consequential thin legs when genuinely new upstream evidence is needed; repeat it if justified. Add a different angle only for a real evidence gap, not as a substitute for either continuation path. - Use
x_get_timelinefor an exact Following, For You, user, bookmarks, list, or community source. Preserve its cursor when another page is useful. Expand consequential posts withx_get_postwhen thread, reply, or quote-post context could confirm, qualify, or challenge the claim. - Synthesize patterns and disagreements across the full evidence set. Distinguish what posts claim, what engagement shows, and what you infer. Canonical X URLs are available when references would improve traceability or the user asks for them. Choose a proportionate set, placement, and style for the specific answer; references may be omitted when they add little value. Do not dump bare URLs or force a fixed citation section unless the user asks.
- Create or change an
x_monitoronly when requested.
Use x_list_runs to find earlier saved research by query, label, status, or creation time. Use x_compare_runs for changes between two saved samples before repeating upstream work. These tools are local. A post absent from the later sample is not evidence of deletion or a decline in discussion. Account, query, lens, and coverage differences matter.
Clusters are lexical groupings of the returned page. Distinct authors or wording do not establish independent corroboration, and translations or synonyms may remain separate. Use explicit recency sorting for chronological historical work; author diversity applies to balanced ranking.
Favor independent coverage and author diversity over volume for its own sake. High engagement is not factual reliability.
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.

