Clickbank Scraper
Analysis
The artifacts match a straightforward ClickBank scraping/export tool, with only disclosed, purpose-aligned notes around npm dependencies, optional affiliate ID use, and optional scheduling.
Findings (3)
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.
"dependencies": { "cheerio": "^1.2.0", "node-fetch": "^2.7.0" }Running npm install will use third-party packages, which is normal for a Node-based HTML scraper but still part of the trusted install surface.
Use OpenClaw cron or n8n workflows to run daily ... "schedule": "0 9 * * *", "command": "CB_AFFILIATE_ID=your_id node scraper.js"
The documentation shows optional recurring execution through cron or n8n.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
affiliateId: process.env.CB_AFFILIATE_ID || 'YOUR_CB_NICKNAME' ... hoplink: vendorId ? makeHoplink(vendorId, CONFIG.affiliateId) : null
The optional affiliate identifier is read from the environment and embedded into generated hoplinks.
