xquik-social-data
Skill12 starsChanged 5 months agoMITView on GitHub
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.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- FuDesign2008/open-skillstheir own version, first seen Nov 6, 2026
- jaskirat1616/grok-skillsword for word, first seen Nov 1, 2026
- JayRHa/agent-skillsword for word, first seen Oct 15, 2026
- sarveshtalele/mcp-skills-registrytheir own version, first seen Jun 12, 2026
Other versions4 projects use a version of this.
Word for word · 2
- jaskirat1616/grok-skills★ 22100% same
- JayRHa/agent-skills★ 12100% same
Edited · 0
None found.
Wrote their own version · 2
- FuDesign2008/open-skills★ 6same name
- sarveshtalele/mcp-skills-registry★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository75 other files it gives its agents.
- 0-templateSkill
- ab-test-analyzerSkill
- adr-authorSkill
- api-designerSkill
- api-docs-writerSkill
- aws-cost-optimizerSkill
- bash-script-hardeningSkill
- blog-post-writerSkill
- book-summarizerSkill
- changelog-keeperSkill
- chart-chooserSkill
- code-reviewerSkill
- competitive-analysisSkill
- concept-explainerSkill
- cover-letter-writerSkill
- cron-schedulerSkill
- data-pipeline-architectSkill
- debug-detectiveSkill
- decision-matrixSkill
- dependency-upgraderSkill
- dockerfile-proSkill
- email-composerSkill
- error-handling-patternsSkill
- event-plannerSkill
- flashcard-generatorSkill
- gdpr-data-mapperSkill
- gift-advisorSkill
- github-actions-builderSkill
- git-workflowSkill
- habit-builderSkill
- incident-postmortemSkill
- interview-prepSkill
- job-description-writerSkill
- json-schema-authorSkill
- kubernetes-manifest-authorSkill
- language-tutorSkill
- meal-plan-builderSkill
- meeting-summarizerSkill
- mermaid-diagram-builderSkill
- nginx-config-proSkill
- observability-setupSkill
- okr-writerSkill
- pandas-data-cleaningSkill
- people-dataSkill
- performance-profilerSkill
- personal-budget-plannerSkill
- presentation-builderSkill
- project-plannerSkill
- prompt-engineerSkill
- proofreaderSkill
- public-speaking-coachSkill
- rag-pipeline-designerSkill
- readme-generatorSkill
- refactoring-guideSkill
- regex-architectSkill
- release-notes-writerSkill
- resume-writerSkill
- salary-negotiatorSkill
- secrets-managerSkill
- secure-code-reviewSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. About 0 are common, 17 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈17
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Use this skill when an agent needs to plan, implement, or verify Xquik social-data workflows.
- Distinctive: line 17
Prefer the published skill package so agents load the full Xquik reference material only when needed.
- Distinctive: line 23
Use the public docs for API and MCP details:
- Very specific: line 33
Use the installed x-twitter-scraper skill for agent-guided endpoint selection.
- Distinctive: line 34
Use the MCP server when the host supports remote MCP tools.
- Distinctive: line 35
Use the REST API when building an application, workflow, or backend integration.
- Distinctive: line 44
Read the relevant Xquik reference before naming endpoints or request fields.
- Distinctive: line 47
Verify the result with the response contract, returned identifiers, webhook signature checks, or a follow-up read where appropriate.
- Distinctive: line 63
Keep Xquik optional in host integrations.
- Distinctive: line 64
Treat connected-account reads and all write actions as approval-gated workflows.
- Distinctive: line 65
Use documented pagination cursors instead of one-shot assumptions for list endpoints.
- Distinctive: line 67
Verify webhook signatures with HMAC-SHA256 before trusting event payloads.
- Distinctive: line 68
Prefer task-specific endpoint references over broad summaries when implementing code.
- Distinctive: line 72
Do not scrape public docs into hardcoded endpoint tables.
- Distinctive: line 73
Do not retry validation errors unchanged.
- Distinctive: line 74
Do not treat an accepted bulk extraction job as completed.
- Distinctive: line 75
Do not expose private account content, API keys, webhook secrets, or connected-account identifiers in public issues or examples.
- Distinctive: line 76
Do not claim official X platform affiliation.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 skills@1.5.3 add Xquik-dev/x-twitter-scraperUse the public docs for API and MCP details:
https://docs.xquik.comhttps://docs.xquik.com/api-reference/overviewhttps://docs.xquik.com/mcp/overview
Workflow
- 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.
- Choose the narrowest integration path:
- Use the installed
x-twitter-scraperskill 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.
- Use the installed
- 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.
- Read the relevant Xquik reference before naming endpoints or request fields. Do not invent parameters, response shapes, limits, or pricing.
- For large reads, use the documented estimate and pagination flow before launching jobs. Continue with cursors until the response reports completion.
- For write actions, require explicit user approval in the calling product or agent flow before sending the request.
- Verify the result with the response contract, returned identifiers, webhook signature checks, or a follow-up read where appropriate.
Decision Guide
| User asks for | Use |
| "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:
x-developer@2.4.16 - 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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

