Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →managedcode/xtwitter-scraper
Use XTwitterScraper when a .NET application needs typed access to Xquik's X automation REST API for tweet search, user lookup, posting workflows, extraction jobs, monitors, webhooks, or giveaway draws. USE FOR: integrating the XTwitterScraper NuGet package; reviewing Xquik API client usage; modeling API-key configuration, pagination, binary exports, raw responses, retries, and webhook/event flows in .NET. DO NOT USE FOR: unrelated stacks; direct browser automation; generic social-media strategy;
Passed 20 of 22 test cases with the skill, and 8 of 22 without it.
and 16 more in the full report
13 fixed7 passed either way1 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
Which environment variable names does the SDK inspect by default for API key authentication and bearer token authentication when initializing without explicit constructor arguments?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies X_TWITTER_SCRAPER_API_KEY as the environment variable for the API key. | Missed | Passed |
| Identifies X_TWITTER_SCRAPER_BEARER_TOKEN as the environment variable for the bearer token. | Missed | Passed |
The instructions your model reads when the skill loads.
XTwitterScraper NuGet package to a .NET applicationConfirm the project actually needs Xquik API access from .NET. If it only needs prompt guidance, use a generic agent or API-design skill instead.
Install the NuGet package:
dotnet add package XTwitterScraper
Configure credentials through environment or secret storage. Prefer X_TWITTER_SCRAPER_API_KEY; keep X_TWITTER_SCRAPER_BASE_URL at its default unless a test fixture intentionally overrides it.
Create XTwitterScraperClient at the composition boundary and inject it or a narrow wrapper into application services. Do not scatter client construction across handlers.
Build typed Params objects for SDK calls instead of manually concatenating query strings.
Treat paginated responses, extraction jobs, binary exports, and webhook events as different flow types. Do not force them through one generic helper.
Preserve typed exceptions. Catch XTwitterScraperRateLimitException, authorization errors, and 5xx errors only where the application can retry, defer, or show a useful state.
Validate with unit tests around your wrapper and integration tests with configured API credentials only when the environment explicitly provides them.
flowchart LR
A["ASP.NET Core or worker service"] --> B["Application wrapper"]
B --> C["XTwitterScraperClient"]
C --> D["Xquik REST API"]
D --> E["Typed response models"]
D --> F["Webhook events"]
D --> G["Binary exports"]
test cases passed, vs 8 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.