AB snapchat-ads-cli
Snapchat Ads data analysis and reporting via snapchat-ads-cli. Use when the user wants to check Snapchat ad performance, pull campaign/ad squad/ad stats, explore ad account structure, inspect creatives, analyze audiences, debug delivery issues, estimate bids and audience size, manage AR lenses, or retrieve billing information. Triggers: "Snapchat Ads", "Snap Ads", "snapchat ad performance", "snapchat campaign stats", "snapchat ad spend", "snapchat pixel", "snapchat audience", "snapchat creatives", "snapchat ad account", "ad squad performance", "snapchat delivery status", "snapchat lenses", "snapchat bid estimate", "snapchat audience size", "snapchat billing".
As a process B 71/100 · Nearly there — weak spots: inputs and preconditions, progress reporting
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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 71/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 51 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3383 tokens
- 100Running it twice. No mutating operations
- low The response is described with custom markup (9 tags): a typed call is more reliable
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
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +5Description quotes 15 example trigger phrases
- +3Description length 667: enough signal without eating the budget
- +4Structure: 33 headings
- +3Step-by-step instructions: 51 items
- +3Output format is stated explicitly
- +4Has examples (21 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.