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.
75
68%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/mobile-app-debugging/skills/mobile-app-debugging/SKILL.mdQuality
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 strong skill description that concisely covers the what (mobile app debugging across platforms) and when (specific problem types and tools). It uses third person voice, includes highly relevant trigger terms that developers would naturally use, and carves out a clear niche distinct from general debugging skills. The description is well-structured and avoids unnecessary verbosity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions/domains: crashes, memory leaks, performance issues, network problems, and names specific tools like Xcode instruments, Android Profiler, React Native debugger, and 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, Android Profiler, React Native debugger, native bridge errors') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'crashes', 'memory leaks', 'performance issues', 'network problems', 'Xcode instruments', 'Android Profiler', 'React Native debugger', 'native bridge errors', 'iOS', 'Android'. These are all terms a developer would naturally use when seeking debugging help. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to mobile app debugging specifically, with distinct triggers like 'Xcode instruments', 'Android Profiler', 'React Native debugger', and 'native bridge errors' that are unlikely to conflict with general debugging or web development skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a broad but shallow reference across multiple mobile platforms. It lacks structured debugging workflows with decision points and validation steps, which is critical for a debugging skill. The content mixes trivially known patterns (console.log, basic logging) with some useful but incomplete guidance, and would benefit from deeper platform-specific files and a clear diagnostic process.
Suggestions
Add a structured debugging workflow with decision tree: e.g., 'Crash? → Check stack trace → If memory-related, use Memory Profiler → If thread-related, check for deadlocks' with explicit validation at each step.
Split platform-specific content into separate files (IOS_DEBUG.md, ANDROID_DEBUG.md, REACT_NATIVE_DEBUG.md) and keep SKILL.md as a concise overview with navigation links.
Remove trivially known patterns (console.log, Log.d/Log.e basics) and replace with non-obvious debugging techniques, tool-specific flags, or common pitfalls that Claude wouldn't already know.
Add concrete examples of diagnosing specific failure modes (e.g., a retain cycle example with fix, an ANR diagnosis with actual profiler output interpretation).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some things Claude already knows (e.g., basic console.log usage, Log.d/Log.e patterns, what ANR and OOM stand for). The XMLHttpRequest interception monkey-patch is a known pattern. Some sections could be tightened. | 2 / 3 |
Actionability | Provides some concrete code snippets and commands, but many are basic/trivial (console.log, Log.d). The iOS section gives LLDB commands which are useful, but the Memory Debugging and Android sections are more descriptive bullet points than executable guidance. The network debugging snippet is concrete but incomplete (missing _url setup). | 2 / 3 |
Workflow Clarity | There is no clear multi-step debugging workflow or sequence. The content is organized as reference lists and snippets but lacks a structured process for diagnosing issues (e.g., 'start here, then check X, if Y then do Z'). The checklist at the end is a testing checklist, not a debugging workflow with validation checkpoints. | 1 / 3 |
Progressive Disclosure | Content is organized into clear sections by platform which aids navigation, but everything is inline in a single file with no references to deeper resources. For a skill covering iOS, Android, and React Native debugging, the breadth warrants splitting into separate files for each platform with this file as an overview. | 2 / 3 |
Total | 7 / 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.
- Repository
- secondsky/claude-skills
- Commit
88da5ff
- 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.