SKILLEMALL.ai
GitHub ↗ RU Sign in

BC google-ads-client-report

Use when someone asks for a monthly Google Ads report for a client, wants the client deck built, needs last month's Google Ads performance written up, asks for an end-of-month PPC report, asks "what do I tell the client", or asks how to present a target they missed — even when they never say the word "report". Also use when the Google Ads section of a client review or QBR is what's wanted. For agencies and in-house teams reporting upward. Google Ads only.

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

Use when someone asks for a monthly Google Ads report for a client, wants the client deck built, needs last month's Google Ads performance written up, asks…

As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureData and analyticstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
85
Run on models
none yet
Process rating
C
51/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 51/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
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 9 mutating operations with no state check
    • 100Tools and files. No external tools needed
    • 100Steps. 26 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3980 tokens
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low 13 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 2 example trigger phrases
    • +3Description length 459: enough signal without eating the budget
    • +4Structure: 14 headings
    • +3Step-by-step instructions: 26 items

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