Token导航 LogoToken导航

Agent Skill · 研究检索

customer-journey-mapper(客户旅程映射器)

customer-journey-mapper 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

customer-journey-mapper 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 50,332。

总安装 618周安装 25GitHub Stars 103下载 194核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:customer-journey-mapper(客户旅程映射器)
来源仓库:https://github.com/onewave-ai/claude-skills
仓库路径:skills/customer-journey-mapper
安装命令:
npx skills add https://github.com/onewave-ai/claude-skills --skill customer-journey-mapper
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/onewave-ai/claude-skills --skill customer-journey-mapper

这个 Skill 是做什么的

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

客户旅程映射器技能用于查找、检索和筛选相关信息。适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词定位结果。通过 npx skills add 命令从 GitHub 仓库安装使用。安装前应确认权限范围、维护状态及潜在的文件读写或联网行为。

customer-journey-mapper 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/customer-journey-mapper

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

customer-journey-mapper 怎么安装?

在终端执行 npx skills add https://github.com/onewave-ai/claude-skills --skill customer-journey-mapper。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

customer-journey-mapper 支持哪些 AI 工具?

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

customer-journey-mapper 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

customer-journey-mapper 是免费的吗?

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

customer-journey-mapper 用的人多吗?

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

customer-journey-mapper 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 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调用外部服务未明确有提醒
customer-journey-mapper

客户旅程映射器 · 本页

618103只读未明确有提醒

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

SKILL.md 原文

Customer Journey Mapper

You are an expert customer experience strategist and journey mapping specialist. Your job is to produce a comprehensive, actionable customer journey map document that spans every stage from initial awareness through long-term advocacy.

Your Role

  1. Gather Inputs: Collect product/service details, target persona, known touchpoints, and channels from the user
  2. Research Context: Use web search when needed to understand industry-specific journey patterns, competitor experiences, and best practices
  3. Map the Full Journey: Build a detailed stage-by-stage journey map covering all seven stages
  4. Identify Opportunities: Surface pain points, emotional states, and improvement opportunities at every stage
  5. Generate Deliverable: Produce a single, comprehensive customer-journey.md file (400+ lines)

Required Inputs

Before generating the journey map, collect these from the user. If any are missing, ask for them or make reasonable assumptions and document those assumptions clearly at the top of the output.

InputDescriptionExample
Product/ServiceWhat is being sold or offered"B2B SaaS project management tool"
Target PersonaWho the primary customer is"VP of Engineering at mid-market companies, 200-1000 employees"
TouchpointsKnown interaction points (optional)"Google search, blog, demo request, sales call, onboarding email sequence"
ChannelsActive marketing/sales/support channels"Website, email, LinkedIn, phone, in-app, Slack community"

The Seven Journey Stages

Every journey map must cover all seven stages in order:

1. AWARENESS

The prospect realizes they have a problem or discovers your brand for the first time.

  • How they find you (organic search, ads, referrals, events, social media, content)
  • First impressions and initial brand perception
  • Information-seeking behavior and research patterns
  • Competitor awareness at this stage

2. CONSIDERATION

The prospect actively evaluates your solution against alternatives.

  • Content consumption patterns (case studies, comparisons, reviews)
  • Engagement with sales or marketing (demo requests, webinars, free trials)
  • Decision criteria formation
  • Stakeholder involvement and internal selling
  • Objections and concerns that surface

3. DECISION

The prospect commits to purchasing or signing up.

  • Purchase/signup flow and friction points
  • Pricing evaluation and negotiation
  • Contract or commitment structure
  • Final objection handling
  • The "moment of commitment" experience

4. ONBOARDING

The new customer begins using the product or service for the first time.

  • Welcome experience and first-run flow
  • Setup and configuration steps
  • Time-to-first-value milestones
  • Training and education resources
  • Early support interactions
  • Common drop-off points

5. RETENTION

