agentleFS
Sign inStart free
calubecalube/mobile-observability/skills/interaction-latency/SKILL.md

interaction-latency

Skill116 starsChanged 11 months agoMITView on GitHub

Measure time from user tap to action completion. Use when tracking button response times, form submissions, add-to-cart, or any tap-triggered operation.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Start span with operation name

    line 32
  2. Distinctive:

    Not tracking failure cases

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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
  1. Capture tap timestamp
  2. Start span with operation name
  3. End span when action confirms success
  4. Include success/failure outcome

Key Thresholds

RatingDuration
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-latency for screen-to-screen transitions (vs single-tap actions)
  • Combine with skills/user-journey-tracking for friction detection on key interactions

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free