Token导航 LogoToken导航

Agent Skill · 研究检索

mobile-ux-audit(移动用户体验审计)

用于辅助界面设计、视觉规范、排版、配色、布局和交互体验优化。它适合让 Agent 根据产品场景整理页面结构、生成 UI 方案、检查视觉一致性或改进组件层级。使用时需要结合现有品牌、设计系统和用户任务,不应只堆装饰元素;涉及真实页面改动时,应通过截图或浏览器预览检查文本溢出、对齐和响应式表现。

mobile-ux-audit 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 26,764。

总安装 3,504周安装 149GitHub Stars 公开资料未说明下载 1,228核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.1.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:mobile-ux-audit(移动用户体验审计)
来源仓库:https://github.com/leooooooow/mobile-ux-audit
安装命令:
openclaw skills install mobile-ux-audit
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install mobile-ux-audit

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于评估移动购物体验中的用户摩擦点,涵盖加载速度、交互设计和结账流程。适合电商产品优化移动端界面与操作流程时使用。mobile-ux-audit 属于研究检索类 Skill,可作为该场景下的辅助能力补充。分析页面结构、识别触控热区并检查视觉一致性。涉及真实页面修改时需通过预览确认文本溢出和对齐效果。

应结合品牌规范与设计系统输出可落地的改进建议。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install mobile-ux-audit;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

mobile-ux-audit 怎么安装?

在终端执行 openclaw skills install mobile-ux-audit。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

mobile-ux-audit 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

mobile-ux-audit 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

mobile-ux-audit 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

mobile-ux-audit 用的人多吗?

公开数据是累计安装 3,504 次,近一周安装 149 次,下载 1,228 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

mobile-ux-audit 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
mobile-ux-audit

移动用户体验审计 · 本页

3,504—需要联网MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
mobile-ux-audit
description
Audit the mobile shopping experience of an ecommerce store for friction points including page load speed, thumb-reach interactions, form length, checkout flow, and pay-method breadth. Use when mobile conversion rate is lagging desktop, before a major redesign, or quarterly as a hygiene pass.

Mobile UX Audit

Mobile is usually 65–80% of ecommerce traffic and ~50% of revenue. The gap between traffic share and revenue share is the audit's job: find the thumb-reach errors, the slow hero images, the checkout fields that kill the sale.

Quick Reference

DecisionStrongAcceptableWeak
LCP (Largest Contentful Paint)≤2.0s on 4G2.0–2.5s>2.5s
INP (Interaction to Next Paint)≤150ms150–300ms>300ms
CLS (Cumulative Layout Shift)≤0.05≤0.1>0.1
Tap targets≥44×44pt with ≥8pt spacing40pt with tight spacing<40pt, close together
Checkout fields≤8 fields, one-page10–12 fields, 2 pages15+ fields, 3+ pages
Pay methodsApple Pay, Google Pay, card, 1 localCard + PayPalCard only
Guest checkoutDefault, no account requiredAccount optional after checkoutForced account creation

Problems this skill solves

  1. Conversion rate 40% lower on mobile than desktop with no clear diagnosis.
  2. Cart abandonment spiking at the address-entry step — usually a mobile-keyboard/autofill problem.
  3. PDP hero image taking 4+ seconds to load because the team uses the same 3000px-wide asset as desktop.
  4. Checkout buttons in the top third of the screen requiring an awkward thumb stretch.
  5. Apple Pay / Google Pay not enabled on a store where 70% of users are on iOS or Android.
  6. Modals and popups that cover the close button on small screens.
  7. Tap targets smaller than the thumb pad, producing fat-finger errors on filters and quantity steppers.

Workflow

Step 1 — Measure Core Web Vitals in the field

