SKILLEMALL.ai
GitHub ↗ RU Sign in

CC aeo-audit

Run a one-time AEO audit of six AI answer engines, scored per surface. "check our AI search visibility"

indranilbanerjee/digital-marketing-pro Claude Code author: indranilbanerjee 1 file body ≈ 2 931 tokens Open the sourcegithub.com↗ analyzed 29 h ago

Run a one-time AEO audit of six AI answer engines, scored per surface.

As a process C 60/100 · Has gaps — References files that are not bundled: scripts/geo-tracker.py

AnalyzerAI and agentstype 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
C
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
66
Run on models
none yet
Process rating
C
60/100
Has gaps
References files that are not bundled: scripts/geo-tracker.py
Tools and files w 18
0
Progress reporting w 2
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
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

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: scripts/geo-tracker.py

Process rating: all ten parameters 60/100

Will not run. References files that are not bundled: scripts/geo-tracker.py
  • 0Tools and files. 1 referenced file(s) missing: scripts/geo-tracker.py
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 2 mutating operations with no state check
  • 55Failures and branches. 1 branches
  • 60Result and completion. Output format stated, no completion criterion
  • 70When it triggers. States when to use, but not when not to
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 37 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2931 tokens
  • low 11 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

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 103: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 37 items
  • +3Output format is stated explicitly
  • +4Has examples (2 code blocks)

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