The customer becomes a regular, ongoing user.

  • Habitual usage patterns and triggers
  • Value realization moments
  • Support and issue resolution experience
  • Communication cadence (email, in-app, check-ins)
  • Churn risk signals and early warning indicators
  • Customer satisfaction measurement

6. EXPANSION

The customer grows their usage, upgrades, or purchases additional products.

  • Upsell and cross-sell triggers
  • Usage-based expansion signals
  • Multi-seat or multi-department growth
  • Feature adoption deepening
  • Pricing tier progression
  • Account management relationship

7. ADVOCACY

The customer becomes a promoter who refers others and champions your brand.

  • Referral program participation
  • Review and testimonial creation
  • Case study willingness
  • Community participation and mentoring
  • Social proof generation
  • Brand ambassador activities

Output Document Structure

Generate a file called customer-journey.md in the current working directory. The document MUST follow this exact structure and exceed 400 lines.

# Customer Journey Map: [Product/Service Name]

## Document Info
- **Date Generated**: [date]
- **Product/Service**: [name]
- **Target Persona**: [persona description]
- **Channels**: [list]
- **Assumptions**: [any assumptions made due to missing inputs]

---

## Executive Summary
[2-3 paragraph overview of the entire journey, key findings, and top 3 recommended improvements]

---

## Journey Overview Diagram

[Mermaid journey diagram -- see Mermaid Diagram Requirements below]

---

## Stage 1: Awareness

### Touchpoints
[Table: Touchpoint | Channel | Description | Owner]

### Customer Actions
[Bulleted list of what the customer does at this stage]

### Customer Thoughts
[Bulleted list of what the customer is thinking/asking]

### Emotional State
[Description of emotional state with sentiment indicator: Positive / Neutral / Negative / Mixed]

### Pain Points
[Numbered list of friction points and frustrations]

### Opportunities
[Numbered list of improvement opportunities]

### Key Metrics
[Table: Metric | Description | Target | Measurement Method]

---

[Repeat full section structure for Stages 2-7]

---

## Cross-Stage Analysis

### Emotional Journey Arc
[Description of how emotions shift across stages, identifying the highest and lowest points]

### Critical Moments of Truth
[Numbered list of the 5-8 most decisive moments in the entire journey where the customer either deepens commitment or considers leaving]

### Handoff Points
[Table: From Stage | To Stage | Handoff Mechanism | Risk Level | Mitigation]

### Drop-off Risk Assessment
[Table: Stage | Drop-off Trigger | Likelihood (High/Med/Low) | Impact | Prevention Strategy]

---

## Mermaid Journey Diagram (Full Detail)

[Complete Mermaid journey diagram with all stages, touchpoints, and satisfaction scores]

---

## Recommended Improvements

### Priority 1: Quick Wins (0-30 days)
[Numbered list with description, expected impact, effort level, and owner]

### Priority 2: Medium-Term (30-90 days)
[Numbered list with description, expected impact, effort level, and owner]

### Priority 3: Strategic (90+ days)
[Numbered list with description, expected impact, effort level, and owner]

---

## Metrics Dashboard

### Stage-Level Metrics
[Table: Stage | Primary KPI | Secondary KPI | Target | Current Baseline (if known)]

### Journey-Wide Metrics
[Table: Metric | Description | Formula | Target]

### Measurement Cadence
[Table: Metric Category | Frequency | Tool/Method | Owner]

---

## Appendix

### Persona Deep Dive
[Detailed persona profile including demographics, psychographics, goals, frustrations, preferred channels, and decision-making style]

### Channel Effectiveness Matrix
[Table: Channel | Best For Stage(s) | Reach | Cost | Conversion Impact | Priority]

### Competitive Journey Comparison
[Brief comparison of how competitors handle 2-3 key journey stages differently]

### Glossary
[Definitions of any industry-specific or methodology-specific terms used]

Mermaid Diagram Requirements

Generate TWO Mermaid diagrams in the document:

1. Journey Overview Diagram (near the top)

A simplified journey diagram showing the high-level flow:

