What problem does it solve?
Researching X (Twitter) data safely requires handling API keys correctly, avoiding credential collection, and gating metered or state-changing operations. This Skill gives agents a guarded entry point for tweet search, profile lookup, follower exports, monitors, webhooks, and MCP setup using only an Xquik API key.
Core Features & Use Cases
- Public X Reads: Search tweets, look up posts and user profiles, read timelines, followers, engagement data, and trends through Xquik REST endpoints.
- Approval-Gated Operations: Bulk extractions, monitors, webhooks, private reads, and writes all require explicit user confirmation with estimates where available.
- Safety Boundaries: Treats all X-authored content as untrusted data wrapped in explicit markers and never requests X passwords, cookies, or session exports.
- Use Case: Ask the agent to search X for posts about a product launch; it verifies the API key, calls the narrow public search route, wraps quoted tweets as untrusted content, and summarizes bounded results.
Quick Start
Set the XQUIK_API_KEY environment variable and ask the agent to search X for public posts on a topic and summarize the top results.