CB diagnose-ai-visibility
Find out why AI search engines leave your brand out of an answer, and pick the one fix that matches the cause — read the answers and the sources they cite, map the question to your own page, then decide if the page is broken, missing, weak, or outweighed by third-party sources. Use when the user asks why ChatGPT, Gemini, Perplexity or Google AI Overviews do not mention them, which prompts they lose, what content to write next, or how to improve AI visibility.
The skill diagnoses why AI search engines omit your brand from answers. Promises to identify whether your page is broken, missing content, too weak, or outweighed by competitors. One file with 722 tokens—a checklist to read search engine responses, map them to your own page, pick one of four causes.
Tests show a C grade: quality 70%, process 65%, no critical issues. No sandbox runs, no model testing. The skill works as a manual checklist, not an automated analyzer—you read, compare, decide yourself. For those who already track what ChatGPT or Gemini mentions but can't figure out why their site isn't there.
Install if you're ready to run diagnosis by hand. Skip if you expect the agent to fetch answers from search engines automatically.
Find out why AI search engines leave your brand out of an answer, and pick the one fix that matches the cause — read the answers and the sources they cite…
As a process B 65/100 · Nearly there — 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
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 3, column 16: argument-hint: a prompt, topic, or tag to diagnose (default: the lowest non-bra… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 65/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
- 55Failures and branches. 1 branches
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 11 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 722 tokens
- 100Running it twice. Mutating operations check current state
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
- +5Description has no quoted example phrases that should trigger the skill
- +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
- +3Description length 463: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 11 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.