x-developer 2.6.5 → 2.6.7

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

@@ -1,8 +1,8 @@
-# Xquik Twitter API Alternative: Search, Export, Monitor, and Automate
+# Xquik Twitter API alternative: search, export, monitor, and automate
 
-This hub routes common developer questions to focused, detailed answers. Each
-guide includes route decisions, data fields, examples, cost controls, failure
-handling, and safety guidance.
+Use this index to find answers about Twitter search, exports, monitoring, and
+API comparisons. Each guide lists routes, fields, examples, cost controls,
+errors, and approval rules.
 
 Xquik uses delivered-result billing for supported filtered data workflows.
 Filtering is not a separate billable step. Excluded rows do not become
@@ -11,9 +11,9 @@ delivered-result charges. Always estimate bulk work before creation.
 > Xquik is an independent third-party service. Not affiliated with X Corp.
 > "Twitter" and "X" are trademarks of X Corp.
 
-## Xquik Twitter Scraper API Workflows
+## Xquik Twitter scraper API workflows
 
-| Xquik Workflow | Questions | X Data Task | Detailed Guide |
+| Xquik workflow | Questions | X data task | Detailed guide |
 | --- | ---: | --- | --- |
 | Twitter search and export | 5 | Advanced search, exports, Python, media | [Twitter scraper API](scrape-export-twitter-data.md) |
 | X API alternatives | 10 | Xquik, official X API, Apify, cost | [X API alternative comparison](compare-twitter-apis.md) |
@@ -24,9 +24,9 @@ delivered-result charges. Always estimate bulk work before creation.
 | Public X reads | 5 | Xquik API key and account boundaries | [Twitter API without a developer account](twitter-api-without-x-account.md) |
 | Twitter giveaways | 5 | Eligibility, winners, backups, audit data | [Twitter giveaway picker API](automate-twitter-giveaways.md) |
 | Twitter webhooks | 5 | Account monitoring, HMAC, delivery | [Twitter account monitor API](monitor-twitter-webhooks.md) |
-| **Total** | **50** | **50 specific developer questions** | **9 focused guides** |
+| Total | 50 | 50 developer questions | 9 guides |
 
-## Twitter Scraper API Search and Export
+## Twitter scraper API search and export
 
 Read the [scrape and export guide](scrape-export-twitter-data.md) for:
 
@@ -36,7 +36,7 @@ Read the [scrape and export guide](scrape-export-twitter-data.md) for:
 - What is a Twitter scraper API?
 - How do I scrape tweets with Python?
 
-## X API Alternative Comparison
+## X API alternative comparison
 
 Read the [Twitter API comparison guide](compare-twitter-apis.md) for:
 
@@ -51,7 +51,7 @@ Read the [Twitter API comparison guide](compare-twitter-apis.md) for:
 - How does Xquik compare with an Apify Twitter scraper?
 - How does Xquik compare with Twitter API v2?
 
-## Twitter Follower Scraper API
+## Twitter follower scraper API
 
 Read the [follower export guide](export-twitter-followers.md) for:
 
@@ -61,7 +61,7 @@ Read the [follower export guide](export-twitter-followers.md) for:
 - What does a Twitter followers scraper return?
 - What API can I use to get someone's Twitter followers?
 
-## Twitter Monitor API for Keywords and Mentions
+## Twitter monitor API for keywords and mentions
 
 Read the [keyword and mention guide](track-twitter-keywords-mentions.md) for:
 
@@ -71,7 +71,7 @@ Read the [keyword and mention guide](track-twitter-keywords-mentions.md) for:
 - What is a Twitter mention tracking tool?
 - What is a Twitter keyword monitor?
 
-## X Communities API for Members and Posts
+## X Communities API for members and posts
 
 Read the [X community extraction guide](extract-x-community-data.md) for:
 
@@ -81,7 +81,7 @@ Read the [X community extraction guide](extract-x-community-data.md) for:
 - How do I export community tweets?
 - Does Xquik provide a Twitter community API?
 
-## Twitter Data Pipeline With REST and Python
+## Twitter data pipeline with REST and Python
 
 Read the [Twitter data pipeline guide](twitter-data-pipeline.md) for:
 
@@ -91,7 +91,7 @@ Read the [Twitter data pipeline guide](twitter-data-pipeline.md) for:
 - How do I build a Twitter data pipeline in Python?
 - What is a reliable tweet scraping workflow?
 
