Bright Data
Analysis
This looks like a straightforward Bright Data search and scraping wrapper, but it uses a Bright Data API key and can send chosen queries or URLs to Bright Data, including for CAPTCHA-bypass scraping.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
Scrape any webpage as markdown. Bypasses bot detection and CAPTCHA.
The broad scraping and bot/CAPTCHA-bypass capability is clearly disclosed and matches the skill purpose, but it is a capability users should consciously direct and use only on appropriate targets.
Source: unknown; Homepage: none
The artifact does not identify an official source or homepage, so users cannot verify from metadata whether it is published by Bright Data, even though the included code is transparent and simple.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
-H "Authorization: Bearer $BRIGHTDATA_API_KEY"
The script authenticates to Bright Data using an environment-provided API key. This is expected for the integration, but it gives the skill access to a provider credential that may incur usage or billing.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
--arg url "$URL" ... curl -s -X POST 'https://api.brightdata.com/request' ... -d "$PAYLOAD"
The user-supplied target URL is sent to Bright Data in the API request. This is purpose-aligned, but it means URLs and scraping requests are shared with the external provider.
