xquik-social-data
Skill6 starsChanged 10 days agoMITView on GitHub
Use when 用户需要从 Xquik 获取公开 X/Twitter 数据、搜索推文、查账号、看趋势、导出样本、整理社媒证据,或说 xquik、Xquik、X/Twitter data、tweet search、social evidence、社媒证据、推文搜索。
- Reads credentials
4 other projects use a version of this.
Adopted by
Most recently taken up by
- jaskirat1616/grok-skillstheir own version, first seen Nov 1, 2026
- JayRHa/AgentSkillstheir own version, first seen Nov 1, 2026
- JayRHa/agent-skillstheir own version, 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 · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- jaskirat1616/grok-skills★ 22same name
- JayRHa/agent-skills★ 12same name
- JayRHa/AgentSkills★ 12same 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 repository80 other files it gives its agents.
- AGENTS.mdAGENTS.md
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-bulk-archive-changeSkill
- openspec-continue-changeSkill
- openspec-exploreSkill
- openspec-ff-changeSkill
- openspec-new-changeSkill
- openspec-onboardSkill
- openspec-sync-specsSkill
- openspec-verify-changeSkill
- ai-proxy-disciplineSkill
- analysis-coreSkill
- android-webview-debugSkill
- article-writerSkill
- astrill-controlSkill
- brainstorm-workflowSkill
- browser-debug-toolkitSkill
- clarifying-question-disciplineSkill
- code-design-reviewSkill
- competitive-researchSkill
- completion-evidence-disciplineSkill
- context-budget-disciplineSkill
- decision-fog-disciplineSkill
- delivery-disciplineSkill
- design-approval-gateSkill
- domain-language-disciplineSkill
- effective-web-researchSkill
- essence-diagnosisSkill
- evolution-reviewSkill
- explain-clearlySkill
- feature-branch-closeoutSkill
- figma-pixel-implementSkill
- figma-pixel-verifySkill
- git-branch-protectSkill
- git-commitSkill
- git-conflict-resolveSkill
- git-release-finishSkill
- git-release-startSkill
- git-worktree-disciplineSkill
- goal-driven-queueSkill
- goal-driven-workflowSkill
- go-deploySkill
- hybrid-debugSkill
- intake-interview-disciplineSkill
- jira-fix-queueSkill
- jira-fix-workflowSkill
- jira-readSkill
- jira-status-lifecycleSkill
- jira-status-writebackSkill
- jira-wiki-markupSkill
- known-issue-researchSkill
- learn-and-improveSkill
- merge-disciplineSkill
- multi-agent-debateSkill
- node-version-disciplineSkill
- opsx-jira-fix-queueSkill
- opsx-jira-fix-workflowSkill
- opsx-solve-workflowSkill
- opsx-workspace-gateSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. 0 are common, 17 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
17
Distinctive
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 10
Use this skill when a task needs current public X/Twitter evidence through Xquik.
- Distinctive: line 11
Keep the work evidence-first: fetch small, relevant samples, cite post IDs or URLs, and separate direct observations from interpretation.
- Distinctive: line 16
Search public posts for a topic, brand, account, incident, product, or campaign.
- Distinctive: line 17
Look up public X/Twitter accounts or posts before writing a summary.
- Distinctive: line 20
Check trends or public activity before drafting a post or recommendation.
- Distinctive: line 22
Do not use this skill for private messages, login-gated content, credential sharing, platform bypassing, or claims that need complete …
- Distinctive: line 31
Never print or store API keys.
- Distinctive: line 38
If the user gives a broad topic, create 3 to 8 short search queries.
- Very specific: line 41
Search posts with GET /x/tweets/search?q=<query>.
- Distinctive: line 42
Use account or post endpoints only when they directly support the task.
- Distinctive: line 43
Keep request batches small and deduplicate by post ID.
- Distinctive: line 48
Keep every conclusion tied to at least one post ID, URL, or account handle.
- Distinctive: line 53
Call out sample size, query bias, language bias, and time-window limits.
- Distinctive: line 103
Do not fabricate posts, counts, links, trends, or account details.
- Distinctive: line 104
Do not infer demographics or intent from a single post.
- Distinctive: line 105
Do not expose secrets, raw credentials, or private implementation details.
- Distinctive: line 106
Do not claim complete coverage of X/Twitter.
- Distinctive: line 107
Prefer exact IDs and URLs over vague summaries.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Xquik Social Data
Use this skill when a task needs current public X/Twitter evidence through Xquik. Keep the work evidence-first: fetch small, relevant samples, cite post IDs or URLs, and separate direct observations from interpretation.
When To Use
- Search public posts for a topic, brand, account, incident, product, or campaign.
- Look up public X/Twitter accounts or posts before writing a summary.
- Compare public conversation themes, sentiment, repeated questions, or complaints.
- Build a traceable evidence set for social listening, OSINT, marketing research, or support triage.
- Check trends or public activity before drafting a post or recommendation.
Do not use this skill for private messages, login-gated content, credential sharing, platform bypassing, or claims that need complete official analytics.
Setup
- API base:
https://xquik.com/api/v1 - Docs:
https://docs.xquik.com - Authentication: send the user's Xquik API key as
x-api-key.
Never print or store API keys. If no API key is available, provide the exact request shape and ask the user to run it in their approved environment.
Workflow
- Clarify scope.
- Topic, account, date range, language, geography, and desired output.
- If the user gives a broad topic, create 3 to 8 short search queries.
- Fetch public evidence.
- Search posts with
GET /x/tweets/search?q=<query>. - Use account or post endpoints only when they directly support the task.
- Keep request batches small and deduplicate by post ID.
- Search posts with
- Normalize findings.
- Preserve
id,text,createdAt, author username, engagement fields, and URL. - Label missing counts as missing, not zero, unless the API response explicitly says zero.
- Keep every conclusion tied to at least one post ID, URL, or account handle.
- Preserve
- Analyze cautiously.
- Group repeated themes.
- Mark sentiment as an interpretation unless the user provided labeled data.
- Call out sample size, query bias, language bias, and time-window limits.
- Return a concise report.
- Scope and queries.
- Evidence count and deduped count.
- Top themes with cited examples.
- Risks, unknowns, and recommended next searches.
Request Examples
curl "https://xquik.com/api/v1/x/tweets/search?q=launch%20feedback" \
-H "x-api-key: $XQUIK_API_KEY"curl "https://xquik.com/api/v1/x/users/search?q=xquik" \
-H "x-api-key: $XQUIK_API_KEY"Output Template
## Scope
- Goal:
- Queries:
- Time window:
## Evidence
- Raw results:
- Deduped results:
- Notable examples:
## Findings
1. Theme:
Evidence:
Confidence:
## Limits
- Sample size:
- Query bias:
- Missing data:
## Next Searches
1.
2.Quality Rules
- Do not fabricate posts, counts, links, trends, or account details.
- Do not infer demographics or intent from a single post.
- Do not expose secrets, raw credentials, or private implementation details.
- Do not claim complete coverage of X/Twitter. Say "sample" unless the user provided a complete export.
- Prefer exact IDs and URLs over vague summaries.
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.

