CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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.

Highly actionable content with copy-paste-ready examples, a clear check-then-fix workflow, and a well-signaled single external reference. The main drag is redundancy: the intro, Explain, and Code Review sections repeat the same freshness rationale and checks, spending tokens on concepts Claude already knows.

Suggestions

Merge the 'Explain' section into the intro or trim it to one sentence — it currently re-explains Google's freshness ranking rationale that Claude already knows and that the intro already states.

Collapse 'Code Review' into 'Check' — the three verification points duplicate the check questions almost verbatim; a single checklist avoids repeating the same content twice.

Add an explicit validation checkpoint after the Fix steps (e.g., 'Verify the JSON-LD with Google's Rich Results Test') so the workflow ends with a concrete post-fix verification step rather than an implicit one.

DimensionReasoningScore

Conciseness

The body is mostly efficient with tight code snippets, but the "Explain" section ("Google's freshness algorithm rewards recently published or updated content...") restates the intro's rationale, and "Code Review" largely repeats the "Check" and "Fix" sections — redundant content that could be trimmed. This sits at 'mostly efficient but includes some unnecessary explanation' rather than the minor-trimming level above.

3 / 5

Actionability

The Fix section provides copy-paste-ready markup for the common cases — a `<time datetime>` element, an Article JSON-LD block with ISO 8601 values, and Open Graph meta tags — and the Check section lists three concrete, verifiable questions. Specific examples fully cover the common cases, matching the top anchor.

5 / 5

Workflow Clarity

A clear Check → Fix → Code Review sequence with concrete steps, but no explicit post-fix validation checkpoint (e.g., re-verify with a structured-data validator) — the verification is implicit in the Code Review checklist. Not 5 because the checkpoint is not an explicit step in the workflow; not 3 because the sequence is well-defined with a verification pass.

4 / 5

Progressive Disclosure

The body is under 50 lines, cleanly sectioned (Quick Reference, Check, Fix, Explain, Code Review), and ends with a clearly signaled one-level-deep pointer to `references/rule.md`, which exists and holds the full code examples and framework guidance — matching the well-organized simple-skill / clear-reference pattern.

5 / 5

Total

17

/

20

Passed

Description

83%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, specific description with a clear niche and an explicit 'Use when...' trigger covering three concrete tasks. Its main weakness is fused what/when phrasing and missing common synonyms like 'structured data' or 'published/updated dates'.

DimensionReasoningScore

Specificity

The description lists three concrete, specific actions — "auditing article or blog pages for date markup", "generating Article JSON-LD with datePublished/dateModified", "checking whether a CMS template surfaces dates correctly" — which comprehensively cover the skill's domain, matching the top anchor rather than the 'minor gaps' level below.

5 / 5

Completeness

Both elements are explicit — the gerund actions state what the skill does and "Use when auditing... or generating... or checking" gives the trigger — but what and when are fused into one clause with no separate concrete trigger phrases (e.g., "when the user mentions missing dates"), placing it between the 4 and 5 anchors and closer to 4.

4 / 5

Trigger Term Quality

Natural terms like "date markup", "Article JSON-LD", "datePublished/dateModified", "CMS template", and "article or blog pages" are present, but common user phrasings such as "structured data", "published/updated dates", or "schema" are missing, so coverage falls just short of the comprehensive synonym-level anchor.

4 / 5

Distinctiveness Conflict Risk

The niche is narrow and well-defined — date markup on article/blog pages via JSON-LD and Open Graph tags — with trigger terms unlikely to fire for sibling SEO or structured-data skills, matching the 'clear niche with distinct triggers' anchor.

5 / 5

Total

18

/

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/content-dates/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.