User Story Mapping
deanpeters/Product-Manager-Skills
Lays out a user journey as activities, steps, and tasks on a two-dimensional map that then informs backlog slicing.
Agent skill
User Journey Tracking
by nexus-labs-automation in nexus-labs-automation/mobile-observability
Track user journeys with intent context and friction signals.
Install User Journey Tracking
$ npx skills add nexus-labs-automation/mobile-observability --skill user-journey-tracking -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nexus-labs-automation/mobile-observability user-journey-tracking --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/nexus-labs-automation/mobile-observability.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/user-journey-tracking .claude/skills/user-journey-tracking && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "user-journey-tracking" agent skill from https://github.com/nexus-labs-automation/mobile-observability/tree/main/skills/user-journey-tracking into .claude/skills/user-journey-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-journey-tracking", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/nexus-labs-automation/mobile-observability/tree/main/skills/user-journey-trackingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add nexus-labs-automation/mobile-observability --skill user-journey-tracking -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nexus-labs-automation/mobile-observability user-journey-tracking --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nexus-labs-automation/mobile-observability.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/user-journey-tracking .agents/skills/user-journey-tracking && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "user-journey-tracking" agent skill from https://github.com/nexus-labs-automation/mobile-observability/tree/main/skills/user-journey-tracking into .agents/skills/user-journey-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-journey-tracking", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nexus-labs-automation/mobile-observability --skill user-journey-tracking -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nexus-labs-automation/mobile-observability user-journey-tracking --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nexus-labs-automation/mobile-observability.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/user-journey-tracking .cursor/skills/user-journey-tracking && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "user-journey-tracking" agent skill from https://github.com/nexus-labs-automation/mobile-observability/tree/main/skills/user-journey-tracking into .cursor/skills/user-journey-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-journey-tracking", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/nexus-labs-automation/mobile-observability.git --path skills/user-journey-tracking--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add nexus-labs-automation/mobile-observability --skill user-journey-tracking -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nexus-labs-automation/mobile-observability user-journey-tracking --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nexus-labs-automation/mobile-observability.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/user-journey-tracking .gemini/skills/user-journey-tracking && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "user-journey-tracking" agent skill from https://github.com/nexus-labs-automation/mobile-observability/tree/main/skills/user-journey-tracking into .gemini/skills/user-journey-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-journey-tracking", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install nexus-labs-automation/mobile-observability user-journey-trackingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add nexus-labs-automation/mobile-observability --skill user-journey-tracking -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nexus-labs-automation/mobile-observability.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/user-journey-tracking .github/skills/user-journey-tracking && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "user-journey-tracking" agent skill from https://github.com/nexus-labs-automation/mobile-observability/tree/main/skills/user-journey-tracking into .github/skills/user-journey-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-journey-tracking", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nexus-labs-automation/mobile-observability --skill user-journey-tracking -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nexus-labs-automation/mobile-observability user-journey-tracking --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nexus-labs-automation/mobile-observability.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/user-journey-tracking .opencode/skills/user-journey-tracking && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "user-journey-tracking" agent skill from https://github.com/nexus-labs-automation/mobile-observability/tree/main/skills/user-journey-tracking into .opencode/skills/user-journey-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-journey-tracking", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
user-journey-tracking- GitHub stars
- 116
- Token cost
- ~638 tokens
- SKILL.md length
- 246 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- MIT
At a glance
Track user journeys with intent context and friction signals.
- Works in 3 steps: Does this help identify what the user… → Does this help determine if they… → Does this help explain why they failed?…
- Instrumenting onboarding
- SKILL.md covers Core Principle, Key Context to Attach, Friction Signals to Track and Outcome Quality, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
User Journey Tracking is an agent skill from nexus-labs-automation/mobile-observability. Track user journeys with intent context and friction signals. Use when instrumenting onboarding, checkout, or any multi-step flow where you need to understand WHY users fail.
Its SKILL.md is about 640 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering Customer journey mapping. The repository describes itself as: Claude Code plugin for mobile app observability: crash reporting, performance monitoring, and instrumentation for iOS, Android, and React Native. The licence is MIT.
When your agent uses it
- Instrumenting onboarding
- Any multi-step flow where you need to understand WHY users fail
Example prompts
- “/user-journey-tracking”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Does this help identify what the user was trying to do? → Add intent context
- Does this help determine if they succeeded? → Track outcomes
- Does this help explain why they failed? → Add friction signals
What it can do on your machine
Read from SKILL.md and the folder at commit 488c97f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
User Journey Tracking loads about 638 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 246 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from nexus-labs-automation/mobile-observability at commit 488c97f, republished under its MIT licence (© nexus-labs-automation). 246 words, ~638 tokens.
Download SKILL.mdSave it as
.claude/skills/user-journey-tracking/SKILL.md (or your agent's skills folder).- name
- user-journey-tracking
- description
- Track user journeys with intent context and friction signals. Use when instrumenting onboarding, checkout, or any multi-step flow where you need to understand WHY users fail.
- triggers
- checkout funnel, conversion tracking, drop-off tracking, onboarding flow, track user funnels, user journey
- priority
- 2
User Journey Tracking
Track not just WHAT users do, but WHETHER they accomplished their goal.
Core Principle
Every journey event should help answer: "Why did users fail to complete their intended task?"
Key Context to Attach
| Field | Example | Purpose |
|---|---|---|
job_name | "checkout" | User's intended task |
job_step | "payment" | Current step in journey |
job_progress | "3/4" | How far they got |
outcome | "success" / "friction" / "abandon" | Did they succeed? |
Friction Signals to Track
Detect user struggle before they contact support:
| Signal | Detection |
|---|---|
| Rage taps | 3+ taps same element in 1s |
| Retry exhaustion | 3+ retries of same action |
| Quick abandonment | Exit within 5s of error |
| Navigation loops | 3+ back navigations without progress |
Outcome Quality
Not just success/failure:
- Completed smoothly — no friction
- Completed with friction — retries, errors, slow
- Abandoned after friction — struggled, then quit
- Abandoned immediately — no engagement
"Completed with friction" is often the most actionable signal.
When to Use This Skill
- Onboarding flows
- Checkout/payment funnels
- Signup/registration
- Any multi-step process
- Feature adoption tracking
Implementation References
| Topic | Reference |
|---|---|
| Full methodology | references/user-focused-observability.md |
| Job-based patterns | references/jtbd.md |
| Friction detection code | references/user-journeys.md |
| Journey correlation | references/user-journeys.md |
Decision Tree
Before adding journey instrumentation:
- Does this help identify what the user was trying to do? → Add intent context
- Does this help determine if they succeeded? → Track outcomes
- Does this help explain why they failed? → Add friction signals
If no to all three → probably don't need it.
Related Skills
- See
skills/instrumentation-planningfor prioritization framework - Combine with
skills/interaction-latencyfor friction detection on key actions - Combine with
skills/navigation-latencyfor screen transition context
© nexus-labs-automation, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/user-journey-tracking of nexus-labs-automation/mobile-observability.
Open the folder on GitHubat commit 488c97f
Compare with similar skills
User Journey Tracking next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| User Journey Tracking this skillnexus-labs-automation/mobile-observability | 116 | — | ~638 | Automated safety check: Pass | MIT | |
| User Story Mappingdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~2.8k | Automated safety check: Pass | Custom licence | |
| QA Critical UXfastrepl/anarlog | 9.5k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Prdjuanandresgs/claude-ctrl | 193 | — | ~2.9k | Automated safety check: Pass | None | |
| Customer Journey Map Builderdeanpeters/Product-Manager-Skills | 7.2k | 1 repos | ~3.7k | Automated safety check: Pass | Custom licence | |
| Super Product Ownersyahiidkamil/Software-Engineer-AI-Agent-Atlas | 401 | — | ~7.9k | Automated safety check: Pass | None |
Similar skills
QA Critical UX
fastrepl/anarlog
QA Anarlog's critical Pro user journey on a signed staging candidate — onboarding, responsive launch, microphone and system-audio capture, automated summaries, and cloud sync.
Prd
juanandresgs/claude-ctrl
Write structured feature specifications with problem statements, user journeys, use cases, functional requirements, and success metrics.
Customer Journey Map Builder
deanpeters/Product-Manager-Skills
Builds a stage-by-stage customer journey map covering actions, touchpoints, emotions, KPIs, goals, and owning teams for one persona and scenario.
Super Product Owner
syahiidkamil/Software-Engineer-AI-Agent-Atlas
Complete Product Owner / Product Manager capability — a wiki-style knowledge map of product practice in active software development: the role and its boundaries, strategy cascade (vision → OKRs →…
Attribution Analysis Modeling
liangdabiao/claude-data-analysis-ultra-main
Perform multi-touch attribution analysis using Markov chains, Shapley values, and custom attribution models.
More from nexus-labs-automation/mobile-observability
All 8 skills in this repoCrash Instrumentation
nexus-labs-automation/mobile-observability
Set up crash instrumentation with actionable context. An agent skill from nexus-labs-automation/mobile-observability.
Instrumentation Planning
nexus-labs-automation/mobile-observability
Plan what to measure in mobile apps. An agent skill from nexus-labs-automation/mobile-observability.
Network Tracing
nexus-labs-automation/mobile-observability
Instrument API requests with spans and distributed tracing. An agent skill from nexus-labs-automation/mobile-observability.
Symbolication Setup
nexus-labs-automation/mobile-observability
Configure crash symbolication for readable stack traces. An agent skill from nexus-labs-automation/mobile-observability.
Interaction Latency
nexus-labs-automation/mobile-observability
Measure time from user tap to action completion. An agent skill from nexus-labs-automation/mobile-observability.
Navigation Latency
nexus-labs-automation/mobile-observability
Measure time from navigation tap to screen fully loaded and interactive.
Related
Categories
Questions about User Journey Tracking
What does User Journey Tracking do?
Track user journeys with intent context and friction signals. User Journey Tracking is an agent skill from nexus-labs-automation/mobile-observability. Track user journeys with intent context and friction signals.
When should I use User Journey Tracking?
User Journey Tracking fits situations like: instrumenting onboarding; any multi-step flow where you need to understand WHY users fail.
How do I install User Journey Tracking in Claude Code?
Run `npx skills add nexus-labs-automation/mobile-observability --skill user-journey-tracking -a claude-code`. Or copy the skill folder (skills/user-journey-tracking in nexus-labs-automation/mobile-observability) into .claude/skills/user-journey-tracking in your project. Claude Code loads it when a task matches its description.
How do I install User Journey Tracking in Codex?
Run `npx skills add nexus-labs-automation/mobile-observability --skill user-journey-tracking -a codex`. Or copy the skill folder (skills/user-journey-tracking in nexus-labs-automation/mobile-observability) into .agents/skills/user-journey-tracking in your project. Codex loads it when a task matches its description.
Can I use User Journey Tracking in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nexus-labs-automation/mobile-observability --skill user-journey-tracking -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/user-journey-tracking, .gemini/skills/user-journey-tracking, .github/skills/user-journey-tracking and .opencode/skills/user-journey-tracking in your project.
What does User Journey Tracking need to run?
SKILL.md names no scripts, command-line tools or credentials: User Journey Tracking is instructions for the agent only.
Does User Journey Tracking access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is User Journey Tracking safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does User Journey Tracking use?
User Journey Tracking is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does User Journey Tracking use?
About 638 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to User Journey Tracking?
Skills that share tags, products or a category with User Journey Tracking: User Story Mapping (deanpeters/Product-Manager-Skills, 7.2k stars), QA Critical UX (fastrepl/anarlog, 9.5k stars), Prd (juanandresgs/claude-ctrl, 193 stars) and Customer Journey Map Builder (deanpeters/Product-Manager-Skills, 7.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains User Journey Tracking?
nexus-labs-automation (a GitHub organization) maintains it in nexus-labs-automation/mobile-observability, which has 116 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on August 23, 2026.
Source: nexus-labs-automation/mobile-observability on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.