@askqa/mcp 1.0.5 → 1.0.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -0,0 +1,55 @@
|
|
|
1
|
+
# Monitor Shopify Add to Cart
|
|
2
|
+
|
|
3
|
+
Use this skill to set up automated monitoring for a Shopify store's add-to-cart flow. When the button breaks — due to an app update, theme change, or platform rollout — AskQA catches it within minutes and sends an alert with a screenshot.
|
|
4
|
+
|
|
5
|
+
## Step 1: Get the store URL
|
|
6
|
+
|
|
7
|
+
Ask the user for their Shopify store URL (e.g. `https://my-store.myshopify.com` or their custom domain). The test works on any public Shopify storefront — no credentials or API keys are needed.
|
|
8
|
+
|
|
9
|
+
## Step 2: Create the test
|
|
10
|
+
|
|
11
|
+
Use the `create_test` MCP tool with these parameters:
|
|
12
|
+
|
|
13
|
+
- `name`: something descriptive like "Shopify add to cart"
|
|
14
|
+
- `url`: the store URL from Step 1
|
|
15
|
+
- `template_id`: `cart-visible`
|
|
16
|
+
|
|
17
|
+
This template opens a real browser, finds a product on the homepage, clicks Add to Cart, and verifies the product lands in the cart — exactly how a customer would do it.
|
|
18
|
+
|
|
19
|
+
## Step 3: Run it once to verify
|
|
20
|
+
|
|
21
|
+
Use `run_test` with the test ID returned from Step 2. Wait for the result.
|
|
22
|
+
|
|
23
|
+
If it passes: great, the test is working correctly. Proceed to Step 4.
|
|
24
|
+
|
|
25
|
+
If it fails: the most common causes on Shopify are:
|
|
26
|
+
- The homepage shows a banner or popup blocking the first product link — let the user know and ask if they want to try a specific product URL instead
|
|
27
|
+
- The store uses an unconventional theme — try passing the product page URL directly as the `url` parameter
|
|
28
|
+
- The add-to-cart button is genuinely broken (that's exactly what this monitor is for!)
|
|
29
|
+
|
|
30
|
+
## Step 4: Schedule hourly monitoring
|
|
31
|
+
|
|
32
|
+
Use `schedule_test` with:
|
|
33
|
+
|
|
34
|
+
- `test_id`: the ID from Step 2
|
|
35
|
+
- `interval`: `hourly`
|
|
36
|
+
|
|
37
|
+
Hourly is the recommended cadence for checkout monitoring — it catches breakage within 60 minutes, well before most customers notice.
|
|
38
|
+
|
|
39
|
+
## Step 5: Set up alerts (optional but recommended)
|
|
40
|
+
|
|
41
|
+
Ask the user how they want to be notified when the test fails. Options:
|
|
42
|
+
|
|
43
|
+
- **Email**: use `add_notification_channel` with `channel_type: email`
|
|
44
|
+
- **Slack**: use the `/setup-slack` skill first, then link the channel
|
|
45
|
+
- **Skip**: they can always check results manually with `get_test_results`
|
|
46
|
+
|
|
47
|
+
## Step 6: Confirm
|
|
48
|
+
|
|
49
|
+
After setup, confirm:
|
|
50
|
+
|
|
51
|
+
- The test is saved and has a passing run
|
|
52
|
+
- A schedule is active (use `list_schedules` to show them)
|
|
53
|
+
- Alerts are configured if they chose that option
|
|
54
|
+
|
|
55
|
+
Let the user know: AskQA will now run this test every hour. If add-to-cart ever breaks, they'll get a notification with a screenshot of exactly where it failed.
|