Add Xquik x-twitter-scraper skill

[kriptoburak]

Summary

• Add Xquik x-twitter-scraper to the app-backed skill catalog.
• Place it near the existing X/Twitter skill entry.
• Use localized, source-backed wording for tweet search, user tweets, follower export, media download, monitoring, webhooks, MCP, SDK, and confirmation-gated write workflows.
• Rebuild the branch from current main so the PR changes only src/data/skills.ts.

Validation

• git diff --check upstream/main...HEAD
• npm run build
• npm audit --omit=dev --json (0 production vulnerabilities)
• Verified the GitHub repository returns HTTP 200.
• Verified the docs link redirects to HTTP 200.
• Scanned the changed entry for secret-like, internal-provider, pricing, and disallowed badge references.

Note: npm run lint is currently blocked because this repo defines an eslint script but does not install eslint. I did not add dependencies for this listing-only change.

[kriptoburak]

Rebased the branch on current main and force-pushed head 3b62bff, so the PR changed-file list is scoped back to src/data/skills.ts only.

Validation after the rebuild:

• git diff --check origin/main...HEAD
• npm ci
• npm run build
• npm audit --omit=dev --json reports 0 production vulnerabilities
• GitHub repo link returns HTTP 200
• Docs link redirects to HTTP 200
• Scoped changed-entry scan found no secret-like text, internal-provider wording, pricing claims, or disallowed badge references

Target-side note: npm run lint still cannot run because the repo defines an eslint script but eslint is not installed. I left dependencies untouched because this PR only adds one catalog row.

[kriptoburak]

Rebased this on current main again and force-pushed head d7ec641.

The PR changed-file list is back to only src/data/skills.ts; the unintended README.md churn is gone. I also rebuilt locally with npm run build, and the existing dependency audit warnings are from the target dependency set rather than this one-file listing change.

[kriptoburak]

Re-scoped this PR after GitHub showed README churn again.

Pushed head 4f4caa5, and the visible diff is back to only src/data/skills.ts.

Validation:

• git diff --check upstream/main...HEAD
• npm ci
• npm run build
• npm audit --omit=dev --json reports 0 production vulnerabilities
• Xquik repo link returns HTTP 200
• Xquik docs URL redirects to https://docs.xquik.com/api-reference/overview, which returns HTTP 200

Target-side note: the fork default branch still has existing dependency alerts, but this PR only changes the one catalog entry.