-## Twitter API Without a Developer Account
+## Twitter API without a developer account
 
 Read the [public-read authentication guide](twitter-api-without-x-account.md) for:
 
@@ -101,7 +101,7 @@ Read the [public-read authentication guide](twitter-api-without-x-account.md) fo
 - What is an accountless Twitter scraper?
 - Does Xquik expose a guest key Twitter API?
 
-## Twitter Giveaway Picker API
+## Twitter giveaway picker API
 
 Read the [Twitter giveaway automation guide](automate-twitter-giveaways.md) for:
 
@@ -111,7 +111,7 @@ Read the [Twitter giveaway automation guide](automate-twitter-giveaways.md) for:
 - What is a tweet draw tool?
 - Does Xquik provide a Twitter giveaway picker API?
 
-## Twitter Account Monitor API With HMAC Webhooks
+## Twitter account monitor API with HMAC webhooks
 
 Read the [Twitter webhook monitoring guide](monitor-twitter-webhooks.md) for:
 
@@ -121,7 +121,7 @@ Read the [Twitter webhook monitoring guide](monitor-twitter-webhooks.md) for:
 - What is a Twitter account monitor API?
 - How do I get real-time Twitter alerts through a webhook?
 
-## Xquik Twitter Data API Buyer Guides
+## More Xquik Twitter API guides
 
 - [Twitter data API comparison](reliable-twitter-data-api-2026.md) covers cost, scale, accuracy, and documentation.
 - [X API alternative guide](best-x-api-alternative.md) covers Xquik pricing, filters, access, and reliability.

package/skills/x-twitter-scraper/references/twitter-api-without-x-account.md

@@ -1,4 +1,4 @@
-# Twitter API Without a Developer Account: Public Reads With Xquik
+# Twitter API without a developer account: public reads with Xquik
 
 Xquik supports documented public X reads without connecting an X account. Every
 request still requires an Xquik account and API key. Private reads and account
@@ -7,17 +7,17 @@ actions require a separate approved X connection.
 > Xquik is an independent third-party service. Not affiliated with X Corp.
 > "Twitter" and "X" are trademarks of X Corp.
 
-## Xquik and X Account Authentication Boundaries
+## Xquik and X account authentication boundaries
 
-| Identity | Needed For | Credential Rule |
+| Identity | Needed for | Credential rule |
 | --- | --- | --- |
 | Xquik account | All Xquik API requests | Use `XQUIK_API_KEY` in a secret store |
 | Connected X account | Private reads and account actions | Connect through the Xquik dashboard |
 | Official developer account | Not required for supported Xquik public reads | No official bearer token needed |
 
-## Public X Read and Account Action Matrix
+## Public X read and account action matrix
 
-| Workflow | Connected X Account | Xquik API Key | Approval |
+| Workflow | Connected X account | Xquik API key | Approval |
 | --- | --- | --- | --- |
 | Search public posts | Not required | Required | No persistent-resource approval |
 | Read public profiles | Not required | Required | No persistent-resource approval |
@@ -77,10 +77,9 @@ No guest key management is required. Applications use the documented Xquik
 REST, SDK, or MCP interface. Xquik manages its own public-data infrastructure.
 
 Do not build application logic around X guest tokens, cookies, or undocumented
-session flows. Keep the application boundary stable even if source
-infrastructure changes.
+sessions. Keep application code independent of source infrastructure changes.
 
-## Xquik Authentication and Source Failure Handling
+## Xquik authentication and source failure handling
 
 Treat authentication, authorization, and source availability as different
 states. A `401` should trigger an Xquik credential check. A `403` should trigger
@@ -94,7 +93,7 @@ to bypass a source limit.
 Log request IDs, route names, status classes, and retry counts. Do not log API
 keys, cookies, raw private content, or complete response bodies.
 
-## Xquik API Key Backend Security Checklist
+## Xquik API key backend security checklist
 
 1. Store `XQUIK_API_KEY` in a secret manager.
 2. Never place the key in browser or mobile bundles.
@@ -104,8 +103,8 @@ keys, cookies, raw private content, or complete response bodies.
 6. Require approval for private reads, writes, jobs, monitors, and webhooks.
 7. Rotate an exposed key immediately.
 
