agentsclimarketplace

Openclaw brand

Skill openclaw/carapace/openclaw-brand

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

Install
npx -y skills add openclaw/carapace --skill openclaw-brand

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

Apply OpenClaw visual identity to logos, typography, imagery, voice, documents, presentations, social graphics, and launch materials. Use when the task changes brand identity rather than ordinary product UI or public-page composition.

SKILL.md

1.7 KB, as published. Nobody here has run it

OpenClaw Brand

Use the canonical identity without turning every surface into a marketing page.

Workflow

  1. Read identity.md for palette, typography, logo, and voice.
  2. Read asset-rights.md before copying or redistributing assets.
  3. Identify the artifact's audience and whether it is product, documentation, or marketing.
  4. Use semantic design tokens when the artifact is code.
  5. Keep status colors functional; do not use them as arbitrary decoration.
  6. Verify contrast, responsive cropping, and text legibility.
  7. Verify logo clearspace only when approved consumer-local guidance defines it; otherwise report that check as unavailable rather than inventing a measurement.

Rules

  • Use sentence case for headings, labels, buttons, and navigation.
  • Let OpenClaw coral carry primary brand emphasis.
  • Use sea-glass green as a restrained secondary accent.
  • Use neutral ink and warm-paper surfaces as the foundation.
  • Prefer Switzer-compatible sans-serif stacks for interface and body copy.
  • Reserve Sentient-compatible serif stacks for editorial accents and quotations.
  • Use system monospace for code unless the consumer already licenses another face.
  • Preserve logo proportions and colors. Do not rotate, distort, outline, or add effects.
  • Use real product, interface, community, or mascot imagery when imagery is needed.
  • Avoid generic technology gradients, decorative blobs, and ornamental glow as a substitute for content.

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.