CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/mobile-app-debugging/skills/mobile-app-debugging/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, well-organized reference of platform-specific debugging tips with a useful checklist and concrete performance targets. Its weaknesses are actionability — several code blocks are commented hints rather than executable instructions — and the absence of an explicit debugging workflow with validation/feedback checkpoints.

Suggestions

Convert commented hints into executable commands, e.g., show LLDB invocations as runnable lldb sessions ('lldb -p <pid>', 'breakpoint set --condition') instead of comment-style annotations.

Add a short ordered debugging workflow (reproduce → isolate via tool X → fix → verify on physical device) so the tips hang off an explicit sequence with checkpoints.

Turn the 60 FPS / memory / launch targets into validation steps in the workflow (e.g., 'measure with Perf Monitor; if > 16ms/frame, profile the JS thread') rather than a standalone table.

DimensionReasoningScore

Conciseness

The body is lean with no padding and no explanation of concepts Claude already knows; sections jump straight to commands, tool pointers, and targets. It matches the score-5 anchor — every token earns its place — with only trivial redundancy (60 FPS appears in the RN section, checklist, and performance table).

5 / 5

Actionability

Guidance is mixed: the XHR interception snippet and Logcat filtering are executable, but much of the 'code' is commented hints rather than runnable content ('// Right-click breakpoint > Edit > Condition: userId == "123"', '// Shake device > Debug JS Remotely', LLDB commands shown only as comments). This lands on the score-3 anchor — some concrete guidance but incomplete, pseudocode-like presentation.

3 / 5

Workflow Clarity

There is no sequenced debugging workflow (reproduce → isolate → fix → verify) and no feedback loops; the debug checklist provides some verification posture but checkpoints are implicit. The sections themselves are coherent and tool-specific, placing this above the incoherent score-2 anchor but squarely at score 3's 'sequence present but checkpoints missing'.

3 / 5

Progressive Disclosure

The skill is self-contained with no bundle files, short, and organized into clearly headed sections (iOS, Android, React Native, Network, Checklist, Performance Targets) with no nesting. Per the rubric's simple-skill guidance, a self-contained, well-sectioned skill with no need for external references earns a 5.

5 / 5

Total

16

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-constructed description with an explicit, concrete 'Use for' trigger clause and good natural-language keyword coverage. Its main weakness is thin action specificity — 'debugging' is the only verb, with coverage expressed through problem types rather than distinct capabilities.

Suggestions

Replace or augment the single verb 'debugging' with a few distinct concrete actions (e.g., 'diagnose crashes, profile memory, trace network requests') to raise action specificity.

Add commonly-used user phrasings as triggers, such as 'app freezing', 'ANR', or 'slow app', to round out keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain ('Mobile app debugging for iOS, Android, cross-platform frameworks') and enumerates problem types ('crashes, memory leaks, performance issues, network problems'), but offers only one concrete action — debugging — rather than several distinct actions. It exceeds the score-2 anchor (domain named, generic action) but lacks the multiple specific actions of the score-4 anchor.

3 / 5

Completeness

It explicitly answers both questions: what ('Mobile app debugging for iOS, Android, cross-platform frameworks') and when, via a concrete 'Use for crashes, memory leaks, performance issues, network problems...' clause with specific trigger phrases. Anti-drift check against the score-4 anchor ('when could be more explicit') confirms the when-clause is already explicit, so the score-5 anchor is the best fit.

5 / 5

Trigger Term Quality

Strong natural terms users would say ('crashes', 'memory leaks', 'performance issues', 'network problems') plus named tools ('Xcode instruments', 'Android Profiler', 'React Native debugger', 'native bridge errors'). A few common variations are missing ('app freezing', 'ANR', 'slow app', 'bug'), which keeps it below the comprehensive synonym coverage of the score-5 anchor.

4 / 5

Distinctiveness Conflict Risk

A clear mobile-specific niche anchored by platform tool names (Xcode instruments, Android Profiler, React Native debugger) gives distinct triggers. Minor overlap risk remains with general debugging or crash-triage skills, keeping it just below the score-5 anchor's 'minimal conflict risk'.

4 / 5

Total

16

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

secondsky/claude-skills

Path

plugins/mobile-app-debugging/skills/mobile-app-debugging/SKILL.md

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.