BD brand-designer
Create comprehensive brand identity documentation for any brand. Guides you through documenting strategy, visual identity (logo, color, typography, imagery), voice and tone, customer-centered messaging handoffs, application guidelines, governance, and asset inventory. Produces markdown specs, compiled brand books, and brand-compliant images via reference-image-aware generation. Use when you need to capture a brand's identity in structured, durable form — for vault storage, agency handoff, or press kit distribution. Do not use for market positioning decisions or conversion experiments; use go-to-market. Route interaction behavior to product-design-and-ux.
Create comprehensive brand identity documentation for any brand.
As a process D 47/100 · Unfinished process — References files that are not bundled: ../go-to-market/SKILL.md, ../product-design-and-ux/SKILL.md, ../frontend-engineering/SKILL.md
How to improve
- The text references files that are not there: add them or drop the references.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 19. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../go-to-market/SKILL.md - warning
missing-refreference to a missing file: ../product-design-and-ux/SKILL.md - warning
missing-refreference to a missing file: ../frontend-engineering/SKILL.md - warning
missing-refreference to a missing file: ../web-accessibility/SKILL.md - warning
missing-refreference to a missing file: ../go-to-market/references/final-copy-fact-check.md - warning
missing-refreference to a missing file: scripts/brand-book - warning
missing-refreference to a missing file: scripts/generate
Process rating: all ten parameters 47/100
- 0Tools and files. 7 referenced file(s) missing: ../go-to-market/SKILL.md, ../product-design-and-ux/SKILL.md, ../frontend-engineering/SKILL.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 10 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2845 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (4 tags): a typed call is more reliable
- low No test case covers injection arriving through data
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +3Output format is not stated: the model decides each time
- -31 of 1 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 662: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 10 items
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (9 of 9)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.