/ Annuaire / Playground / claude-ecom
← Tous les serveurs ↗ GitHub
● Communauté takechanman1228 ⚡ Instantané

claude-ecom

par takechanman1228 · takechanman1228/claude-ecom

Drop a sales CSV in; get a KPI decomposition, ranked findings, and concrete next actions — powered by a Python analysis backend.

A Claude Code skill for e-commerce operators. Takes an orders or sales CSV and produces a structured business review: revenue decomposition, conversion and AOV trends, customer cohort signals, and a prioritized action list. Runs a Python backend so math is correct, not LLM-guessed.

▶ Voir la démo 📦 Installer 💡 Cas d'usage

Pourquoi l'utiliser

Fonctionnalités clés

Démo en direct

Aperçu en pratique

claude-ecom-skill.replay ▶ prêt
0/0

Installation

Dépôt de l’auteur · Documentation officielle des Skills Claude

Cas d'usage

Usages concrets : claude-ecom

Weekly sales review in 10 minutes instead of 2 hours

👤 DTC founders, e-commerce managers ⏱ ~15 min beginner

Quand l'utiliser : Monday morning review of last week's numbers.

Déroulement
  1. Hand over the CSV
    Use claude-ecom. Here's last week's orders.csv — do a KPI decomposition and tell me what moved.✓ Copié
    → Revenue, CVR, AOV numbers with week-over-week deltas
  2. Ask for findings
    Rank the top 3 findings by impact. Be specific — named SKUs, traffic sources, time windows.✓ Copié
    → Findings with data points, not 'revenue went up'
  3. Extract actions
    For each finding, propose one concrete action I can take this week.✓ Copié
    → Action list I could paste in a Monday standup

Résultat : A weekly review I actually read.

Pièges
  • Garbage CSVs produce garbage reviews — Clean the export first — merge refunds, exclude test orders
Combiner avec : filesystem

Understand why a specific SKU is underperforming

👤 Product managers, merchandisers ⏱ ~20 min intermediate

Quand l'utiliser : A hero SKU suddenly slowed down and you need to know whether it's traffic, conversion, or pricing.

Déroulement
  1. Filter to SKU
    Use claude-ecom. Focus on SKU SHIRT-BLK-M for the last 60 days. Decompose revenue into traffic × CVR × AOV and compare to the prior 60.✓ Copié
    → Decomposition with clear delta per factor
  2. Check channel split
    Is the drop concentrated in one channel or across all?✓ Copié
    → Channel breakdown with concentration analysis

Résultat : A diagnosis, not a vibe.

Customer cohort retention report from order data

👤 Growth teams watching LTV ⏱ ~30 min intermediate

Quand l'utiliser : Quarterly review of cohort repeat rates.

Déroulement
  1. Cohort the data
    Use claude-ecom. Build a monthly acquisition-cohort retention table — orders/customer by month since first order.✓ Copié
    → Triangular retention table
  2. Compare cohorts
    Which cohort is best? Worst? What's different about them?✓ Copié
    → Hypotheses grounded in the data

Résultat : A retention view you could share with an investor.

Pièges
  • Short data windows distort recent cohorts — Flag cohorts with <3 months of history as provisional

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

claude-ecom-skill + filesystem

Point at a folder of weekly CSVs for automated trend analysis

Run the weekly review for each CSV in data/weekly/ and build a running dashboard.✓ Copié
claude-ecom-skill + bigquery-server

Instead of CSVs, pull from a warehouse

Query BigQuery for last week's orders and feed into claude-ecom for the review.✓ Copié

Outils

Ce que ce MCP expose

OutilEntréesQuand appelerCoût
load_csv path, column mapping Starting any analysis local
kpi_decompose date range Weekly / monthly review local Python
rank_findings analysis output After decomposition 0
cohort_table cohort granularity Retention analysis local

Coût et limites

Coût d'exécution

Quota d'API
None
Tokens par appel
Moderate — summary tables only, not raw rows
Monétaire
Free (needs local Python)
Astuce
Aggregate in Python; never paste raw orders rows into prompts.

Sécurité

Permissions, secrets, portée

Stockage des identifiants : None
Sortie de données : Order summaries and findings are sent to Claude API; raw rows can stay local if you keep aggregation server-side

Dépannage

Erreurs courantes et correctifs

Column mapping fails

Standard Shopify/Woo exports work out of the box. For custom exports, supply a column map in the prompt.

Wild numbers in the output

Check for duplicate order rows or non-currency values in the revenue column

Alternatives

claude-ecom vs autres

AlternativeQuand l'utiliserCompromis
Looker Studio / Metabase dashboardsYou want persistent dashboards, not one-shot reviewsSetup cost; no LLM-generated narrative
Shopify's own reportsQuick built-in viewsShallow; no cross-store or cohort analysis

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills