Agent skill

Content Dates Audit

by thedaviddias in thedaviddias/Front-End-Checklist

Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.

MITAuto-check passedMarketing & SEO

Install Content Dates Audit

skills CLI
$ npx skills add thedaviddias/Front-End-Checklist --skill content-dates -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install thedaviddias/Front-End-Checklist content-dates --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/content-dates .claude/skills/content-dates && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
content-dates
GitHub stars
74k
Token cost
~691 tokens
SKILL.md length
271 words
Files
2 (incl. references)
Skills in repo
390
Repo updated
First seen
Licence
MIT

At a glance

Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.

  • Works in 4 steps: Add a visible publication date in the… → Add datePublished and dateModified to… → Add Open Graph article time tags to → …
  • Auditing blog posts for missing or inconsistent date markup
  • SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

For each article or blog page the skill runs a three-part check: is there a visible published date in the body or byline, does the JSON-LD Article or BlogPosting block carry `datePublished` and `dateModified` in ISO 8601 format, and does the page head include the `article:published_time` and `article:modified_time` Open Graph tags.

Fixes are spelled out as steps: add a machine-readable `time` element with a `datetime` attribute to the byline, extend the JSON-LD block, add the two meta tags, and make the CMS or build system update `dateModified` when content is saved. The guidance says to change `dateModified` only for meaningful edits, not trivial ones or every deploy, and gives the reasoning that search engines use dates to judge freshness. Fuller examples and framework-specific notes are in `references/rule.md`.

When your agent uses it

  • Auditing blog posts for missing or inconsistent date markup
  • Generating Article JSON-LD that includes datePublished and dateModified
  • Checking that a CMS template shows dates both on the page and in the head
  • Reviewing a pull request that changes an article layout

Example prompts

  • “Audit the posts under /blog for visible dates and Article JSON-LD.”
  • “Add datePublished and dateModified to the BlogPosting schema in our article template.”
  • “Google shows the wrong date for our guide pages. Check how the dates are marked up.”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Add a visible publication date in the page byline: March 15, 2024.
  2. Add datePublished and dateModified to the Article JSON-LD block
  3. Add Open Graph article time tags to
  4. Ensure your CMS or build system updates dateModified automatically on content saves.

What it can do on your machine

Read from SKILL.md and the folder at commit e8d14d0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are json and html).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • frontendchecklist.io

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Content Dates Audit loads about 691 tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 48 tokens; SKILL.md has 271 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~48
When it runs · the whole SKILL.md, loaded when a task matches
~691
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 271 words, ~691 tokens.

Download SKILL.mdSave it as .claude/skills/content-dates/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
content-dates
description
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.
metadata.category
seo
metadata.priority
medium
metadata.difficulty
intermediate
metadata.estimatedTime
10
metadata.source
frontendchecklist.io
metadata.url
https://frontendchecklist.io/rules/seo/content-dates

Show published and updated dates

Google uses publication and modification dates to assess content freshness, which influences rankings for time-sensitive queries. Visible dates also build user trust by signalling that content is current and maintained.

Quick Reference

  • Include a visible published date and a dateModified in JSON-LD for every article or blog post
  • Use ISO 8601 format (2024-03-15T10:00:00Z) in structured data; human-readable in the visible UI
  • Update dateModified only when content meaningfully changes — not on trivial edits

Check

On each article or blog page, check: (1) Is there a visible published date in the page body or byline? (2) Does the JSON-LD Article or BlogPosting block include datePublished and dateModified properties in ISO 8601 format? (3) Does the <head> include <meta property="article:published_time"> and <meta property="article:modified_time"> Open Graph tags?

Fix

  1. Add a visible publication date in the page byline: <time datetime="2024-03-15">March 15, 2024</time>.
  2. Add datePublished and dateModified to the Article JSON-LD block:
    json
    {
      "@type": "Article",
      "datePublished": "2024-03-15T10:00:00Z",
      "dateModified": "2024-11-20T14:30:00Z"
    }
  3. Add Open Graph article time tags to <head>:
    html
    <meta property="article:published_time" content="2024-03-15T10:00:00Z">
    <meta property="article:modified_time" content="2024-11-20T14:30:00Z">
  4. Ensure your CMS or build system updates dateModified automatically on content saves.

Explain

Google's freshness algorithm rewards recently published or updated content for time-sensitive queries. Structured date markup lets Google confidently surface the correct date in search snippets; without it, Google must guess from page text or HTTP headers, often producing wrong or missing dates.

Code Review

Verify that Article or BlogPosting JSON-LD includes both datePublished and dateModified in ISO 8601 format. Check that <time datetime='...'> elements in the body use machine-readable dates. Confirm dateModified updates when content changes, not just on every deploy.


For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/rules/seo/content-dates

© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/content-dates of thedaviddias/Front-End-Checklist.

  • SKILL.md
  • references/rule.md

Open the folder on GitHubat commit e8d14d0

Compare with similar skills

Content Dates Audit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Content Dates Audit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Content Dates Audit this skillthedaviddias/Front-End-Checklist74k—~691Automated safety check: PassMIT
HTML Metadata Fixeribelick/ui-skills9.5k2 repos~1.1kAutomated safety check: PassMIT
Roier SEOdavila7/claude-code-templates32k—~2.7kAutomated safety check: PassMIT
SEO Validatesoftspark/ai-toolkit179—~3.9kAutomated safety check: NotesApache-2.0
Site ArchitectureAvdLee/RocketSimApp80411 repos~3.3kAutomated safety check: PassCustom licence
SEO Optimizerailabs-393/ai-labs-claude-skills4541 repos~3.2kAutomated safety check: PassMIT

