Experience Map
- 973 installs
- 1.9k repo stars
- Updated June 14, 2026
- owl-listener/designer-skills
Experience-map is a UX design agent skill that visualizes the complete user journey across every touchpoint and channel before developers commit to features or distribution channels.
About
Experience-map is an owl-listener designer-skills agent skill for holistic, systems-level user journey mapping. It structures experience maps along a horizontal axis of six phases: awareness, evaluation, onboarding, regular use, advanced use, and advocacy/departure. Vertical layers capture user actions and key decisions, touchpoints such as website, app, email, support, and community, plus channels spanning desktop, mobile, in-person, and automated systems. Product teams and developers reach for experience-map before feature scoping when they need to see cross-channel relationships and gaps rather than a linear single-flow journey map. The output guides channel prioritization and feature commitment with ecosystem-wide visibility.
- Creates a full ecosystem experience map with six fixed phases: Awareness, Evaluation, Onboarding, Regular Use, Advanced
- Maps six vertical layers per phase: User Actions, Touchpoints, Channels, Emotions, Pain Points, Opportunities
- Visualizes ecosystem relationships including data flows and human-automated handoffs
- Always maps current state before future state
- Supports both digital and physical touchpoints in one unified view
Experience Map by the numbers
- 973 all-time installs (skills.sh)
- +42 installs in the week ending Jul 29, 2026 (Skillselion tracking)
- Ranked #407 of 1,888 Design & UI/UX skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/owl-listener/designer-skills --skill experience-mapAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 973 |
|---|---|
| repo stars | ★ 1.9k |
| Security audit | 3 / 3 scanners passed |
| Last updated | June 14, 2026 |
| Repository | owl-listener/designer-skills ↗ |
How do you map multi-channel user journeys?
Visualize the complete user journey across every touchpoint before committing to features or channels.
Who is it for?
Product developers and designers scoping multi-channel products who need ecosystem-level journey visibility before building features.
Skip if: Skip experience-map when you only need a single-screen UI wireframe without cross-channel journey context.
When should I use this skill?
A team asks to map user touchpoints, channels, journey phases, or ecosystem relationships before feature decisions.
What you get
Experience map with phased user actions, touchpoints, and channel layers across the full ecosystem.
- Experience map document
- Touchpoint and channel layer diagram
By the numbers
- Covers 6 journey phases from awareness through advocacy/departure
Files
Experience Map
You are an expert in mapping complex, multi-channel user experiences at a systems level.
What You Do
You create experience maps showing the entire ecosystem of user interactions across touchpoints, channels, and time.
Structure
Horizontal Axis: Phases
Awareness, evaluation, onboarding, regular use, advanced use, advocacy/departure.
Vertical Layers
- User Actions — what the user does, key decisions
- Touchpoints — website, app, email, support, community
- Channels — desktop, mobile, in-person, automated vs human
- Emotions — confidence, frustrations, delight
- Pain Points — friction, confusion, information gaps
- Opportunities — improvements, new touchpoints
Ecosystem Relationships
How touchpoints connect, data flow between channels, human-automated handoffs.
When to Use
New products, omnichannel evaluation, ecosystem gap analysis, cross-team alignment.
Best Practices
- Map current state before future state
- Include digital and physical touchpoints
- Involve cross-org stakeholders
- Validate with research, not assumptions
Related skills
Frontend DesignGenerate distinctive, production-grade frontend interfaces and components that avoid generic AI aesthetics.698k164k
Web Design GuidelinesAutomatically audit frontend code against the latest Vercel Web Interface Guidelines for consistency, accessibility, and UX quality.486k29.4k
Lark WhiteboardGenerate valid Lark Whiteboard (Feishu Board) documents with correctly placed connectors, automatic routing, and proper schema compliance directly from agent inst382k15.8k
Sleek Design Mobile AppsGenerate mobile app screens and UI from plain English descriptions using the Sleek.design API.315k470
Design Taste FrontendOverride generic LLM frontend output with intentional, metric-driven UI/UX taste.284k66.9k
Ui Ux Pro MaxGet instant, high-quality UI/UX decisions, component recommendations, style guidance, and code improvements across web and mobile projects.282k109kFAQ
What phases does experience-map include?
Experience-map includes six horizontal phases—awareness, evaluation, onboarding, regular use, advanced use, and advocacy/departure—each layered with user actions, touchpoints, and channels.
When should teams use experience-map?
Teams should use experience-map before committing to features or channels when they need a holistic view of user interactions across website, app, email, support, and community touchpoints.
Is Experience Map safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.