Evaluate a web page or task flow against evidence-based conversion and usability criteria, then rank the fixes most likely to return value.
Install & Download
1. ClawHub CLI
The fastest way to install a skill directly from the registry.
npx clawhub@latest install ui-roi-audit
2. Manual Installation
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
3. Prompt Installation
Copy this prompt to OpenClaw to install it automatically.
Help me install ui-roi-audit using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Prefer to download?
Get the raw skill files in a ZIP archive.
What is UI ROI Audit?
UI ROI Audit helps teams assess landing pages, product pages, forms, checkout flows, and task-driven interfaces according to whether they move people toward a defined business or user goal. Instead of relying on taste, it scores applicable criteria with page evidence and separates sourced findings from the auditor’s own observations.
The workflow turns an interface review into an actionable, prioritized report. It ranks gaps by exposure, severity, and effort, and estimates potential conversion value or avoided task costs when the necessary data is available. Openclaw Skills users can run the audit without external dependencies; screenshots and browser access are helpful but optional.
UI ROI Audit Use Cases
- Investigate why a landing page, product page, form, or checkout is not converting.
- Prioritize interface improvements using funnel drop-off, exposure, severity, and implementation effort.
- Assess a single task-driven screen or flow with an observable success condition.
- Justify a proposed design investment with conservative, assumption-based ROI ranges.
- Review usability and estimate time, support, training, or rework costs that a fix could avoid.
- Produce a source-cited audit that distinguishes criterion-based findings from uncited observations.
How UI ROI Audit Works
- Frame the audit: Identify the target, interface type, audience, success goal, relevant traffic source, available metrics, and observed viewport. Audit one page, screen, or flow per run.
- Inventory the experience: Record content, actions, navigation, inputs, feedback, errors, recovery paths, and observable states. For conversion pages, also capture the value proposition, imagery, price, and trust signals. Mark unavailable states as not observed.
- Select and score criteria: Load the relevant page-type and content criteria for conversion pages. Score each applicable item Pass, Partial, Fail, or N/A, and attach page evidence to every Partial or Fail. For a task-only interface, skip conversion-content scoring.
- Assess usability when applicable: Load the usability module for task-driven interfaces or when usability review is requested. Keep usability findings separate from conversion-content findings when both apply.
- Prioritize and estimate: Rate gaps by exposure, severity, and effort, then rank the most consequential, low-effort fixes. Estimate conversion value or avoided task costs only when inputs support it; otherwise report a qualitative assessment and name missing data.
- Deliver the report: Follow the report contract for output structure, citations, failure handling, and final checks.
UI ROI Audit Setup
The skill runs without external dependencies. Provide the required audit inputs before starting:
- A target URL, screenshot, pasted content, or task flow.
- The interface type: landing, home, category, detail/product, form, checkout, or task-driven.
- One success goal, such as purchase, lead, signup, call, completed task, time saved, or cost avoided.
- For a landing page, the ad or link that sends visitors to it.
- Optional metrics: monthly visits, conversion rate, average order or lead value, implementation cost, and funnel drop-off.
Ask for missing target, type, or goal information before auditing. If optional metrics are unavailable, continue qualitatively and do not invent numbers. Load only the supporting references needed for the audit:
| Need | Reference |
|---|---|
| Conversion page criteria | references/page-type-criteria.md — load only the relevant page-type section |
| Embedded form or checkout | Also load the matching form or checkout section |
| Content and trust review | references/content-and-trust-criteria.md |
| ROI estimate or value assessment | references/roi-model.md |
| Task usability review | references/usability-roi-module.md |
| Before using a statistic or benchmark | references/source-limitations.md |
| Final report requirements | references/report-contract.md |
| Example report format | examples/sample-audit.md |
| Bibliography and reuse guidance | ATTRIBUTION.md |
No CLI installation or configuration command is specified in the skill.
UI ROI Audit Data Schema & Taxonomy
The skill describes an audit report structure rather than a generated-file or machine-readable data format. Organize findings into these sections:
| Section | Contents |
|---|---|
| Audit frame | Target, type, goal, audience/users, relevant traffic source, available data, and observed viewport |
| Content inventory | Ordered page or flow elements, actions, inputs, feedback, errors, recovery, and observation limits |
| Conversion criteria | Applicable criterion IDs, Pass/Partial/Fail/N/A scores, and page evidence for every Partial or Fail |
| Usability findings | A separate scored table when the usability module is run |
| Priorities | Ranked top three findings with exposure, severity, effort, and ROI range or qualitative status |
| Sources and limitations | Criterion citations, assumptions, unavailable states, and missing inputs |
Supporting knowledge is organized in references/, with the sample report in examples/sample-audit.md and bibliography and reuse notes in ATTRIBUTION.md. Mark unobserved states explicitly; do not score them as failures. Keep auditor observations distinct from sourced findings, and exclude uncited observations from the ranked recommendations.
UI ROI Audit Advanced Features
- Modular reference loading: Load only the criteria and report resources relevant to the page type, embedded form or checkout, content-and-trust review, ROI question, or usability scope.
- Separate conversion and usability assessments: Keep findings from the two modules distinct when both apply.
- Evidence and citation discipline: Attach criterion IDs and page evidence to sourced findings; label other observations as the auditor’s own and keep them out of the ranking.
- Conservative ROI reasoning: Use explicit assumptions and ranges, never promise uplift, and switch to a qualitative assessment when required data is missing.
- Funnel-aware prioritization: Focus on where money or task success is lost, ranking gaps using exposure, severity, and effort rather than page prestige.
- Observation-limit handling: Record viewport and unavailable states so unobserved mobile, error, or post-submit behavior is not misrepresented as a failure.
- Defined scope and handoff: Audit one page, screen, or flow per run; leave replacement copy to a content-design workflow.
SKILL.md
Loading
Related Openclaw Skills
Line Length Optimizer
Check whether body text has a readable line length and get a concrete, responsive CSS width recommendation.
Microtypography
A precise, non-rewriting typesetting pass that improves text for publication while explaining every change.
Posterly Social Publishing
Posterly lets an AI agent manage social publishing through hosted MCP, from account discovery and post validation to confirmed scheduling and publishing.
Glyph Fidelity
Glyph Fidelity audits transformed text and typography edge cases to help preserve readable, consistent letterforms.
Zitieku Handwriting Practice Assistant
Turn a learner’s handwriting goals into a practical practice plan and a link to an editable, printable Chinese handwriting worksheet.
Alibaba Cloud OSS Endpoint & Internal Network Diagnosis
Find out which Alibaba Cloud OSS endpoint matches your bucket and why endpoint, internal-network, or custom-domain access is failing.
Featured*
