XTwitterScraper

Trigger On

• adding the XTwitterScraper NuGet package to a .NET application
• searching tweets, reading tweet/user data, running extraction jobs, or monitoring X accounts through Xquik from .NET
• posting tweets, replies, likes, reposts, follows, or DMs through typed SDK methods
• exporting extraction results, handling raw responses, retries, rate limits, or API errors
• wiring Xquik webhook events into ASP.NET Core, workers, queues, or background processing

Workflow

1. Confirm the project actually needs Xquik API access from .NET. If it only needs prompt guidance, use a generic agent or API-design skill instead.
2. Install the NuGet package:

``bash dotnet add package XTwitterScraper ``

1. 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.
2. Create XTwitterScraperClient at the composition boundary and inject it or a narrow wrapper into application services. Do not scatter client construction across handlers.
3. Build typed Params objects for SDK calls instead of manually concatenating query strings.
4. Treat paginated responses, extraction jobs, binary exports, and webhook events as different flow types. Do not force them through one generic helper.
5. Preserve typed exceptions. Catch XTwitterScraperRateLimitException, authorization errors, and 5xx errors only where the application can retry, defer, or show a useful state.
6. Validate with unit tests around your wrapper and integration tests with configured API credentials only when the environment explicitly provides them.

Deliver

• a narrow package integration with XTwitterScraper
• centralized credential and client configuration
• typed request and response usage for the specific Xquik endpoint family
• explicit pagination, export, raw-response, retry, and webhook handling where needed
• tests that cover wrapper behavior without requiring live credentials by default

Validate

• dotnet restore resolves XTwitterScraper
• dotnet build succeeds without leaking credential values into source or logs
• unit tests cover the application wrapper around the SDK
• live integration tests are skipped unless the API key environment is explicitly configured
• webhook handlers validate signatures or event authenticity before processing
• retries and background jobs are scoped to operations that are safe for the application to replay

Related skills