SKILLEMALL.ai
GitHub ↗ RU Sign in

AC seo-audit

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.

alirezarezvani/claude-skills Agent Skills author: alirezarezvani MIT 7 files body ≈ 1 761 tokens Open the sourcegithub.com↗ analyzed 2 d ago

When the user wants to audit, review, or diagnose SEO issues on their site.

As a process C 62/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, progress reporting

AnalyzerMarketingtype 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
A
98/100
safety, quality, tests
Safety 60%
100
Quality 40%
96
Run on models
none yet
Process rating
C
62/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

    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

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 62/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 85Steps. 60 steps, 1 vague phrases
    • 100When it triggers. States when to use and when not to
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1761 tokens
    • 100Running it twice. Mutating operations check current state
    • 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

    • +4Description does not say when NOT to use the skill (false activations)
    • +4No input/output examples
    • +2Single-language instructions
    • +5Description quotes 7 example trigger phrases
    • +3Description length 350: enough signal without eating the budget
    • +4Structure: 13 headings
    • +3Step-by-step instructions: 60 items
    • +3Output format is stated explicitly
    • +4Reference files are cited in the instructions (4 of 4)
    • +3All 2 scripts are documented
    • +1License stated

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