BC marketing-brand-playbook
World-Class Marketing & Brand Playbook. Use for: brand positioning, brand strategy, value propositions, content creation, content marketing, content calendars, digital marketing, SEO (search engine optimization), SEM (search engine marketing), paid social, social media marketing, email marketing, email campaigns, drip sequences, automation, public relations, PR strategy, press releases, media relations, crisis communications, market research, competitive analysis, customer segmentation, audience research, personas, storytelling, brand narrative, community building, community management, conversion rate optimization (CRO), A/B testing, landing pages, funnel optimization, go-to-market strategy, launch marketing, growth marketing, brand identity, messaging frameworks, positioning statements, taglines, campaign planning, marketing strategy, marketing plans, KPIs, marketing metrics, attribution, influencer marketing, creator partnerships, UGC, thought leadership, content distribution, repurposing, social media SEO, GEO (generative engine optimization), zero-click optimization. Trigger when discussing ANY marketing, branding, growth, or go-to-market topic. If the user asks about positioning a product, writing marketing copy, planning a campaign, building an audience, optimising conversions, or any related marketing discipline — use this skill. If in doubt, use this skill.
As a process C 55/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- Shorten the description to 1024 characters.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1389 chars, limit 1024 - warning
body-longSKILL.md body ≈ 5574 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 55/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 15 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Failures and branches. 6 branches
- 70Execution cost. Instruction body is 5574 tokens
- 100Steps. 71 steps
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 top-level sections: this looks like several domains in one skill
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)
- +3Description length 1388: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 52 headings
- +3Step-by-step instructions: 71 items
- +4Has examples (8 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 50.