Token导航 LogoToken导航TokenDH.com
研究检索需要联网clawhub未标认证来源可访问clear审计提醒

customer-research-dv客户研究 dv

Agent Skill

customer-research-dv 用于处理浏览器自动化、网页检查和页面信息提取,适合在 OpenClaw 中需要让 Agent 打开页面、读取网页或验证前端流程时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

4,158

周安装

175

GitHub Stars

公开资料未说明

下载量

1,456
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:customer-research-dv(客户研究 dv)
来源仓库:https://github.com/clawdiri-ai/customer-research-dv
安装命令:
openclaw skills install customer-research-dv
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install customer-research-dv

简介

通过论坛挖掘、调查访谈和竞品评论分析开展深度客户研究。

  • 适用于验证市场需求、识别用户痛点和优化产品定位。
  • 支持情绪分析与多源数据整理,输出结构化洞察报告。
  • 涉及外部网站抓取时需注意合规性与反爬机制限制。
  • customer-research-dv 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Customer Research & Validation Skill

Trigger conditions:

  • User asks to validate a product idea, persona, or market assumption
  • User mentions "customer research", "validate assumption", "talk to users"
  • User requests Reddit/forum mining, competitor analysis, or sentiment analysis
  • User wants to generate surveys or interview scripts
  • User asks about customer pain points, needs, or jobs-to-be-done

Purpose

Pre-pipeline validation for DaVinci Enterprises products. Ensures marketing strategy is built on real customer signal, not assumptions. Prevents building features nobody wants.

What It Does

  1. Reddit/Forum Mining — Extract threads, comments, sentiment from subreddits and forums
  2. Survey Generation — Convert research questions into structured surveys
  3. Interview Scripts — Generate customer interview guides with probing questions
  4. Persona Validation — Test persona assumptions against real user behavior
  5. Competitor Review Scraping — Aggregate reviews from G2, Trustpilot, Reddit
  6. Sentiment Analysis — Aggregate and score customer sentiment across sources

Usage

Quick Start

# Validate a product hypothesis via Reddit mining
scripts/reddit-miner.sh --subreddit "personalfinance" --query "FIRE calculator" --limit 50

# Generate a customer interview script
scripts/interview-generator.sh --persona "FIRE enthusiast" --problem "retirement planning tools"

# Scrape competitor reviews
scripts/competitor-scraper.sh --product "Personal Capital" --sources "g2,trustpilot,reddit"

Integration with Marketing Pipeline

This skill feeds into the content strategy workflow:

  1. Discovery → Run customer research to identify pain points
  2. Validation → Test persona assumptions against real data
  3. Strategy → Build content pillars around validated needs
  4. Execution → Ogilvy creates content targeting real customer language

Output format: JSON reports to data/research/ for downstream consumption.

Scripts

reddit-miner.sh

Fetch Reddit threads matching keywords, extract sentiment, output structured JSON.

Usage:

./scripts/reddit-miner.sh --subreddit SUBREDDIT --query "search terms" [--limit N] [--sentiment]

Output: data/research/reddit-{subreddit}-{timestamp}.json

interview-generator.sh

Generate customer interview script from persona + problem statement.

Usage:

./scripts/interview-generator.sh --persona "description" --problem "pain point"

Output: Markdown interview guide to stdout

competitor-scraper.sh

Aggregate reviews from multiple sources, extract themes and sentiment.

Usage:

./scripts/competitor-scraper.sh --product "Product Name" --sources "g2,trustpilot,reddit"

Output: data/research/competitor-{product}-{timestamp}.json

Output Schema

All scripts output to data/research/ with consistent JSON schema:

{
  "meta": {
    "skill": "customer-research",
    "script": "reddit-miner",
    "timestamp": "2026-03-22T00:43:00Z",
    "query": {...}
  },
  "findings": [
    {
      "source": "reddit",
      "source_id": "thread_abc123",
      "text": "I wish there was a FIRE calculator that...",
      "sentiment": 0.65,
      "themes": ["pain point", "feature request"],
      "metadata": {...}
    }
  ],
  "summary": {
    "total_sources": 47,
    "avg_sentiment": 0.42,
    "top_themes": ["complexity", "cost", "trust"],
    "key_insights": ["Users want transparency", "Price sensitivity high"]
  }
}

Dependencies

  • jq — JSON processing
  • curl — HTTP requests
  • Reddit API access (optional: can scrape public threads without auth)
  • OpenClaw LLM access for sentiment analysis

Example Workflow

Scenario: Validate demand for FIRE Sim product

  1. Mine Reddit pain points:
   ./scripts/reddit-miner.sh --subreddit "financialindependence" \
     --query "retirement calculator problems" --limit 100 --sentiment
  1. Scrape Personal Capital reviews:
   ./scripts/competitor-scraper.sh --product "Personal Capital" \
     --sources "g2,trustpilot,reddit"
  1. Generate interview script:
   ./scripts/interview-generator.sh \
     --persona "30-40 tech worker, $200K income, aiming FIRE by 45" \
     --problem "existing retirement tools too conservative or too complex"
  1. Analyze findings:

- Review JSON outputs in data/research/ - Identify recurring themes, pain points, language patterns - Validate/invalidate persona assumptions - Feed insights into content strategy

  1. Document learnings:

- Update projects/davinci-enterprises/customer-insights.md - Flag validated needs for product roadmap - Inform Ogilvy content pillars with real customer language

Quality Gates

  • Minimum sample size: 30+ sources per research question
  • Sentiment confidence: Only report sentiment scores with >50 samples
  • Theme validation: Themes must appear in ≥3 independent sources
  • Source diversity: Mix Reddit, review sites, forums (not just one platform)

Anti-Patterns

Don't:

  • Build features based on one Reddit comment
  • Cherry-pick data to confirm existing beliefs
  • Skip competitor analysis (reinventing the wheel wastes time)
  • Ignore negative sentiment (it's the most valuable signal)

Do:

  • Let data challenge your assumptions
  • Track quotes verbatim (real customer language = gold for content)
  • Cross-reference findings across sources
  • Document what you disproved, not just what you confirmed

Integration Points

  • Content Strategy: Feed validated pain points to Ogilvy for pillar creation
  • Product Roadmap: Link research findings to JIRA/task tickets
  • Persona Database: Update persona definitions based on validation results
  • Marketing Copy: Extract customer language for landing pages, ads

Maintenance

  • Research data retention: 90 days (then archive to cold storage)
  • Re-run validation quarterly for active products
  • Update scripts when Reddit/review site APIs change
  • Log failed scrapes to logs/customer-research-errors.log

Next Steps After Running Research:

  1. Review findings in data/research/
  2. Update persona docs with validated/invalidated assumptions
  3. Create content strategy tasks based on identified pain points
  4. Schedule customer interviews if online research raises questions
  5. Document learnings in project-specific CONTEXT.md

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

80.38%
按下载量换算1,170

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills