content-dates

Use when auditing article or blog pages for date markup, generating Article JSON-LD with datePublished/dateModified, or checking whether a CMS template surfaces dates correctly.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

A tight, actionable, well-structured single-purpose skill with copy-paste code, explicit check/fix/review checkpoints, and a properly disclosed one-level reference. Its only real weakness is redundancy — the Explain and Code Review sections repeat the intro and Check sections, inflating token cost without adding guidance.

Suggestions

Remove the 'Explain' section (or collapse it to one non-redundant sentence inside the intro) — it restates the freshness rationale already given in the opening paragraph, which is a concept Claude already knows.

Merge 'Code Review' into 'Check' as a short post-fix verification list; the two sections currently enumerate nearly the same JSON-LD and <time> element checks.

Trim 'Quick Reference' to only the guidance not already covered by Check/Fix (e.g., the ISO 8601 format rule and the dateModified-only-on-meaningful-changes policy) instead of restating all three bullet points.

Dimension	Reasoning	Score
Conciseness	The body is mostly actionable but carries avoidable redundancy: the 'Explain' section re-explains Google's freshness rationale already stated in the intro (a concept Claude knows), 'Code Review' ('Verify that Article or BlogPosting JSON-LD includes both datePublished and dateModified…') largely restates 'Check', and 'Quick Reference' duplicates Check/Fix items — more than the minor trimming of the anchor above.	3 / 5
Actionability	Fully executable, copy-paste-ready guidance throughout: a concrete '<time datetime="2024-03-15">March 15, 2024</time>' element, a complete Article JSON-LD block with both date properties, Open Graph meta tags, and three specific inspection questions — the common cases are covered with no meaningful gaps.	5 / 5
Workflow Clarity	A coherent Check → Fix → Code Review flow with explicit validation checkpoints (three numbered inspection questions, four numbered fix steps, and post-fix confirmation points); as a single-purpose skill under 50 lines with an unambiguous action, it meets the top anchor under the simple-skill provision — only the loop-back re-check instruction is implicit rather than explicit.	5 / 5
Progressive Disclosure	SKILL.md serves as a clean overview and points to a clearly signaled, verified one-level-deep reference ('see references/rule.md') that holds the full examples and verification details; the split is appropriate and navigation is easy, matching the top anchor.	5 / 5
	Total	18 / 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 with an explicit, well-formed 'Use when…' trigger clause and three concrete, domain-specific actions. It is clearly distinguishable from other skills; the only weakness is modest synonym coverage and omission of the visible-date/Open Graph aspects of the task.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'auditing article or blog pages for date markup', 'generating Article JSON-LD with datePublished/dateModified', 'checking whether a CMS template surfaces dates correctly' — but omits capabilities the skill body covers (visible date display, Open Graph time tags), leaving minor gaps that keep it below the comprehensive anchor.	4 / 5
Completeness	The 'Use when…' clause explicitly states when to invoke the skill with concrete trigger phrases, and the gerund actions (auditing, generating, checking) explicitly state what it does — both questions are answered explicitly, matching the top anchor rather than the 'when could be more specific' anchor below it.	5 / 5
Trigger Term Quality	Good natural keyword coverage ('article', 'blog pages', 'date markup', 'Article JSON-LD', 'datePublished', 'dateModified', 'CMS template'), but common variations users would actually say — 'published date', 'last updated', 'structured data', 'freshness' — are missing, so it falls short of the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (SEO date markup on article/blog pages) with distinct technical triggers (JSON-LD datePublished/dateModified, CMS template date surfacing), making conflict with other skills minimal.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/content-dates/SKILL.md
Commit: 7bfd868

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.