/SKILL.md
Universal brand guideline engine for producing, reviewing, and suggesting brand-compliant marketing materials for ANY company. Use this skill whenever a task involves brand identity, visual consistency, marketing collateral, or corporate design standards. Triggers include: brand guidelines, brand book, visual identity, corporate identity, brand compliance, brand review, brand audit, marketing materials, social media copy, poster design, banner design, PPT template, presentation template, company brochure, brand colors, typography guidelines, tone of voice, brand voice, logo usage, brand assets, style guide, design system, marketing collateral, campaign materials, brand consistency check. Also trigger when a user mentions producing materials like posters, banners, social posts, company introductions, pitch decks, brochures, flyers, email templates, or video storyboards and wants them to follow a specific brand look-and-feel. Even if the user doesn't say "brand guideline" explicitly, use this skill when any visual or verbal consistency with a company identity is implied.
npx skillsauth add esekasa/brand-consistency-ai-skill brand-guidelinesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
A universal skill for producing, reviewing, and advising on brand-compliant materials across any company. This skill turns a brand configuration file into an active quality gate — every deliverable you produce or review passes through brand rules automatically.
The skill operates in three modes depending on what the user needs:
| Mode | Trigger | What Happens |
|------|---------|--------------|
| Configure | User provides brand info or uploads a brand guide | Parse → generate brand-config.json |
| Produce | User asks to create a deliverable (poster, PPT, copy…) | Load config → apply brand rules → create output |
| Review | User asks to check/audit existing material | Load config → run compliance checklist → report issues |
Every task begins here. Check if a brand-config.json exists in the working directory or
in the user's uploaded files.
If config exists: Read it and confirm the brand name with the user.
If config does NOT exist: Ask the user for brand information. They may:
Then generate the config by running:
python3 <skill-path>/scripts/init_brand_config.py --output brand-config.json
Edit the output JSON to fill in the user's brand details. The config structure covers every
aspect of brand identity — see references/brand-config-template.md for the full schema
and field-by-field guidance.
Minimum viable config (enough to start producing materials):
{
"brand_name": "Company Name",
"colors": {
"primary": [{"name": "Main", "hex": "#000000"}],
"accent": [{"name": "Accent", "hex": "#FF6600"}]
},
"typography": {
"heading_font": "Poppins",
"body_font": "Inter"
}
}
Even a partial config is useful — the skill will work with whatever is provided and flag gaps when they matter for the specific deliverable.
When the user provides brand source material (a PDF brand book, a website, verbal descriptions),
your job is to extract structured brand data into brand-config.json.
Read the source material carefully. For PDFs, extract text; for images, describe visual elements; for websites, note colors, fonts, and layout patterns.
Map to the config schema. Walk through each section of references/brand-config-template.md
and fill what you can find.
Infer what's missing. If a brand guide shows a blue header but doesn't list the hex code, eyeball it or ask the user. If tone-of-voice examples exist but no explicit personality traits are listed, derive them from the examples.
Ask to fill gaps. Present the user with a summary of what you found vs. what's still missing. Prioritize gaps that affect near-term deliverables.
Validate colors. Run scripts/validate_brand.py --config brand-config.json --check colors
to ensure contrast ratios meet WCAG AA for all foreground/background combinations.
Save and confirm. Write the final brand-config.json and give the user a visual summary:
color swatches (as an HTML or SVG artifact), font hierarchy, and key verbal guidelines.
When a user asks you to create any marketing material, follow this workflow:
Read references/deliverable-specs.md to find the matching deliverable type and its specs.
Common types:
| Category | Deliverables | |----------|-------------| | Social Media | Instagram post/story/reel, Facebook post/cover, LinkedIn post/banner, Twitter/X post, TikTok, WeChat Moments, Xiaohongshu | | Digital Ads | Web banner (IAB sizes), display ads, email header | | Presentations | Pitch deck, company intro, sales deck, keynote template | | Print | Poster (A3/A2/A1), flyer (A5/A4), brochure, business card, letterhead | | Long-form | Company brochure/lookbook, annual report, brand book itself | | Video | Storyboard, title card, end card, lower-third template | | Copy | Taglines, social captions, website copy, email campaigns, press releases |
For every deliverable, apply these rules from the brand config:
Visual rules (read references/visual-identity.md for details):
Verbal rules (read references/tone-of-voice.md for details):
Consult the size table in references/deliverable-specs.md for exact dimensions, DPI,
file format, and bleed requirements. Key principles:
Before delivering ANY material, run the brand compliance review:
python3 <skill-path>/scripts/validate_brand.py --config brand-config.json --material <output-file>
Also mentally walk through the checklist in references/review-checklist.md:
When a user asks you to review or audit materials for brand compliance:
Load the brand config and understand the full brand system.
Examine the material. For images, describe what you see (colors, fonts, layout, logo usage). For documents, read the content. For presentations, check each slide.
Score against the checklist. Use references/review-checklist.md and score each
category (Visual Identity, Typography, Color, Logo, Imagery, Copy, Format).
Generate a compliance report with this structure:
# Brand Compliance Report — [Material Name]
## Overall Score: X/100
## Summary
One-paragraph overview of compliance level.
## Findings
### Passes (what's correct)
- ...
### Issues (what needs fixing)
For each issue:
- **What**: Description of the violation
- **Where**: Location in the material
- **Rule**: Which brand guideline it violates
- **Fix**: Specific recommended correction
## Recommendations
Prioritized list of improvements.
Offer to fix. For each issue found, offer to produce a corrected version.
This skill often works alongside other creation skills. The brand config acts as a constraint layer on top of their output:
| Partner Skill | How Brand Guidelines Applies | |---------------|------------------------------| | pptx | Apply brand colors, fonts, and logo to presentation templates. Use brand imagery style. | | docx | Apply brand fonts, heading styles, and color accents to documents. Enforce tone of voice. | | xlsx | Apply brand colors to chart formatting and header styling. | | pdf | Ensure generated PDFs follow brand typography and color rules. |
When invoking a partner skill, pass the relevant brand parameters explicitly:
When writing copy for social media or marketing channels, adapt the brand voice to each
platform's conventions. Read references/tone-of-voice.md for the full framework, but
here's the quick reference:
| Platform | Max Length | Tone Shift | Format Notes | |----------|-----------|------------|-------------| | LinkedIn | 3000 chars | More professional, thought-leadership | Paragraphs, minimal emoji | | Instagram | 2200 chars | Visual-first, lifestyle-oriented | Short paragraphs, strategic emoji, 3-5 hashtags | | Twitter/X | 280 chars | Punchy, conversational | One core message, 1-2 hashtags max | | Facebook | 500 chars optimal | Community-oriented, storytelling | Questions work well, link-friendly | | WeChat | 2000 chars | Relationship-focused, informative | Longer form OK, image-text mix | | Xiaohongshu | 1000 chars | Authentic, personal, lifestyle | Emoji-rich, tip-style formatting, 10+ hashtags | | Email Subject | 50 chars | Direct, benefit-focused | Front-load the value proposition | | Email Body | Varies | Warm but professional | Clear CTA, scannable sections |
The brand-config.json is structured into these top-level sections:
| Section | Purpose | Reference |
|---------|---------|-----------|
| brand_name | Company name | — |
| brand_identity | Mission, values, positioning, personality | references/brand-config-template.md |
| colors | Full color palette with codes | references/visual-identity.md |
| typography | Font families, sizes, hierarchy | references/visual-identity.md |
| logo | Usage rules, variants, clear space | references/visual-identity.md |
| imagery | Photography/illustration style | references/visual-identity.md |
| verbal_identity | Tone, terminology, key messages | references/tone-of-voice.md |
| deliverable_defaults | Per-type default settings | references/deliverable-specs.md |
These are typically pre-installed. If not, install with:
pip install Pillow python-pptx python-docx openpyxl --break-system-packages
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
development
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.