BC organic-traffic-drop-diagnosis
Works out why organic search traffic dropped suddenly, from live Google Search Console data (and GA4 when connected) in your Coupler.io workspace — finds the date it broke, then splits the lost clicks by section, page, country, device and brand to name the most likely cause: tracking, migration, a site-wide ranking fall, one section, lost demand or seasonality. Use for "why did my organic traffic drop", "our SEO traffic fell off a cliff", "did we get hit by a Google update", "traffic dropped after the redesign", "search clicks halved last week", "is it the site or is it tracking" — even when the user never says "diagnosis". This is the sudden-break view: one date, one cause to check first. For a slow slide on individual pages use content-decay-analysis. Needs Google Search Console; GA4 optional.
Works out why organic search traffic dropped suddenly, from live Google Search Console data (and GA4 when connected) in your Coupler.io workspace — finds the…
As a process C 55/100 · Has gaps — weak spots: result and completion, inputs and preconditions, progress reporting
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 55/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
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 4126 tokens
- 100Steps. 32 steps
- 100Consistency. Name and required fields are in place
- 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 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 806: 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: 32 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.