AB Platform Promo Radar
Cross-platform promotion radar for mainland China shopping platforms that tracks the hottest current campaigns across Taobao, Tmall, JD, PDD, VIPSHOP, and similar marketplaces, ranks them by real savings, participation friction, category fit, freshness, and urgency, and tells the user which promotions are actually worth chasing right now.
As a process B 71/100 · Nearly there — weak spots: inputs and preconditions, consistency
How to improve
- 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
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - note
frontmatter-keyunknown frontmatter key "slug"
Process rating: all ten parameters 71/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Consistency. Frontmatter name (Platform Promo Radar) differs from the folder (promotion)
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 120 steps
- 100Execution cost. Instruction body is 1686 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 340: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 120 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.