Token导航 LogoToken导航

Agent Skill · 研究检索

journey-mapping(旅程地图)

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

journey-mapping 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证为 MIT,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 52,984。

总安装 541周安装 23GitHub Stars 61下载 190核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/melodic-software/claude-code-plugins --skill journey-mapping

这个 Skill 是做什么的

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

用于查找、检索和筛选相关信息。适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词、任务场景或来源线索快速定位候选结果。通过 npx skills add 命令从指定仓库安装并使用。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

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

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

journey-mapping 怎么安装?

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

journey-mapping 支持哪些 AI 工具?

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

journey-mapping 需要什么权限?

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

journey-mapping 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

journey-mapping 用的人多吗?

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

journey-mapping 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 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调用外部服务未明确有提醒
journey-mapping

旅程地图 · 本页

54161只读MIT通过

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

SKILL.md 原文

Journey Mapping

Create user and customer journey maps to understand experiences, identify pain points, and discover improvement opportunities. A human-centered complement to process-focused value stream mapping.

What is a Journey Map?

A journey map visualizes a user's experience over time as they accomplish a goal. Unlike process maps (which show what happens), journey maps show how it feels from the user's perspective.

ElementDefinitionPurpose
PersonaWho is taking the journeyFocus on specific user type
PhasesMajor stages of the journeyOrganize the experience
TouchpointsInteractions with your systemIdentify contact points
ActionsWhat the user doesUnderstand behavior
ThoughtsWhat the user thinksUnderstand mindset
EmotionsHow the user feelsIdentify emotional peaks/valleys
Pain PointsFriction and frustrationsTarget improvements
OpportunitiesWays to improvePrioritize enhancements

Journey Types

TypeScopeWhen to Use
Current StateHow things are todayIdentify problems
Future StateDesired experienceDesign solutions
Day-in-the-LifeFull day across contextsUnderstand broader context
Service BlueprintJourney + backstage operationsDesign service delivery

Workflow

Phase 1: Preparation

Step 1: Define the Journey Scope
## Journey Definition

**Journey Name:** New Customer Onboarding
**Persona:** Sarah - First-time SaaS Buyer
**Goal:** Successfully adopt the product and get first value
**Trigger:** Signs up for trial
**End State:** Completes first project successfully
**Time Frame:** First 30 days
Step 2: Select or Create Persona
## Persona: Sarah - First-time SaaS Buyer

**Demographics:**
- Age: 32
- Role: Marketing Manager
- Company: Mid-size B2B
- Tech Savviness: Moderate

**Goals:**
- Streamline team workflows
- Prove ROI to leadership
- Look good to her team

**Frustrations:**
- Limited time to learn new tools
- Past bad experiences with complex software
- Pressure to show quick results

**Quote:** "I need something that works out of the box."

Phase 2: Map the Journey

Step 1: Identify Phases

Typical journey phases:

DomainCommon Phases
PurchaseAwareness → Consideration → Decision → Purchase
OnboardingSign-up → Setup → First Use → Habit Formation
SupportIssue → Search → Contact → Resolution → Follow-up
RenewalReview → Evaluate → Negotiate → Renew/Churn
Step 2: Map Touchpoints and Actions

For each phase:

## Phase: Setup

### Touchpoints
- Welcome email
- Product UI (setup wizard)
- Help documentation
- Onboarding video

### Actions
1. Opens welcome email
2. Clicks "Get Started"
3. Enters company info
4. Invites team members
5. Configures first workspace
Step 3: Capture Thoughts and Emotions
## Phase: Setup - Experience

| Step | Thought | Emotion | Intensity |
|------|---------|---------|-----------|
| Opens email | "Let's see if this is worth it" | Curious, skeptical | Neutral |
| Clicks Get Started | "Okay, here we go" | Hopeful | Slightly positive |
| Company info form | "Why so many fields?" | Frustrated | Negative |
| Invites team | "Easy enough" | Relieved | Positive |
| First workspace | "This is actually nice!" | Pleased | Very positive |
Step 4: Identify Pain Points
## Pain Points - Setup Phase

| Pain Point | Severity | Evidence | Root Cause |
|------------|----------|----------|------------|
| Too many required fields | High | Drop-off data, complaints | Legacy form design |
| Unclear field labels | Medium | Support tickets | Jargon-heavy copy |
| No save-and-continue | High | Abandoned setups | Technical limitation |
| Team invite confusion | Medium | Support volume | Poor UX |
Step 5: Identify Opportunities
## Opportunities - Setup Phase

| Opportunity | Impact | Effort | Priority |
|-------------|--------|--------|----------|
| Progressive disclosure (fewer upfront fields) | High | Low | 1 |
| Save progress functionality | High | Medium | 2 |
| Contextual help tooltips | Medium | Low | 3 |
| Interactive setup tutorial | Medium | High | 4 |

Phase 3: Visualize the Journey

