BC Email Marketing Command Center
Complete email marketing system — strategy, sequences, segmentation, automation, deliverability, and analytics. Build campaigns that convert.
Complete email marketing system — strategy, sequences, segmentation, automation, deliverability, and analytics.
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
ProcedureData and analyticsWriting and documentsMarketingtype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 6697 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 24 mutating operations with no state check
- 40Consistency. Frontmatter name (Email Marketing Command Center) differs from the folder (afrexai-email-marketing)
- 50Failures and branches. 0 branches, has a failure section
- 70Execution cost. Instruction body is 6697 tokens
- 100Tools and files. No external tools needed
- 100Steps. 74 steps
- 100Progress reporting. Reports progress
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 141: enough signal without eating the budget
- +4Structure: 40 headings
- +3Step-by-step instructions: 74 items
- +4Has examples (23 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.