CtrlK
BlogDocsLog inGet started
Tessl Logo

article

Use when auditing metadata, crawlability, structured data, or indexability related to Implement valid Article structured data. Verify the rendered HTML and HTTP response rather than relying only on source files.

65

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/article/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

A lean, well-organized audit skill that correctly delegates implementation detail to a single real reference file, but the body opens by explaining a concept Claude already knows, lacks an in-body executable code example, and has no explicit post-fix validation step.

Suggestions

Trim or remove the opening "Structured data helps your content appear as rich results..." sentence — Claude already knows what structured data and rich results are.

Add a minimal copy-paste JSON-LD template (a few lines) in the Fix section so the body is actionable without opening the reference.

Add an explicit post-fix verification step (e.g., re-validate the rendered HTML and JSON-LD with a structured data testing tool) to close the Check→Fix loop.

DimensionReasoningScore

Conciseness

Mostly lean, but the opening "Structured data helps your content appear as rich results (like Top Stories or rich snippets), significantly increasing click-through rates and visibility" explains a concept Claude already knows.

2 / 3

Actionability

Quick Reference lists concrete types/properties ("Article, NewsArticle, or BlogPosting", "headline, image, datePublished, and author"), but the Fix step "Add a JSON-LD script block containing the Article schema with correct metadata" gives no executable example in the body — the actual code is delegated to the reference.

2 / 3

Workflow Clarity

A Check→Fix sequence is present ("Verify that the page contains valid Article structured data" then "Add a JSON-LD script block..."), but there is no explicit re-validation checkpoint after the fix.

2 / 3

Progressive Disclosure

Clear overview with a well-signaled one-level-deep reference — "see `references/rule.md`" (verified present) — and no nested reference chaining.

3 / 3

Total

9

/

12

Passed

Description

100%

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 with an explicit "Use when" trigger, concrete auditing/verification actions, and natural SEO terms, well-scoped to Article structured data. It clearly answers both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "auditing metadata, crawlability, structured data, or indexability" and "Verify the rendered HTML and HTTP response" — rather than vague language.

3 / 3

Completeness

Explicitly answers both: the "Use when auditing..." clause gives the trigger, and "Verify the rendered HTML and HTTP response rather than relying only on source files" states what to do.

3 / 3

Trigger Term Quality

Covers natural terms an SEO practitioner would actually say — "metadata", "crawlability", "structured data", "indexability", "rendered HTML and HTTP response" — with good variation.

3 / 3

Distinctiveness Conflict Risk

Scoped to "Implement valid Article structured data" with distinct SEO-audit triggers, making it a clear niche unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.