Openclaw Skills provides a structured frontend workflow for diagnosing and fixing mobile responsive layout, navbar, and cross-device UI issues.
The fastest way to install a skill directly from the registry.
npx clawhub@latest install mobile-responsive-layout-fixer-010622
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
Copy this prompt to OpenClaw to install it automatically.
Help me install mobile-responsive-layout-fixer-010622 using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Get the raw skill files in a ZIP archive.
Openclaw Skills for Mobile Responsive Layout Fixer helps frontend developers, designers, startup teams, and maintainers turn vague responsiveness problems into a repeatable remediation workflow. It is built for the kinds of issues that break usability on phones and desktops alike: cramped layouts, broken navigation, overflow, and inconsistent breakpoint behavior.
The skill emphasizes practical, local-first execution. It restates the user's goal, gathers only the missing constraints that materially change the result, generates the strongest implementation or analysis path, and validates the output against explicit success criteria. When source evidence or review criteria matter, it points to references/requirement-plan.md, making Openclaw Skills useful for both quick triage and deeper implementation support.
references/requirement-plan.md before finalizing the response.No package installation is required to use this skill in Openclaw Skills; you mainly need to add it to your skill library and provide the right context when invoking it.
mobile-responsive-layout-fixer to your Openclaw Skills workspace or agent skill registry.mkdir -p references
touch references/requirement-plan.md
references/requirement-plan.md with breakpoint notes, screenshots, source evidence, or acceptance criteria.The skill uses a lightweight, documentation-driven schema centered on the SKILL.md file and one optional reference artifact.
| Element | Location | Purpose | Notes |
|---|---|---|---|
| Skill metadata | SKILL.md frontmatter (name, description) |
Identifies the skill and the trigger intent | The description encodes validated demand and when to use the skill |
| Requirement block | ## Requirement |
Captures the core problem statement | Includes demand score, evidence count, and target audience |
| Workflow | ## Workflow |
Defines the execution lifecycle | Six-step process from framing to validation |
| Expected outputs | ## Expected Outputs |
Defines deliverables | Tailored answer, reusable checklist, verification note |
| Validation rules | ## Validation |
Quality gate for final output | Must be actionable, self-contained, and explicit about assumptions |
| Triggers | ## Triggers |
Matching taxonomy for invocation | creative-and-content, mobile responsive, responsive design, navbar, layout, frontend |
| Reference evidence | references/requirement-plan.md |
Optional supporting context | Used for source evidence, planning details, or review criteria |
references/requirement-plan.md for deeper planning context.Loading
A workflow helper that reviews other skills for usefulness, safety, overlap, and publish readiness before you install, keep, merge, rename, or publish them.

Design safe proactive agent workflows that detect recurring needs, suggest timely actions, and stay governed by approvals, cooldowns, and audit logs.

A pre-activation security gate that audits skill folders for risky code, secrets, permissions, and release blockers before you trust or publish them.

A workflow skill that converts failed runs, corrections, and audit findings into small, verified improvements without uncontrolled drift.

Openclaw Skills for turning vague errors into clear, actionable messages that explain what failed, why it failed, and what to do next.

A demand-backed workflow helper in Openclaw Skills that turns Weather-style requests into reliable, local-friendly artifacts, fixes, and decision aids.








































