AB pinterest-ads-cli
Pinterest Ads data analysis and reporting via pinterest-ads-cli. Use when the user wants to check Pinterest ad performance, pull campaign/ad group/ad stats, explore ad account structure, inspect audiences, analyze billing, browse product catalogs, discover trending search terms, or retrieve analytics with attribution windows. Triggers: "Pinterest Ads", "Pinterest ad performance", "Pinterest campaign stats", "Pinterest ad spend", "Pinterest analytics", "Pinterest audience", "Pinterest catalogs", "Pinterest trends", "Pinterest keywords", "Pinterest billing", "Pinterest lead forms", "Pinterest conversion tags", "Pinterest shopping", "Pinterest feeds".
As a process B 69/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 69/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
- 70Execution cost. Instruction body is 4559 tokens
- 100Steps. 37 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. No mutating operations
- low The response is described with custom markup (41 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 14 example trigger phrases
- +3Description length 656: enough signal without eating the budget
- +4Structure: 52 headings
- +3Step-by-step instructions: 37 items
- +3Output format is stated explicitly
- +4Has examples (33 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.