ecommerce-competitor-analyzer

buluslan/ecommerce-competitor-analyzer · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/buluslan/ecommerce-competitor-analyzer --skill ecommerce-competitor-analyzer
0 commentsdiscussion
summary

Automated scraping and AI-powered analysis of e-commerce products across Amazon, Temu, and Shopee.

  • Extracts product data (title, price, rating, reviews) from multiple platforms via batch scraping with error isolation, ensuring single failures don't halt processing
  • Analyzes each product across four dimensions: copywriting strategy and keyword frequency, visual design methodology, customer review sentiment, and market positioning gaps
  • Outputs results in dual formats: structured Google
skill.md

E-commerce Competitor Analyzer Skill

Quick Start (For AI)

When to use this skill: When user asks to analyze, research, or extract insights from e-commerce products (Amazon, Temu, Shopee).

What you should do:

  1. Extract product identifiers (ASINs or URLs) from user input
  2. Call the scraper script to get product data
  3. Call the AI analysis with the analysis prompt template
  4. Output results in BOTH formats: Google Sheets + Markdown

Input examples:

Output requirements:

  • Google Sheets table with: ASIN, Title, Price, Rating, 4 analysis summaries
  • Markdown report with detailed 4-dimensional analysis

How AI Should Process Requests

Step 1: Extract Product Identifiers

From user input, extract all ASINs and/or URLs:

Example inputs:

"Analyze these Amazon products:
B0C4YT8S6H
B08N5WRQ1Y
B0CLFH7CCV"

Extract: ['B0C4YT8S6H', 'B08N5WRQ1Y', 'B0CLFH7CCV']

Mixed input handling:

"Analyze B0C4YT8S6H and https://amazon.com/dp/B08N5WRQ1Y"

Extract: ['B0C4YT8S6H', 'B08N5WRQ1Y'] (extract ASIN from URL)

Step 2: Batch Scrape Product Data

For each product identifier:

  1. Detect platform (use scripts/detect-platform.js if available)
  2. Call appropriate scraper (Amazon: scripts/scrape-amazon.js)
  3. Use Olostep API with configured API key from .env

Batch processing pattern:

// Process all products in parallel
const products = ['B0C4YT8S6H', 'B08N5WRQ1Y', 'B0CLFH7CCV'];
const results = await Promise.allSettled(
  products.map(asin => scrapeAmazon(asin))
);

// Handle failures gracefully
const successful = results.filter(r => r.status === 'fulfilled');
const failed = results.filter(r => r.status === 'rejected');

Step 3: Batch AI Analysis

For each successfully scraped product:

  1. Read the analysis prompt from prompts/analysis-prompt-base.md
  2. Replace product data placeholders in the prompt
  3. Call Gemini API (model: gemini-3-flash-preview)
  4. Extract structured analysis results

Analysis framework (4 dimensions):

  1. 文案构建逻辑与词频分析 (The Brain) - Copywriting strategy & keywords
  2. 视觉资产设计思路 (The Face) - Visual design methodology
  3. 评论定量与定性分析 (The Voice) - Review sentiment analysis
  4. 市场维态与盲区扫描 (The Pulse) - Market positioning & blind spots

Step 4: Generate Dual Format Output

Format 1: Google Sheets (Structured Data)

Write to Google Sheets with columns: | ASIN | 产品标题 | 价格 | 评分 | 文案分析摘要 | 视觉分析摘要 | 评论分析摘要 | 市场分析摘要 |

Sheet selection priority:

  1. User explicitly specified Sheet ID/Name/URL
  2. Default from .env (GOOGLE_SHEETS_ID)
  3. Ask user to provide Sheet ID

Format 2: Markdown Report (Detailed Analysis)

Generate file: 竞品分析-YYYY-MM-DD.md

Structure:

# Amazon Competitor Analysis Report

## Analysis Overview
- Products analyzed: 3
- Analysis date: 2026-01-29
- Total time: ~5 minutes

---

## Product 1: B0C4YT8S6H

### Basic Information
- Title: [Product title]
- Price: [Price]
- Rating: [Rating]

### Copywriting Strategy & Keyword Analysis
[Full analysis...]

### Visual Asset Design Methodology
[Full analysis...]

### Customer Review Analysis
[Full analysis...]

### Market Positioning & Competitive Intelligence
[Full analysis...]

---

File Structure

ecommerce-competitor-analyzer.skill/
├── SKILL.md                                # This file (AI instructions)
├── platforms.yaml                          # Platform configurations (URL patterns, regex)
├── .env.example                            # Configuration template (API keys)
├── prompts/                                # AI prompt templates
│   └── analysis-prompt-base.md            # Base analysis framework (from n8n)
├── scripts/                                # Processing scripts
│   ├── detect-platform.js                 # Platform detection utility
│   ├── scrape-amazon.js                   # Amazon scraper (Olostep API)
│   └── batch-processor.js                 # Batch processing engine
└── references/                             # Documentation
    └── n8n-workflow-analysis.md           # n8n workflow insights

Configuration Files

