smithery/nexus-labs-automation

navigation-latency

Measure time from navigation tap to screen fully loaded and interactive. Use when tracking screen transitions, deep links, or tab switches.

Installation

$ npx skills add smithery/nexus-labs-automation --skill navigation-latency

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/nexus-labs-automation · top by installs.

npx skills add smithery/nexus-labs-automation

Browse all from smithery/nexus-labs-automation

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,594 B
  • docs SUMMARY.md 165 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Navigation Latency

Time from tap to destination screen interactive (TTI).

Phases

TAP → TRANSITION → VIEW_INIT → DATA_LOAD → INTERACTIVE
     |_____________________________________________|
                   Navigation Latency

When to Use

  • Tab bar taps
  • List item → detail screen
  • Deep link → target screen
  • Any screen-to-screen transition

Key Thresholds

Rating Duration
Good <400ms
Acceptable <1s
Poor >1s

Measurement Points

  1. onNavigationStart - user taps (source screen)
  2. onViewAppear - destination view visible
  3. onContentReady - data loaded, interactive

Implementation

See references/ui-performance.md (Navigation Latency section) for:

  • iOS: NavigationLatencyTracker with os_signpost
  • Android: Fragment/Activity lifecycle hooks
  • React Native: React Navigation listeners

Common Mistakes

  • Measuring only view appear (missing data load)
  • Not correlating source → destination
  • Ignoring warm vs cold screen loads

Related Skills

  • See skills/interaction-latency for button/tap response times (vs full screen loads)
  • Combine with skills/user-journey-tracking to correlate navigation with user intent