calubecalube/mobile-observability/skills/instrumentation-planning/SKILL.md

instrumentation-planning

Skill116 starsChanged 11 months agoMITView on GitHub

Plan what to measure in mobile apps. Use when starting observability, prioritizing instrumentation, or asking "what should I track?

In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- crash-instrumentationSkill
- interaction-latencySkill
- navigation-latencySkill
- network-tracingSkill
- session-replaySkill
- symbolication-setupSkill
- user-journey-trackingSkill

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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

Distinctive:
Use OTel-compatible span/attribute names now (zero cost, easier migration later):
line 47

≈ “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

Instrumentation Planning

Strategic guidance for what to measure using Jobs-to-be-Done framework.

Core Question

For each user job, ask:

Did it complete? → completion rate
How long? → duration (p50, p95, p99)
What failed? → error type, context
Did they give up? → drop-off rate

Priority Tiers

Tier	Focus	Examples
1	Crashes & errors	Crash reporting, error boundaries
2	User context	User ID, session ID, device info
3	Performance	App start, screen load, network
4	Breadcrumbs	Navigation, user actions
5	Business metrics	Funnels, feature usage

Implementation Order

Day 1:  Crash reporting + User context
Week 1: Breadcrumbs + Release tracking
Week 2: Performance spans
Month 1: Business metrics

Future-Proofing

Use OTel-compatible span/attribute names now (zero cost, easier migration later):

http.request.method not method
ui.screen.load not screenLoad
app.start.cold not coldStart

See references/otel-mobile.md for full naming conventions.

Anti-Patterns

Measure everything (noise, battery drain)
Skip symbolication (unreadable crashes)
Block main thread for telemetry
Log PII in breadcrumbs

Implementation

See references/instrumentation-patterns.md for:

Detailed 5-tier checklist
Span naming conventions
Sampling strategies
Testing checklist

See references/jtbd.md for full Jobs-to-be-Done framework.

Related Skills

See skills/user-journey-tracking for implementing JTBD instrumentation
See skills/crash-instrumentation for Tier 1 (crashes)
See skills/symbolication-setup for Tier 1 (readable stack traces)

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