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.
86
82%
Does it follow best practices?
Impact
89%
1.18xAverage score across 3 eval scenarios
Passed
No known issues
Quality
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 domain (mobile app debugging), specifies platforms (iOS, Android, cross-platform), lists concrete problem types users would encounter, and includes specific tool names as 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 mentioned (Xcode, Android Profiler, React Native). Unlikely to conflict with general debugging or web development skills due to mobile-specific terminology. | 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, concise reference for mobile debugging across multiple platforms with good code examples and a useful checklist. However, it lacks depth in workflow guidance (no feedback loops for debugging processes) and some sections are too brief to be fully actionable. The single-file structure works but could benefit from progressive disclosure for this breadth of content.
Suggestions
Add explicit debugging workflows with validation steps, e.g., 'If Memory Graph shows retain cycle: 1. Identify the cycle, 2. Add weak reference, 3. Re-run Memory Graph to verify fix'
Expand incomplete guidance like 'Use Memory Graph Debugger' with specific steps or menu paths to make it fully actionable
Consider splitting platform-specific content into separate files (IOS_DEBUG.md, ANDROID_DEBUG.md, REACT_NATIVE_DEBUG.md) with SKILL.md as an overview
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient, providing only essential commands, code snippets, and checklists without explaining basic concepts Claude already knows. Every section delivers actionable information without padding. | 3 / 3 |
Actionability | Provides concrete code examples and commands, but some guidance is incomplete or surface-level (e.g., 'Use Memory Graph Debugger' without showing how, network interception snippet is partial). Mix of executable code and brief pointers. | 2 / 3 |
Workflow Clarity | The debug checklist provides a clear sequence, but there are no explicit validation checkpoints or feedback loops for debugging workflows. Steps like 'Profile with Instruments > Leaks' lack follow-up actions if issues are found. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is inline in one file. For a skill covering three platforms plus network debugging, some content could be split into separate files with clear references. | 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.
90d6bd7
Table of Contents
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.