Automated scraping and AI-powered analysis of e-commerce products across Amazon, Temu, and Shopee.
Works with
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
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionecommerce-competitor-analyzerExecute the skills CLI command in your project's root directory to begin installation:
Fetches ecommerce-competitor-analyzer from buluslan/ecommerce-competitor-analyzer and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate ecommerce-competitor-analyzer. Access via /ecommerce-competitor-analyzer in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
31
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
31
stars
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:
Input examples:
Output requirements:
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)
For each product identifier:
scripts/detect-platform.js if available)scripts/scrape-amazon.js).envBatch 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');
For each successfully scraped product:
prompts/analysis-prompt-base.mdAnalysis framework (4 dimensions):
Format 1: Google Sheets (Structured Data)
Write to Google Sheets with columns: | ASIN | 产品标题 | 价格 | 评分 | 文案分析摘要 | 视觉分析摘要 | 评论分析摘要 | 市场分析摘要 |
Sheet selection priority:
.env (GOOGLE_SHEETS_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...]
---
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
Contains platform-specific configurations:
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"
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.
The AI analysis uses a proven 4-dimensional framework. The exact prompt is stored in:
prompts/analysis-prompt-base.md
Key sections:
Important: Use the prompt EXACTLY as provided in the template without modifications.
https://api.olostep.com/v2/agent/web-agentcomments_to_scrape: 100 (matching n8n config)gemini-3-flash-preview (cost-effective)gemini-2-flash-thinking (for complex analysis)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`);
| 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 |
function detectPlatform(urlOrId) {
// Direct ASIN
if (/^[A-Z0-9]{10}$/.test(urlOrId)) {
return { platform: <Make data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
ailabs-393/ai-labs-claude-skills
ecommerce-competitor-analyzer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: ecommerce-competitor-analyzer is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for ecommerce-competitor-analyzer matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend ecommerce-competitor-analyzer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: ecommerce-competitor-analyzer is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: ecommerce-competitor-analyzer is focused, and the summary matches what you get after install.
ecommerce-competitor-analyzer reduced setup friction for our internal harness; good balance of opinion and flexibility.
ecommerce-competitor-analyzer has been reliable in day-to-day use. Documentation quality is above average for community skills.
ecommerce-competitor-analyzer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
ecommerce-competitor-analyzer has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 53