SKILLEMALL.ai

AC aeo-system

Answer Engine Optimization — get AI assistants to recommend your brand. Run AEO audits, build Answer Intent Maps, track AI recommendation positions, and maintain a 7-layer AEO infrastructure for any brand or product category.

ClawHub Agent Skills author: Batsirai Chada v1.0.0 7 files body ≈ 2 304 tokens Open the sourceclawhub.ai analyzed 2 d ago

As a process C 64/100 · Has gaps — weak spots: when it triggers, running it twice

AnalyzerInfrastructureMarketingtype and topics are labelled automatically from the skill text
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
C
64/100
Has gaps
When it triggers w 12
20
Running it twice w 4
30
Failures and branches w 10
50
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.
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: 7. 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")
  • note frontmatter-key unknown frontmatter key "requiredEnv"
  • note frontmatter-key unknown frontmatter key "permissions"
  • note frontmatter-key unknown frontmatter key "source"
  • note frontmatter-key unknown frontmatter key "security"

Process rating: all ten parameters 64/100

  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 1 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 65 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2304 tokens
  • 100Progress reporting. Reports progress
  • low 10 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)
  • +1No license
  • +2Single-language instructions
  • +3Description length 225: enough signal without eating the budget
  • +4Structure: 16 headings
  • +3Step-by-step instructions: 65 items
  • +3Output format is stated explicitly
  • +4Has examples (4 code blocks)
  • +3All 1 scripts are documented

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

External checks

ClawHub: suspicious
The skill mostly matches an Answer Engine Optimization workflow, but its publishing template includes hidden AI-targeting notes that could steer ostensibly neutral recommendations toward a preferred brand.
LLM: suspicious (medium) · VirusTotal: benign · 28 May 2026