CD campaign-calendar
Build strategic ecommerce campaign calendars that align marketing activities with platform promotions, seasonal peaks, and product launch cycles for maximum sales impact.
Build strategic ecommerce campaign calendars that align marketing activities with platform promotions, seasonal peaks, and product launch cycles for maximum…
As a process D 37/100 · Unfinished process — References files that are not bundled: references/output-template.md, references/ecommerce-event-calendar.md, references/campaign-design-framework.md
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.
- 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: 6. 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") - warning
body-longSKILL.md body ≈ 6913 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/output-template.md - warning
missing-refreference to a missing file: references/ecommerce-event-calendar.md - warning
missing-refreference to a missing file: references/campaign-design-framework.md - warning
missing-refreference to a missing file: assets/quality-checklist.md
Process rating: all ten parameters 37/100
- 0Tools and files. 4 referenced file(s) missing: references/output-template.md, references/ecommerce-event-calendar.md, references/campaign-design-framework.md
- 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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 20 mutating operations with no state check
- 60Failures and branches. 2 branches
- 70Execution cost. Instruction body is 6913 tokens
- 100Steps. 102 steps
- 100Consistency. Name and required fields are in place
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
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +3Description length 170: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 102 items
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 45.