Instrumentation Planning

Organization

nexus-labs-automation

instrumentation-planning

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

Overview

Publisher	nexus-labs-automation
Repository	`mobile-observability`
Skill name	`instrumentation-planning`
Stars	116
Forks	12
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by nexus-labs-automation on GitHub. Read the source before you install it.

Installation

Install the Instrumentation Planning AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/nexus-labs-automation/mobile-observability/tree/main/skills/instrumentation-planning

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/nexus-labs-automation/mobile-observability.git /tmp/mobile-observability
mkdir -p .claude/skills
cp -r /tmp/mobile-observability/skills/instrumentation-planning .claude/skills/instrumentation-planning

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Instrumentation Planning in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Instrumentation Planning on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Instrumentation Planning is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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)

Frequently asked questions

What does the Instrumentation Planning AI skill do?

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

Why use Instrumentation Planning on TypingMind?

Because you install it once and use it with any model. Instrumentation Planning is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Instrumentation Planning in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/nexus-labs-automation/mobile-observability/tree/main/skills/instrumentation-planning. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Instrumentation Planning?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Instrumentation Planning?

As many as you like. As long as a model supports skills, you can use Instrumentation Planning with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Instrumentation Planning AI skill free?

Yes. It is published on GitHub by nexus-labs-automation under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Brainstorming

obra

CommunityPopular

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Executing Plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Using Superpowers

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

Loop Me

Grill me about specs for the workflows I want to build, within this workspace.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Instrumentation Planning

Core Question

Priority Tiers

Implementation Order

Future-Proofing

Anti-Patterns

Implementation

Related Skills

Frequently asked questions

Related AI Skills

Set up your own AI workspace now