BC worldcup-2026-moment-marketing
A World Cup moment-marketing (newsjacking) engine for businesses. Any brand uses it daily to pull the biggest talking point from a 2026 World Cup match, tie it to their own industry, and produce one ready-to-post piece — a short article/post (LinkedIn, Medium, blog, email newsletter) or a short-video script (TikTok, Reels, YouTube Shorts). Built for restaurants, gyms, real estate, e-commerce, coaches, agencies, and any local or B2B business doing real-time World Cup marketing.
A World Cup moment-marketing (newsjacking) engine for businesses.
As a process C 56/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 56/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (worldcup-2026-moment-marketing) differs from the folder (world-cup-marketing-for-small-biz)
- 50When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 85Steps. 32 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 1227 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 481: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 32 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.