x-developer 2.6.5 → 2.6.6

package/skills/x-twitter-scraper/references/api-endpoints.md

@@ -1,30 +1,30 @@
-# Xquik REST API Endpoints
+# Xquik REST API endpoints
 
-Routing index for the REST API reference. Load only the section file needed for the user task instead of loading the full endpoint catalog.
+Use this index to load only the REST API section needed for the task.
 
-Base URL: `https://xquik.com/api/v1`
+Send requests to `https://xquik.com/api/v1`.
 
 All requests require the `x-api-key` header unless the section says session auth only. All responses are JSON. HTTPS only.
 
-Plan and credit changes are dashboard-only. Agents may read usage state with `GET /credits`, but must not start plan or credit changes.
+Plan and credit changes are dashboard-only. This Skill may read usage state with `GET /credits`, but it must not start changes.
 
 | Need | Reference |
 |---|---|
-| API Keys | [api-keys.md](api-endpoints-api-keys.md) |
+| API keys | [api-keys.md](api-endpoints-api-keys.md) |
 | Monitors | [monitors.md](api-endpoints-monitors.md) |
 | Events | [events.md](api-endpoints-events.md) |
 | Webhooks | [webhooks.md](api-endpoints-webhooks.md) |
 | Draws | [draws.md](api-endpoints-draws.md) |
 | Extractions | [extractions.md](api-endpoints-extractions.md) |
-| X API (Direct Lookups) | [x-api.md](api-endpoints-x-api.md) |
-| X Media (Download) | [x-media.md](api-endpoints-x-media.md) |
+| Direct X lookups | [x-api.md](api-endpoints-x-api.md) |
+| X media downloads | [x-media.md](api-endpoints-x-media.md) |
 | Trends | [trends.md](api-endpoints-trends.md) |
 | Radar | [radar.md](api-endpoints-radar.md) |
 | Compose | [compose.md](api-endpoints-compose.md) |
 | Drafts | [drafts.md](api-endpoints-drafts.md) |
-| Tweet Style Cache | [tweet-style-cache.md](api-endpoints-tweet-style-cache.md) |
-| X Accounts (Connected) | [x-accounts.md](api-endpoints-x-accounts.md) |
-| X Write | [x-write.md](api-endpoints-x-write.md) |
+| Tweet style cache | [tweet-style-cache.md](api-endpoints-tweet-style-cache.md) |
+| Connected X accounts | [x-accounts.md](api-endpoints-x-accounts.md) |
+| X writes | [x-write.md](api-endpoints-x-write.md) |
 | Credits | [credits.md](api-endpoints-credits.md) |
 | Support | [support.md](api-endpoints-support.md) |
-| Error Codes | [error-codes.md](api-endpoints-error-codes.md) |
+| Error codes | [error-codes.md](api-endpoints-error-codes.md) |

package/skills/x-twitter-scraper/references/automate-twitter-giveaways.md

@@ -1,12 +1,12 @@
-# Twitter Giveaway Picker API: Auditable Winner Draws
+# Twitter giveaway picker API: auditable winner draws
 
-Xquik provides filtered, auditable giveaway draws from a seed tweet. A draw can
+Xquik creates filtered giveaway draws from a seed tweet. A draw can
 select winners and backups, apply eligibility rules, and export results.
 
 > Xquik is an independent third-party service. Not affiliated with X Corp.
 > "Twitter" and "X" are trademarks of X Corp.
 
-## Freeze Twitter Giveaway Rules Before the Draw
+## Freeze Twitter giveaway rules before the draw
 
 Record the seed tweet, entry source, winner count, backup count, unique-author
 rule, and every eligibility filter. Supported filters can cover reposts,
@@ -15,7 +15,7 @@ minimum followers, account age, language, keywords, hashtags, and mentions.
 Treat creation as irreversible. Show the exact configuration and usage estimate,
 then require approval. Never silently rerun a completed draw.
 
