Brand guidelines builder
Skill zapier/gtm-cheat-codes/skills/marketing/brand-guidelines-builder
Help non-designers evaluate work against brand guidelines and know what to fix.From its SKILL.md
npx -y skills add zapier/gtm-cheat-codes --skill brand-guidelines-builderAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
0.9 KB, 170 tokens by cl100k_base, as published. Nobody here has run it
Brand Guidelines Builder
Use this skill to review creative assets, campaign ideas, or page concepts against a brand system.
Workflow
- Ask for the asset, brief, audience, and channel when missing.
- Review color, typography, logo usage, imagery, layout, and tone.
- Score alignment and explain issues in plain language.
- Provide prioritized fixes and escalation guidance.
Zapier MCP And SDK Role
- Use Zapier MCP to read approved brand docs, asset libraries, and design references.
- Use Zapier SDK only if the team wants a repeatable review intake queue or feedback log.
- Keep official guideline changes and final external use human-approved.
Guardrails
- Do not invent brand rules.
- Link only to approved public or team-approved brand resources.
- Keep feedback practical and kind.
What ships with it: 5 files
3.4 KB alongside SKILL.md
- metadata.yaml547 B
- ONBOARDING-PROMPT.md603 B
- README.md790 B
- SCHEMA-MAP.md578 B
- SETUP.md941 B
Gives 0 of the 12 instructions most marketing audience skills give in 170 tokens
Counted across 690 of the 894 authors here whose files we hold, read 2026-08-07
- Apply Poppins font to headingsin 41 of 690, across 6 files
- Apply Lora font to body textin 41 of 690, across 6 files
- Use Arial fallback for headingsin 39 of 690, across 4 files
- Use Georgia fallback for body textin 39 of 690, across 4 files
- Maintain text hierarchy and formattingin 39 of 690, across 4 files
- Use accent colors for non-text shapesin 38 of 690, across 3 files
- Use RGB values for precise color matchingin 38 of 690, across 3 files
- Use brand colors for primary text and backgroundsin 36 of 690, across 1 file
- Read product marketing context file before asking questions, starting, or auditingin 35 of 690, across 23 files
- Use active voice instead of passive voicein 26 of 690, across 10 files
- Implement or generate appropriate JSON-LD structured datain 24 of 690, across 17 files
- Prioritize clarity over clevernessin 22 of 690, across 8 files
Said here and by no other author read
- ask for the asset brief audience and channel
- review color typography logo imagery layout and tone
- score alignment and explain issues in plain language
- provide prioritized fixes and escalation guidance
- use Zapier MCP to read approved brand documents
- use Zapier SDK for repeatable review intake queues
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.