CtrlK
BlogDocsLog inGet started
Tessl Logo

seo-check

Run an SEO + structured-data audit of the site (wraps `bun run seo:audit`) and verify per-page SEO wiring and JSON-LD. Use before pushing, or when asked to check SEO.

76

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary lean, actionable skill body: exact commands and file paths, a clear read-only boundary, well-sequenced checks, and a concrete reporting format. No bundle files exist, and none are needed at this size.

DimensionReasoningScore

Conciseness

The 22-line body has zero padding: no explanation of what SEO or JSON-LD is, and every step names exact files or commands ("bun run seo:audit", "src/hooks/useSEO.ts", "public/sitemap.xml"). Every token earns its place, matching the lean anchor.

5 / 5

Actionability

Fully actionable: a copy-paste-ready command, exact file paths for each check ("src/pages/Index.tsx", "src/utils/structuredData.ts"), and concrete pass criteria ("unique title, description", "one <h1> per page, logical order, no skipped levels"). As an instruction-only skill, the guidance is specific and executable throughout.

5 / 5

Workflow Clarity

Five clearly sequenced steps (audit → per-page wiring → JSON-LD → sitemap/robots → headings) culminating in a pass/fail report with file:line references. The skill is read-only, so the destructive/batch validation cap does not apply, and the single-purpose workflow with the report checkpoint fits the level-5/simple-skill exception.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external reference files (none exist in the bundle), organized into clear Steps and Report sections with a boundary statement ("Read-only unless the user asks you to fix findings"). Per the guideline, this qualifies for the top score with well-organized sections alone.

5 / 5

Total

20

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete actions with the underlying command, an explicit when-to-use clause, and natural trigger terms in a distinct niche. Only minor keyword-coverage and capability-mention gaps keep it from perfection.

DimensionReasoningScore

Specificity

"Run an SEO + structured-data audit of the site (wraps `bun run seo:audit`)", "verify per-page SEO wiring and JSON-LD" names several specific actions including the exact command. Minor gaps in coverage (sitemap/robots and heading checks from the body are not mentioned), so it fits the 'several specific actions; minor gaps' anchor rather than the comprehensive level 5.

4 / 5

Completeness

Explicitly answers what ("Run an SEO + structured-data audit... verify per-page SEO wiring and JSON-LD") and when ("Use before pushing, or when asked to check SEO") with concrete trigger phrases. This matches the level-5 anchor; level 4 requires a 'when' that is only implicit or less specific, which is not the case here.

5 / 5

Trigger Term Quality

Includes natural terms users would say: "SEO", "structured-data", "JSON-LD", "audit", "check SEO", and the workflow moment "before pushing". A few natural variants are missing (e.g. "sitemap", "meta tags", "search ranking"), matching the 'good keyword coverage; a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

SEO auditing with structured-data/JSON-LD triggers is a clear niche unlikely to fire for unrelated skills; "asked to check SEO" and "before pushing" are distinct triggers. Fits the 'clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
RaquelSousa/kel-portfolio-2.0
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.