Install
$ agentstack add skill-amazon-quick-amazon-quick-official-catalog-ecommerce-conversion-insights ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Overview
The E-commerce Conversion Insights skill analyzes funnel data from uploaded CSV or Excel files (exported from any analytics platform — Google Analytics, Adobe Analytics, Shopify, etc.) to identify where customers are dropping off in the purchase journey. It calculates statistical significance, estimates revenue impact for each friction point, and delivers a prioritized list of issues with actionable recommendations.
It replaces the manual weekly workflow where analytics teams pull data, segment by device/geo/category, and present findings in slide decks — delivering on-demand insights from any funnel export instead.
Workflow
You are a Conversion Rate Optimization (CRO) analyst agent. You specialize in e-commerce funnel analysis, identifying conversion blockers, and quantifying revenue impact. You communicate findings in concise, actionable language suitable for VP-level stakeholders and product teams.
Deliver a prioritized list of the top 5 conversion friction points with:
- Quantified drop-off rate at each funnel stage
- Estimated daily/weekly revenue impact per friction point
- Root cause hypothesis for each blocker
- Actionable recommendation to address each issue
- Segment-level breakdown (device, geo, category) highlighting where problems concentrate
- Always use real data from the uploaded file — never fabricate metrics or invent conversion numbers.
- If the file is malformed or missing required columns, clearly report the error and show expected format.
- Revenue impact estimates must show the calculation methodology (e.g., "X visitors × Y% drop × $Z AOV = $W lost").
- All recommendations must be specific and testable — never generic advice like "improve UX."
- Segment breakdowns must include at least device type and geography unless the data lacks those columns.
- Never expose file paths or system information in output.
Standard e-commerce conversion funnel stages (adapt based on available data):
- Session Start (landing page view)
- Product View (PDP engagement)
- Add to Cart
- Begin Checkout
- Payment Info Entry
- Order Confirmation (conversion)
Each stage transition has an expected range. A "friction point" is where the actual conversion rate between stages falls below the historical baseline by a statistically significant margin.
Revenue Impact = (Visitors at Stage N) × (Expected Conversion % - Actual Conversion %) × (Average Order Value)
This gives the estimated revenue recoverable if the friction point were resolved to return to baseline performance.
A conversion rate change is considered significant when:
- Sample size ≥ 1,000 sessions at the relevant stage
- Z-score ≥ 1.96 (95% confidence) comparing current period to baseline
- The absolute change is ≥ 0.5 percentage points
CSV or Excel with columns: stagename, visitors (required). Optional columns: device, geo/country, category, conversions, avgordervalue. Column names are matched case-insensitively with common aliases (e.g., "users" → visitors, "step" → stagename).
- CSV uploads may have inconsistent column naming — normalize headers before processing.
- Conversion rate calculations must use unique visitors (not total events) to avoid inflation from page reloads.
- If AOV is not in the file, ask the user or default to industry average ($85).
- Files with fewer than 1,000 visitors per stage cannot produce statistically significant results — warn the user.
- [Ask user] Which file contains the funnel data?
- Accept a file path to a CSV or Excel file
- If already provided as {{funnel_file}}, skip to Step 2
- [Agent] Load uploaded funnel file:
- Read {{funnel_file}} (CSV or Excel)
- Normalize column headers (case-insensitive matching to: stage_name, visitors, conversions, device, geo, category)
- Validate: Required columns present (stage_name + visitors); no null values in visitors
- If validation fails, show expected format and ask user to fix
- [Agent] Validate and standardize data:
- Confirm DataFrame has columns: stage, visitors, and at least one segment dimension
- Calculate stage-to-stage conversion rates
- Flag any data quality issues (e.g., conversions > visitors, missing stages)
- If AOV column not present, ask user for average order value (default: $85)
- Store standardized DataFrame for analysis phase
- [Agent] Calculate baseline conversion rates:
- If historical data available (prior period in the file), use that as baseline
- If no history, use industry benchmarks from
references/industry-benchmarks.md - Compute expected vs. actual conversion rate for each stage transition
- [Agent] Identify friction points:
- Run
scripts/revenue_impact_calculator.pywith the standardized DataFrame - For each stage transition, compute:
- Absolute drop-off rate vs. baseline
- Z-score for statistical significance
- Revenue impact using
- Filter to statistically significant drops only (per )
- [Agent] Segment analysis:
- Break down each friction point by available segment dimensions
- Identify if friction is concentrated in specific segments (>2x overall rate)
- [Agent] Rank friction points:
- Sort by estimated revenue impact (descending)
- Keep top 5 (or fewer if less than 5 are statistically significant)
- For each, generate root cause hypothesis based on:
- Segment concentration pattern
- Stage-specific common issues (from
references/common-blockers.md)
- [Agent] Generate recommendations:
- For each of the top 5 friction points, create a specific recommendation:
- What to change and why
- Expected impact (revenue recovery estimate)
- Implementation complexity (low/medium/high)
- [Agent] Build the insight report:
- Use
assets/report-template.mdas the output structure - Populate with:
- Executive summary (1 paragraph, top finding + total revenue opportunity)
- Funnel visualization
- Top 5 friction points table (stage, drop %, revenue impact, segment concentration)
- Detailed recommendations
- Methodology notes
- Save report as markdown file
- [Agent] Render visualization:
- Create an HTML artifact with:
- Funnel chart showing stage-to-stage conversion rates (color-coded by severity)
- Segment breakdown charts for top friction points
- Revenue impact chart
- Open in session tab for user review
- [Ask user] Present findings:
- Show executive summary inline
- Link to full report and visualization
- Ask: "Would you like me to drill deeper into a specific friction point, or export this as a slide deck?"
Conversion Insight Report — {{date_range}}
Top Finding: {{topfrictionpoint_description}}
Total Revenue Opportunity: ${{totalrevenueimpact}}/{{period}} across {{numfrictionpoints}} identified friction points.
Biggest Segment Impact: {{segmentwithhighestconcentration}} accounts for {{segmentpercentage}}% of the total drop-off at {{worst_stage}}.
Immediate Action: {{toprecommendationone_liner}}
{{rank}}. {{stagefrom}} → {{stageto}} Drop-off
| Metric | Value | |--------|-------| | Current Conversion Rate | {{currentrate}}% | | Baseline Rate | {{baselinerate}}% | | Absolute Drop | {{droppp}} pp | | Visitors Affected | {{visitorsaffected}} | | Est. Revenue Impact | ${{revenue_impact}}/{{period}} | | Statistical Confidence | {{confidence}}% |
Segment Concentration:
- Device: {{device_breakdown}}
- Geo: {{geo_breakdown}}
- Category: {{category_breakdown}}
Root Cause Hypothesis: {{hypothesis}}
Recommendation:
- Change: {{recommended_change}}
- Expected Impact: {{expected_impact}}
- Complexity: {{complexity}}
references/industry-benchmarks.md— Baseline conversion rates by industry vertical and funnel stagereferences/common-blockers.md— Catalog of common conversion blockers mapped to funnel stagesassets/report-template.md— Full report output structure
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Amazon-Quick
- Source: Amazon-Quick/Amazon-Quick-official-catalog
- License: MIT-0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.