platforms.yaml

Contains platform-specific configurations:

  • URL patterns for platform detection
  • ASIN extraction regex patterns
  • Scraper API endpoints
  • Data extraction patterns

Key sections:

platforms:
  amazon:
    url_patterns: ["amazon.com", "amazon.co.uk", ...]
    asin_regex:
      standard: "/dp/([A-Z0-9]{10})"
    scraper:
      provider: "olostep"
      api_endpoint: "https://api.olostep.com/v2/agent/web-agent"

.env.example

Template for required API keys:

OLOSTEP_API_KEY=your_olostep_api_key_here
GEMINI_API_KEY=your_gemini_api_key_here
GOOGLE_SHEETS_ID=YOUR_GOOGLE_SHEETS_ID_HERE

Critical: Always check if .env file exists and contains required keys before processing.


Analysis Prompt Template

The AI analysis uses a proven 4-dimensional framework. The exact prompt is stored in: prompts/analysis-prompt-base.md

Key sections:

  1. Role: 10-year experienced Amazon Operations Director & Brand Strategist
  2. Goal: Deep scan of product listing to extract strategic insights
  3. Output Structure:
    • Part 1: 文案构建逻辑与词频分析
    • Part 2: 视觉资产设计思路
    • Part 3: 评论定量与定性分析
    • Part 4: 市场维态与盲区扫描

Important: Use the prompt EXACTLY as provided in the template without modifications.


API Services

Olostep API (Web Scraping)

  • Purpose: Scrape Amazon product pages with rendered JavaScript
  • Endpoint: https://api.olostep.com/v2/agent/web-agent
  • Cost: 1000 free requests/month, then $0.002/request
  • Key param: comments_to_scrape: 100 (matching n8n config)

Google Gemini API (AI Analysis)

  • Purpose: Generate comprehensive product analysis
  • Model: gemini-3-flash-preview (cost-effective)
  • Cost: ~$0.001/product
  • Alternative: gemini-2-flash-thinking (for complex analysis)

Google Sheets API (Data Storage)

  • Purpose: Export structured results
  • Authentication: OAuth2 service account
  • Cost: Free tier

Error Handling

Batch Processing with Error Isolation

Critical pattern from n8n workflow:

const items = productIdentifiers;
const results = await Promise.allSettled(
  items.map(async (item, index) => {
    try {
      const data = await scrapeProduct(item);
      const analysis = await analyzeWithAI(data);
      return { success: true, index, data: analysis };
    } catch (error) {
      // Single failure doesn't stop batch
      return { success: false, index, error: error.message };
    }
  })
);

// Report results
const successful = results.filter(r => r.status === 'fulfilled' && r.value.success);
const failed = results.filter(r => r.status === 'rejected' || !r.value.success);

console.log(`Processed: ${successful.length} succeeded, ${failed.length} failed`);

Common Errors & Solutions

Error Cause Solution
OLOSTEP_API_KEY not found Missing .env file Check .env exists and contains key
Invalid ASIN format Malformed ASIN Validate ASIN: 10 alphanumeric chars
Scraping timeout Slow page load Increase timeout or retry
Gemini rate limit Too many requests Add delay between batches

Platform Detection Logic

function detectPlatform(urlOrId) {
  // Direct ASIN
  if (/^[A-Z0-9]{10}$/.test(urlOrId)) {
    return { platform: <
how to use ecommerce-competitor-analyzer

How to use ecommerce-competitor-analyzer on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add ecommerce-competitor-analyzer
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/buluslan/ecommerce-competitor-analyzer --skill ecommerce-competitor-analyzer

The skills CLI fetches ecommerce-competitor-analyzer from GitHub repository buluslan/ecommerce-competitor-analyzer and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/ecommerce-competitor-analyzer

Reload or restart Cursor to activate ecommerce-competitor-analyzer. Access the skill through slash commands (e.g., /ecommerce-competitor-analyzer) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.653 reviews
  • Li Sharma· Dec 28, 2024

    ecommerce-competitor-analyzer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Chaitanya Patil· Dec 20, 2024

    Keeps context tight: ecommerce-competitor-analyzer is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Fatima Park· Dec 20, 2024

    Registry listing for ecommerce-competitor-analyzer matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Yuki Jackson· Dec 8, 2024

    I recommend ecommerce-competitor-analyzer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Ishan Malhotra· Dec 4, 2024

    Keeps context tight: ecommerce-competitor-analyzer is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Sophia Haddad· Dec 4, 2024

    Solid pick for teams standardizing on skills: ecommerce-competitor-analyzer is focused, and the summary matches what you get after install.

  • Zara Rahman· Nov 27, 2024

    ecommerce-competitor-analyzer reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Li Sethi· Nov 23, 2024

    ecommerce-competitor-analyzer has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Kiara Gupta· Nov 23, 2024

    ecommerce-competitor-analyzer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Piyush G· Nov 11, 2024

    ecommerce-competitor-analyzer has been reliable in day-to-day use. Documentation quality is above average for community skills.

showing 1-10 of 53

1 / 6