Menu
Search X/Twitter users, tweets, and trends with Xquik REST API endpoints.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Guide human-centered design processes using empathy-driven methodologies across Empathize, Define, Ideate, Prototype, and Test phases.
Identify disruption opportunities using Blue Ocean Strategy, Jobs-to-be-Done, and business model innovation frameworks.
Apply systematic problem-solving methodologies including TRIZ, Theory of Constraints, root cause analysis, and creative solution generation.
Craft compelling narratives using 25+ proven story frameworks including Hero Journey, story circles, and pitch structures.
Create data flow diagrams (DFD) in Excalidraw format showing data movement between systems and processes.
Create system architecture diagrams, ERDs, UML diagrams, or general technical diagrams in Excalidraw format.
| name | xquik-twitter-api |
| description | Search X/Twitter users, tweets, and trends with Xquik REST API endpoints. |
| tags | ["api","social-media","twitter","x"] |
Use this skill when a task needs X/Twitter search, user lookup, trend checks, or lightweight social data collection through Xquik.
XQUIK_API_KEY.https://xquik.com/api/v1 as the REST API base URL.X-API-Key header for authenticated REST requests.https://docs.xquik.com or https://xquik.com/openapi.yaml when the
task needs a route not shown here.| Task | Route | Notes |
|---|---|---|
| Confirm account access | GET /account | Fastest key smoke test |
| Search users | GET /x/users/search | Use a username or keyword query |
| Search tweets | GET /x/tweets/search | Use X search syntax in q |
| Get trends | GET /x/trends | Optional woeid and count query params |
| Use remote MCP | https://xquik.com/mcp | Add your API key in the client |
curl -sS -H "X-API-Key: ${XQUIK_API_KEY}" \
"https://xquik.com/api/v1/account"
If this returns 401, stop and ask for a valid Xquik API key. Do not continue
with unauthenticated probes.
curl -sS -H "X-API-Key: ${XQUIK_API_KEY}" \
"https://xquik.com/api/v1/x/users/search?q=xquik"
Use this before user-specific routes when you have a handle, display name, or ambiguous account reference.
curl -sS -H "X-API-Key: ${XQUIK_API_KEY}" \
"https://xquik.com/api/v1/x/tweets/search?q=from:xquik&limit=5"
Use native X search syntax in q. Keep the first query narrow, inspect results,
then widen with keywords, dates, or account filters.
curl -sS -H "X-API-Key: ${XQUIK_API_KEY}" \
"https://xquik.com/api/v1/x/trends?woeid=1&count=10"
Use trends when the task asks for timely topics or a search seed list.
For follow-up work, store normalized records in memory:
{
"xquik": {
"queries": [
{
"query": "from:xquik",
"route": "/api/v1/x/tweets/search",
"checked_at": "2026-06-13T00:00:00Z",
"result_ids": ["1234567890123456789"]
}
]
}
}
Deduplicate by tweet ID, user ID, and query before taking follow-up actions.