Token导航 LogoToken导航

Agent Skill · 研究检索

ecommerce-competitor-analyzer(电子商务竞争对手分析器)

ecommerce-competitor-analyzer 用于记录任务执行中的错误、用户纠正、经验和能力缺口,适合在 Codex、Claude、Cursor、Gemini CLI 中希望让 Agent 持续沉淀问题、修正和最佳实践时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

ecommerce-competitor-analyzer 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为接触敏感数据;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 5,971。

总安装 23,672周安装 967GitHub Stars 40下载 7,581核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:ecommerce-competitor-analyzer(电子商务竞争对手分析器)
来源仓库:https://github.com/buluslan/ecommerce-competitor-analyzer
仓库路径:skills/ecommerce-competitor-analyzer
安装命令:
npx skills add https://github.com/buluslan/ecommerce-competitor-analyzer --skill ecommerce-competitor-analyzer
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

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

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

对 Amazon、Temu 和 Shopee 上的电子商务产品进行自动抓取和人工智能分析。

通过批量抓取和错误隔离从多个平台提取产品数据(标题、价格、评级、评论),确保单一故障不会停止处理 从四个维度分析每个产品:文案策略和关键词频率、视觉设计方法、客户评论情绪和市场定位差距 以两种格式输出结果:结构化 Google Sheets 表格和包含战略见解的详细 Markdown 报告 支持并行批量处理产品标识符(ASIN 或 URL),使用 Gemini AI 和 Olostep 抓取 API,每个产品的典型分析可在 1-2 分钟内完成

来源仓库内路径:skills/ecommerce-competitor-analyzer

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/buluslan/ecommerce-competitor-analyzer --skill…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

ecommerce-competitor-analyzer 怎么安装?

在终端执行 npx skills add https://github.com/buluslan/ecommerce-competitor-analyzer --skill ecommerce…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

ecommerce-competitor-analyzer 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

ecommerce-competitor-analyzer 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

ecommerce-competitor-analyzer 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

ecommerce-competitor-analyzer 用的人多吗?

公开数据是累计安装 23,672 次,近一周安装 967 次,下载 7,581 次,GitHub 40 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

ecommerce-competitor-analyzer 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
ecommerce-competitor-analyzer

电子商务竞争对手分析器 · 本页

23,67240接触敏感数据未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

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

ErrorCauseSolution
OLOSTEP_API_KEY not foundMissing.env fileCheck.env exists and contains key
Invalid ASIN formatMalformed ASINValidate ASIN: 10 alphanumeric chars
Scraping timeoutSlow page loadIncrease timeout or retry
Gemini rate limitToo many requestsAdd delay between batches

Platform Detection Logic

function detectPlatform(urlOrId) {
  // Direct ASIN
  if (/^[A-Z0-9]{10}$/.test(urlOrId)) {
    return { platform: 'amazon', id: urlOrId };
  }

  // Amazon URL patterns
  if (/amazon\.(com|co\.uk|de|es|fr|it|ca|co\.jp)/i.test(urlOrId)) {
    const asinMatch = urlOrId.match(/\/dp\/([A-Z0-9]{10})/i);
    if (asinMatch) {
      return { platform: 'amazon', id: asinMatch[1] };
    }
  }

  // Other platforms (future)
  // if (/temu\.com/i.test(urlOrId)) return { platform: 'temu', id: extractId(urlOrId) };

  return null;
}

Implementation Notes

Current Version: Phase 1 MVP

Supported Platforms: Amazon (US only) Input Method: Dialog-based (ASINs or URLs) Output Format: Google Sheets table + Markdown report

Roadmap

  • ✅ Phase 1: Amazon MVP (current)
  • 🔄 Phase 2: Add Temu & Shopee platforms
  • 🔄 Phase 3: Cross-platform comparison
  • 🔄 Phase 4: Historical tracking & price alerts

Design Philosophy

This skill follows the error isolation pattern from the n8n workflow:

  • Single product failure NEVER stops the entire batch
  • Always report both successes and failures
  • Provide detailed error messages for debugging

Performance Benchmarks

OperationTimeCost
Single product scrape~30 seconds$0.002 (Olostep)
Single product analysis~45 seconds$0.001 (Gemini)
Total per product~1-2 minutes~$0.003
Batch of 10 products~10-15 minutes (parallel)~$0.03

References

  • n8n Workflow: Based on v81 workflow logic
  • Platform Config: See platforms.yaml for URL patterns and extraction rules
  • Analysis Prompt: See prompts/analysis-prompt-base.md for exact prompt template

Important Reminders for AI

  1. ALWAYS extract ALL product identifiers from user input before processing
  2. ALWAYS use batch processing with Promise.allSettled for error isolation
  3. ALWAYS generate BOTH output formats: Google Sheets + Markdown
  4. NEVER modify the analysis prompt - use it exactly as provided
  5. ALWAYS validate.env exists before starting processing
  6. ALWAYS report processing summary: X succeeded, Y failed
  7. If Google Sheets ID is missing, ask user to provide it
  8. Use the exact prompt from prompts/analysis-prompt-base.md without any modifications

平台分布

Codex

33.02%
按下载量换算2,503

Claude

31.73%
按下载量换算2,405

Cursor

19.49%
按下载量换算1,478

Gemini CLI

9.69%
按下载量换算735

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills