Agent skill
interaction-latency
Measure time from user tap to action completion. Use when tracking button response times, form submissions, add-to-cart, or any tap-triggered operation.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/development/interaction-latency-nexus-labs-automatio-mobile-observability
SKILL.md
Interaction Latency
Time from user tap to action successfully completed.
When to Use
- "Add to cart" button tapped → cart updated
- "Submit" button tapped → form processed
- "Like" button tapped → state changed
- Any tap that triggers async work
Measurement Pattern
TAP → START_SPAN → [async work] → END_SPAN
- Capture tap timestamp
- Start span with operation name
- End span when action confirms success
- Include success/failure outcome
Key Thresholds
| Rating | Duration |
|---|---|
| Good | <300ms |
| Acceptable | <1s |
| Poor | >1s |
Implementation
See references/ui-performance.md (Entry Point Latency section) for platform-specific code.
Common Mistakes
- Ending span on API call start (not completion)
- Not tracking failure cases
- Missing the tap timestamp (starting late)
Related Skills
- See
skills/navigation-latencyfor screen-to-screen transitions (vs single-tap actions) - Combine with
skills/user-journey-trackingfor friction detection on key interactions
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?