Back to skill
Skillv1.0.0
ClawScan security
Dropship Product Pipeline · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
SuspiciousMar 5, 2026, 11:15 PM
- Verdict
- suspicious
- Confidence
- medium
- Model
- gpt-5-mini
- Summary
- The skill's instructions and required credentials line up with a dropshipping pipeline, but there are important inconsistencies and missing pieces (no code or install spec, registry metadata omits the env/binaries listed in SKILL.md) that make it unclear what you would actually run or where sensitive data would go.
- Guidance
- Do not run unknown node scripts referenced by this SKILL.md without inspecting them first. The SKILL.md lists many secrets (CJ, WooCommerce, WordPress, Flux Kontext, OpenAI) and will transmit product photos/metadata to external AI services — consider privacy and IP implications. Resolve the metadata mismatch: the registry claims no required envs/binaries but SKILL.md requires node and many keys. Ask the publisher for the pipeline code (scripts/pipeline.js) and review it line-by-line (or run it in an isolated test environment) before supplying real credentials. If you proceed, create least-privilege API keys (restrict to needed scopes and test with a dry-run), and prefer non-production stores/accounts for initial testing.
Review Dimensions
- Purpose & Capability
- noteThe SKILL.md describes CJ Dropshipping → image generation (Flux Kontext / OpenAI) → WooCommerce/WordPress publishing which coherently requires CJ, FAL/OPENAI, WooCommerce, and WP credentials. However, the registry metadata above the SKILL.md lists no required env vars or binaries while SKILL.md lists many — this mismatch is unexpected and reduces trust.
- Instruction Scope
- concernThe instructions tell the agent/user to run node scripts (node scripts/pipeline.js) that are not included in the skill bundle. The pipeline will send real CJ product photos to third-party image-generation services (Flux Kontext and OpenAI) and will publish to WooCommerce/WordPress. That’s consistent with the stated purpose but raises data-exfiltration and privacy considerations — product images and product metadata will be transmitted to external AI services. The SKILL.md also references a local cj-supplier-selection.json file and writing pipeline-result-{slug}.json, so you must review any script that implements those behaviors before running.
- Install Mechanism
- noteNo install spec (instruction-only) reduces installation risk. However, the skill requires node and an unspecified scripts/pipeline.js that is not provided in the bundle — the instructions assume you have or will place code on disk. That gap is suspicious: either the skill is only documentation for a separate code repo, or it expects you to obtain/run external code not reviewed here.
- Credentials
- noteThe SKILL.md requests multiple secrets (FAL_KEY, OPENAI_API_KEY, CJ_ACCESS_TOKEN, WOO_URL/WOO_KEY/WOO_SECRET, WP_URL/WP_USER/WP_APP_PASS) that are proportional to the described pipeline. Requiring both Flux Kontext and OpenAI keys is explained (primary + fallback). The registry metadata's omission of these env vars is an inconsistency to resolve before trusting the skill. Ensure keys are scoped/limited (read-only or limited-scope API keys) where possible.
- Persistence & Privilege
- okThe skill does not request always:true and has no install that would grant persistent privileged presence. The SKILL.md indicates outputs written to local files (hero-*.jpg, pipeline-result-*.json) which is normal for a pipeline. There is no evidence here the skill modifies other skills or system-wide agent settings.