BD brand
Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.
Brand voice, visual identity, messaging frameworks, asset management, brand consistency.
As a process D 35/100 · Unfinished process — References files that are not bundled: scripts/<file>, assets/design-tokens.json, assets/design-tokens.*
The same skill appears in 1 more place: ui-ux-pro-max-skill
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- 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: 18. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/<file> - warning
missing-refreference to a missing file: assets/design-tokens.json - warning
missing-refreference to a missing file: assets/design-tokens.* - warning
missing-refreference to a missing file: assets/design-tokens.css - warning
missing-refreference to a missing file: references/{subcommand}.md
Process rating: all ten parameters 35/100
- 0Tools and files. 5 referenced file(s) missing: scripts/<file>, assets/design-tokens.json, assets/design-tokens.*
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Steps. 12 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 901 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (3 tags): a typed call is more reliable
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 183: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (11 of 11)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.
In the sandbox The scripts kept to themselves
The skill's scripts were run in a throwaway machine: no network, fake keys in the home directory, a tracer watching. We wrote down what they did. Reaching for the network or for secrets caps the technical grade at C; a quiet run adds no points.
Запущено 4 скрипта; каждому дали двадцать секунд, поддельный домашний каталог с ключами и сеть, в которой ничего нет.
scripts/extract-colors.cjs | ничего за пределами своей папки |
scripts/inject-brand-context.cjs | ничего за пределами своей папки |
scripts/sync-brand-to-tokens.cjs | ничего за пределами своей папки |
scripts/validate-asset.cjs | ничего за пределами своей папки |
12 Oct 2026