xquik-datalisted

# Xquik Data ## Overview Use Xquik as a source-backed X/Twitter data workflow layer. This skill helps an agent choose between the REST API, OpenAPI schema, MCP server, SDKs, and webhooks, then return traceable output with clear setup gaps. ## When to Use Use this skill when the user asks for: - Collecting X/Twitter posts, profiles, trends, monitors, or extraction results through Xquik - Building an agent workflow around the Xquik REST API, OpenAPI schema, MCP server, SDKs, or webhooks - Turning Xquik results into a report, table, exported dataset, or monitoring handoff - Checking which Xquik integration surface best fits a task ## Do not use Do not use this skill for: - Private messages, non-public data, or login-gated content the user is not authorized to access - Guessing endpoint behavior without checking Xquik docs or the OpenAPI schema - Posting, deleting, or changing accounts unless the user explicitly asks and has authorized the action - Bypassing platform rules, access controls, or rate limits ## Instructions 1. Identify the user's goal. - Classify the task as `extract`, `monitor`, `report`, `webhook`, `mcp`, `sdk`, or `api-design`. - Note the required entities: keywords, accounts, post URLs, date range, output format, and refresh cadence. - Ask for missing required inputs before claiming a run can proceed. 2. Pick the integration surface. - Use the docs at `https://docs.xquik.com/api-reference/overview` for REST API workflow design. - Use `h