CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mobile-testing

Use when reviewing CI coverage, automated checks, or test strategy related to Test on real mobile devices and viewports. Focus on whether the rule is continuously verified, not just documented.

Quality

70%

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 ./skills/mobile-testing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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.

The body is a well-organized overview that correctly delegates implementation and code to a single clearly-signaled reference file, but it opens with a motivational paragraph duplicated verbatim from the reference and surfaces no validation/verification steps in the main body. Actionable specifics like named breakpoints, tools, and device priorities keep the guidance concrete despite having no inline code.

Suggestions

Trim or cut the opening 'why it matters' paragraph — it duplicates references/rule.md's 'Why It Matters' verbatim and explains motivation Claude already knows.

Surface a validation step in the Fix section from the reference's Verification guidance, e.g. 'Run the Playwright mobile project locally and confirm it fails when the rule is violated.'

Add a one-line pointer to the reference's Verification section (e.g. 'See references/rule.md → Verification for the confirm-it-fails checklist') so the review workflow includes a checkpoint without inlining it.

DimensionReasoningScore

Conciseness

The intro paragraph ('More than 55% of global web traffic comes from mobile devices... only appear on real devices') explains motivation Claude already knows and duplicates references/rule.md's 'Why It Matters' section verbatim, while the Quick Reference, Check/Fix/Explain/Code Review sections are tight and directive. Not 4 because that paragraph is a noticeable share of a ~30-line body; not 2 because everything else is lean with no other padding.

3 / 5

Actionability

Concrete, executable direction is given: 'Check for Playwright device emulation, mobile viewport tests', 'Add Playwright tests using mobile device presets', '375px (iPhone SE), 390px (iPhone 14), 768px (iPad)', 'Use BrowserStack or similar services', with full code promised and delivered in references/rule.md. Not 5 because the body itself contains no code or commands and defers all executable detail to the reference; not 3 because named tools, breakpoints, and services make the guidance directly actionable for an instruction-only skill.

4 / 5

Workflow Clarity

The 'Check → Fix → Explain → Code Review' sections form a coherent, purpose-labeled sequence, but no validation checkpoints appear in the body — the verification steps ('confirm it fails when the rule is violated', 'automation blocks regressions') exist only in references/rule.md and are never surfaced. Not 4 because checkpoints are absent rather than a minor gap; not 2 because the section sequence is clear and each step is well defined for a non-destructive review task.

3 / 5

Progressive Disclosure

The body is a ~30-line overview with clear sections and a single well-signaled, one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md') that exists and contains exactly that content, including complete Playwright config and test code. Not 4 because the split between overview and detail is appropriate and navigation is trivial; the duplicated intro paragraph is penalized under conciseness rather than structure.

5 / 5

Total

15

/

20

Passed

Description

62%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.

The description has an explicit, concrete 'Use when...' trigger and a clearly distinct mobile-testing niche, but its capability statement is thin and it misses natural synonyms like 'mobile testing', 'responsive', or 'device emulation'. The generic verification-focused trigger clause also risks overlap with sibling rule skills that share the same template.

Suggestions

Add a concrete 'what' clause naming the skill's capabilities, e.g. 'Checks for mobile test configurations, adds Playwright tests with mobile device presets, and reviews CI enforcement of mobile viewports.'

Include common natural synonyms users would say: 'mobile testing', 'responsive', 'device emulation', 'cross-browser'.

Make the trigger clause more specific to this rule (e.g. 'real device and viewport test coverage') so it cannot fire for sibling CI-verification rule skills.

DimensionReasoningScore

Specificity

The description names the domain ('Test on real mobile devices and viewports') and 1-2 concrete actions ('reviewing CI coverage, automated checks, or test strategy', 'Focus on whether the rule is continuously verified'), but never states the skill's actual capabilities (checking for mobile test configs, adding Playwright device-preset tests, reviewing CI enforcement). Not 2 because concrete review actions and their objects are named; not 4 because the action coverage is thin and framed almost entirely as a trigger.

3 / 5

Completeness

The 'when' is explicit and concrete ('Use when reviewing CI coverage, automated checks, or test strategy related to Test on real mobile devices and viewports'), and a 'what' is stated ('Focus on whether the rule is continuously verified, not just documented'), though it is a single thin directive rather than a capability list. Not 5 because the 'what' lacks concrete capability statements; not 3 because 'when' is explicit, not merely implied.

4 / 5

Trigger Term Quality

Natural keywords are present — 'CI coverage', 'automated checks', 'test strategy', 'mobile devices', 'viewports' — but common variations users would actually say are missing: 'mobile testing', 'responsive', 'device emulation', 'cross-browser'. Not 4 because several natural synonyms are absent; not 2 because multiple relevant natural keywords appear.

3 / 5

Distinctiveness Conflict Risk

The niche 'Test on real mobile devices and viewports' is distinct, but the generic template trigger 'reviewing CI coverage, automated checks, or test strategy... whether the rule is continuously verified' would equally match sibling frontend-checklist rule skills, creating minor overlap risk with closely related testing skills. Not 5 because of that template overlap; not 3 because the mobile device/viewport scope is specific enough to distinguish it from unrelated skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/mobile-testing/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.