SKILLEMALL.ai
GitHub ↗ RU Sign in

AB schema-markup

Design, validate, and optimize schema.org structured data for eligibility, correctness, and measurable SEO impact. Use when the user wants to add, fix, audit, or scale schema markup (JSON-LD) for rich results. This skill evaluates whether schema should be implemented, what types are valid, and how to deploy safely according to Google guidelines.

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 1 710 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Design, validate, and optimize schema.org structured data for eligibility, correctness, and measurable SEO impact. Use when the user wants to add, fix, audit…

As a process B 71/100 · Nearly there — weak spots: inputs and preconditions, progress reporting

AnalyzerWriting and documentsMarketingtype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
87
Run on models
none yet
Process rating
B
71/100
Nearly there
Inputs and preconditions w 11
0
Progress reporting w 2
0
Failures and branches w 10
55
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: 1. 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 71/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 55Failures and branches. 1 branches
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 85Steps. 85 steps, 1 vague phrases
    • 100Tools and files. Tools declared in frontmatter
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1710 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

    • +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 347: enough signal without eating the budget
    • +4Structure: 50 headings
    • +3Step-by-step instructions: 85 items
    • +3Output format is stated explicitly
    • +4Has examples (1 code blocks)

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