agentleFS
anotbanotb/x-signal/skills/x-research/SKILL.md

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

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
  1. Very specific:

    Call x_status only when service, sign-in, or rate health is uncertain.

    line 8
  2. Very specific:

    Use x_search_accounts when the task needs people, organizations, experts, emerging accounts, or an exact handle.

    line 9
  3. Very specific:

    Use x_get_timeline for an exact Following, For You, user, bookmarks, list, or community source.

    line 13
  4. Very specific:

    Create or change an x_monitor only when requested.

    line 15

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

X research

  1. Call x_status only when service, sign-in, or rate health is uncertain.
  2. Use x_search_accounts when 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.
  3. 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 and responseLimit from the requested breadth; do not request 200 by habit or impose an arbitrary global result ceiling.
  4. Let long research run when it is still gathering useful evidence. Poll with x_get_run using view: "summary"; pass the returned revision as ifRevision on later polls so unchanged progress stays small. Read full evidence when it changes or completes. If a result is running with retryAt, retain its runId, continue independent reasoning, and poll after retryAt. Do not launch replacement searches or rapid status probes during the backoff window.
  5. Inspect totalPosts, the evidence-page cursor, per-leg requested/returned counts, continuation availability, query coverage, lenses, authors, clusters, warnings, and failed legs. Use x_get_evidence to read more already-stored records without touching X. Use x_continue_search on 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.
  6. Use x_get_timeline for an exact Following, For You, user, bookmarks, list, or community source. Preserve its cursor when another page is useful. Expand consequential posts with x_get_post when thread, reply, or quote-post context could confirm, qualify, or challenge the claim.
  7. 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.
  8. Create or change an x_monitor only 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.