SKILLEMALL.ai
GitHub ↗ RU Sign in

AA seo-page

Deep single-page SEO analysis covering on-page elements, content quality, technical meta tags, schema, images, and performance. Use when user says "analyze this page", "check page SEO", or provides a single URL for review.

sickn33/agentic-awesome-skills Claude Code author: sickn33 MIT 1 file body ≈ 932 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Deep single-page SEO analysis covering on-page elements, content quality, technical meta tags, schema, images, and performance.

As a process A 86/100 · Runs to the end — weak spots: 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
93/100
safety, quality, tests
Safety 60%
95
Quality 40%
89
Run on models
none yet
Process rating
A
86/100
Runs to the end
Progress reporting w 2
0
Failures and branches w 10
50
When it triggers w 12
70
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: seo-page (sickn33/agentic-awesome-skills)

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

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 · 1

    ✓ No critical or high findings

    Medium and low: 1
    • medium Broad scope meta-broad-allowed-tools SKILL.md:1
      Broad tool permissions pre-approved: Bash
      allowed-tools: Read Grep Glob Bash WebFetch

    Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "risk"
    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "date_added"
    • note frontmatter-key unknown frontmatter key "user-invokable"
    • note edit-residue the text marks something as outdated (lines 38): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 86/100

    • 0Progress reporting. Says nothing while it works
    • 50Failures and branches. 0 branches, has a failure section
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. Tools declared in frontmatter
    • 100Steps. 35 steps
    • 100Result and completion. Output format and completion criterion are stated
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 932 tokens
    • 100Running it twice. No mutating operations

    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)
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 2 example trigger phrases
    • +3Description length 222: enough signal without eating the budget
    • +4Structure: 17 headings
    • +3Step-by-step instructions: 35 items
    • +3Output format is stated explicitly
    • +4Has examples (1 code blocks)

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