Skip to content
cccskills
FreePublished on GitHub

openclaw-brand

Apply OpenClaw’s brand identity to documents, presentations, social graphics, and launch materials. The skill guides color, typography, logo use, imagery, and writing tone, with checks for contrast, cropping, and text readability.

OriginalShow the original description

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.

openclaw/clawhub
See how to install

Good for

  • Align documents and presentations with the brand
  • Unify social graphics and launch materials
  • Review logo use, typography, and colors
  • Check contrast, image cropping, and text readability

Files included (3)

  • SKILL.md1.7 KB
  • references/asset-rights.md802 B
  • references/identity.md1.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

autoreview

FreeSummary

Review code using shared OpenClaw instructions and a Python helper, while also following the target repository’s review requirements. This skill points to a common installation that supplies the actual review procedure.

  • Reviewing code with shared OpenClaw instructions
  • Applying repository-specific review requirements
  • Keeping shared review instructions up to date
openclaw/clawhub9.5KUpdated Oct 19, 2026

axiom-alerting

FreeSummary

Create and manage Axiom alert rules and notification destinations through its API. Connect alerts to email, Slack, or webhooks, check monitor history, and adjust thresholds and evaluation schedules to address excessive or missing alerts.

  • Set up error alerts and notification destinations
  • Tune monitors that send too many alerts
  • Investigate monitors that never trigger
openclaw/clawhub9.5KUpdated Oct 19, 2026

axiom-sre

FreeSummary

Investigate production incidents and bugs using logs, metrics, and code evidence. The skill guides hypothesis testing, root cause analysis, fix validation, and reusable investigation notes, with access to configured observability tools such as Axiom.

  • Investigate production outages and rising error rates
  • Trace causes using logs, metrics, and code
  • Reproduce bugs and validate minimal fixes
openclaw/clawhub9.5KUpdated Oct 19, 2026

building-dashboards

FreeSummary

Design and build Axiom dashboards from logs or metrics, the numerical measurements of system behavior. Create charts, filters, and layouts for monitoring and reporting, or migrate existing Splunk and Grafana panels while validating queries against available data.

  • Build a service health monitoring dashboard
  • Create interactive filters for investigating logs
  • Migrate dashboards from Splunk or Grafana
openclaw/clawhub9.5KUpdated Oct 19, 2026

clawhub-content-rights-correspondence

FreeSummary

Drafts, previews, sends, and records emails for existing ClawHub content rights cases. It supports publisher removal notices and requester updates, requires approval of the final draft, and preserves the exact correspondence in the case record.

  • Preparing a skill removal notice for a publisher
  • Sending a requester a progress update or closure note
  • Preserving sent correspondence in an existing rights case
openclaw/clawhub9.5KUpdated Oct 19, 2026

clawhub-convex

FreeSummary

Apply ClawHub-specific rules when developing with Convex, including deployment targeting, runtime checks, data migrations, search performance, and skill statistics. It also directs specialized work to the appropriate companion skills.

  • Changing Convex functions or schemas
  • Planning production data migrations
  • Reviewing search query performance
openclaw/clawhub9.5KUpdated Oct 19, 2026

See all skills by openclaw

Report a problem with this skill