SKILLEMALL.ai
GitHub ↗ RU Sign in

AB ad-campaign-analyzer

Use this skill when the user shares ad campaign performance data and asks what to cut, scale, or test. Trigger for prompts like "analyze my ad campaigns", "where am I wasting ad spend", "reallocate my ad budget", "which ads are actually working", or "ROAS analysis". Do not trigger for campaign planning or creative generation without performance data.

github/awesome-copilot Agent Skills author: github MIT 1 file body ≈ 3 276 tokens Open the sourcegithub.com↗ analyzed 28 h ago

Trigger for prompts like "analyze my ad campaigns", "where am I wasting ad spend", "reallocate my ad budget", "which ads are actually working", or "ROAS…

As a process B 65/100 · Nearly there — weak spots: inputs and preconditions, failures and branches, running it twice

AnalyzerMarketingtype and topics are labelled automatically from the skill text
Runs in: GitHub Copilot / VS Code Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
97/100
safety, quality, tests
Safety 60%
100
Quality 40%
93
Run on models
none yet
Process rating
B
65/100
Nearly there
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

    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: 1. 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 65/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 2 mutating operations with no state check
    • 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. 52 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3276 tokens
    • low 10 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

    • +4Description does not say when NOT to use the skill (false activations)
    • +2Single-language instructions
    • +5Description quotes 5 example trigger phrases
    • +3Description length 352: enough signal without eating the budget
    • +4Structure: 25 headings
    • +3Step-by-step instructions: 52 items
    • +3Output format is stated explicitly
    • +4Has examples (4 code blocks)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 93.