Vercel Optimize Audit
vercel-labs/agent-skills
Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.
Agent skill
Instrumentation Planning
by nexus-labs-automation in nexus-labs-automation/mobile-observability
Plan what to measure in mobile apps. An agent skill from nexus-labs-automation/mobile-observability.
Install Instrumentation Planning
$ npx skills add nexus-labs-automation/mobile-observability --skill instrumentation-planning -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nexus-labs-automation/mobile-observability instrumentation-planning --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/nexus-labs-automation/mobile-observability.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/instrumentation-planning .claude/skills/instrumentation-planning && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "instrumentation-planning" agent skill from https://github.com/nexus-labs-automation/mobile-observability/tree/main/skills/instrumentation-planning into .claude/skills/instrumentation-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "instrumentation-planning", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/nexus-labs-automation/mobile-observability/tree/main/skills/instrumentation-planningType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add nexus-labs-automation/mobile-observability --skill instrumentation-planning -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nexus-labs-automation/mobile-observability instrumentation-planning --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nexus-labs-automation/mobile-observability.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/instrumentation-planning .agents/skills/instrumentation-planning && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "instrumentation-planning" agent skill from https://github.com/nexus-labs-automation/mobile-observability/tree/main/skills/instrumentation-planning into .agents/skills/instrumentation-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "instrumentation-planning", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nexus-labs-automation/mobile-observability --skill instrumentation-planning -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nexus-labs-automation/mobile-observability instrumentation-planning --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nexus-labs-automation/mobile-observability.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/instrumentation-planning .cursor/skills/instrumentation-planning && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "instrumentation-planning" agent skill from https://github.com/nexus-labs-automation/mobile-observability/tree/main/skills/instrumentation-planning into .cursor/skills/instrumentation-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "instrumentation-planning", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/nexus-labs-automation/mobile-observability.git --path skills/instrumentation-planning--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add nexus-labs-automation/mobile-observability --skill instrumentation-planning -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nexus-labs-automation/mobile-observability instrumentation-planning --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nexus-labs-automation/mobile-observability.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/instrumentation-planning .gemini/skills/instrumentation-planning && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "instrumentation-planning" agent skill from https://github.com/nexus-labs-automation/mobile-observability/tree/main/skills/instrumentation-planning into .gemini/skills/instrumentation-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "instrumentation-planning", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install nexus-labs-automation/mobile-observability instrumentation-planningInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add nexus-labs-automation/mobile-observability --skill instrumentation-planning -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nexus-labs-automation/mobile-observability.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/instrumentation-planning .github/skills/instrumentation-planning && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "instrumentation-planning" agent skill from https://github.com/nexus-labs-automation/mobile-observability/tree/main/skills/instrumentation-planning into .github/skills/instrumentation-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "instrumentation-planning", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nexus-labs-automation/mobile-observability --skill instrumentation-planning -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nexus-labs-automation/mobile-observability instrumentation-planning --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nexus-labs-automation/mobile-observability.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/instrumentation-planning .opencode/skills/instrumentation-planning && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "instrumentation-planning" agent skill from https://github.com/nexus-labs-automation/mobile-observability/tree/main/skills/instrumentation-planning into .opencode/skills/instrumentation-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "instrumentation-planning", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
instrumentation-planning- GitHub stars
- 116
- Token cost
- ~517 tokens
- SKILL.md length
- 168 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- MIT
At a glance
Plan what to measure in mobile apps. An agent skill from nexus-labs-automation/mobile-observability.
- Starting observability
- SKILL.md covers Core Question, Priority Tiers, Implementation Order and Future-Proofing, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Prioritizing instrumentation
What it does
Instrumentation Planning is an agent skill from nexus-labs-automation/mobile-observability. Plan what to measure in mobile apps. Use when starting observability, prioritizing instrumentation, or asking "what should I track?"
Its SKILL.md is about 520 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Observability. The repository describes itself as: Claude Code plugin for mobile app observability: crash reporting, performance monitoring, and instrumentation for iOS, Android, and React Native. The licence is MIT.
When your agent uses it
- Starting observability
- Prioritizing instrumentation
- Asking what should I track?
Example prompts
- “what should I track?”
- “/instrumentation-planning”
What it can do on your machine
Read from SKILL.md and the folder at commit 488c97f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Instrumentation Planning loads about 517 tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 168 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from nexus-labs-automation/mobile-observability at commit 488c97f, republished under its MIT licence (© nexus-labs-automation). 168 words, ~517 tokens.
Download SKILL.mdSave it as
.claude/skills/instrumentation-planning/SKILL.md (or your agent's skills folder).- name
- instrumentation-planning
- description
- Plan what to measure in mobile apps. Use when starting observability, prioritizing instrumentation, or asking "what should I track?"
- triggers
- planning telemetry, prioritize instrumentation, start observability, what should I track, what to measure, where to begin
- priority
- 1
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 metricsFuture-Proofing
Use OTel-compatible span/attribute names now (zero cost, easier migration later):
http.request.methodnotmethodui.screen.loadnotscreenLoadapp.start.coldnotcoldStart
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-trackingfor implementing JTBD instrumentation - See
skills/crash-instrumentationfor Tier 1 (crashes) - See
skills/symbolication-setupfor Tier 1 (readable stack traces)
© nexus-labs-automation, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/instrumentation-planning of nexus-labs-automation/mobile-observability.
Open the folder on GitHubat commit 488c97f
Compare with similar skills
Instrumentation Planning next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Instrumentation Planning this skillnexus-labs-automation/mobile-observability | 116 | — | ~517 | Automated safety check: Pass | MIT | |
| Vercel Optimize Auditvercel-labs/agent-skills | 32k | 8 repos | ~4.3k | Automated safety check: Pass | None | |
| Kubeshark Installerkubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Notes | Apache-2.0 | |
| Kubeshark KFL2 Filter Referencekubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Pass | Apache-2.0 | |
| KubeSphere ServiceMesh Managerkubesphere/kubesphere | 17k | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Kubernetes Network Root Cause Analysiskubeshark/kubeshark | 12k | — | ~5.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Kubeshark Installer
kubeshark/kubeshark
Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.
Kubeshark KFL2 Filter Reference
kubeshark/kubeshark
Syntax reference for KFL2, the CEL-based display filter language used to search Kubernetes network traffic captured by Kubeshark, loaded before any filter is written.
KubeSphere ServiceMesh Manager
kubesphere/kubesphere
Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.
Kubernetes Network Root Cause Analysis
kubeshark/kubeshark
Investigates past Kubernetes incidents from Kubeshark traffic snapshots: takes captures, dissects API calls, extracts PCAPs and compares traffic over time.
Caveman Gateway Setup
JuliusBrussee/caveman
Routes every LLM call in a repository through the Caveman Cloud gateway in record mode, so requests and costs are measured without changing behavior.
More from nexus-labs-automation/mobile-observability
All 8 skills in this repoCrash Instrumentation
nexus-labs-automation/mobile-observability
Set up crash instrumentation with actionable context. An agent skill from nexus-labs-automation/mobile-observability.
Network Tracing
nexus-labs-automation/mobile-observability
Instrument API requests with spans and distributed tracing. An agent skill from nexus-labs-automation/mobile-observability.
Symbolication Setup
nexus-labs-automation/mobile-observability
Configure crash symbolication for readable stack traces. An agent skill from nexus-labs-automation/mobile-observability.
Interaction Latency
nexus-labs-automation/mobile-observability
Measure time from user tap to action completion. An agent skill from nexus-labs-automation/mobile-observability.
Navigation Latency
nexus-labs-automation/mobile-observability
Measure time from navigation tap to screen fully loaded and interactive.
User Journey Tracking
nexus-labs-automation/mobile-observability
Track user journeys with intent context and friction signals.
Related
Categories
Questions about Instrumentation Planning
What does Instrumentation Planning do?
Plan what to measure in mobile apps. An agent skill from nexus-labs-automation/mobile-observability. Instrumentation Planning is an agent skill from nexus-labs-automation/mobile-observability. Plan what to measure in mobile apps.
When should I use Instrumentation Planning?
Instrumentation Planning fits situations like: starting observability; prioritizing instrumentation; asking what should I track?.
How do I install Instrumentation Planning in Claude Code?
Run `npx skills add nexus-labs-automation/mobile-observability --skill instrumentation-planning -a claude-code`. Or copy the skill folder (skills/instrumentation-planning in nexus-labs-automation/mobile-observability) into .claude/skills/instrumentation-planning in your project. Claude Code loads it when a task matches its description.
How do I install Instrumentation Planning in Codex?
Run `npx skills add nexus-labs-automation/mobile-observability --skill instrumentation-planning -a codex`. Or copy the skill folder (skills/instrumentation-planning in nexus-labs-automation/mobile-observability) into .agents/skills/instrumentation-planning in your project. Codex loads it when a task matches its description.
Can I use Instrumentation Planning in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nexus-labs-automation/mobile-observability --skill instrumentation-planning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/instrumentation-planning, .gemini/skills/instrumentation-planning, .github/skills/instrumentation-planning and .opencode/skills/instrumentation-planning in your project.
What does Instrumentation Planning need to run?
SKILL.md names no scripts, command-line tools or credentials: Instrumentation Planning is instructions for the agent only.
Does Instrumentation Planning access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Instrumentation Planning safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Instrumentation Planning use?
Instrumentation Planning is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Instrumentation Planning use?
About 517 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Instrumentation Planning?
Skills that share tags, products or a category with Instrumentation Planning: Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars), Kubeshark Installer (kubeshark/kubeshark, 12k stars), Kubeshark KFL2 Filter Reference (kubeshark/kubeshark, 12k stars) and KubeSphere ServiceMesh Manager (kubesphere/kubesphere, 17k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Instrumentation Planning?
nexus-labs-automation (a GitHub organization) maintains it in nexus-labs-automation/mobile-observability, which has 116 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on August 23, 2026.
Source: nexus-labs-automation/mobile-observability on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.