cs-customer-journey-map SKILL.md skillA
cs-customer-journey-map from polar-bear-org/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add polar-bear-org/claude-skills/cs-customer-journey-map@git:20261026.a2f0899Pins git:20261026.a2f0899 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- polar-bear-org/claude-skills
- Path
packs/ai-for-customer-service-pack/skills/cs-customer-journey-map/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261026.a2f0899, committed Oct 26, 2026
- First version recorded
- Sep 27, 2026
- Size
- 5,267 bytes
- Repository stars
- 51
- License
- a license file GitHub does not identify
Builds a customer journey map from real tickets, with phases, actions, thoughts and feelings, the contact points where customers get confused and write in, and rewrites of the messages that cause it. Use for "run cs-customer-journey-map", "customer journey map", "why do customers keep contacting us", "customers don't read the emails", "map where customers get confused", "rewrite our order emails", "journey map from tickets", "where do our tickets start", part of the AI for Customer Service…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Customer Journey Map ## When To Use Customers do not read, then contact us furious, five times. The answer they missed was somewhere: a sign-up email, an order screen, a policy page. This map answers one question: at which step of their journey do customers get lost, and which words we sent put them there? ## When Not To Use If you already know where it breaks and need to see the internal handoffs behind it, run the Service Blueprint. If you have no tickets or comments for the journey, do not draw one from memory: tag a few weeks of tickets first with the Ticket Taxonomy. ## Inputs - One journey, for example "order to delivery" or "sign-up to first use" - Tickets or survey comments from that journey, with reason tags if you have them - The messages customers see on the way: emails, screens, help pages, policy text If you have none of this, I start from the journey's name and the steps as you describe them, and mark the output as a first draft with every emotion as a guess to check. ## Approach …
Read the whole file at its exact version.
How to install
mdr add polar-bear-org/claude-skills/cs-customer-journey-map@sha256:4d824b9f408c1c74The line at the top of this page pins the label git:20261026.a2f0899, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_7ls7hinjqvbhw6r6)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 27, 2026 and Oct 26, 2026, about one every 29 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261026.a2f0899 latest | 2026-10-26 | a2f0899 | 5,267 B | A | view · diff |
| git:20260927.63d5f36 | 2026-09-27 | 63d5f36 | 5,219 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5267 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
polar-bear-org/claude-skills · 51 stars · license a license file GitHub does not identify · pushed 2026-10-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7ls7hinjqvbhw6r6 GET https://markdownregistry.com/api/v1/resolve?ref=polar-bear-org/claude-skills/cs-customer-journey-map GET https://markdownregistry.com/api/v1/blob/4d824b9f408c1c7430dff69f0e4b268e66cce13170a15b625b71f61f0b14bdb0
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.