Standard Journey Map Format
PHASE:      | Awareness    | Sign-up      | Setup        | First Use    | Habit
------------|--------------|--------------|--------------|--------------|--------
TOUCHPOINTS | Ads, blog    | Landing page | Email, UI    | Product      | Product
            |              | pricing page | docs         |              | email
------------|--------------|--------------|--------------|--------------|--------
ACTIONS     | Researches   | Compares     | Creates      | Explores     | Daily
            | solutions    | plans        | account      | features     | usage
------------|--------------|--------------|--------------|--------------|--------
THOUGHTS    | "Is there    | "Which plan  | "This is     | "How do I    | "This
            | a better     | is right?"   | taking       | do X?"       | saves
            | way?"        |              | too long"    |              | time"
------------|--------------|--------------|--------------|--------------|--------
EMOTIONS    |     😐       |      🤔      |      😣      |      😕      |     😊
            |  Neutral     |   Uncertain  |  Frustrated  |   Confused   |  Happy
------------|--------------|--------------|--------------|--------------|--------
PAIN POINTS | Too many     | Pricing      | Long form    | Feature      | None
            | options      | confusion    | No save      | discoverability
------------|--------------|--------------|--------------|--------------|--------
OPPORTUN-   | Clear        | Simpler      | Reduce       | Better       | Celebrate
ITIES       | comparisons  | pricing      | friction     | onboarding   | wins

Phase 4: Emotion Curve

Visualize emotional highs and lows:

EMOTION
  😊 +2  |                                              ___/
  😌 +1  |         ___/\                              /
  😐  0  |____/\__/      \            ___           /
  😕 -1  |                \          /   \__      _/
  😣 -2  |                 \________/          \_/

         |--Awareness--|--Sign-up--|--Setup--|--First Use--|--Habit--|
                                      ↑
                               Pain Point: Long form

Phase 5: Identify Moments of Truth

Moments of Truth are critical interactions that disproportionately impact the overall experience:

Moment TypeDefinitionExample
Zero Moment of Truth (ZMOT)Pre-purchase researchReading reviews
First Moment of Truth (FMOT)Initial encounterLanding page
Second Moment of Truth (SMOT)Using the productFirst workflow
Ultimate Moment of Truth (UMOT)Sharing experienceReferral/review
## Moments of Truth

| Moment | Phase | Current Experience | Desired Experience |
|--------|-------|-------------------|-------------------|
| FMOT | Landing | Overwhelming options | Clear value prop |
| SMOT | First Use | Confusion, need help | Guided success |
| UMOT | Habit | No celebration | Achievement sharing |

Output Formats

Narrative Summary

## Journey Map Summary

**Journey:** [Name]
**Persona:** [Name]
**Date:** [ISO date]
**Analyst:** journey-facilitator

### Journey Overview
[2-3 sentence summary of the end-to-end experience]

### Emotional Journey
- **Highest Point:** [Phase] - [Why]
- **Lowest Point:** [Phase] - [Why]
- **Overall Arc:** [Description]

### Critical Pain Points
1. **[Pain Point]** (Phase: [X]) - [Impact and evidence]
2. **[Pain Point]** (Phase: [X]) - [Impact and evidence]

### Top Opportunities
1. **[Opportunity]** - Impact: High, Effort: Low
2. **[Opportunity]** - Impact: High, Effort: Medium

### Moments of Truth
- **Make or Break Moment:** [Description]
- **Current State:** [Assessment]
- **Recommendation:** [Action]

Structured Data (YAML)

journey_map:
  name: "New Customer Onboarding"
  version: "1.0"
  date: "{ISO-8601-date}"
  analyst: "journey-facilitator"
  type: current_state

  persona:
    name: "Sarah"
    archetype: "First-time SaaS Buyer"
    goals:
      - "Get value quickly"
      - "Look good to leadership"
    frustrations:
      - "Limited time"
      - "Complex tools"

  journey:
    goal: "Successfully adopt and get first value"
    trigger: "Signs up for trial"
    end_state: "Completes first project"
    time_frame: "30 days"

  phases:
    - name: "Awareness"
      order: 1
      touchpoints:
        - channel: "Web"
          type: "Blog post"
        - channel: "Email"
          type: "Marketing email"
      actions:
        - "Researches solutions"
        - "Reads comparison articles"
      thoughts:
        - "Is there a better way?"
      emotions:
        overall: neutral
        intensity: 0
      pain_points: []
      opportunities:
        - name: "Clear comparison content"
          impact: medium
          effort: low

    - name: "Setup"
      order: 3
      touchpoints:
        - channel: "Email"
          type: "Welcome email"
        - channel: "Product"
          type: "Setup wizard"
      actions:
        - "Opens welcome email"
        - "Starts setup wizard"
        - "Enters company info"
      thoughts:
        - "This is taking too long"
        - "Why so many fields?"
      emotions:
        overall: frustrated
        intensity: -2
      pain_points:
        - description: "Long form with many required fields"
          severity: high
          evidence: "40% drop-off rate"
        - description: "No save-and-continue"
          severity: high
          evidence: "Support tickets"
      opportunities:
        - name: "Progressive disclosure"
          impact: high
          effort: low
        - name: "Save progress"
          impact: high
          effort: medium

  moments_of_truth:
    - type: "First Moment (FMOT)"
      phase: "Sign-up"
      current_state: "Overwhelming options"
      desired_state: "Clear value proposition"
      priority: high

    - type: "Second Moment (SMOT)"
      phase: "First Use"
      current_state: "Confusion, needs help"
      desired_state: "Guided success path"
      priority: high

  summary:
    emotion_arc: "Curious → Frustrated → Confused → Satisfied"
    highest_point:
      phase: "Habit"
      reason: "Realizes time savings"
    lowest_point:
      phase: "Setup"
      reason: "Long form, no progress saving"
    top_recommendation: "Reduce setup friction through progressive disclosure"

