SKILLEMALL.ai

BC tiktok-ads-placement-location-and-device-breakdown

Use for "is Pangle wasting my money", "should I turn off automatic placement", "how is Search Feed doing", "which countries are working on TikTok", "is iOS or Android converting", "what time of day should I be running", or "where is my budget actually going" — even when the user never says "placement". Covers where and when the ads are shown, and what each of those is worth. TikTok Ads only.

coupler-io/skills Agent Skills author: coupler-io 1 file body ≈ 3 416 tokens Open the sourcegithub.com↗ analyzed 7 d ago

Use for "is Pangle wasting my money", "should I turn off automatic placement", "how is Search Feed doing", "which countries are working on TikTok", "is iOS or…

As a process C 63/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches

AnalyzerMarketingtype and topics are labelled automatically from the skill text
JSON
Technical rating
B
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
85
Run on models
none yet
Process rating
C
63/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
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 63/100

    • 0Result and completion. Does not say what the result is
    • 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
    • 100Tools and files. No external tools needed
    • 100Steps. 26 steps
    • 100When it triggers. States when to use and when not to
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3416 tokens
    • 100Running it twice. Mutating operations check current state
    • 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

    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 8 example trigger phrases
    • +3Description length 394: enough signal without eating the budget
    • +4Structure: 13 headings
    • +3Step-by-step instructions: 26 items

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