BD seo-client-report
Builds the monthly SEO report a client reads, from live Google Search Console data (and GA4 when connected) in your Coupler.io workspace — every KPI scored against target and against last month and last year, non-brand growth separated from brand, wins with numbers, a misses section that names the problem first, and recommendations someone can be held to. Use when someone asks for a monthly SEO report for a client, wants the organic section of a client deck, needs last month's search performance written up, asks "what do I tell the client about SEO", or asks how to present an SEO target they missed — even when they never say the word "report". For agencies and in-house teams reporting upward. For the operator's own read use google-search-console-keyword-opportunities or content-decay-analysis. Needs Google Search Console; GA4 optional.
Builds the monthly SEO report a client reads, from live Google Search Console data (and GA4 when connected) in your Coupler.io workspace — every KPI scored…
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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: 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 43/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. 13 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 34 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3735 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)
- +3Description length 847: 120–800 characters recommended
- +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
- +4Structure: 14 headings
- +3Step-by-step instructions: 34 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.