mobile-app-debugging
Mobile app debugging for iOS, Android, cross-platform frameworks. Use for crashes, memory leaks, performance issues, network problems, or encountering Xcode instruments, Android Profiler, React Native debugger, native bridge errors.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill mobile-app-debugging86
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It clearly defines the scope (mobile debugging across iOS, Android, and cross-platform), lists specific problem types users would encounter, and includes platform-specific tool names that serve as excellent trigger terms. The 'Use for...' clause provides explicit guidance on when to select this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and problem types: 'crashes, memory leaks, performance issues, network problems' along with specific tools like 'Xcode instruments, Android Profiler, React Native debugger, native bridge errors'. | 3 / 3 |
Completeness | Clearly answers both what ('Mobile app debugging for iOS, Android, cross-platform frameworks') and when ('Use for crashes, memory leaks, performance issues, network problems, or encountering Xcode instruments...') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'iOS', 'Android', 'crashes', 'memory leaks', 'performance issues', 'network problems', 'Xcode instruments', 'Android Profiler', 'React Native debugger', 'native bridge errors' - all terms developers naturally use when seeking debugging help. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on mobile app debugging with platform-specific tools (Xcode, Android Profiler, React Native). The combination of mobile platforms and debugging-specific triggers makes it unlikely to conflict with general debugging or web development skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a solid quick-reference for mobile debugging across platforms with good conciseness and practical code snippets. However, it reads more as a reference card than a debugging workflow guide—it tells you what tools exist but doesn't fully guide you through systematic debugging processes with validation checkpoints.
Suggestions
Add explicit debugging workflows with validation steps, e.g., 'Profile memory > Identify leak > Fix > Re-profile to confirm resolution'
Make code examples more complete and executable—the XMLHttpRequest intercept needs the _url property to be set, and LLDB examples could show a complete debugging session
Consider splitting platform-specific content into separate files (IOS_DEBUG.md, ANDROID_DEBUG.md, REACT_NATIVE_DEBUG.md) with SKILL.md as an overview with links
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting only actionable debugging commands and techniques without explaining what mobile debugging is or how debuggers work. Every section delivers practical value without padding. | 3 / 3 |
Actionability | Provides concrete code snippets and commands, but some are incomplete or context-dependent (e.g., the XMLHttpRequest intercept is missing _url setup, LLDB commands lack context). The checklist is actionable but the code examples are more illustrative than copy-paste ready. | 2 / 3 |
Workflow Clarity | The debug checklist provides a clear sequence, but the debugging workflows themselves lack explicit validation steps or feedback loops. For example, memory debugging mentions tools but doesn't guide through a diagnose-fix-verify cycle. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections by platform, but everything is inline in one file. For a skill covering three platforms plus cross-platform frameworks, splitting detailed platform guides into separate files with links would improve navigation. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.