Mermaid Diagrams

Journey Flow:

journey
    title New Customer Onboarding Journey
    section Awareness
        Reads blog post: 5: Customer
        Watches demo video: 4: Customer
    section Sign-up
        Views pricing: 3: Customer
        Selects plan: 4: Customer
    section Setup
        Fills long form: 2: Customer
        Invites team: 4: Customer
    section First Use
        Explores features: 3: Customer
        Completes first task: 5: Customer
    section Habit
        Daily usage: 5: Customer

Emotion Curve (Mermaid XYChart):

xychart-beta
    title "Emotional Journey"
    x-axis ["Awareness", "Sign-up", "Setup", "First Use", "Habit"]
    y-axis "Emotion" -3 --> 3
    line [0, -1, -2, 1, 2]

Multi-Persona Workshop

For comprehensive journey analysis, run parallel persona agents:

Persona AgentPerspectiveFocus
first-time-user-personaNew to productOnboarding friction
power-user-personaExperiencedAdvanced needs
admin-personaManagementConfiguration, oversight
support-seeker-personaNeeds helpSupport experience

When to Use

ScenarioUse Journey Mapping?
UX redesignYes - understand current experience
Service designYes - design end-to-end experience
Customer complaintsYes - find pain points
Onboarding optimizationYes - improve adoption
Process improvementPartial - combine with VSM
Technical architectureNo - wrong level of abstraction

Integration

Upstream

  • stakeholder-analysis - Understand user stakeholders
  • process-modeling - Process context
  • Persona research - User research inputs

Downstream

  • Requirements - Experience requirements
  • UX design - Design improvements
  • value-stream-mapping - Operational improvements

Related Skills

  • value-stream-mapping - Process efficiency perspective
  • stakeholder-analysis - Stakeholder needs
  • capability-mapping - Capability touchpoints
  • root-cause-analysis - Investigate pain point causes
  • prioritization - Prioritize opportunities
  • decision-analysis - Evaluate improvement options

User-Facing Interface

When invoked directly by the user, this skill operates as follows.

Arguments

  • <journey-description>: Description of the journey to map (e.g., "customer purchasing a subscription")
  • --mode: Mapping mode (default: guided)

- full: Comprehensive journey with detailed touchpoint analysis (~10K tokens) - quick: Rapid journey mapping (~4K tokens) - guided: Interactive journey discovery (variable)

  • --persona: Optional persona name to use (creates new if not provided)
  • --dir: Output directory (default: docs/analysis/)

Execution Workflow

  1. Parse Arguments - Extract journey description, mode, and persona. If no description provided, ask the user who is taking the journey, what they are trying to accomplish, and where the journey starts and ends.
  2. Define or Select Persona - Use provided persona, create default from context (Quick/Full), or interactively define (Guided).
  3. Execute Based on Mode:

- Full: Spawn the journey-facilitator agent for thorough mapping with 4-6 phases, emotion curves, Moments of Truth (ZMOT/FMOT/SMOT/UMOT), and prioritized opportunities. - Quick: Rapid mapping with 4-5 phases, key touchpoints, obvious pain points, and top 3 opportunities. - Guided: Interactive discovery using AskUserQuestion for research approach and empathy depth, then walk through persona, scope, phases, phase deep-dives, moments of truth, and opportunities.

  1. Generate Output - Produce journey map markdown, Mermaid journey diagram, emotion curve (xychart-beta), pain point inventory, and opportunity backlog.
  2. Save Results - Save to docs/analysis/journey-map-[persona-name].md (or custom --dir).
  3. Suggest Follow-Ups - Recommend stakeholder-analysis for journey owners, value-stream-mapping for operations behind pain points, and capability-mapping for touchpoint-capability links.

Version History

  • v1.0.0 (2025-12-26): Initial release

平台分布

Antigravity

26.73%
按下载量换算51

Claude Code

22.47%
按下载量换算43

trae

16.8%
按下载量换算32

windsurf

12.98%
按下载量换算25

Codex

9.1%
按下载量换算17

Gemini CLI

3.44%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

继续浏览同类 Skills