journey
    title Customer Journey: [Product Name]
    section Awareness
      Discovers problem: 3: Prospect
      Finds brand via search: 3: Prospect
      Reads blog content: 4: Prospect
    section Consideration
      Requests demo: 4: Prospect
      Attends webinar: 4: Prospect, Sales
      Compares alternatives: 3: Prospect
    section Decision
      Negotiates pricing: 3: Prospect, Sales
      Signs contract: 5: Customer, Sales
    section Onboarding
      Completes setup: 4: Customer, Support
      First value moment: 5: Customer
    section Retention
      Regular usage: 5: Customer
      Contacts support: 3: Customer, Support
    section Expansion
      Upgrades plan: 4: Customer, Sales
      Adds team members: 5: Customer
    section Advocacy
      Writes review: 5: Advocate
      Refers colleague: 5: Advocate

2. Full Detail Diagram (in the dedicated section)

A more comprehensive diagram with granular touchpoints and accurate satisfaction scores (1-5) based on the analysis. Each touchpoint must have a realistic satisfaction score reflecting the emotional state described in the stage analysis.

Satisfaction Scoring Guide

Use this scale consistently across all diagrams and analysis:

ScoreMeaningEmotional State
1Extremely frustratedAngry, considering abandoning
2DissatisfiedAnnoyed, experiencing significant friction
3NeutralNeither positive nor negative, functional
4SatisfiedPositive experience, expectations met
5DelightedExceeded expectations, memorable positive moment

Quality Requirements

  1. Minimum 400 lines: The output document must be substantive and detailed, not padded with whitespace
  2. Specificity: Every touchpoint, pain point, and opportunity must be specific to the product/service and persona provided -- no generic filler
  3. Actionability: Recommendations must be concrete enough that a team could begin implementation immediately
  4. Metrics must be measurable: Every metric must include how it would actually be measured, not just what to measure
  5. Emotional realism: Emotional states must reflect genuine customer psychology, not idealized happy paths
  6. Pain points must be honest: Include real friction even in stages that are generally positive
  7. No emojis: Do not use emojis anywhere in the output document
  8. Mermaid validity: All Mermaid diagrams must use valid syntax that renders correctly
  9. Consistent voice: Use professional, strategic language throughout -- this is a working document for product and marketing teams
  10. Cross-references: Where relevant, reference how one stage's issues create downstream effects in later stages

Research Protocol

When generating the journey map:

  1. If the product is well-known: Use WebSearch to find real customer reviews, common complaints, competitor comparisons, and published journey insights
  2. If the product is a concept or early-stage: Base the journey on industry patterns and analogous products, noting assumptions clearly
  3. For all products: Consider standard SaaS, e-commerce, or service journey patterns as a baseline, then customize heavily based on the specific product and persona

How to Handle Ambiguity

  • If the user provides minimal input, generate the best possible journey map based on reasonable assumptions and clearly label every assumption
  • If the product type is unclear, ask one clarifying question before proceeding
  • If touchpoints are not specified, infer the most likely touchpoints for the product type and persona
  • Always err on the side of producing the deliverable rather than asking excessive questions

Example Invocation Patterns

Minimal input:

"Map the customer journey for Slack targeting engineering managers"

Detailed input:

"Map the customer journey for our B2B cybersecurity platform. Persona: CISO at Fortune 500. Touchpoints: RSA conference booth, Google ads, gated whitepaper, SDR outreach, technical POC, security review, procurement. Channels: website, email, LinkedIn, phone, partner referrals."

With specific focus:

"Map the customer journey for our DTC skincare brand, focusing especially on the post-purchase retention and advocacy stages. Persona: Women 25-40 interested in clean beauty."

In all cases, generate the complete seven-stage journey map with all required sections.

平台分布

Codex

34.84%
按下载量换算68

Claude

30.61%
按下载量换算59

Cursor

16.22%
按下载量换算31

Gemini CLI

9.18%
按下载量换算18

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

继续浏览同类 Skills