Scrapling Fetch

支持自动绕过 Cloudflare Turnstile 和微信公众号反爬机制的网页内容抓取工具，输出干净Markdown或纯文本。

This skill appears to do the scraping it claims, but there are red flags you should address before installing or running it: - Hard-coded billing API key: scripts/fetch_paid.py contains a visible BILLING_API_KEY value. Do not use the paid script as-is — that key may belong to someone else, could be revoked, or could be abused to query/charge the billing service. Replace it with your own key (or modify the script to read the key from an environment variable) before using paid mode. - VENV path mismatch: both scripts call a hard-coded VENV_PYTHON (/Users/gaolei/...) which likely won't exist on your machine. Update the path to your environment or run the scripts with your python interpreter to avoid unintentionally invoking an unexpected interpreter. - Missing/ambiguous install step: the repo mentions pip install and playwright install, but the registry has no install spec. Ensure dependencies (scrapling, playwright, requests, etc.) are installed in an isolated virtualenv before running. - Network & legal considerations: the tool bypasses anti-bot protections. Verify you have legal/rightful permission to scrape target sites and review terms of service before using bypass techniques. - Operational safety: run initial tests against safe/public pages. If you must use paid mode, prefer a modified script that reads BILLING_API_KEY from an environment variable (not hard-coded), verify the billing endpoint behavior, and confirm the SKILL_ID and payment flows are legitimate. If you are not comfortable making these code changes, avoid enabling the paid mode and prefer the free/fast path (Jina) after installing dependencies in a controlled environment. If you plan to share the skill, remove embedded secrets and fix the venv/path assumptions first.

Type: OpenClaw Skill Name: scrapling-fetch Version: 1.1.0 The skill contains a critical Python code injection vulnerability in both `scripts/fetch.py` and `scripts/fetch_paid.py`, where the `url` argument is unsanitized and embedded directly into a string executed via `subprocess.run`. It also implements a non-standard monetization system using an obscure third-party service (skillpay.me) with a hardcoded API key, which tracks usage and requests payments. Furthermore, the scripts contain hardcoded local file paths (e.g., `/Users/gaolei/...`), indicating poor packaging and potential execution failures on other systems.