user-journey-tracking

user-journey-tracking is a skill for Claude Code from nexus-labs-automation/mobile-observability. It costs 39 tokens per session (593 once invoked), scanned A, original, MIT.

A way to record each step in a user's task, along with whether they succeeded, struggled, or quit. It adds context such as the intended job, current step, progress, and signs of frustration.

In plain words
What is it for?
Use it to study onboarding, checkout, payments, and other multi-step flows. It helps identify issues such as repeated taps, failed retries, quick exits, and navigation loops.
Why use it?
Basic analytics shows what users clicked but not whether they achieved their goal or why they stopped. This helps distinguish smooth completions from retries, errors, and abandonment.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the mobile-observability plugin — 8 skills, 2 commands, 2 agents shipped together

Good fit Use it to study onboarding, checkout, payments, and other multi-step flows. It helps identify issues such as repeated taps, failed retries, quick exits, and navigation loops.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nexus-labs-automation/mobile-observability/user-journey-tracking
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add nexus-labs-automation/mobile-observability --skill user-journey-tracking
Clone the repo
git clone --depth 1 https://github.com/nexus-labs-automation/mobile-observability

Made for: Claude Code.

Or install mobile-observability, the plugin that ships this one along with the rest of its 8 skills, 2 commands, 2 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for user-journey-tracking

README.md
[![agentmods](https://agentmods.dev/badge/skills/nexus-labs-automation/mobile-observability/user-journey-tracking/github.svg)](https://agentmods.dev/skills/nexus-labs-automation/mobile-observability/user-journey-tracking)
Your own site
<a href="https://agentmods.dev/skills/nexus-labs-automation/mobile-observability/user-journey-tracking"><img src="https://agentmods.dev/badge/skills/nexus-labs-automation/mobile-observability/user-journey-tracking/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for user-journey-tracking

Your own site · 80×15
<a href="https://agentmods.dev/skills/nexus-labs-automation/mobile-observability/user-journey-tracking"><img src="https://agentmods.dev/badge/skills/nexus-labs-automation/mobile-observability/user-journey-tracking.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 593 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00039 $0.00593
Opus 5 $0.00019 $0.00296
Sonnet 5 $0.00008 $0.00119
Haiku 4.5 $0.00004 $0.00059

Measured 12d ago against content hash a94b55ff6d4d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

user-journey-tracking scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/user-journey-tracking/SKILL.md · 85 lines

How it starts

The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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:

  1. Does this help identify what the user was trying to do? → Add intent context
  2. Does this help determine if they succeeded? → Track outcomes
  3. Does this help explain why they failed? → Add friction signals

If no to all three → probably don't need it.

  • See skills/instrumentation-planning for prioritization framework
  • Combine with skills/interaction-latency for friction detection on key actions
  • Combine with skills/navigation-latency for screen transition context

Read the full file on GitHub · 85 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 85 lines · 39 tokens per session scan A a94b55ff6d4d

Subscribe to this mod's changes

user-journey-tracking is a skill published in the GitHub repository nexus-labs-automation/mobile-observability (116 stars, last pushed 19d ago), licensed MIT. It adds 39 tokens to every session and 593 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

onesub

Use this skill when the user wants to add in-app purchases (subscriptions, consumables, or non-consumables) to a React Native / Expo mobile app. onesub is the open-source server side of react-native-iap — one line of Express middleware validates Apple StoreKit 2 and Google Play Billing receipts. Pair it with the…

jeonghwanko/onesub · 0 tokens

storekit

In-app purchases and subscriptions on iOS/iPadOS/macOS with StoreKit 2 (iOS 26 era) — fetch products with Product.products(for:), buy with Product.purchase and switch on PurchaseResult (.success/.pending/.userCancelled), always unwrap VerificationResult (.verified/.unverified), gate access from…

TalissonVitorino/kmp-ios-skills · 242 tokens

play-billing-library-version-upgrade

Use this skill when upgrading or migrating an Android project from any legacy Google Play Billing Library (PBL) version to the latest stable version of PBL.

TalissonVitorino/kmp-ios-skills · 39 tokens

in-app-purchase-expert

Professional In App Purchase Expert skill. Build performance-tuned, secure, and intuitive mobile applications for iOS and Android.

AtulPurohit/Antigravity-Awesome-Skills · 31 tokens

in-app-purchase

Professional In App Purchase Expert skill. Build performance-tuned, secure, and intuitive mobile applications for iOS and Android.

AtulPurohit/Antigravity-Awesome-Skills · 29 tokens

argent-device-interact

Interact with an iOS simulator, Android emulator, or Chromium (CDP) app using argent MCP tools. Use when tapping UI elements, performing gestures, scrolling/swiping, typing text, pressing hardware buttons, launching apps, opening URLs, taking screenshots, waiting for an element to appear or disappear, or checking…

software-mansion/argent · 78 tokens