agentsclimarketplace

Xquik social data

Skill JayRHa/AgentSkills/skills/xquik-social-data

The largest community-driven library of Agent Skills (SKILL.md + scripts/references/examples) for Claude, Codex, Gemini CLI, Cursor and friends.

Install
npx -y skills add JayRHa/AgentSkills --skill xquik-social-data

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

  • 3 stars3 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

Use this skill when the user needs X or Twitter social data extraction, tweet search, profile and follower lookup, media download, webhook monitoring, MCP setup, or REST API integration with Xquik and the x-developer skill package.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

4.5 KB, as published. Nobody here has run it

Xquik Social Data

Overview

Use this skill when an agent needs to plan, implement, or verify Xquik social-data workflows. Xquik provides an installable agent skill, REST API, MCP server, webhooks, bulk extraction jobs, and confirmation-gated X actions for developer workflows.

Keywords: Xquik, x-developer, x-twitter-scraper, X API, Twitter API, tweet search, followers, following, media download, webhooks, MCP, social data extraction, giveaway draw, account monitoring.

Setup

Prefer the published skill package so agents load the full Xquik reference material only when needed.

npx [email protected] add Xquik-dev/x-twitter-scraper

Use the public docs for API and MCP details:

  • https://docs.xquik.com
  • https://docs.xquik.com/api-reference/overview
  • https://docs.xquik.com/mcp/overview

Workflow

  1. Confirm the task needs X social data or X account automation. If it is only general web research, use the user's normal research tools instead.
  2. Choose the narrowest integration path:
    • Use the installed x-twitter-scraper skill for agent-guided endpoint selection.
    • Use the MCP server when the host supports remote MCP tools.
    • Use the REST API when building an application, workflow, or backend integration.
  3. Map the user's goal to a public capability:
    • Tweet search and lookup for keywords, URLs, IDs, hashtags, and advanced search operators.
    • User profile lookup, recent posts, likes, media, followers, following, and verified followers.
    • Bulk extraction for replies, quotes, reposts, favoriters, communities, lists, Spaces, mentions, articles, and people search.
    • Media download for tweet images, GIFs, and videos.
    • Monitors and HMAC webhooks for account or keyword activity.
    • Giveaway draws from tweet replies with configurable filters.
    • Confirmation-gated posting and account actions when the user explicitly requests them.
  4. Read the relevant Xquik reference before naming endpoints or request fields. Do not invent parameters, response shapes, limits, or pricing.
  5. For large reads, use the documented estimate and pagination flow before launching jobs. Continue with cursors until the response reports completion.
  6. For write actions, require explicit user approval in the calling product or agent flow before sending the request.
  7. Verify the result with the response contract, returned identifiers, webhook signature checks, or a follow-up read where appropriate.

Decision Guide

User asks forUse
"Find tweets about..."Tweet search
"Get this user's followers"Follower extraction
"Download media from this tweet"Media download
"Track new posts from this account"Account monitor plus webhook
"Build an agent tool for X data"MCP server or REST API
"Post this tweet"Confirmation-gated write action
"Run a reply giveaway"Giveaway draw

Best Practices

  • Keep Xquik optional in host integrations. Do not replace an existing provider unless the user asks.
  • Treat connected-account reads and all write actions as approval-gated workflows.
  • Use documented pagination cursors instead of one-shot assumptions for list endpoints.
  • Store API keys and webhook secrets in the host secret manager. Never paste them into examples, logs, or pull requests.
  • Verify webhook signatures with HMAC-SHA256 before trusting event payloads.
  • Prefer task-specific endpoint references over broad summaries when implementing code.

Common Pitfalls

  • Do not scrape public docs into hardcoded endpoint tables. Link to the source docs or install the skill package.
  • Do not retry validation errors unchanged. Fix the request shape first.
  • Do not treat an accepted bulk extraction job as completed. Poll the documented job status endpoint.
  • Do not expose private account content, API keys, webhook secrets, or connected-account identifiers in public issues or examples.
  • Do not claim official X platform affiliation. Describe Xquik as a developer platform for X workflows.

Supporting Resources

  • Published package: [email protected]
  • Source repository: https://github.com/Xquik-dev/x-twitter-scraper
  • Product docs: https://docs.xquik.com
  • API reference: https://docs.xquik.com/api-reference/overview
  • MCP guide: https://docs.xquik.com/mcp/overview

Gives 1 of the 12 instructions most apis services skills give

Counted across 424 of the 426 authors here whose files we hold, read 2026-08-06

  • use plural nouns for resource namesin 41 of 424, across 32 files
  • use cursor-based pagination for large datasetsin 35 of 424, across 20 files
  • include rate limit headers in responsesin 25 of 424, across 13 files
  • Use kebab-case for multi-word resourcesin 23 of 424, across 13 files
  • version APIs in the URL pathin 19 of 424, across 9 files
  • use semantic HTTP status codesin 18 of 424, across 8 files
  • verify webhook signatureshere, and in 18 of 424, across 11 files
  • use query parameters for filteringin 17 of 424, across 6 files
  • use async database operationsin 14 of 424, across 7 files
  • wrap successful responses in a data fieldin 13 of 424, across 3 files
  • prefix sorting parameters with a hyphen for descending orderin 13 of 424, across 3 files
  • set appropriate HTTP status codesin 13 of 424, across 6 files

Said here and by no other author read

  • confirm the task needs X social data
  • choose the narrowest integration path
  • map the user goal to a capability
  • read the reference before naming endpoints
  • use pagination for large reads
  • require explicit approval for write actions

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.