agentsclimarketplace

Openclaw design audit

Skill openclaw/carapace/openclaw-design-audit

Canonical web design tokens, styles, and agent guidance for OpenClaw

Install
npx -y skills add openclaw/carapace --skill openclaw-design-audit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 28 days oldThe repository was created 28 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Audit OpenClaw frontend code and rendered interfaces for Carapace drift, token misuse, primitive reimplementation, accessibility problems, responsive defects, and off-brand copy. Use for design reviews, compliance checks, or scheduled audit-and-fix workflows.

SKILL.md

1.9 KB, as published. Nobody here has run it

OpenClaw Design Audit

Separate mechanical violations from judgment. Report suggestions as suggestions unless a documented rule makes them violations.

Workflow

  1. Read rubric.md and run every applicable category.
  2. Read the consumer's installed Carapace version and current commit SHA.
  3. Read the version-matched token contract and consumer adapters from the installed product guidance skill: openclaw-carapace for new installs or the openclaw-design-system compatibility alias for an upgraded lock.
  4. Read the brand or marketing references when those categories apply.
  5. Run deterministic source checks before judgment-based review.
  6. Inspect representative rendered routes at desktop and mobile sizes.
  7. Check light and dark themes where supported.
  8. Emit the JSON and Markdown defined in report-format.md.
  9. When asked to fix findings, apply only narrow changes allowed by fix-policy.md.
  10. For scheduled ClawHub delivery, follow github-pr-delivery.md.

Evidence

Each finding must include:

  • file and line
  • category and severity
  • stable rule ID
  • concise remediation
  • Carapace reference
  • whether the finding is mechanical or judgment-based

Curation

  • Include every error.
  • Rank warnings before informational findings, then by affected-file count.
  • Surface at most five non-error findings in the concise report.
  • Summarize remaining non-error findings by count.
  • Treat zero errors, zero warnings, and five or fewer informational findings as no significant drift.
  • Never invent source locations or visual evidence.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.