AC brand-voice
When the user wants to define, document, or enforce their brand voice and style guide. Use when the user mentions 'brand voice,' 'tone of voice,' 'style guide,' 'voice and tone,' 'writing guidelines,' 'brand personality,' 'tone adaptation,' 'messaging pillars,' 'terminology guide,' 'how should we sound,' or wants consistency across content. Creates `.agents/brand-voice-guide.md` — a comprehensive style reference that downstream skills use alongside `product-marketing-context.md`. For foundational positioning context, see product-marketing-context.
As a process C 54/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 54/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Consistency. Frontmatter name (brand-voice) differs from the folder (abm-brand-voice)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Failures and branches. 15 branches
- 85Steps. 55 steps, 1 vague phrases
- 100Execution cost. Instruction body is 3242 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The skill ranks results itself: that belongs to the system behind the tool, not the model
- 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
- +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 553: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 55 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.