mobile-optimization — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited mobile-optimization (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Audit the page for mobile-friendliness.
| Check | Status |
|---|---|
Missing <meta name="viewport"> | ❌ FAIL "Page will not render correctly on mobile" |
Present but missing width=device-width | ⚠️ WARN |
Contains user-scalable=no or maximum-scale=1 | ⚠️ WARN "Disabling zoom hurts accessibility" |
| Properly configured | ✅ PASS |
Scan all elements with inline style="..." for width: Npx:
width > 500px → ⚠️ WARN "May cause horizontal scrolling on mobile"Scan inline styles for font-size: Npx:
font-size < 12px → ⚠️ WARN "Difficult to read on mobile"Check interactive elements (<a>, <button>, <input type="submit">, <input type="button">) with inline height style:
height < 48px → ⚠️ WARN "Too small for touch targets"overflow-x: hidden or overflow: hidden → ⚠️ WARN "Verify content is not clipped on mobile"<link rel="stylesheet" media="..."> found → ✅ PASS "Media-query-specific stylesheets found"<table> elements → ⚠️ WARN "Tables can be difficult to read on mobile. Consider responsive table patterns"display: none or visibility: hidden should be excluded from touch target checksuser-scalable=no — flag as ⚠️ WARN but note context~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.