BC topic-cluster-performance
Groups your search traffic by topic instead of by page, from live Google Search Console data in your Coupler.io workspace — each topic's clicks, impressions, CTR and position, its share of clicks against its share of pages, its trend, and how much rests on one page — so you can see which topics earn their place and which take effort without paying back. Topics come from a saved rule, the site's URL folders, or patterns you give it. Use for "which topics perform best in search", "how is our blog doing by category", "which content clusters drive organic traffic", "what topics should we write more about", "which sections of the site are growing in Google", "topic cluster report" — even when the user never says "cluster". This is the topic-level view. For page-level quick wins use google-search-console-keyword-opportunities. Google Search Console only.
Groups your search traffic by topic instead of by page, from live Google Search Console data in your Coupler.io workspace — each topic's clicks, impressions…
As a process C 63/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
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 63/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 65Failures and branches. 3 branches
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 29 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2743 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 860: 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 7 example trigger phrases
- +4Structure: 14 headings
- +3Step-by-step instructions: 29 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.