ClawHub

Dropshipping Operations

v1.0.0

Dropshipping business operations for Shopify/WooCommerce store owners sourcing from AliExpress, CJDropshipping, or US suppliers. Order tracking, supplier com...

⭐ 0· 30·0 current·0 all-time
by@joshbuildswithdoit
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description align with the SKILL.md content: order management, supplier/customer templates, product research, and financial checklists are all coherent for a dropshipping operations assistant.
ℹ
Instruction Scope
The instructions are scoped to templates, checklists, and reporting. They explicitly ask the user to provide store URL, top products, primary supplier contacts, and financial targets; this is relevant to the stated purpose but involves business-sensitive data. The instructions do not direct the agent to read system files, environment variables, or external endpoints.
✓
Install Mechanism
No install spec and no code files — instruction-only skill. This minimizes code-execution and supply-chain risk.
ℹ
Credentials
The skill requests no environment variables, credentials, or config paths (proportionate). However it asks users to paste business-sensitive information (store URL, supplier contacts, ad spend/ROAS) into the agent, which could expose confidential data if shared carelessly.
✓
Persistence & Privilege
always is false and the skill does not request persistent system presence or modify other skills. It operates as a normal, user-invocable instruction-only skill.
Assessment
This skill appears internally consistent and doesn't install code or request system credentials, but it does ask you to provide sensitive business data (store URL, top products by revenue, supplier contact details, ad spend/ROAS). Before sharing: avoid pasting admin/API keys, full customer lists, or payment processor credentials; redact or summarize sensitive fields where possible (e.g., share product SKUs and anonymized metrics rather than raw customer data). If you need supplier contact templates, prefer placeholder contact info rather than real PII during testing. Monitor outputs for leaked identifiers and only share additional confidential data with trusted, authenticated integrations or tools.

Like a lobster shell, security has layers — review code before you run it.

latestvk971s8c7eja71jjzhjyd3d9x2s84z3ca

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments