afrexai-web-scraping-engine_skill

This skill helps you design, implement, and audit scalable web scraping pipelines while ensuring legality, reliability, and data quality.
  • Python

2.6k

GitHub Stars

3

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill afrexai-web-scraping-engine

  • _meta.json316 B
  • README.md2.9 KB
  • SKILL.md31.9 KB

Overview

This skill is a complete web scraping and data extraction engine covering legal compliance, architecture, anti-detection, parsing, and production data pipelines. It provides practical decision rules, request and browser patterns, and operational best practices for building reliable, scalable scrapers in Python. Use it to design compliant, maintainable, and robust scraping systems at scale.

How this skill works

The skill inspects target sites for legal constraints (robots.txt, ToS, data classification) and produces an architecture brief that matches content rendering and anti-bot posture. It provides ready patterns for HTTP requests, browser automation (Playwright), parsing (JSON-LD, Open Graph, CSS/XPath, tables), pagination, proxy strategies, and monitoring/validation pipelines. It also gives anti-detection and escalation rules for Cloudflare and other WAFs.

When to use it

  • Building a new scraper or choosing tools for a target site
  • Assessing legal risk before starting a data collection project
  • Scaling single-page scrapers into production pipelines
  • Bypassing complex JavaScript rendering and anti-bot defenses safely
  • Designing retries, rate limits, and monitoring for reliable operations

Best practices

  • Start with a legal compliance check: robots.txt, ToS, PII and copyright
  • Prefer official APIs when available; only scrape when justified
  • Use structured sources first (JSON-LD, Open Graph, microdata) before CSS/XPath
  • Implement retries, exponential backoff, random jitter and respect Retry-After
  • Match headers and UA distributions to proxy geo and simulate natural navigation
  • Validate, deduplicate, and version data before storage; monitor success rates

Example use cases

  • Crawl e-commerce listings daily for price monitoring with pagination and dedupe
  • Extract product metadata from JS-heavy SPAs using Playwright and JSON-LD
  • Set up competitor monitoring with scheduled scrapers, proxy rotation, and alerts
  • Migrate a manual scraping workflow to Scrapy/Crawlee with a production pipeline
  • Recover tabular datasets from archived pages using pandas.read_html and validation

FAQ

Not always. Use proxies for high-volume scraping, geo-targeting, or when sites show anti-bot blocks. Start with datacenter proxies and escalate to residential/mobile only if you see blocks or low success rates.

How should I handle sites that block AI crawlers in robots.txt?

Respect those directives. If you need the data, request permission, use an official API, or find alternative sources. Collecting data for AI training requires explicit attention to AI-specific blocks.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational