agentleFS
Sign inStart free
ronaldshipsronaldships/foundvia-discovery/skills/seo-slug-dates/SKILL.md

seo-slug-dates

Skill29 starsChanged 38 days agoMITView on GitHub

Audit publication dates, dateModified, and sitemap lastmod for truthful source records, and migrate away from synthetic slug-derived history. Use when page dates are generated, inaccurate, or reset on every build.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use scripts/dates.ts to validate explicit date records.

    line 12
  2. Distinctive:

    Check displayed dates, schema, and sitemap consistently.

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Truthful content dates

This skill keeps its existing name for discoverability but withdraws the former hash-based date-distribution approach. Deterministic invented dates are still invented. Shared dates are valid when the underlying events happened together.

Inspect callers of publishedAt, updatedAt, datePublished, dateModified, and sitemap lastmod. Use actual CMS, database, frontmatter, or verified content history; a deployment timestamp is not automatically a significant content-update timestamp. Preserve real dates. Omit optional dates when no reliable record exists.

Use scripts/dates.ts to validate explicit date records. It exports contentDates; the old slug-generated-date functions have been removed. Update callers intentionally and run the project's typecheck/build before deployment. Document the migration rather than silently changing dates across a live site.

Check displayed dates, schema, and sitemap consistently. Confirm chronology and meaningful content changes; do not require dates to differ across pages. No ranking or citation improvement is promised.

Source: Google sitemap guidance. See migration explanation.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free