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.
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.
$ npx skills add thedaviddias/Front-End-Checklist --skill content-dates -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist content-dates --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "content-dates" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/content-dates into .claude/skills/content-dates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-dates", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/content-datesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add thedaviddias/Front-End-Checklist --skill content-dates -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist content-dates --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/content-dates .agents/skills/content-dates && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "content-dates" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/content-dates into .agents/skills/content-dates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-dates", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill content-dates -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist content-dates --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/content-dates .cursor/skills/content-dates && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "content-dates" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/content-dates into .cursor/skills/content-dates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-dates", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/thedaviddias/Front-End-Checklist.git --path skills/content-dates--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add thedaviddias/Front-End-Checklist --skill content-dates -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist content-dates --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/content-dates .gemini/skills/content-dates && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "content-dates" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/content-dates into .gemini/skills/content-dates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-dates", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install thedaviddias/Front-End-Checklist content-datesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add thedaviddias/Front-End-Checklist --skill content-dates -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/content-dates .github/skills/content-dates && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "content-dates" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/content-dates into .github/skills/content-dates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-dates", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill content-dates -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install thedaviddias/Front-End-Checklist content-dates --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/content-dates .opencode/skills/content-dates && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "content-dates" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/content-dates into .opencode/skills/content-dates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-dates", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
content-datesAudits 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.
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`.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit e8d14d0. It shows what the files ask for, not the result of running them.
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.
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.
Links to these hosts (documentation or services it may open):
frontendchecklist.ioFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 271 words, ~691 tokens.
.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.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.
dateModified in JSON-LD for every article or blog post2024-03-15T10:00:00Z) in structured data; human-readable in the visible UIdateModified only when content meaningfully changes — not on trivial editsOn 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?
<time datetime="2024-03-15">March 15, 2024</time>.datePublished and dateModified to the Article JSON-LD block:{
"@type": "Article",
"datePublished": "2024-03-15T10:00:00Z",
"dateModified": "2024-11-20T14:30:00Z"
}<head>:<meta property="article:published_time" content="2024-03-15T10:00:00Z">
<meta property="article:modified_time" content="2024-11-20T14:30:00Z">dateModified automatically on content saves.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.
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
SKILL.md and 1 other file (references) in skills/content-dates of thedaviddias/Front-End-Checklist.
Open the folder on GitHubat commit e8d14d0
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Content Dates Audit this skillthedaviddias/Front-End-Checklist | 74k | — | ~691 | Automated safety check: Pass | MIT | |
| HTML Metadata Fixeribelick/ui-skills | 9.5k | 2 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Roier SEOdavila7/claude-code-templates | 32k | — | ~2.7k | Automated safety check: Pass | MIT | |
| SEO Validatesoftspark/ai-toolkit | 179 | — | ~3.9k | Automated safety check: Notes | Apache-2.0 | |
| Site ArchitectureAvdLee/RocketSimApp | 804 | 11 repos | ~3.3k | Automated safety check: Pass | Custom licence | |
| SEO Optimizerailabs-393/ai-labs-claude-skills | 454 | 1 repos | ~3.2k | Automated safety check: Pass | MIT |
ibelick/ui-skills
Audits and fixes page titles, meta descriptions, canonical URLs, Open Graph and Twitter cards, favicons, JSON-LD and robots directives.
davila7/claude-code-templates
Technical SEO auditor and fixer. An agent skill from davila7/claude-code-templates.
softspark/ai-toolkit
SEO validator: meta/OG, Schema.org, hreflang, Core Web Vitals, crawlability.
AvdLee/RocketSimApp
When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking.
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.
ever-works/ever-works
Optimize for search engine visibility and ranking. An agent skill from ever-works/ever-works.
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.
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.
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.
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).
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.
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.
Categories
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.
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.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Content Dates Audit is instructions for the agent only.
SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.
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.
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.
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.
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.
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.