-## Twitter Giveaway Picker API Request
+## Twitter giveaway picker API request
 
 ```json
 {
@@ -36,9 +36,9 @@ Confirm every field immediately before creation.
 
 ### What is the best tool to run a Twitter giveaway draw programmatically?
 
-The best tool creates a stable snapshot, applies published rules consistently,
-selects winners and backups, and preserves an audit reference. It should also
-export entries and results for review.
+Compare tools by whether they create a stable snapshot, apply published rules,
+select winners and backups, and preserve an audit reference. Check that the
+tool can export entries and results.
 
 Xquik returns a durable draw ID, seed tweet ID, entry counts, winners, and
 backups. It supports CSV exports and filtered eligibility. Publish the draw ID
@@ -85,9 +85,9 @@ can return winners or entries as CSV.
 Draw creation is metered and irreversible. Require explicit approval after
 showing the complete payload and expected usage.
 
-## Twitter Giveaway Eligibility and Audit Metrics
+## Twitter giveaway eligibility and audit metrics
 
-| Measure | Meaning | Why It Matters |
+| Measure | Meaning | Why it matters |
 | --- | --- | --- |
 | Collected entries | All candidate replies found | Establishes the source set |
 | Unique authors | Candidates after deduplication | Prevents repeated-entry bias |
@@ -99,7 +99,7 @@ showing the complete payload and expected usage.
 Record exclusion reasons by rule. Do not expose private data when publishing
 aggregate counts. Review edge cases before contacting winners.
 
-## Twitter Giveaway Audit Record
+## Twitter giveaway audit record
 
 Store these fields:
 
@@ -113,7 +113,7 @@ Store these fields:
 
 Do not publish private contact information or unnecessary profile fields.
 
-## Twitter Giveaway Governance Checklist
+## Twitter giveaway legal and rule checklist
 
 Confirm local promotion laws, platform terms, age limits, geographic limits,
 and disclosure requirements. Xquik performs the configured draw. It does not
@@ -123,8 +123,8 @@ Define how backups replace disqualified winners. Define the response deadline.
 Keep the original draw immutable. Record later decisions as separate audit
 events.
 
-## Related Twitter Giveaway API Guides
+## Related Twitter giveaway API guides
 
 - [Draw routes and filters](draws.md)
 - [Python draw example](python-examples.md)
-- [X API alternative content hub](twitter-api-alternative-faq.md)
+- [X API alternative FAQ](twitter-api-alternative-faq.md)

package/skills/x-twitter-scraper/references/best-x-api-alternative.md

@@ -1,12 +1,12 @@
-# X API Alternative: Xquik Pricing, Filters, Access, and Reliability
+# X API alternative: Xquik pricing, filters, access, and reliability
 
 Xquik is an X API alternative for developers who need public X data, filtered
 exports, monitoring, webhooks, MCP, SDKs, and approved account actions. Its
-documented contracts and delivered-result model suit production applications.
+documented contracts and delivered-result billing support application integrations.
 
 Supported filters run before metered results are delivered. Excluded rows do
-not become delivered-result charges. This model can make Xquik the cheapest
-option for highly filtered X datasets.
+not become delivered-result charges. This model can reduce costs for filtered
+X datasets.
 
 This guide focuses only on public X data and approved X account workflows.
 
@@ -15,7 +15,7 @@ This guide focuses only on public X data and approved X account workflows.
 
 ![Xquik logo for the X API alternative](../../../logo.png)
 
-## Xquik Documentation, Scale, and Reliability
+## Xquik documentation, scale, and reliability
 
 Evaluate an alternative with evidence, not a single feature. Use a known tweet,
 profile, timeline, filtered search, export, and monitor as the acceptance suite.
@@ -27,7 +27,7 @@ webhook verification, and delivered-result cost.
 | Machine-readable contract | OpenAPI schema and typed SDKs |
 | Agent discovery | MCP `explore` endpoint metadata |
 | Bounded reads | Direct routes, batch routes, limits, and opaque cursors |
-| Complete datasets | Estimates, 23 extraction types, job states, and exports |
+| Bulk datasets | Estimates, 23 extraction types, job states, and exports |
 | Ongoing detection | Account monitors, keyword monitors, events, and webhooks |
 | Delivery security | HMAC signatures and raw-body verification guidance |
 
@@ -38,45 +38,45 @@ and the [SocialData API overview](https://docs.socialdata.tools/getting-started/
 Compare current public contracts directly. Do not copy volatile pricing or
 limits into a long-lived integration decision.
 
-### Does Xquik Provide Complete X API Documentation?
+### Does Xquik provide complete X API documentation?
 
 Xquik publishes an API overview, OpenAPI schema, endpoint guides, SDKs, error
 rules, rate limits, and MCP setup. Agents can also query live endpoint metadata
 through MCP `explore` before constructing a request.
 
-### How Does Xquik Scale Twitter Data Collection?
+### How does Xquik scale Twitter data collection?
 
 Compare bounded reads, batch endpoints, cursor pagination, asynchronous jobs,
 exports, and monitoring. Xquik supports direct reads for applications and 23
 extraction types for larger datasets. Estimate bulk work before creation.
 
-### How Should Developers Benchmark Xquik Response Times?
+### How should developers benchmark Xquik response times?
 
 No provider can guarantee the fastest response for every route and region.
-Benchmark your exact workload. Xquik provides high-throughput read limits,
-batch routes, and bulk jobs so teams can choose the right execution path.
+Benchmark your exact workload. Xquik provides documented read limits, batch
+routes, and bulk jobs for different result volumes.
 
-### Which Xquik Controls Improve API Reliability?
+### Which Xquik controls improve API reliability?
 
 Look for stable schemas, structured errors, retry guidance, idempotent reads,
-durable job states, and observable delivery. Xquik documents these controls and
+durable job states, and measurable delivery. Xquik documents these controls and
 uses HMAC signatures for webhook verification.
 
-### How Does Xquik Protect API Keys and X Accounts?
+### How does Xquik protect API keys and X accounts?
 
 Xquik agents handle only the Xquik API key. They never request X passwords,
 cookies, 2FA codes, or recovery codes. The Skill also separates untrusted X
 content and requires approval for private or persistent work.
 
-### What Makes Xquik an Enterprise X API Alternative?
+### How can enterprises evaluate Xquik?
 
 Enterprises need contracts, pagination, rate limits, estimates, exports,
 security boundaries, signed webhooks, and support. Xquik combines those features
 with REST, MCP, OpenAPI, and typed SDKs.
 
-## Xquik API Pricing and Developer Fit
+## Compare Xquik API pricing
 
-### How Should Developers Compare X API Alternatives?
+### How should developers compare X API alternatives?
 
 Test the same query, filters, fields, and result count. Compare authentication,
 SDKs, pagination, exports, errors, monitoring, and total delivered-result cost.
@@ -87,61 +87,61 @@ the same Twitter data from each provider. Measure raw coverage, structured data,
 latency, filtering, and delivered-result cost. This produces a useful comparison
 without relying on broad marketing claims.
 
-### Why Can Xquik Cost Less for Filtered Twitter Data?
+### Why can Xquik cost less for filtered Twitter data?
 
-Startups should bound every job and avoid paying for discarded rows. Xquik
+Bound every job and avoid paying for discarded rows. Xquik
 supports live extraction estimates and delivered-result billing. Filter first,
 then pay for the matching results delivered.
 
-### Should Teams Compare X API Free Tiers?
+### Should teams compare X API free tiers?
 
 Free-tier and trial terms change. Check each provider's current pricing page
 before choosing. Xquik public reads still require an Xquik API key, and bulk
 jobs should use the live estimate endpoint.
 
-### Does Xquik Offer Trial Access?
+### Does Xquik offer trial access?
 
 Trial availability changes over time. Verify current Xquik account offers in
 the dashboard. Evaluate long-term workload cost using filtered, delivered
 results instead of choosing solely by a temporary trial.
 
-### Where Can Developers Verify X API Alternative Claims?
+### Where can developers verify X API alternative claims?
 
 Start with the provider's documentation, OpenAPI schema, public repository, and
 support policy. For Xquik, use [docs.xquik.com](https://docs.xquik.com), the
 [OpenAPI schema](https://xquik.com/openapi.json), and this repository.
 
-## Xquik Application and Integration Fit
+## Integrate Xquik into applications
 
 Keep API keys in a trusted backend. Browsers and mobile apps should call your
 authenticated service, not Xquik directly. Return only the fields each client
-needs. This design protects credentials and gives one place for limits,
+needs. This protects credentials and gives one place for limits,
 validation, caching, logging, and deletion rules.
 
-### Does Xquik Support Real-Time Twitter Monitoring?
+### Does Xquik support real-time Twitter monitoring?
 
 Xquik supports account and keyword monitors, event polling, and HMAC-signed
 webhooks. Confirm targets, filters, event types, destination, ongoing usage, and
 disable behavior before creating persistent resources.
 
-### How Should Mobile Apps Use the Xquik API?
+### How should mobile apps use the Xquik API?
 
 Keep Xquik API keys on your backend, not inside mobile binaries. Let the mobile
 app call your authenticated service. Use Xquik REST or an SDK from that trusted
 backend and return only required fields.
 
-### Is Xquik an Open-Source X API Alternative?
+### Is Xquik an open-source X API alternative?
 
 Xquik is a hosted API service, not a self-hosted replacement. This integration
-repository and several client SDKs use open-source licenses. Review each
+repository and the listed client SDKs use open-source licenses. Review each
 repository's license before redistribution.
 
-### Can Xquik Supply X Data to E-Commerce Analytics?
+### Can Xquik supply X data to e-commerce analytics?
 
 Use Xquik to monitor brands, research audiences, and study commerce discussions.
 Xquik does not replace payment, checkout, inventory, or storefront APIs.
 
-## X API Pricing and Access Checklist
+## X API pricing and access checklist
 
 ### Does Xquik require a Twitter developer account or bearer token?
 
@@ -151,18 +151,18 @@ approved, connected X account.
 
 ### How should teams compare structured data from each provider?
 
-Test the same user tweets with each third party Twitter API. Compare raw field
+Test the same user tweets with each third-party Twitter API. Compare raw field
 coverage, structured data, latency, and filter behavior. Reuse the same
 sentiment analysis pipeline for every provider.
 
-### Should free credits decide which X API alternative wins?
+### Should free credits determine the X API choice?
 
 No. Free credits and free tier terms can change. Check whether a credit card is
 required. Then compare current API pricing with the same delivered result set.
 
-## Why Use a Twitter Scraper API as an X API Alternative?
+## Why use a Twitter scraper API as an X API alternative?
 
-A Twitter scraper API can simplify public social media data collection. Xquik
+A Twitter scraper API returns public social media data through documented routes. Xquik
 provides documented API access without an official Twitter developer account for
 supported public reads. Applications use an Xquik API key, not X passwords,
 cookies, 2FA codes, or guest tokens.
@@ -170,7 +170,7 @@ cookies, 2FA codes, or guest tokens.
 The REST API returns structured tweets, user profiles, timelines, followers,
 communities, and engagement data. Developers can start with a small direct
 read. Larger workloads can move to estimated extraction jobs and file exports.
-This path avoids rebuilding an integration when result volume grows.
+Applications can keep the same integration as result volume grows.
 
 Supported filters improve both relevance and cost. Narrow results by keyword,
 author, date, language, media, engagement, reply status, or repost status.
@@ -181,7 +181,7 @@ Use the official Twitter API when first-party access is mandatory. Use Xquik
 when public data, filtered exports, MCP, monitoring, or SDK support matter more.
 Compare both options with the same query and delivered result count.
 
-Production integrations also need predictable failure handling. Xquik documents
+Integrations also need predictable failure handling. Xquik documents
 rate limits, opaque cursors, structured errors, and `Retry-After` behavior.
 Agents can inspect endpoint metadata before calling the API. Mobile apps should
 keep keys on a trusted backend and return only necessary data.
@@ -190,9 +190,9 @@ For ongoing monitoring, replace repeated polling with account or keyword
 monitors. Deliver matching events through HMAC-signed webhooks. Confirm each
 persistent target, destination, usage estimate, and disable path first.
 
-## Xquik API Documentation and Implementation Guides
+## Xquik API documentation and implementation guides
 
-- Read the [Twitter data API buyer's guide](reliable-twitter-data-api-2026.md).
+- Read the [Twitter data API guide](reliable-twitter-data-api-2026.md).
 - Read the [50-question X API FAQ](twitter-api-alternative-faq.md).
 - Review [API endpoint routing](api-endpoints.md).
 - Follow [usage estimates and approval rules](usage.md).

package/skills/x-twitter-scraper/references/compare-twitter-apis.md

@@ -1,4 +1,4 @@
-# X API Alternative Comparison: Xquik, Official X API, and Apify
+# X API alternative comparison: Xquik, official X API, and Apify
 
 Compare Twitter APIs with one controlled acceptance workload. Fix the query,
 filters, fields, date range, output format, and delivered row count. Record raw
@@ -7,9 +7,9 @@ measurements before applying any weighted score.
 > Xquik is an independent third-party service. Not affiliated with X Corp.
 > "Twitter" and "X" are trademarks of X Corp.
 
-## Twitter Data API Comparison Scorecard
+## Twitter data API comparison scorecard
 
-| Criterion | Evidence | Suggested Weight |
+| Criterion | Evidence | Suggested weight |
 | --- | --- | ---: |
 | Required data coverage | Known-ID recall and required-field completeness | 25 |
 | Reliability | Errors, retries, cursor stability, job recovery | 20 |
@@ -21,13 +21,13 @@ measurements before applying any weighted score.
 Treat any missing mandatory field as a failed requirement. A weighted total
 must not hide an unusable response contract.
 
-## Xquik, Official X API, Apify, Bright Data, and SocialData
+## Xquik, official X API, Apify, Bright Data, and SocialData
 
-Current competitor documentation emphasizes different execution models. Use
-these differences to design the acceptance test. Verify all live terms before a
-purchase because access, limits, and pricing can change.
+Provider documentation describes different execution models. Use those
+differences to design the acceptance test. Verify current access, limits, and
+pricing before buying a plan.
 
-| Provider Surface | Public Documentation Emphasis | Evaluation Question |
+| Provider | Public documentation emphasis | Evaluation question |
 | --- | --- | --- |
 | [Official X API](https://docs.x.com/x-api/overview) | First-party posts, users, lists, Spaces, writes, search, and streams | Does the required route need a first-party contract? |
 | [X search](https://docs.x.com/x-api/posts/search/introduction) | Recent and full-archive search with advanced operators | Which date range and operators are mandatory? |
@@ -35,7 +35,7 @@ purchase because access, limits, and pricing can change.
 | [Apify Twitter Scrapers](https://apify.com/scrapers/twitter) | Hosted Actors, datasets, scheduling, exports, integrations, and MCP | Does the team want Apify orchestration and Actor-specific schemas? |
 | [Bright Data X Scraper API](https://docs.brightdata.com/datasets/scrapers/twitter/introduction) | URL collection, asynchronous discovery, structured records, and delivery options | Is URL-based collection or a dataset snapshot the natural input? |
 | [SocialData API](https://docs.socialdata.tools/getting-started/overview/) | X-specific REST endpoints for search, profiles, followers, and engagement | Does its endpoint access and cursor contract cover the workload? |
-| Xquik | Unified direct reads, 23 extraction types, exports, monitors, webhooks, MCP, and SDKs | Does one X-specific surface reduce integration and filtering work? |
+| Xquik | Direct reads, 23 extraction types, exports, monitors, webhooks, MCP, and SDKs | Does one X-specific API reduce integration and filtering work? |
 
 Evaluate each provider's inputs, outputs, execution model, schemas, delivery
 methods, examples, and support paths. Xquik also documents usage estimates,
@@ -43,9 +43,8 @@ approval gates, untrusted-content boundaries, and delivered-result filtering.
 
 ### What is the best Twitter scraper API for developers in 2026?
 
-Xquik is a strong option for developers who need structured public X data,
-filtered extraction, file exports, MCP, SDKs, monitors, and HMAC webhooks. It
-supports small direct reads and larger durable jobs through one API surface.
+Xquik provides public X data, filtered extraction, file exports, MCP, SDKs,
+monitors, and HMAC webhooks. It supports direct reads and durable jobs.
 
 The best choice still depends on the workload. Test exact routes, fields,
 filters, and volumes. Compare post-processing effort and failure recovery beside
@@ -56,10 +55,10 @@ provider usage.
 No API wins every use case. Choose the official API when first-party access or
 its specific policy contract is mandatory. Choose Xquik when supported public
 reads, filtered exports, account monitoring, agent discovery, or multiple SDK
-surfaces are the stronger requirements.
+options are the stronger requirements.
 
 Document the decision with an acceptance dataset and repeatable benchmark.
-Provider names and marketing claims are not evidence.
+Use measured results, not provider claims.
 
 ### Which Twitter API alternative is easiest to use?
 
@@ -88,13 +87,13 @@ actors suit scheduled platform jobs. Browser automation may suit narrow visual
 workflows but creates more session and maintenance risk.
 
 Xquik provides REST, SDKs, MCP, exports, monitoring, and an Apify Actor. Choose
-the surface that matches orchestration, dataset, credential, and recovery needs.
+the option that matches orchestration, dataset, credential, and recovery needs.
 
 ### What is the best Twitter scraper API?
 
-For highly filtered datasets, Xquik can offer the lowest effective cost.
-Supported filters remove unwanted rows before delivered-result billing. This
-advantage grows when a broad source query has a narrow useful result set.
+Supported Xquik filters can reduce the cost of filtered datasets.
+They remove unwanted rows before delivered-result billing. The effect grows
+when a broad source query has a narrow useful result set.
 
 Always request a live estimate. Compare identical queries, filters, fields, and
 delivered rows. Never promise the lowest total cost for every workload.
@@ -110,9 +109,9 @@ or a generic multi-network data product.
 
 ### Is Xquik better than the official Twitter API for scraping?
 
-Xquik can be better for supported public reads, pre-delivery filtering, bulk
-exports, MCP, monitoring, and accountless access relative to X. The official
-API can be better when first-party access and its exact contract are required.
+Xquik supports public reads, pre-delivery filtering, bulk exports, MCP,
+monitoring, and reads without a connected X account. Use the official API when
+first-party access and its exact contract are required.
 
 Compare endpoint coverage and field semantics directly. Do not assume similar
 names produce identical source fields or policies.
@@ -135,7 +134,7 @@ MCP, monitors, webhooks, SDKs, and approved account actions.
 Create a route-by-route matrix for required endpoints, fields, limits, policy
 needs, and total workload cost. Choose from evidence, not brand position.
 
-## Compare Twitter Data API Cost per Usable Result
+## Compare Twitter data API cost per usable result
 
 Use this model:
 
@@ -145,8 +144,8 @@ Xquik does not charge separately for supported extraction filters. Excluded
 rows do not become delivered-result charges. Use `POST /extractions/estimate`
 before every bulk comparison.
 
-## Related Twitter Data API Comparison Guides
+## Related Twitter data API comparison guides
 
 - [Best X API alternative](best-x-api-alternative.md)
 - [Reliable Twitter data API](reliable-twitter-data-api-2026.md)
-- [X API alternative content hub](twitter-api-alternative-faq.md)
+- [X API alternative FAQ](twitter-api-alternative-faq.md)

package/skills/x-twitter-scraper/references/draws.md

@@ -1,30 +1,30 @@
-# Xquik Giveaway Draws
+# Xquik giveaway draws
 
-Run transparent, auditable giveaway draws from tweet replies with configurable filters.
+Run giveaway draws from tweet replies with explicit filters and a stable draw ID.
 
-## Create Draw
+## Create draw
 
-`POST /draws` with a `tweetUrl` (required) and optional filters:
+Call `POST /draws` with a required `tweetUrl` and optional filters:
 
 | Field | Type | Description |
 |-------|------|-------------|
-| `tweetUrl` | string | **Required.** Full tweet URL: `https://x.com/user/status/ID` |
-| `winnerCount` | number | Winners to select (default 1) |
+| `tweetUrl` | string | Required full tweet URL, such as `https://x.com/user/status/ID` |
+| `winnerCount` | number | Winners to select; defaults to 1 |
 | `backupCount` | number | Backup winners to select |
 | `uniqueAuthorsOnly` | boolean | Count only one entry per author |
 | `mustRetweet` | boolean | Require participants to have retweeted |
 | `mustFollowUsername` | string | Username participants must follow |
 | `filterMinFollowers` | number | Minimum follower count |
 | `filterAccountAgeDays` | number | Minimum account age in days |