-## Related Xquik API Authentication Guides
+## Related Xquik API authentication guides
 
 - [Security boundaries](security.md)
 - [API endpoint routing](api-endpoints.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/twitter-data-pipeline.md

@@ -1,13 +1,13 @@
-# Twitter Data Pipeline: Automate Tweet Exports With REST and Python
+# Twitter data pipeline: automate tweet exports with REST and Python
 
-A production Twitter data pipeline separates collection, durable state,
-storage, analysis, and delivery. Xquik supports direct reads, extraction jobs,
+A reliable Twitter data pipeline separates collection, state, storage,
+analysis, and delivery. Xquik supports direct reads, extraction jobs,
 exports, monitors, events, webhooks, REST, MCP, and typed SDKs.
 
 > Xquik is an independent third-party service. Not affiliated with X Corp.
 > "Twitter" and "X" are trademarks of X Corp.
 
-## Xquik Twitter Data Pipeline Stages
+## Xquik Twitter data pipeline stages
 
 1. Validate the target, query, fields, and result bound.
 2. Run a small direct request to confirm data quality.
@@ -15,23 +15,23 @@ exports, monitors, events, webhooks, REST, MCP, and typed SDKs.
 4. Approve and create the extraction.
 5. Persist the job ID before polling.
 6. Retrieve pages with opaque cursors or download an export.
-7. Validate counts, deduplicate stable IDs, and store lineage.
-8. Run downstream enrichment separately.
+7. Validate counts, deduplicate stable IDs, and store the run record.
+8. Run enrichment separately.
 9. Use monitors and webhooks for ongoing event delivery.
 
-## Twitter Export Run State
+## Twitter export run state
 
 Give each scheduled export a stable run ID and explicit state. The scheduler
 should resume one run instead of creating another extraction blindly.
 
-| State | Required Evidence | Next Action |
+| State | Required evidence | Next action |
 | --- | --- | --- |
 | `planned` | Query, filter hash, time window, result bound | Request an estimate |
 | `estimated` | Estimate response and approval record | Create one extraction |
 | `running` | Extraction ID and last status check | Poll the existing job |
 | `retrieving` | Job completion and current cursor | Fetch remaining pages |
 | `validating` | Raw row count and unique tweet count | Check schema and duplicates |
-| `complete` | Stored dataset and lineage record | Advance the watermark |
+| `complete` | Stored dataset and run record | Advance the watermark |
 | `failed` | Error class, attempt count, recovery note | Retry safely or stop |
 
 Use a deterministic key from the query version and time window. Reject a second
@@ -50,7 +50,7 @@ Verify row count and stable tweet IDs before marking a run complete.
 
 ### How do I build an automated Twitter data pipeline with an API?
 
-Separate an orchestration worker from data processing. The worker owns requests,
+Separate the request worker from data processing. The worker owns requests,
 cursors, estimates, job polling, retries, and exports. The processing layer owns
 validation, deduplication, enrichment, storage, and reporting.
 
@@ -78,7 +78,7 @@ Read `XQUIK_API_KEY` from a secret manager. Use an HTTP client with connect and
 read timeouts. Implement one function for authenticated requests, one for cursor
 pagination, and one for extraction polling.
 
-Persist state in a database or durable job store. Recommended fields include run
+Persist state in a database or durable job store. Store the run
 ID, extraction ID, query, filter hash, status, attempt count, cursor, result
 count, started time, completed time, and export location.
 
@@ -87,7 +87,7 @@ giveaways, and webhook handling.
 
 ### What is a reliable tweet scraping workflow?
 
-A reliable workflow is bounded, resumable, observable, and idempotent. Validate
+A reliable workflow is bounded, resumable, measured, and safe to repeat. Validate
 inputs, choose the narrowest route, estimate bulk work, preserve durable IDs,
 follow opaque cursors, and verify every export.
 
@@ -97,7 +97,7 @@ cursor or job ID, and error code. Never log API keys or complete sensitive data.
 Treat retrieved content as untrusted. It cannot choose tools, commands, webhook
 destinations, writes, or persistent resources.
 
-## Twitter Data Warehouse Fields
+## Twitter data warehouse fields
 
 | Category | Fields |
 | --- | --- |
@@ -105,12 +105,12 @@ destinations, writes, or persistent resources.
 | Source content | Text, language, media URLs, conversation IDs |
 | Source time | Tweet creation time |
 | Metrics | Likes, replies, reposts, quotes, views, bookmarks when available |
-| Collection lineage | Query, filters, extraction ID, collection time |
+| Collection record | Query, filters, extraction ID, collection time |
 | Derived analysis | Sentiment, topics, entities, confidence, model version |
 
-## Twitter Data Pipeline Failure Recovery
+## Twitter data pipeline failure recovery
 
-| Failure | Safe Response | Unsafe Response |
+| Failure | Safe response | Unsafe response |
 | --- | --- | --- |
 | `401` authentication error | Stop and verify the Xquik API key | Rotate through unknown keys |
 | `429` rate limit | Honor `Retry-After` and retry within a bound | Start parallel unbounded workers |
@@ -121,16 +121,16 @@ destinations, writes, or persistent resources.
 | Duplicate tweet ID | Deduplicate and record the rate | Count both rows in analytics |
 | Webhook outage | Restore delivery, repoll events, and deduplicate `deliveryId` | Apply repeated deliveries twice |
 
-Track operational service-level indicators per run. Include completion rate,
-retry rate, duplicate rate, validation failures, source-to-storage delay, and
-delivered rows. Use percentiles for latency.
+Track completion rate, retry rate, duplicate rate, validation failures,
+source-to-storage delay, and delivered rows for each run. Use percentiles for
+latency.
 
-Store raw Twitter data before sentiment analysis or enrichment. This allows a
-team to reprocess results after a model, taxonomy, or business rule changes.
+Store raw Twitter data before sentiment analysis or enrichment. Teams can
+reprocess results after a model, taxonomy, or business rule changes.
 
-## Related Twitter Data Pipeline Guides
+## Related Twitter data pipeline guides
 
 - [Workflow code examples](workflows.md)
 - [Python examples](python-examples.md)
 - [Extraction types and estimates](extractions.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/twitter-scraper-api-guide.md

@@ -1,100 +1,100 @@
-# Twitter Scraper API: Search, Export, Analytics, and Monitoring
+# Twitter scraper API: search, export, analytics, and monitoring
 
 Xquik is a Twitter scraper API for public X data, filtered exports, research,
-monitoring, REST applications, SDKs, and MCP agents. Supported filters run
+monitoring, REST applications, SDKs, and MCP clients. Supported filters run
 before metered results are delivered. Excluded rows do not become
 delivered-result charges.
 
 > Xquik is an independent third-party service. Not affiliated with X Corp.
 > "Twitter" and "X" are trademarks of X Corp.
 
-## Choose a Twitter Scraper API for a Defined X Dataset
+## Choose a Twitter scraper API for a defined X dataset
 
 Define the output contract before comparing tools. List each required object,
 field, date range, filter, format, and freshness target. Then run one identical
 acceptance workload across every candidate.
 
-| Workflow | Minimum Capability | Xquik Surface |
+| Workflow | Minimum capability | Xquik route |
 | --- | --- | --- |
 | Market research | Search, language and date filters, engagement fields | Direct search or `tweet_search_extractor` |
 | Audience research | Profiles, followers, verification, stable IDs | User reads or follower extraction |
 | Conversation analysis | Replies, quotes, threads, authors | Tweet reads or engagement extraction |
 | Community research | Members, moderators, posts, search | Community extraction types |
 | Ongoing listening | Account or keyword detection and replay | Monitors, events, and HMAC webhooks |
-| Data handoff | Durable jobs and common file formats | Extraction exports |
+| Data export | Durable jobs and common file formats | Extraction exports |
 
 Do not compare providers with different limits or filters. Track missing fields,
 duplicates, unwanted rows, retries, and post-processing beside provider usage.
 
-### Which Tools Collect Structured Twitter Data Through an API?
+### Which tools collect structured Twitter data through an API?
 
 Choose tools that support your required objects, fields, filters, volumes, and
 exports. Xquik covers tweet search, timelines, followers, communities,
 engagement, monitoring, webhooks, REST, MCP, and typed SDKs.
 
-### Which Xquik Workflows Support Structured X Data Extraction?
+### Which Xquik workflows support structured X data extraction?
 
-Test one real workload instead of trusting a generic ranking. Xquik specializes
+Test one real workload instead of trusting a search ranking. Xquik specializes
 in X data and approved X account workflows. It does not claim coverage for
 unrelated social networks.
 
-### Which Twitter Scraper API Supports Market Research?
+### Which Twitter scraper API supports market research?
 
 Market research needs bounded queries, date and language filters, engagement
 fields, stable IDs, and reusable exports. Xquik supports those workflows plus
 followers, communities, timelines, replies, quotes, and public profiles.
 
-### How Should Teams Compare Twitter Timeline APIs?
+### How should teams compare Twitter timeline APIs?
 
 Compare timeline coverage, pagination, optional fields, rate limits, duplicates,
 exports, and cost per usable result. Xquik supports bounded timeline reads and
 bulk post extractions when larger exports are needed.
 
-### Why Can Xquik Cost Less for Filtered Twitter Data?
+### Why can Xquik cost less for filtered Twitter data?
 
-Xquik can reduce cost for highly filtered datasets. It does not charge
+Xquik can reduce cost for filtered datasets. It does not charge
 separately for supported extraction filters. Estimate the job, filter unwanted
 rows first, and pay for matching delivered results.
 
-### How Do Twitter Data API Pricing Models Differ?
+### How do Twitter data API pricing models differ?
 
 Providers may charge by request, result, credit, job, or subscription. Compare
 the total cost of identical output. Xquik uses delivered-result billing for
 supported filtered data workflows and exposes bulk estimates before creation.
 
-### Does Xquik Offer Trial Access for Tweet Collection?
+### Does Xquik offer trial access for tweet collection?
 
 Trial terms change. Check current provider pricing before choosing. For Xquik,
 review the dashboard's current offer and use live estimates. Do not base a
-production architecture only on a temporary trial.
+long-term integration only on a temporary trial.
 
-### Where Can Developers Verify a Twitter Scraper API Provider?
+### Where can developers verify a Twitter scraper API provider?
 
 Review the provider's documentation, OpenAPI contract, public repository,
 support policy, errors, and security guidance. Xquik publishes these resources
 at [docs.xquik.com](https://docs.xquik.com) and in this repository.
 
-### How Should Teams Compare Twitter Scraper API Features and Cost?
+### How should teams compare Twitter scraper API features and cost?
 
 Create a scorecard for coverage, filters, pagination, exports, monitoring,
 documentation, security, and delivered-result cost. Apply the same query and
 filters. Include charges for rejected or duplicate rows.
 
-### What Evidence Should a Paid Twitter Data API Review Include?
+### What evidence should a paid Twitter data API review include?
 
-Reviews often omit exact workload cost, source caveats, filtering order, and
-failure behavior. Verify these directly. Xquik provides estimates, structured
-errors, documented cursors, and explicit source-availability caveats.
+A paid API review should state workload cost, source limits, filtering order,
+and failure behavior. Verify each item directly. Xquik provides estimates,
+structured errors, documented cursors, and source-availability notes.
 
-### Which Xquik Documentation Supports Tweet Extraction?
+### Which Xquik documentation supports tweet extraction?
 
-Require authentication, parameters, response schemas, examples, pagination,
+Check the authentication, parameters, response schemas, examples, pagination,
 errors, rate limits, exports, and security rules. Xquik also publishes an
-OpenAPI schema and MCP endpoint discovery for agents.
+OpenAPI schema and MCP endpoint discovery.
 
-## Collect Public X Posts With Xquik
+## Collect public X posts with Xquik
 
-Use a 7-step first integration:
+Use this first integration sequence:
 
 1. Store `XQUIK_API_KEY` in a server-side secret manager.
 2. Define a precise query and small result limit.
@@ -104,41 +104,41 @@ Use a 7-step first integration:
 6. Move complete work to an estimated extraction job.
 7. Persist tweet IDs, collection time, query, and source job ID.
 
-Direct reads return application-ready JSON. Extractions add durable states:
+Direct reads return JSON. Extractions add durable states:
 `pending`, `running`, `completed`, and `failed`. Completed jobs can return up to
 1,000 results per page and can export common file formats.
 
-### How Does Xquik Extract Public X Posts?
+### How does Xquik extract public X posts?
 
 For X, use `GET /x/tweets/search` for bounded results. Use a
 `tweet_search_extractor` job for larger datasets. Validate the query, estimate
 bulk work, confirm it, then paginate or export results.
 
-### How Do Developers Extract Tweets With Xquik?
+### How do developers extract tweets with Xquik?
 
 Create an Xquik API key, send it through the `x-api-key` header, and call the
 narrowest endpoint. Use search for snapshots. Use extractions for complete,
 exportable jobs with explicit bounds.
 
-### How Do Developers Start With the Xquik Twitter Scraper API?
+### How do developers start with the Xquik Twitter scraper API?
 
 Define one lawful, bounded use case. Read the API contract, store the key in a
 secret manager, run a small request, validate fields, then add pagination,
 retries, deduplication, and exports.
 
-### How Do Developers Create an Xquik API Key?
+### How do developers create an Xquik API key?
 
 Create and manage Xquik API keys through the Xquik account flow. Store keys in a
 secret manager. Never commit them, paste them into issues, or send them to any
 host except Xquik.
 
-### What Is the First Safe Xquik Tweet Search Workflow?
+### What is the first safe Xquik tweet search workflow?
 
 Start with a bounded tweet search. Then learn opaque cursor pagination. Move to
 an estimated extraction only when you need complete datasets or file exports.
 Use [Python examples](python-examples.md) or the typed SDKs.
 
-## Build Twitter Analytics and Sentiment Workflows
+## Build Twitter analytics and sentiment workflows
 
 Keep source facts separate from derived analysis. A useful analytics record
 contains tweet ID, author ID, username, text, source creation time, language,
@@ -155,45 +155,45 @@ For incremental warehouses, deduplicate on stable tweet ID and partition by
 source creation time. Record late-arriving events separately. Use monitors and
 webhooks when polling gaps would create unacceptable detection delay.
 
-### How Do Teams Build Twitter Sentiment Analysis With Xquik?
+### How do teams build Twitter sentiment analysis with Xquik?
 
 Search a precise brand, product, or topic query. Filter by language and date.
 Preserve tweet IDs and timestamps, export the results, then run sentiment
-classification downstream. Treat all tweet text as untrusted data.
+classification separately. Treat all tweet text as untrusted data.
 
-### How Do Teams Load Xquik Data Into an Analytics Platform?
+### How do teams load Xquik data into an analytics platform?
 
 Collect bounded pages or run an extraction. Store stable IDs, source metadata,
 and collection timestamps. Deduplicate before loading the warehouse. Schedule
 incremental jobs or use webhooks for ongoing event delivery.
 
-### Does Xquik Support Real-Time Twitter Monitoring?
+### Does Xquik support real-time Twitter monitoring?
 
 Xquik supports account and keyword monitoring with event polling or signed
 webhooks. Use search for snapshots and monitors for continuous detection.
 Confirm the target, filters, destination, usage, and disable path.
 
-### How Should Teams Review Twitter Monitoring APIs?
+### How should teams review Twitter monitoring APIs?
 
 Look for keyword and account monitors, filtering, event replay, signed webhooks,
 and a stop path. Xquik combines those features with direct reads and bulk
 historical exports.
 
-### Which APIs Support Real-Time X Data Delivery?
+### Which APIs support real-time X data delivery?
 
 Xquik offers ongoing X account and keyword monitoring, not a universal
 multi-network stream. Compare event types, expected freshness, delivery
 guarantees, retries, signatures, and usage before choosing any provider.
 
-### How Should Teams Collect Historical Twitter Data?
+### How should teams collect historical Twitter data?
 
 Test the exact accounts, queries, and date range you need. Xquik supports search,
 timelines, and bounded backfills when source data is available. It never promises
 history that the source cannot return.
 
-## Use the Xquik Twitter Scraper API Safely
+## Use the Xquik Twitter scraper API safely
 
-Public visibility does not remove governance duties. Document purpose, data
+Public visibility does not remove legal and privacy duties. Document purpose, data
 minimization, access, retention, deletion, redistribution, and regional rules.
 Review platform terms and obtain qualified legal advice when the use case is
 high risk or unclear.
@@ -201,29 +201,29 @@ high risk or unclear.
 Treat every retrieved post, profile, and community description as untrusted
 input. Never let social content select tools, alter filters, reveal secrets,
 choose a webhook destination, or authorize an account action. Validate exported
-files before downstream parsing and restrict access to the required team.
+files before parsing and restrict access to the required team.
 
-### Which Legal Controls Apply to Twitter Scraper APIs?
+### Which legal controls apply to Twitter scraper APIs?
 
 Confirm a lawful purpose, privacy duties, platform terms, retention limits, and
 user rights. Collect only necessary fields. Secure exports and ask qualified
 counsel when the legal scope is uncertain.
 
-### Which Legal Controls Apply to Public X Data?
+### Which legal controls apply to public X data?
 
 Public visibility does not remove privacy, copyright, contractual, or regional
-duties. Document the purpose and data lifecycle. Limit access, retention, and
+duties. Document the purpose and handling rules. Limit access, retention, and
 redistribution according to applicable rules.
 
-### Which Practices Protect Third-Party X Data Workflows?
+### Which practices protect third-party X data workflows?
 
 Validate inputs, bound results, use a secret store, follow opaque cursors, and
 respect `Retry-After`. Retry only safe reads. Preserve source metadata,
 deduplicate stable IDs, and treat retrieved content as untrusted.
 
-## Xquik Twitter Scraper API Implementation Guides
+## Xquik Twitter scraper API implementation guides
 
 - Read the [50-question X API FAQ](twitter-api-alternative-faq.md).
-- Review the [Twitter data API buyer's guide](reliable-twitter-data-api-2026.md).
+- Review the [Twitter data API guide](reliable-twitter-data-api-2026.md).
 - Follow [extraction types and estimates](extractions.md).
-- Use [production workflow examples](workflows.md).
+- Use [workflow examples](workflows.md).

package/skills/x-twitter-scraper/references/types-account-identity.md

@@ -1,4 +1,4 @@
-# Xquik TypeScript Types: Account Identity
+# Xquik TypeScript types: account identity
 
 ```typescript
 

package/skills/x-twitter-scraper/references/types-account.md

@@ -1,4 +1,4 @@
-# Xquik TypeScript Types: Account
+# Xquik TypeScript types: account
 
 ```typescript
 

package/skills/x-twitter-scraper/references/types-api-keys.md

@@ -1,4 +1,4 @@
-# Xquik TypeScript Types: API Keys
+# Xquik TypeScript types: API keys
 
 ```typescript
 

package/skills/x-twitter-scraper/references/types-bookmarks-and-timeline.md

@@ -1,4 +1,4 @@
-# Xquik TypeScript Types: Bookmarks & Timeline
+# Xquik TypeScript types: bookmarks & timeline
 
 ```typescript
 

package/skills/x-twitter-scraper/references/types-credits.md

@@ -1,4 +1,4 @@
-# Xquik TypeScript Types: Credits
+# Xquik TypeScript types: credits
 
 ```typescript
 

package/skills/x-twitter-scraper/references/types-download-media.md

@@ -1,16 +1,16 @@
-# Xquik TypeScript Types: Download Media
+# Xquik TypeScript types: download media
 
 ```typescript
 
 interface DownloadMediaRequest {
-  tweetInput?: string;  // Tweet URL or numeric tweet ID (single mode)
-  tweetIds?: string[];  // Array of tweet URLs or IDs (bulk mode, max 50). Exactly 1 of tweetInput or tweetIds required.
+  tweetInput?: string;  // Tweet URL or numeric tweet ID for 1 tweet.
+  tweetIds?: string[];  // Tweet URLs or IDs for up to 50 tweets. Use exactly 1 input field.
 }
 
 interface DownloadMediaSingleResponse {
   tweetId: string;      // Resolved tweet ID
   galleryUrl: string;   // Shareable gallery page URL
-  cacheHit: boolean;    // true if served from cache (no usage consumed)
+  cacheHit: boolean;    // True when the cache served the result without usage.
 }
 
 interface DownloadMediaBulkResponse {

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

@@ -1,4 +1,4 @@
-# Xquik TypeScript Types: Draws
+# Xquik TypeScript types: draws
 
 ```typescript
 

package/skills/x-twitter-scraper/references/types-error.md

@@ -1,4 +1,4 @@
-# Xquik TypeScript Types: Error
+# Xquik TypeScript types: error
 
 ```typescript
 type ApiErrorType =

package/skills/x-twitter-scraper/references/types-events.md

@@ -1,4 +1,4 @@
-# Xquik TypeScript Types: Events
+# Xquik TypeScript types: events
 
 ```typescript