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

92%

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%

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

The content is actionable and well-structured with executable examples, a clear workflow, and a clean one-level reference. The only weakness is mild redundancy: the freshness rationale is explained twice, which slightly hurts token efficiency.

Suggestions

Consolidate the freshness rationale — state it once (e.g. in 'Explain') and trim the opening paragraph to avoid repeating content Google-ranking logic Claude already knows.

Consider merging or trimming the 'Explain' and 'Code Review' sections where they overlap (both restate ISO 8601 and dateModified-on-change guidance) to tighten the token budget.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete code, but the freshness rationale is restated in both the intro and the 'Explain' section, adding conceptual explanation Claude already knows; it could be tightened without losing clarity.	2 / 3
Actionability	It provides fully executable JSON-LD and HTML snippets, a <time datetime> example, and a specific ISO 8601 format — copy-paste ready with no pseudocode.	3 / 3
Workflow Clarity	As a single-task skill it has a clear Check → Fix → Code Review sequence with an explicit verification checklist ('Verify that ... JSON-LD includes both datePublished and dateModified', 'Confirm dateModified updates when content changes').	3 / 3
Progressive Disclosure	The skill is under 50 lines, well-organized into clear sections, and points to a single verified one-level-deep reference ('see references/rule.md') for full details, matching the simple-skill allowance for a top score.	3 / 3
	Total	11 / 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.

This is a strong description: it opens with an explicit 'Use when' trigger, lists three concrete actions, and uses natural language a user would actually say. It clearly answers both what the skill does and when to use it with low conflict risk.

Dimension	Reasoning	Score
Specificity	The description lists three distinct concrete actions — 'auditing article or blog pages for date markup', 'generating Article JSON-LD with datePublished/dateModified', and 'checking whether a CMS template surfaces dates correctly' — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	It opens with an explicit 'Use when ...' trigger clause and names multiple actions, clearly answering both what the skill does and when to invoke it.	3 / 3
Trigger Term Quality	Natural terms a user would say are well covered ('article or blog pages', 'dates', 'JSON-LD', 'CMS template', 'datePublished/dateModified'), matching the anchor for good coverage of natural terms rather than just jargon.	3 / 3
Distinctiveness Conflict Risk	The niche is narrow and specific — date markup on article/blog pages with structured-data and CMS signals — making it clearly distinguishable and unlikely to trigger for unrelated skills.	3 / 3
	Total	12 / 12 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: 48405aa

Reviewed: about 9 hours 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.