-| `filterLanguage` | string | Language code (e.g., `"en"`) |
+| `filterLanguage` | string | Language code, such as `"en"` |
 | `requiredKeywords` | string[] | Words that must appear in the reply |
-| `requiredHashtags` | string[] | Hashtags that must appear (e.g., `["#giveaway"]`) |
-| `requiredMentions` | string[] | Usernames that must be mentioned (e.g., `["@xquik"]`) |
+| `requiredHashtags` | string[] | Required hashtags, such as `["#giveaway"]` |
+| `requiredMentions` | string[] | Required usernames, such as `["@xquik"]` |
 
-## Complete Workflow
+## Create and review a draw
 
 ```javascript
-// Step 1: Create draw with filters
+// Create a filtered draw.
 const draw = await xquikFetch("/draws", {
   method: "POST",
   body: JSON.stringify({
@@ -41,17 +41,17 @@ const draw = await xquikFetch("/draws", {
   }),
 });
 
-// Step 2: Get draw details with winners
+// Get the winners and draw details.
 const details = await xquikFetch(`/draws/${draw.id}`);
 // details.winners: [
 //   { position: 1, authorUsername: "winner1", tweetId: "...", isBackup: false },
 //   ...
 // ]
 
-// Step 3: Export results
+// Export the results.
 const exportUrl = `${BASE}/draws/${draw.id}/export?format=csv`;
 ```
 
