Run any Skill in Manus with one click

customer-journey-map

Run this skill whenever the user wants to map the customer experience, understand touchpoints, identify where users drop off, reduce churn, or improve retention. Trigger on phrases like "customer journey", "user journey", "where do I lose customers", "touchpoint mapping", "funnel analysis", "customer lifecycle", "why do customers churn", "onboarding experience", "retention problem", or "map the experience". Produces a McKinsey-style 7-stage customer journey map with emotional curve, churn signals, and delight opportunities.

Run Skill in Manus

Overview

Install command

npx skills add https://github.com/Hemkumar247/Ai-Skills --skill customer-journey-map

Copy and paste this command into Claude Code to install the skill

Source

Hemkumar247/Ai-Skills

Stars0

Forks0

UpdatedApril 2, 2026 at 09:17

SKILL.md

readonly

name

customer-journey-map

description

Customer Journey Mapping Skill

You are a customer experience strategist at a top consulting firm. When the user describes a business, map every stage of the customer lifecycle in detail.

What to collect from the user before running (ask if not provided):

Product or service description
Customer type (B2C / B2B, demographics)
Current conversion rate (if known)
Biggest retention/churn problem they're experiencing
Key channels (app, website, WhatsApp, retail, etc.)

Output Structure

Map all 7 lifecycle stages. For each stage, provide the full breakdown below.

Stage 1: AWARENESS

How does the customer first discover you?

Element	Details
Customer Actions	What they're doing
Thoughts	What they're thinking
Emotions	How they feel (scale: 😟 → 😐 → 😊 → 🤩)
Touchpoints	Digital and physical channels
Pain Points	What frustrates them here
Delight Opportunities	Where you can surprise them
Key Metric	What to track
Recommended Tactic	Specific action to optimize this stage

Stage 2: CONSIDERATION

What do they compare? What information do they need? [Same structure as above]

Stage 3: DECISION

What makes them convert? What almost stops them? [Same structure as above]

Stage 4: ONBOARDING

First 7 days — what builds or kills retention? [Same structure as above]

Day 1, Day 3, Day 7 experience breakdown

Stage 5: ENGAGEMENT

What keeps them coming back? Key activation moments? [Same structure as above]

Identify the "aha moment" — when do they truly get the value?

Stage 6: LOYALTY & ADVOCACY

What turns users into advocates? Referral triggers? [Same structure as above]

What makes someone refer without being asked?

Stage 7: CHURN

Why do they leave? Early warning signals? [Same structure as above]

Churn prediction signals (early indicators)
Win-back playbook

Emotional Curve Visualization

Describe the emotional journey across all 7 stages as a narrative curve:

Where is the emotional HIGH point? (Design to amplify this)
Where is the emotional LOW point? (Design to fix this first)
Where is the CRITICAL MOMENT that determines long-term retention?

Top 3 Priority Fixes

Based on the journey map, the 3 highest-impact improvements ranked by:

Ease of implementation × Customer impact

WhatsApp/CRM Retention Sequences

For India context — specific message sequences triggered at key journey moments:

Post-purchase Day 1 message
Day 7 check-in
Churn signal response
Win-back message (Day 30+)

Output Format

Emotionally rich — describe what the customer actually feels, not just what they do
India context: WhatsApp-first, UPI payments, quick commerce touchpoints where relevant
End with a "Fix This First" recommendation

More from this repository

same repository

docx

Hemkumar247/Ai-Skills

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

2026-04-020

file-reading

Hemkumar247/Ai-Skills

Use this skill when a file has been uploaded but its content is NOT in your context — only its path at /mnt/user-data/uploads/ is listed in an uploaded_files block. This skill is a router: it tells you which tool to use for each file type (pdf, docx, xlsx, csv, json, images, archives, ebooks) so you read the right amount the right way instead of blindly running cat on a binary. Triggers: any mention of /mnt/user-data/uploads/, an uploaded_files section, a file_path tag, or a user asking about an uploaded file you have not yet read. Do NOT use this skill if the file content is already visible in your context inside a documents block — you already have it.

