Build, run, and customize a LaunchMyStore e-commerce store from natural language. Use when the user wants to scaffold an app, ship a storefront / checkout / admin extension, build and deploy a WASM Function, configure App Bridge actions (Toast, Modal, ResourcePicker, SessionToken, TitleBar...), manage products / orders / customers / themes via the LaunchMyStore MCP server, or write Aqua (Liquid-dialect) theme code. Triggers include: "build a LaunchMyStore app", "lms cli", "add a discount function", "set up app bridge", "manage my store with AI", "write a theme block", "install an extension", "deploy a function", "use launchmystore", "lms", or any mention of LaunchMyStore / launchmystore.io.
69
85%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Security
2 findings — 2 medium severity. This skill can be installed but you should review these findings before use.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Third-party content exposure detected (high risk: 0.80). The skill's MCP workflows (references/07-merchant-mcp.md and related examples) instruct the agent to call tools like get_products, get_reviews, theme_read_file, theme_read_file/theme_write_file, chat_with_data and image_to_listing (including user-provided image URLs), so the agent will fetch and read merchant- and user-generated third‑party content that could contain embedded instructions affecting subsequent actions.
The skill is specifically designed for direct financial operations, giving the agent the ability to move money or execute financial transactions — such as payment processing, cryptocurrency operations, banking integrations, or market order execution.
Direct money access detected (high risk: 1.00). The LaunchMyStore skill is explicitly designed to operate an e-commerce merchant stack end-to-end via its MCP server and developer surfaces. The doc explicitly references checkout, billing, managing products/orders/customers, and even describes destructive merchant-data actions such as "refunding orders" (which it requires confirmation for). Those are concrete money-moving/financial operations performed against a merchant store (billing/refunds/checkout). Although it does not name a specific third-party gateway like Stripe/PayPal, the skill's primary purpose is merchant financial operations (billing, refunds, checkout) rather than a generic automation tool. Therefore it grants direct financial execution capabilities.
3bf5125
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.