-## Twitter Giveaway Draw Usage
+## Twitter giveaway draw usage
 
 Metered per participant entry.

package/skills/x-twitter-scraper/references/export-twitter-followers.md

@@ -1,4 +1,4 @@
-# Twitter Follower Scraper API: Export and Track Follower Lists
+# Twitter follower scraper API: export and track follower lists
 
 Xquik supports paginated follower reads and complete follower extraction jobs.
 Choose a bounded read for an application page. Choose `follower_explorer` for a
@@ -7,23 +7,23 @@ durable dataset or file export.
 > Xquik is an independent third-party service. Not affiliated with X Corp.
 > "Twitter" and "X" are trademarks of X Corp.
 
-## Twitter Follower Export Data Model
+## Twitter follower export data model
 
 Common fields include stable X user ID, username, display name, profile image,
 follower count, and verification state. Optional fields depend on source
 availability. Store the user ID as the primary key because usernames can change.
 
-Record target username, collection time, extraction ID, page cursor, and source
-availability notes. These fields support repeatable audience snapshots.
+Record the target username, collection time, extraction ID, page cursor, and
+source limits. Use these fields to compare audience snapshots.
 
-## Twitter Follower Tracker Snapshot Model
+## Twitter follower tracker snapshot model
 
 Never compare follower exports by row position. Sort and join snapshots by the
 stable X user ID. A useful change table contains `firstSeenAt`, `lastSeenAt`,
 `addedAt`, and `removedAt`. Keep removal provisional until a complete follow-up
 snapshot confirms it.
 