Pull the last 28 days of real-user metrics from PageSpeed Insights (CrUX), Google Search Console, or your RUM tool (Datadog, New Relic, Sentry, or Shopify's built-in). Record p75 LCP, INP, CLS for mobile. Compare to the Quick Reference table. Lab-test tools (Lighthouse) give consistent scores but do not reflect real users — always lead with field data.

Step 2 — Walk the funnel on a real device

Not an emulator, not Chrome DevTools device mode. Use an actual iPhone and an actual mid-range Android (Pixel 6a or similar — not the latest flagship). Walk: home → category → PDP → add to cart → cart → checkout → payment. Note every friction: slow load, mis-sized tap target, layout shift, confusing state, keyboard-covers-field moment.

Step 3 — Audit thumb reach

The comfortable thumb zone on a 6-inch phone is the bottom two-thirds of the screen. Anything in the top third (headers, close buttons, primary CTAs) requires a reach or a hand shift. Map every primary CTA on the funnel and flag anything above the middle.

Step 4 — Audit form fields

List every field in the checkout. Score each: required or optional, keyboard type (email, tel, numeric), autocomplete attribute, inline validation. Target ≤8 required fields total. Common kill-fields: "confirm password," "phone number for delivery updates," "how did you hear about us."

Step 5 — Audit the payment step

List enabled pay methods. For every market the store serves:

  • Apple Pay enabled with domain verification? Required for iOS conversion.
  • Google Pay enabled? Required for Android conversion.
  • One local method per region (iDEAL in NL, Bancontact in BE, Klarna / Afterpay for installments, SEPA in EU, Pix in BR, UPI in IN).
  • Card fields with proper keyboard (numeric, cardtype icons, CVV as numeric).
  • 3DS flow is not full-page redirect (use inline 3DS).

Step 6 — Image and asset audit

  • Hero images: served as WebP or AVIF, responsive srcset, ≤200KB at mobile breakpoint.
  • Below-fold images: lazy-loaded.
  • Fonts: WOFF2, subset to used characters, preloaded for critical text.
  • No layout shift from image or ad loads (width and height attributes or aspect-ratio boxes).
  • Video: don't autoplay. If used, poster image first, lazy-load the <video> element.

Step 7 — Document findings with priority

Produce a ranked list: P0 (blocks checkout), P1 (measurably hurts conversion), P2 (polish). Each item gets the friction described, the screen(s) affected, and a concrete fix.

Example 1 — Shopify store, 62% mobile traffic, 28% mobile conversion rate vs. desktop

Findings from a 2-hour audit:

  • P0: Apple Pay not enabled despite 58% of mobile users on iOS. Domain unverified in Apple Pay portal. Estimated impact: +8–12% mobile checkout completion.
  • P0: Checkout has 14 fields including optional company name, phone "for delivery," and a captcha that fails 30% of the time on mobile. Impact: +5–8% checkout completion from field reduction.
  • P1: Hero image is a 4000px JPEG at 1.2MB. Re-export at 1200px WebP (~120KB). LCP drops from 3.8s to 1.9s.
  • P1: Add-to-cart button top-right of PDP on mobile, requiring thumb reach. Move to sticky-bottom.
  • P1: Filter modal on category page covers the close-X behind the OS status bar on iPhone. Add 44pt top padding.
  • P2: "Suggested for you" section loads below the hero with a 300ms layout shift (CLS 0.18). Reserve space.
  • P2: Login prompt appears after 15 seconds on every page. Reduce to once-per-session.

Estimated combined lift: 20–30% on mobile conversion over 4–6 weeks after deployment.

Example 2 — Headless store (Next.js + commerce API), strong desktop, poor mobile INP

The team already optimizes LCP and CLS and has green Core Web Vitals on desktop. Mobile INP is 420ms — users tap and nothing happens for nearly half a second.

  • P0: Main-thread blocked by an analytics bundle firing synchronously on every route change. Move to a web worker or defer 2 seconds after route settle. Expected INP drop: 420ms → 180ms.
  • P0: The "add to cart" handler calls three tracking scripts synchronously before showing the cart drawer. Fire tracking async, show drawer immediately. Expected: drawer opens in <100ms instead of 600ms.
  • P1: Image carousel on PDP uses a heavy library (40KB) that blocks interaction. Swap for CSS-scroll-snap approach, 2KB, same UX.
  • P1: Variant selector re-renders the entire PDP on each change. Memoize properly or split into a sibling component.
  • P2: Service worker caches stale HTML for 24h, so bug fixes don't reach users fast. Reduce TTL to 1h and add a "fresh version available" toast.

Strong teams still have mobile-INP debt. The fix is usually "less JavaScript on tap," not "smaller hero image."

Common mistakes

  1. Auditing only on the latest iPhone. A mid-range Android at 4G is the real median user.
  2. Using Lighthouse as the only signal. Lab scores miss cold-start jank and main-thread contention.
  3. Treating mobile as "desktop minus width." The thumb pattern, keyboard behavior, and attention span are fundamentally different.
  4. Fixing LCP with a CDN and declaring victory. LCP is three factors: server response, render-blocking resources, and hero-asset size. The CDN only touches one.
  5. Forcing account creation before checkout. This is a 20%+ conversion hit on cold traffic.
  6. Modals with no visible close button on 4-inch screens. Test on a small device; buttons crop out.
  7. Infinite-scroll product listing without pagination cues. Users feel lost and leave.
  8. Autoplay video on mobile. Eats data, battery, and autoplay policies often block it anyway.
  9. Sticky headers that eat 20% of vertical real estate. On a phone, every pixel counts.
  10. Not testing with JavaScript disabled. Many mobile users have flaky JS loading; a site that only works with full JS is broken for them.

Resources

  • references/output-template.md — Audit report template with P0/P1/P2 structure.
  • references/core-web-vitals.md — How to measure and interpret LCP, INP, CLS in the field.
  • references/checkout-checklist.md — Mobile checkout audit checklist with field-by-field notes.
  • references/thumb-zones.md — Thumb-reach diagrams and interaction patterns.
  • assets/mobile-audit-checklist.md — Full pre-publish audit checklist.

平台分布

OpenClaw

76.14%
按下载量换算935

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills