GitHub Actions
callstackincubator/agent-skills
GitHub Actions workflow patterns for React Native iOS simulator and Android emulator cloud builds with downloadable artifacts.
Agent skill
Crash Instrumentation
by nexus-labs-automation in nexus-labs-automation/mobile-observability
Set up crash instrumentation with actionable context. An agent skill from nexus-labs-automation/mobile-observability.
Install Crash Instrumentation
$ npx skills add nexus-labs-automation/mobile-observability --skill crash-instrumentation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nexus-labs-automation/mobile-observability crash-instrumentation --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/crash-instrumentation .claude/skills/crash-instrumentation && 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 "crash-instrumentation" agent skill from https://github.com/nexus-labs-automation/mobile-observability/tree/main/skills/crash-instrumentation into .claude/skills/crash-instrumentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crash-instrumentation", 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/crash-instrumentationType 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 crash-instrumentation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nexus-labs-automation/mobile-observability crash-instrumentation --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/crash-instrumentation .agents/skills/crash-instrumentation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "crash-instrumentation" agent skill from https://github.com/nexus-labs-automation/mobile-observability/tree/main/skills/crash-instrumentation into .agents/skills/crash-instrumentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crash-instrumentation", 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 crash-instrumentation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nexus-labs-automation/mobile-observability crash-instrumentation --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/crash-instrumentation .cursor/skills/crash-instrumentation && 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 "crash-instrumentation" agent skill from https://github.com/nexus-labs-automation/mobile-observability/tree/main/skills/crash-instrumentation into .cursor/skills/crash-instrumentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crash-instrumentation", 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/crash-instrumentation--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 crash-instrumentation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nexus-labs-automation/mobile-observability crash-instrumentation --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/crash-instrumentation .gemini/skills/crash-instrumentation && 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 "crash-instrumentation" agent skill from https://github.com/nexus-labs-automation/mobile-observability/tree/main/skills/crash-instrumentation into .gemini/skills/crash-instrumentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crash-instrumentation", 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 crash-instrumentationInstalls 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 crash-instrumentation -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/crash-instrumentation .github/skills/crash-instrumentation && 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 "crash-instrumentation" agent skill from https://github.com/nexus-labs-automation/mobile-observability/tree/main/skills/crash-instrumentation into .github/skills/crash-instrumentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crash-instrumentation", 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 crash-instrumentation -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 crash-instrumentation --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/crash-instrumentation .opencode/skills/crash-instrumentation && 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 "crash-instrumentation" agent skill from https://github.com/nexus-labs-automation/mobile-observability/tree/main/skills/crash-instrumentation into .opencode/skills/crash-instrumentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crash-instrumentation", 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
crash-instrumentation- GitHub stars
- 116
- Token cost
- ~744 tokens
- SKILL.md length
- 213 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- MIT
At a glance
Set up crash instrumentation with actionable context. An agent skill from nexus-labs-automation/mobile-observability.
- Configuring crash capture
- SKILL.md covers Core Principle, Breadcrumb Strategy, Error Boundaries and What NOT to Attach, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Error boundaries
What it does
Crash Instrumentation is an agent skill from nexus-labs-automation/mobile-observability. Set up crash instrumentation with actionable context. Use when configuring crash capture, error boundaries, or breadcrumb strategies.
Its SKILL.md is about 740 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 Error handling and Observability. It works with Android, iOS and React Native. 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
- Configuring crash capture
- Error boundaries
- Breadcrumb strategies
Example prompts
- “/crash-instrumentation”
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 (its code samples are swift and kotlin).
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
Crash Instrumentation loads about 744 tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 213 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). 213 words, ~744 tokens.
Download SKILL.mdSave it as
.claude/skills/crash-instrumentation/SKILL.md (or your agent's skills folder).- name
- crash-instrumentation
- description
- Set up crash instrumentation with actionable context. Use when configuring crash capture, error boundaries, or breadcrumb strategies.
- triggers
- breadcrumb strategy, capture crashes, crash context, crash reporting, debug crashes, error boundaries
- priority
- 1
Crash Instrumentation
Capture crashes with the context needed to debug them.
Core Principle
A crash report without context is useless. Every crash should include:
| Context | Why | Example |
|---|---|---|
screen | Where it happened | "CheckoutScreen" |
job_name | What user was doing | "checkout" |
job_step | Where in the flow | "payment" |
breadcrumbs | What led here | Last 20 user actions |
app_version | Release correlation | "1.2.3" |
user_segment | Who's affected | "premium", "trial" |
Breadcrumb Strategy
Breadcrumbs are the trail leading to a crash. Capture:
| Category | What to Log | Example |
|---|---|---|
navigation | Screen transitions | "HomeScreen → CartScreen" |
user | Taps, inputs, gestures | "Tapped checkout button" |
network | API calls (not payloads) | "POST /api/orders started" |
state | Key state changes | "Cart updated: 3 items" |
error | Non-fatal errors | "Retry #2 for payment" |
Limit: Keep last 20-50 breadcrumbs. More is noise.
Error Boundaries
Catch errors before they crash the app:
// iOS - capture context before crash
func captureError(_ error: Error, screen: String, job: String?) {
Observability.captureError(error, context: [
"screen": screen,
"job_name": job ?? "unknown",
"session_duration": sessionDuration(),
"memory_pressure": memoryPressure()
])
}// Android - uncaught exception handler
Thread.setDefaultUncaughtExceptionHandler { thread, throwable ->
Observability.captureError(throwable, mapOf(
"thread" to thread.name,
"screen" to currentScreen,
"job_name" to currentJob
))
previousHandler?.uncaughtException(thread, throwable)
}What NOT to Attach
| Don't | Why |
|---|---|
| Full stack traces in breadcrumbs | Redundant, SDK captures this |
| User input text | PII risk |
| Full request/response bodies | Size limits, PII |
| Entire app state | Unbounded, noise |
Crash Types to Handle
| Platform | Type | Instrumentation |
|---|---|---|
| iOS | EXC_BAD_ACCESS | Breadcrumbs, memory context |
| iOS | SIGKILL (watchdog) | Background task tracking |
| Android | ANR | Main thread breadcrumbs |
| Android | OutOfMemoryError | Memory tracking |
| React Native | JS exceptions | Error boundaries |
Implementation
See references/crash-reporting.md for:
- Platform-specific crash capture setup
- Breadcrumb implementation patterns
- Vendor SDK configuration
See skills/symbolication-setup for 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/crash-instrumentation of nexus-labs-automation/mobile-observability.
Open the folder on GitHubat commit 488c97f
Compare with similar skills
Crash Instrumentation 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 |
|---|---|---|---|---|---|---|
| Crash Instrumentation this skillnexus-labs-automation/mobile-observability | 116 | — | ~744 | Automated safety check: Pass | MIT | |
| GitHub Actionscallstackincubator/agent-skills | 1.7k | 1 repos | ~703 | Automated safety check: Pass | MIT | |
| DiagnoseCherryHQ/cherry-studio-app | 4k | — | ~1.8k | Automated safety check: Pass | AGPL-3.0 | |
| Code Guidelinesgetsentry/sentry-react-native | 1.8k | — | ~3.2k | Automated safety check: Pass | MIT | |
| Community Migrationjingjing2222/react-native-nitro-geolocation | 115 | — | ~3.5k | Automated safety check: Pass | MIT | |
| Diagnosing Stacktrace SymbolicationPostHog/posthog | 40k | — | ~2.2k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
Diagnose
CherryHQ/cherry-studio-app
Opt-in evidence-first causal diagnosis for bugs, browser or app/device failures, flaky behavior, and performance regressions.
- Official
Code Guidelines
getsentry/sentry-react-native
Enforce Sentry React Native SDK code guidelines for implementation, refactoring, and review.
Community Migration
jingjing2222/react-native-nitro-geolocation
Migrate React Native apps from @react-native-community/geolocation to react-native-nitro-geolocation.
- Official
Diagnosing Stacktrace Symbolication
PostHog/posthog
Help users debug PostHog Error Tracking stack-trace symbolication for any supported platform — JavaScript/TypeScript web, React Native (Hermes), Android (Proguard / R8), or iOS / macOS (dSYM).
Nitro Sound Workflows
hyochan/react-native-nitro-sound
A skill your agent uses for react-native-nitro-sound repository work that should follow the project workflows for PR review, code audit, knowledge compilation, full verification, iOS or Android…
More from nexus-labs-automation/mobile-observability
All 8 skills in this repoInstrumentation Planning
nexus-labs-automation/mobile-observability
Plan what to measure in mobile apps. 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
Works with
Categories
Questions about Crash Instrumentation
What does Crash Instrumentation do?
Set up crash instrumentation with actionable context. An agent skill from nexus-labs-automation/mobile-observability. Crash Instrumentation is an agent skill from nexus-labs-automation/mobile-observability. Set up crash instrumentation with actionable context.
When should I use Crash Instrumentation?
Crash Instrumentation fits situations like: configuring crash capture; error boundaries; breadcrumb strategies.
How do I install Crash Instrumentation in Claude Code?
Run `npx skills add nexus-labs-automation/mobile-observability --skill crash-instrumentation -a claude-code`. Or copy the skill folder (skills/crash-instrumentation in nexus-labs-automation/mobile-observability) into .claude/skills/crash-instrumentation in your project. Claude Code loads it when a task matches its description.
How do I install Crash Instrumentation in Codex?
Run `npx skills add nexus-labs-automation/mobile-observability --skill crash-instrumentation -a codex`. Or copy the skill folder (skills/crash-instrumentation in nexus-labs-automation/mobile-observability) into .agents/skills/crash-instrumentation in your project. Codex loads it when a task matches its description.
Can I use Crash Instrumentation 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 crash-instrumentation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/crash-instrumentation, .gemini/skills/crash-instrumentation, .github/skills/crash-instrumentation and .opencode/skills/crash-instrumentation in your project.
What does Crash Instrumentation need to run?
SKILL.md names no scripts, command-line tools or credentials: Crash Instrumentation is instructions for the agent only.
Does Crash Instrumentation 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 Crash Instrumentation 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 Crash Instrumentation use?
Crash Instrumentation 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 Crash Instrumentation use?
About 744 tokens (SKILL.md is roughly 3k 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 Crash Instrumentation?
Skills that share tags, products or a category with Crash Instrumentation: GitHub Actions (callstackincubator/agent-skills, 1.7k stars), Diagnose (CherryHQ/cherry-studio-app, 4k stars), Code Guidelines (getsentry/sentry-react-native, 1.8k stars) and Community Migration (jingjing2222/react-native-nitro-geolocation, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Crash Instrumentation?
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.