E-Commerce Personalization
v1.0.0Design personalization strategies for e-commerce stores. Product recommendations, dynamic content, customer segmentation, and personalized email/SMS based on...
⭐ 1· 83·0 current·0 all-time
bynexscope-ai@nexscope
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The name/description (personalization strategies for e‑commerce) align with the SKILL.md content (segmentation, recommendations, A/B testing, privacy guidance). The skill does not request unrelated credentials, binaries, or system access that would be out of scope for advisory work.
Instruction Scope
Runtime instructions are limited to asking the user clarifying questions, applying frameworks, and producing structured recommendations. The SKILL.md does not instruct the agent to read local files, export arbitrary data, or access system environment variables.
Install Mechanism
The registry contains no formal install spec (instruction-only), but SKILL.md suggests an npx install (npx skills add nexscope-ai/eCommerce-Skills). That command would fetch and run third‑party code; while common for JS packages, it is an external operation outside the skill bundle and should be reviewed before running.
Credentials
The skill declares no required environment variables, credentials, or config paths. For a consultancy/advisory skill this is proportionate. It does reference integrations (Shopify, WooCommerce, etc.) but does not request tokens — expected for a strategy/design skill.
Persistence & Privilege
The skill is not forced always-on and uses default autonomous invocation settings. There is no code in the bundle that would persist or modify other skills or agent configuration.
Assessment
This skill appears to be a straightforward advisory/instruction skill and matches its description. Before installing or running the suggested npx command, review the remote package/repository (nexscope-ai/eCommerce-Skills) to verify the publisher and inspect the code or package contents; avoid running npx on untrusted sources in a production environment. If you plan to connect real stores (Shopify, WooCommerce, etc.), never paste API keys or secrets into chat — instead use the platform's secure app/auth flows. If you want stronger assurance, ask for the GitHub repo URL to inspect code, look for an official homepage or organization identity, and test any remote install in an isolated environment.Like a lobster shell, security has layers — review code before you run it.
latestvk97brzqkscjmsfz3mb49bbvh3583ndc8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.