agentleFS
glideaglidea/supersearch-skills/skills/x-search/SKILL.md

x-search

Skill4 starsChanged 3 months agoMITView on GitHub

Search X for real-time updates, reactions, trending discussions, posts from specified accounts, and social sentiment. Return source-post links.

7 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

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 0

    Distinctive

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

    Use YYYY-MM-DD for --from and --to.

    line 15

“Common” is measured: kept by at least 6 in 10 of the 5 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 Search

Run:

node scripts/search.mjs "search query"
node scripts/search.mjs "search query" --from 2026-07-01 --to 2026-08-01

Use YYYY-MM-DD for --from and --to. Either option may be used independently.

When citations are present, cite only those links. When search_executed is true but no citations are returned, summarize content while stating that the upstream service provided no citable source posts. Do not misreport this as no discussion. When search_executed is false, state that the upstream search did not run.

End every response with a ## References section. Keep links next to supported claims and repeat the used links here, deduplicated and comma-separated on one website line:

## References

X: [result title](https://example.com), [result title](https://example.com)

List only links actually used in the answer. When none exist, write No citable sources. below the heading.

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.