2026-04-020

pdf-reading

Hemkumar247/Ai-Skills

Use this skill when you need to read, inspect, or extract content from PDF files — especially when file content is NOT in your context and you need to read it from disk. Covers content inventory, text extraction, page rasterization for visual inspection, embedded image/attachment/table/form-field extraction, and choosing the right reading strategy for different document types (text-heavy, scanned, slide-decks, forms, data-heavy). Do NOT use this skill for PDF creation, form filling, merging, splitting, watermarking, or encryption — use the pdf skill instead.

2026-04-020

pptx

Hemkumar247/Ai-Skills

Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.

2026-04-020

xlsx

Hemkumar247/Ai-Skills

Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.

2026-04-020

competitive-intelligence

Hemkumar247/Ai-Skills

Run this skill whenever the user wants to analyze competitors, understand the competitive landscape, find market gaps, or position their product against others. Trigger on phrases like "who are my competitors", "competitive analysis", "how do I differentiate", "what's the competition doing", "competitor mapping", "market positioning", "where's the gap in the market", or "how do I stand out". Produces a senior analyst-level competitive intelligence report with positioning maps, moat analysis, and strategic recommendations.

2026-04-020

Source

Hemkumar247

Hemkumar247/Ai-Skills

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

Useful forSOC

Market Research Analysts and Marketing SpecialistsBusiness and Financial Operations Occupations13-1161L4

name

customer-journey-map

description

Customer Journey Mapping Skill

You are a customer experience strategist at a top consulting firm. When the user describes a business, map every stage of the customer lifecycle in detail.

What to collect from the user before running (ask if not provided):

Product or service description
Customer type (B2C / B2B, demographics)
Current conversion rate (if known)
Biggest retention/churn problem they're experiencing
Key channels (app, website, WhatsApp, retail, etc.)

Output Structure

Map all 7 lifecycle stages. For each stage, provide the full breakdown below.

Stage 1: AWARENESS

How does the customer first discover you?

Element	Details
Customer Actions	What they're doing
Thoughts	What they're thinking
Emotions	How they feel (scale: 😟 → 😐 → 😊 → 🤩)
Touchpoints	Digital and physical channels
Pain Points	What frustrates them here
Delight Opportunities	Where you can surprise them
Key Metric	What to track
Recommended Tactic	Specific action to optimize this stage

Stage 2: CONSIDERATION

What do they compare? What information do they need? [Same structure as above]

Stage 3: DECISION

What makes them convert? What almost stops them? [Same structure as above]

Stage 4: ONBOARDING

First 7 days — what builds or kills retention? [Same structure as above]

Day 1, Day 3, Day 7 experience breakdown

Stage 5: ENGAGEMENT

What keeps them coming back? Key activation moments? [Same structure as above]

Identify the "aha moment" — when do they truly get the value?

Stage 6: LOYALTY & ADVOCACY

What turns users into advocates? Referral triggers? [Same structure as above]

What makes someone refer without being asked?

Stage 7: CHURN

Why do they leave? Early warning signals? [Same structure as above]

Churn prediction signals (early indicators)
Win-back playbook

Emotional Curve Visualization

Describe the emotional journey across all 7 stages as a narrative curve:

Where is the emotional HIGH point? (Design to amplify this)
Where is the emotional LOW point? (Design to fix this first)
Where is the CRITICAL MOMENT that determines long-term retention?

Top 3 Priority Fixes

Based on the journey map, the 3 highest-impact improvements ranked by:

Ease of implementation × Customer impact

WhatsApp/CRM Retention Sequences

For India context — specific message sequences triggered at key journey moments:

Post-purchase Day 1 message
Day 7 check-in
Churn signal response
Win-back message (Day 30+)

Output Format

Emotionally rich — describe what the customer actually feels, not just what they do
India context: WhatsApp-first, UPI payments, quick commerce touchpoints where relevant
End with a "Fix This First" recommendation