xquik-data-cn

Xquik data

Overview

Use Xquik as a source-backed entry point for X/Twitter data workflows. This skill helps agents choose the appropriate approach among the REST API, OpenAPI schema, MCP server, SDK, and webhook, and output traceable data results and configuration gaps.

When to use

Use this skill when the user has the following needs:

• Collect X/Twitter posts, profiles, trends, monitoring, or extraction results through Xquik
• Build agent workflows around the Xquik REST API, OpenAPI schema, MCP server, SDK, or webhook
• Organize Xquik results into reports, tables, exported datasets, or monitoring handoff notes
• Determine which Xquik integration method is best suited for a given task

Do not use

This skill should not be used in the following scenarios:

• Direct messages, non-public data, or logged-in content the user does not have permission to access
• Guessing endpoint behavior without checking the Xquik documentation or OpenAPI schema
• Posting, deleting content, or modifying account status without the user's explicit authorization
• Bypassing platform rules, access controls, or rate limits

Usage instructions

1. Clarify the user's goal.

   • Classify the task as extract、monitor、report、webhook、mcp、sdk or api-design。
   • Record the necessary entities: keywords, accounts, post URLs, time range, output format, and refresh frequency.
   • Ask first when necessary inputs are missing; do not directly claim it can be run.

2. Choose the integration method.

   • For REST API workflow design, check first https://docs.xquik.com/api-reference/overview。
   • Check when endpoint names, request fields, or response structures are involved https://xquik.com/openapi.json。
   • Check when the user needs an agent-native MCP connection https://docs.xquik.com/mcp/overview。
   • Prefer webhook when the user needs event delivery rather than polling.

3. Safely check the access method and secrets.

   • Confirm whether the user already has an Xquik API key, MCP configuration, SDK client, or webhook secret.
   • Do not print, save, or repeat API keys or webhook secrets.
   • When credentials are missing, only prepare clear configuration steps; do not fabricate keys.

4. Design the request plan.

   • Clearly write the endpoint or tool, input fields, output fields, pagination plan, and retry expectations.
   • Do not write endpoints or fields not confirmed by the OpenAPI schema as runnable examples.
   • For analysis tasks, prefer read-only collection by default.

5. Run or prepare the workflow.

   • If a configured client or MCP tool already exists, run the smallest safe request first.
   • If there is no client, provide a copyable plan and required fields based on public documentation.
   • For recurring tasks, explain the webhook or monitor configuration method and failure handling.

6. Return traceable results.

   • Output the input scope, source method, result count, key fields, limitations, and next steps.
   • Distinguish data returned by Xquik from agent analysis recommendations.
   • Clearly mark partial data, missing credentials, empty results, or unsupported operations.

Default output

# Xquik 数据工作流

## 范围
- 目标：
- 来源方式：
- 输入：
- 凭证：

## 请求计划
- 端点或工具：
- 必填字段：
- 分页或刷新：
- 输出字段：

## 结果摘要
- 状态：
- 条目数：
- 关键字段：
- 限制：

## 下一步
- ...

Reference links

• Xquik API overview:https://docs.xquik.com/api-reference/overview
• Xquik OpenAPI schema：https://xquik.com/openapi.json
• Xquik MCP overview:https://docs.xquik.com/mcp/overview
• Xquik MCP manifest：https://xquik.com/.well-known/mcp.json

Limitations and known issues

• Actual operation requires a valid Xquik API key, a configured MCP connection, or an SDK client.
• X/Twitter data access depends on user authorization, request scope, and Xquik API limits.
• API details may change; check the public documentation or OpenAPI schema before writing runnable code.