SKILLEMALL.ai
GitHub ↗ RU Sign in

CD seo

Run a broad SEO audit across technical SEO, on-page SEO, schema, sitemaps, content quality, AI search readiness, and GEO / Audit SEO menyeluruh (Technical, On-Page, Schema, Sitemap, E-E-A-T, GEO)

roedyrustam/vibes-plug Agent Skills author: roedyrustam MIT 5 files body ≈ 2 420 tokens Open the sourcegithub.com↗ analyzed 4 h ago

Run a broad SEO audit across technical SEO, on-page SEO, schema, sitemaps, content quality, AI search readiness, and GEO / Audit SEO menyeluruh (Technical…

As a process D 35/100 · Unfinished process — References files that are not bundled: /features, /blog

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
C
80/100
safety, quality, tests
Safety 60%
100
Quality 40%
49
Run on models
none yet
Process rating
D
35/100
Unfinished process
References files that are not bundled: /features, /blog
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
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: 5. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Unexpected scalar at node end at line 3, column 23: author: "Roedy Rustam" ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: /features
  • warning missing-ref reference to a missing file: /blog
  • note edit-residue the text marks something as outdated (lines 30): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 35/100

Will not run. References files that are not bundled: /features, /blog
  • 0Tools and files. 2 referenced file(s) missing: /features, /blog
  • 0Result and completion. Does not say what the result is
  • 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
  • 20When it triggers. No condition that starts the skill
  • 100Steps. 30 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2420 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

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -44 reference files, but SKILL.md never points to them: the model will not open them
  • +1No license
  • +2Single-language instructions
  • +3Description length 195: enough signal without eating the budget
  • +4Structure: 26 headings
  • +3Step-by-step instructions: 30 items
  • +4Has examples (7 code blocks)

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