agentleFS
Sign inStart free
Discriminative-shoji607Discriminative-shoji607/ui-skills/skills/fixing-metadata/SKILL.md

fixing-metadata

Skill3 starsChanged 5 months agoMITView on GitHub

Audit and fix HTML metadata including page titles, meta descriptions, canonical URLs, Open Graph tags, Twitter cards, favicons, JSON-LD structured data, and robots directives. Use when adding SEO metadata, fixing social share previews, reviewing Open Graph tags, setting up canonical URLs, or shipping new pages that need correct meta tags.

We split this skill into the rules it gives an agent

22 rules. 21 are common, 0 are distinctive, and 1 is very specific to this project.

  • 21

    Common

    Most of the 6 edited versions we read keep these.

  • 0

    Distinctive

    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. Common:

    Ensure title, description, canonical, and og:url all agree with each other

    line 16
  2. Common:

    Verify social cards render correctly on a real URL, not localhost

    line 17
  3. Common:

    Keep diffs minimal and scoped to metadata only — do not refactor unrelated code

    line 18
  4. Common:

    do not emit duplicate title, description, canonical, or robots tags

    line 48
  5. Common:

    every page must have safe defaults for title and description

    line 51
  6. Common:

    every page must have a title

    line 55
  7. Common:

    use a consistent title format across the site

    line 56
  8. Common:

    keep titles short and readable, avoid stuffing

    line 57
  9. Common:

    use noindex only for private, duplicate, or non-public pages

    line 64
  10. Common:

    prefer correct image dimensions and stable aspect ratios

    line 73
  11. Common:

    use a sensible og:type, usually website or article

    line 75
  12. Common:

    do not add JSON-LD unless it clearly maps to real page content

    line 88
  13. Common:

    do not invent ratings, reviews, prices, or organization details

    line 90
  14. Common:

    prefer one structured data block per page unless required

    line 91
  15. Common:

    add hreflang alternates only when pages truly exist

    line 97
  16. Common:

    prefer minimal changes, do not refactor unrelated code

    line 102
  17. Common:

    do not migrate frameworks or SEO libraries unless requested

    line 103
  18. Very specific:

    follow the project's existing metadata pattern (Next.js metadata API, react-helmet, manual head, etc.)

    line 104
  19. Common:

    ensure title, description, canonical, and og:url agree

    line 109
  20. Common:

    verify social cards on a real URL, not localhost

    line 110
  21. Common:

    prefer stable, boring metadata over clever or dynamic

    line 111
  22. Common:

    keep diffs minimal and scoped to metadata only

    line 112

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “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

Workflow

  1. Identify pages with missing or incorrect metadata (titles, descriptions, canonical, OG tags)
  2. Audit against the priority rules below — fix critical issues (duplicates, indexing) first
  3. Ensure title, description, canonical, and og:url all agree with each other
  4. Verify social cards render correctly on a real URL, not localhost
  5. Keep diffs minimal and scoped to metadata only — do not refactor unrelated code

when to apply

Reference these guidelines when:

  • adding or changing page titles, descriptions, canonical, robots
  • implementing Open Graph or Twitter card metadata
  • setting favicons, app icons, manifest, theme-color
  • building shared SEO components or layout metadata defaults
  • adding structured data (JSON-LD)
  • changing locale, alternate languages, or canonical routing
  • shipping new pages, marketing pages, or shareable links

rule categories by priority

prioritycategoryimpact
1correctness and duplicationcritical
2title and descriptionhigh
3canonical and indexinghigh
4social cardshigh
5icons and manifestmedium
6structured datamedium
7locale and alternateslow-medium
8tool boundariescritical

quick reference

1. correctness and duplication (critical)

  • define metadata in one place per page, avoid competing systems
  • do not emit duplicate title, description, canonical, or robots tags
  • metadata must be deterministic, no random or unstable values
  • escape and sanitize any user-generated or dynamic strings
  • every page must have safe defaults for title and description

2. title and description (high)

  • every page must have a title
  • use a consistent title format across the site
  • keep titles short and readable, avoid stuffing
  • shareable or searchable pages should have a meta description
  • descriptions must be plain text, no markdown or quote spam

3. canonical and indexing (high)

  • canonical must point to the preferred URL for the page
  • use noindex only for private, duplicate, or non-public pages
  • robots meta must match actual access intent
  • previews or staging pages should be noindex by default when possible
  • paginated pages must have correct canonical behavior

4. social cards (high)

  • shareable pages must set Open Graph title, description, and image
  • Open Graph and Twitter images must use absolute URLs
  • prefer correct image dimensions and stable aspect ratios
  • og:url must match the canonical URL
  • use a sensible og:type, usually website or article
  • set twitter:card appropriately, summary_large_image by default

5. icons and manifest (medium)

  • include at least one favicon that works across browsers
  • include apple-touch-icon when relevant
  • manifest must be valid and referenced when used
  • set theme-color intentionally to avoid mismatched UI chrome
  • icon paths should be stable and cacheable

6. structured data (medium)

  • do not add JSON-LD unless it clearly maps to real page content
  • JSON-LD must be valid and reflect what is actually rendered
  • do not invent ratings, reviews, prices, or organization details
  • prefer one structured data block per page unless required

7. locale and alternates (low-medium)

  • set the html lang attribute correctly
  • set og:locale when localization exists
  • add hreflang alternates only when pages truly exist
  • localized pages must canonicalize correctly per locale

8. tool boundaries (critical)

  • prefer minimal changes, do not refactor unrelated code
  • do not migrate frameworks or SEO libraries unless requested
  • follow the project's existing metadata pattern (Next.js metadata API, react-helmet, manual head, etc.)

review guidance

  • fix critical issues first (duplicates, canonical, indexing)
  • ensure title, description, canonical, and og:url agree
  • verify social cards on a real URL, not localhost
  • prefer stable, boring metadata over clever or dynamic
  • keep diffs minimal and scoped to metadata only

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.
  • Other versions9 projects use a version of this.

    Word for word · 3

    1. ibelick/ui-skills★ 10k100% same
    2. master5d/claude-design-skills★ 26100% same
    3. julianromli/faiz-skills★ 16100% same

    Edited · 5

    1. agentset-ai/agentset★ 2.1k87% same
    2. kapishdima/soundcn★ 86487% same
    3. hsynozdamar-byte/claude-skills-edited★ 496% same
    4. ClaireAll/skills★ 295% same
    5. sanmidable/skills★ 296% same

    Wrote their own version · 1

    1. jscraik/Agent-Skills★ 9same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use create-design-md, better-interface and 7 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • ItamarZand88Skill

      create-design-md

      Create a new DESIGN.md file for any website, app, or custom design system. Use when the user wants to document a design system in DESIGN.md format, extract design tokens from a URL or existing CSS, create a custom design system from scratch, author a DESIGN.md for their own project, or contribute a new design to the awesome-design-md collection. Also trigger when user mentions "design system documentation", wants to formalize their app's visual language, or asks to create or generate a DESIGN.md file.

      Also in 4 projects that use this

    • AnasX7Skill

      better-interface

      Combines all of the `better-*` skills into a single review across accessibility, layout, writing, typography, color and UI polish.

      Also in 3 projects that use this

    • AnasX7Skill

      better-accessibility

      Helps your project comply with accessibility standards and best practices.

      Also in 3 projects that use this

    • VercelSkill

      emil-design-eng

      This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

      Also in 4 projects that use this

    • +5 more from AnasX7
  • In this repository5 other files it gives its agents.

Does it work?

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

Reviews can't be read right now.

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