CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

77%

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

78%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.

The body is a well-organized, appropriately brief overview for a simple audit/fix skill: it gives concrete schema types and required properties, a coherent Check→Fix→Code Review sequence, and cleanly delegates implementation detail to an existing one-level reference file. The only notable improvement is trimming the opening sentence explaining what structured data does, which Claude already knows.

DimensionReasoningScore

Conciseness

The body is lean and sectioned, with one concept-explanation sentence Claude already knows — 'Structured data helps your content appear as rich results... significantly increasing click-through rates and visibility' — which could be trimmed. This is a minor instance of over-explanation, matching the 'efficient; minor instances of over-explanation that could be trimmed' anchor rather than the fully lean anchor 5.

4 / 5

Actionability

Concrete, actionable specifics are given: schema types ('Article, NewsArticle, or BlogPosting'), required properties ('headline, image, datePublished, and author'), and the JSON-LD format directive, with full executable code in references/rule.md. Minor gaps remain — 'with correct metadata for the current page' is vague and no inline example of the JSON-LD block appears — so it is mostly executable guidance rather than fully copy-paste ready (anchor 4, not 5).

4 / 5

Workflow Clarity

A clear Check → Fix → Explain → Code Review sequence is present with verification checkpoints mentioned ('Verify that the page contains valid Article structured data with all required properties', 'describe how to verify the final page output'). Not a 5 because there is no explicit post-fix re-validation feedback loop or named validation tooling in the body itself; not capped at 3 since this is a non-destructive, single-purpose audit skill.

4 / 5

Progressive Disclosure

The body is a concise overview with well-organized sections and a single clearly signaled one-level-deep reference — 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — and that file exists and holds the implementation detail and code example without further nesting. This matches the clear-overview, well-signaled one-level-deep reference anchor.

5 / 5

Total

17

/

20

Passed

Description

66%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.

The description has an explicit and well-scoped 'Use when' trigger plus a useful verification directive, and includes natural SEO audit keywords. Its weaknesses are that the capability statement is embedded in the trigger clause rather than standalone, action coverage is narrow, and the broad category-level trigger terms create real overlap risk with sibling SEO skills.

Suggestions

Lead with a standalone capability statement in third person (e.g., 'Audits pages for valid Article structured data and verifies the rendered HTML and HTTP response...') followed by the 'Use when' clause, so both what and when are explicit.

Add distinctive trigger synonyms such as 'JSON-LD', 'schema markup', or 'rich results' that are specific to Article structured data to reduce overlap with sibling SEO skills that also trigger on 'metadata', 'crawlability', and 'indexability'.

Narrow the trigger terms to what is distinctive of this rule (e.g., 'Use when auditing Article/NewsArticle/BlogPosting structured data') rather than the whole SEO category.

DimensionReasoningScore

Specificity

Names the domain ('Implement valid Article structured data') and two concrete actions — 'auditing metadata, crawlability, structured data, or indexability' and 'Verify the rendered HTML and HTTP response rather than relying only on source files' — which matches the '1-2 concrete actions, but not comprehensive' anchor. It is not a 4 because it does not enumerate several distinct specific actions beyond the audit/verify pair.

3 / 5

Completeness

Both parts are present: an explicit 'Use when auditing metadata, crawlability, structured data, or indexability' trigger clause and a 'what' expressed through 'Verify the rendered HTML and HTTP response rather than relying only on source files'. Not a 5 because the capability statement is folded into the 'when' clause rather than being a clear standalone 'what' with concrete trigger phrases.

4 / 5

Trigger Term Quality

Good natural keyword coverage — 'metadata', 'crawlability', 'structured data', 'indexability', 'rendered HTML', 'HTTP response' — terms a user auditing SEO would plausibly say. Not a 5 because common synonyms and phrasings like 'JSON-LD', 'schema markup', 'rich results', or 'SEO audit' are missing.

4 / 5

Distinctiveness Conflict Risk

The qualifier 'related to Implement valid Article structured data' scopes it, but the leading triggers 'metadata, crawlability, structured data, or indexability' are generic across the entire SEO category and would equally fire sibling checklist skills (canonical URLs, robots rules, meta tags), so overlap risk with similar skills remains. Not a 4 because the overlap extends beyond just closely related skills.

3 / 5

Total

14

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/article/SKILL.md

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.