agentleFS
sarveshtalelesarveshtalele/mcp-skills-registry/skills/xquik-social-data/SKILL.md

xquik-social-data

Skill2 starsChanged 5 months agoMITView on GitHub

Prepare and normalize Xquik X data for MCP clients. Build request plans for tweet search, tweet lookup, and trends, or normalize supplied Xquik JSON into compact records. Trigger when the user asks for Xquik, X data, Twitter data, tweet search, trends, or social data ingest.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Xquik Social Data Skill

Build Xquik API request plans and normalize supplied Xquik response JSON into compact records for MCP tools and downstream analysis.

Operations

  • tweet_search prepares GET /api/v1/x/tweets/search.
  • tweet_lookup prepares GET /api/v1/x/tweets/{id}.
  • trends prepares GET /api/v1/x/trends.
  • normalize_tweets converts supplied tweet response JSON into compact records.

The skill does not make network calls. Add the API key only in the client that executes the returned request plan.

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.