Similar skills

  • HTML Metadata Fixer

    ibelick/ui-skills

    Audits and fixes page titles, meta descriptions, canonical URLs, Open Graph and Twitter cards, favicons, JSON-LD and robots directives.

    9.5k GitHub starsUsed in 2 repos~1.1k tokens
    Marketing & SEOAuto-check passed
  • Roier SEO

    davila7/claude-code-templates

    Technical SEO auditor and fixer. An agent skill from davila7/claude-code-templates.

    32k GitHub stars~2.7k tokensUpdated today
    Frontend & DesignAuto-check passed
  • SEO Validate

    softspark/ai-toolkit

    SEO validator: meta/OG, Schema.org, hreflang, Core Web Vitals, crawlability.

    179 GitHub stars~3.9k tokensUpdated yesterday
    Marketing & SEOAuto-check: notes
  • Site Architecture

    AvdLee/RocketSimApp

    When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking.

    804 GitHub starsUsed in 11 repos~3.3k tokens
    Marketing & SEOAuto-check passed
  • SEO Optimizer

    ailabs-393/ai-labs-claude-skills

    This skill should be used when analyzing HTML/CSS websites for SEO optimization, fixing SEO issues, generating SEO reports, or implementing SEO best practices.

    454 GitHub starsUsed in 1 repo~3.2k tokens
    Marketing & SEOAuto-check passed
  • SEO

    ever-works/ever-works

    Optimize for search engine visibility and ranking. An agent skill from ever-works/ever-works.

    162 GitHub starsUsed in 10 repos~2.9k tokens
    Marketing & SEOAuto-check passed

More from thedaviddias/Front-End-Checklist

All 390 skills in this repo
  • FAQPage Schema Markup

    thedaviddias/Front-End-Checklist

    Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.

    74k GitHub stars~774 tokensUpdated 3 days ago
    Auto-check passed
  • Favicon Audit and Setup

    thedaviddias/Front-End-Checklist

    Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.

    74k GitHub stars~731 tokensUpdated 3 days ago
    Auto-check passed
  • Content Freshness Signals

    thedaviddias/Front-End-Checklist

    Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.

    74k GitHub stars~741 tokensUpdated 3 days ago
    Auto-check passed
  • Geo Meta Tags Audit

    thedaviddias/Front-End-Checklist

    Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).

    74k GitHub stars~763 tokensUpdated 3 days ago
    Auto-check passed
  • Improve a Front-End Checklist Rule

    thedaviddias/Front-End-Checklist

    Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.

    74k GitHub stars~1.3k tokensUpdated 3 days ago
    Auto-check passed
  • Front-End Checklist npm Package Finder

    thedaviddias/Front-End-Checklist

    Finds two or three well-maintained npm packages for a Front-End Checklist rule, checks download and release thresholds, and adds them to the rule's frontmatter.

    74k GitHub stars~989 tokensUpdated 3 days ago
    Auto-check passed

Questions about Content Dates Audit

What does Content Dates Audit do?

Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing. For each article or blog page the skill runs a three-part check: is there a visible published date in the body or byline, does the JSON-LD Article or BlogPosting block carry `datePublished` and `dateModified` in ISO 8601 format, and does the page head include the `article:published_time` and `article:modified_time` Open Graph tags.

When should I use Content Dates Audit?

Content Dates Audit fits situations like: auditing blog posts for missing or inconsistent date markup; generating Article JSON-LD that includes datePublished and dateModified; checking that a CMS template shows dates both on the page and in the head; reviewing a pull request that changes an article layout.

How do I install Content Dates Audit in Claude Code?

Run `npx skills add thedaviddias/Front-End-Checklist --skill content-dates -a claude-code`. Or copy the skill folder (skills/content-dates in thedaviddias/Front-End-Checklist) into .claude/skills/content-dates in your project. Claude Code loads it when a task matches its description.

How do I install Content Dates Audit in Codex?

Run `npx skills add thedaviddias/Front-End-Checklist --skill content-dates -a codex`. Or copy the skill folder (skills/content-dates in thedaviddias/Front-End-Checklist) into .agents/skills/content-dates in your project. Codex loads it when a task matches its description.

Can I use Content Dates Audit in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedaviddias/Front-End-Checklist --skill content-dates -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/content-dates, .gemini/skills/content-dates, .github/skills/content-dates and .opencode/skills/content-dates in your project.

What does Content Dates Audit need to run?

SKILL.md names no scripts, command-line tools or credentials: Content Dates Audit is instructions for the agent only.

Does Content Dates Audit access the network?

SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.

Is Content Dates Audit safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Content Dates Audit use?

Content Dates Audit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Content Dates Audit use?

About 691 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.

What are the alternatives to Content Dates Audit?

Skills that share tags, products or a category with Content Dates Audit: HTML Metadata Fixer (ibelick/ui-skills, 9.5k stars), Roier SEO (davila7/claude-code-templates, 32k stars), SEO Validate (softspark/ai-toolkit, 179 stars) and Site Architecture (AvdLee/RocketSimApp, 804 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Content Dates Audit?

thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,412 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.

Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.