Shopify Link Checkout
WarnAudited by ClawScan on May 10, 2026.
Overview
This skill is built to complete real online purchases and includes payment credential handling plus explicit bot-detection bypass techniques, so it should be reviewed carefully before use.
Review this skill before installing. It is meant to make real purchases, uses sensitive payment and identity information, and contains explicit anti-bot bypass instructions. Only use it in a tightly controlled environment, with a spend-limited payment method, after confirming the exact purchase details, and only where browser automation is permitted.
Findings (5)
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.
The agent could place a real order and charge an approved payment method once the checkout script is run.
The script automatically selects a shipping option and clicks the final purchase button. This is aligned with the purchasing purpose, but it is a high-impact financial action without an in-script final confirmation or total verification step.
if (sr.length > 0) await sr[0].click(); ... await page.locator('button:has-text("Pay now")').first().click();Only use this after explicitly confirming the exact merchant, item, quantity, shipping method, taxes, fees, and maximum charge; consider adding a mandatory final human approval immediately before clicking Pay now.
Using the skill may evade store anti-bot protections and could violate merchant policies or cause checkout behavior the store is trying to block.
The skill explicitly instructs the agent to bypass merchant bot-detection controls during checkout.
Always use `https://{domain}/cart/{variantId}:1` to enter checkout. This bypasses Cloudflare bot detection that blocks direct `/checkout` navigation.Do not use this skill to bypass bot-detection or anti-abuse systems; remove stealth/bypass guidance and require checkout only where automation is permitted.
A user may not realize the skill needs access to payment authority, API secrets, and local Stripe Link session material.
The skill depends on payment-session credentials and Shopify API secrets, and references a local credential file, while the registry metadata declares no required credentials or config paths.
Requires: Stripe Link CLI authenticated, Shopify Catalog API credentials, Playwright with Chromium. ... Backup credentials from `~/.config/link-cli-nodejs/config.json`.
Declare all required credentials and config paths in metadata, avoid vague credential backup instructions, and scope payment credentials to one purchase with clear user approval.
Sensitive payment details may be visible outside the browser checkout flow even if the card is spend-limited.
The workflow passes raw one-time card number, expiration, and CVC as command-line arguments. This is purpose-aligned for checkout, but payment data in argv can be exposed through shell history, logs, or process listings depending on the runtime.
node scripts/shopify-checkout.mjs <store-domain> <variant-id> <card-number> <MM/YY> <cvc> ...
Prefer passing card details through a protected input channel, temporary file with strict permissions, or stdin, and avoid logging full command lines.
If the downloads are tampered with or versions drift, Chromium could load untrusted native libraries.
The optional Chromium dependency instructions download native Debian packages over HTTP and extract them into a library path, without checksum or signature verification in the artifact.
BASE="http://deb.debian.org/debian/pool/main" ... curl -sLO "$BASE/n/nspr/libnspr4_4.35-1_amd64.deb"
Use trusted package managers or HTTPS sources with checksum/signature verification, and pin dependency versions where possible.