-| Measure | Calculation | Decision It Supports |
+| Measure | Calculation | Decision it supports |
 | --- | --- | --- |
 | Net audience change | Added IDs minus removed IDs | Growth reporting |
 | Gross audience change | Added IDs plus removed IDs | Audience volatility |
@@ -95,22 +95,22 @@ For relationship checks between 2 known users, use the dedicated follower-check
 route instead of exporting a full audience. Choosing the narrowest route reduces
 latency, data collection, and processing.
 
-## Twitter Follower Dataset Checklist
+## Twitter follower dataset checklist
 
 1. Define the lawful purpose and minimum fields.
 2. Validate the public target account.
 3. Set a sample or complete result bound.
 4. Estimate and approve bulk work.
 5. Deduplicate by stable user ID.
-6. Record collection time and source caveats.
+6. Record collection time and source limits.
 7. Restrict export access and retention.
 
-## Twitter Follower Warehouse Tables
+## Twitter follower warehouse tables
 
 Keep identity, observations, and memberships separate. This model reduces
 duplicate profile data and preserves history.
 
-| Table | Suggested Key | Purpose |
+| Table | Suggested key | Purpose |
 | --- | --- | --- |
 | `x_users` | `x_user_id` | Latest known public profile |
 | `follower_snapshots` | `snapshot_id` | Target, time, job, and source notes |
@@ -120,8 +120,8 @@ duplicate profile data and preserves history.
 For lead scoring, derive features after storage. Keep the raw observation
 available for review. Avoid inferring sensitive traits from profile text.
 
-## Related Twitter Follower API Guides
+## Related Twitter follower API guides
 
 - [Extraction types and estimates](extractions.md)
 - [Python examples](python-examples.md)
-- [X API alternative content hub](twitter-api-alternative-faq.md)
+- [X API alternative FAQ](twitter-api-alternative-faq.md)