SKILLEMALL.ai

AF on-page-seo-auditor

Use when the user asks to "audit page SEO", "on-page SEO check", "SEO score", "page optimization", "what SEO issues does this page have", "what is wrong with this page SEO", "score my page", or "why is this page not ranking". Performs comprehensive on-page SEO audits to identify optimization opportunities including title tags, meta descriptions, headers, content quality, internal linking, and image optimization. For server, speed, and crawl issues, see technical-seo-checker. For full EEAT content quality scoring, see content-quality-auditor.

modbender/skill-library-mcp Agent Skills author: modbender MIT 2 files body ≈ 6 589 tokens Open the sourcegithub.com analyzed 2 d ago

Use when the user asks to "audit page SEO", "on-page SEO check", "SEO score", "page optimization", "what SEO issues does this page have", "what is wrong with…

As a process F 51/100 · Will not run — References files that are not bundled: ../../research/keyword-research/, ../../research/competitor-analysis/, ../../research/serp-analysis/

AnalyzerMarketingtype 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
F
51/100
Will not run
References files that are not bundled: ../../research/keyword-research/, ../../research/competitor-analysis/, ../../research/serp-analysis/
Tools and files w 18
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  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: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 6589 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: ../../research/keyword-research/
  • warning missing-ref reference to a missing file: ../../research/competitor-analysis/
  • warning missing-ref reference to a missing file: ../../research/serp-analysis/
  • warning missing-ref reference to a missing file: ../../research/content-gap-analysis/
  • warning missing-ref reference to a missing file: ../../build/seo-content-writer/
  • warning missing-ref reference to a missing file: ../../build/geo-content-optimizer/
  • warning missing-ref reference to a missing file: ../../build/meta-tags-optimizer/
  • warning missing-ref reference to a missing file: ../../build/schema-markup-generator/
  • warning missing-ref reference to a missing file: ../technical-seo-checker/
  • warning missing-ref reference to a missing file: ../internal-linking-optimizer/
  • warning missing-ref reference to a missing file: ../content-refresher/
  • warning missing-ref reference to a missing file: ../../monitor/rank-tracker/
  • warning missing-ref reference to a missing file: ../../monitor/backlink-analyzer/
  • warning missing-ref reference to a missing file: ../../monitor/performance-reporter/
  • warning missing-ref reference to a missing file: ../../monitor/alert-manager/
  • warning missing-ref reference to a missing file: ../../cross-cutting/content-quality-auditor/
  • warning missing-ref reference to a missing file: ../../cross-cutting/domain-authority-auditor/
  • warning missing-ref reference to a missing file: ../../cross-cutting/entity-optimizer/
  • warning missing-ref reference to a missing file: ../../cross-cutting/memory-management/
  • warning missing-ref reference to a missing file: ../../CONNECTORS.md
  • warning missing-ref reference to a missing file: ../../references/core-eeat-benchmark.md

Process rating: all ten parameters 51/100

Will not run. References files that are not bundled: ../../research/keyword-research/, ../../research/competitor-analysis/, ../../research/serp-analysis/
  • 0Tools and files. 21 referenced file(s) missing: ../../research/keyword-research/, ../../research/competitor-analysis/, ../../research/serp-analysis/
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 5 mutating operations with no state check
  • 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
  • 70Execution cost. Instruction body is 6589 tokens
  • 85Steps. 50 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • low 14 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)
  • +2Single-language instructions
  • +5Description quotes 8 example trigger phrases
  • +3Description length 547: enough signal without eating the budget
  • +4Structure: 32 headings
  • +3Step-by-step instructions: 50 items
  • +3Output format is stated explicitly
  • +4Has examples (22 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)
  • +1License stated

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