Xquik x data workflows

Skill charlieviettq/awesome-agent-skill/.cursor/skills/ai-agent-systems/xquik-x-data-workflows

Curated skill pack for LLM agents in engineer and science workflow (Cursor & Claude ready).

Install

npx -y skills add charlieviettq/awesome-agent-skill --skill xquik-x-data-workflows

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

22 stars22 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Source-check and plan Xquik REST API or remote MCP workflows for X data tasks. Triggers: "Xquik", "X/Twitter data workflow", "tweet search API", "X MCP server".

SKILL.md

3.3 KB, 671 tokens by cl100k_base, as published. Nobody here has run it

Xquik X Data Workflows

Contract

Help the user decide whether Xquik is the right public X data integration surface for a requested workflow, then produce a safe, source-backed plan for using its REST API or remote MCP server.

When To Use

The user asks for Xquik by name.
The task needs X/Twitter search, profile tweets, follower export, media handling, monitoring, webhooks, or agent access to X data.
The user wants an MCP setup for X data through https://xquik.com/mcp.
The user wants to compare REST API and MCP setup options for an agent workflow.

When Not To Use

The task is unrelated to X/Twitter data or social workflows.
The user asks for spam, credential theft, evasion, or platform abuse.
The workflow requires private account writes and the user has not explicitly requested them.
Public Xquik docs or source metadata cannot verify the endpoint, package, or setup path.

Phases

Confirm the workflow category: read-only data access, monitoring, webhook delivery, API exploration, or write action.
Source-check public references before giving setup instructions:
- https://docs.xquik.com/mcp/overview
- https://xquik.com/.well-known/mcp.json
- https://xquik.com/openapi.json
- https://github.com/Xquik-dev/x-twitter-scraper
Pick the smallest integration surface:
- Use REST when the user needs application code, typed clients, or direct HTTP control.
- Use remote MCP when an agent needs tool access through an MCP client.
- Use the source repository when the user needs package, SDK, or implementation context.
Keep credentials out of prompts, logs, URLs, and shell history. Use placeholders such as XQUIK_API_KEY and tell the user to store the real value in their client or environment.
Treat write actions as opt-in. Ask for explicit user intent before posting, replying, sending messages, changing account state, or configuring public webhooks.
Validate the proposed path with a public link check or schema check when possible, and report any unknowns.

Output Format

Recommended surface: REST, MCP, or source repo.
Public sources checked.
Minimal setup steps with placeholder credentials only.
Safety notes for credentials, account writes, webhooks, and user data.
Validation steps or the exact blocker that prevented validation.

Anti-Patterns

Do not paste API keys, bearer tokens, cookies, or account credentials.
Do not claim capabilities that are not backed by public docs, OpenAPI, MCP discovery, or source metadata.
Do not describe private infrastructure, routing mechanics, or cost mechanics.
Do not default to write actions when the requested workflow can be read-only.
Do not bypass user consent, rate limits, or platform rules.

Related Skills

mcp-builder - when designing a new MCP server or tool contract.
agent-tool-contracts - when mapping Xquik into a broader agent tool surface.
api-and-interface-design - when wrapping Xquik in an application API.