agentleFS
ridelink0ridelink0/ultimate-frontend-skills/skills/link-preview/SKILL.md

link-preview

Skill7 starsChanged 12 days agoMITView on GitHub

Build and validate per-page rich link previews with 1200x630 PNG images, Open Graph and Twitter metadata, original visual references and source provenance. Uses deep research and image deep research before review.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every emitted public HTML page needs its own title, description, canonical URL, 1200x630 PNG, …

    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

Link preview cards

Load deep-research for the current Open Graph/crawler contract and image-deep-research when selecting visual references or licensed imagery. Open references before describing them. Evaluate subject specificity, title readability, truthful imagery and crop-safe content; do not present AI tell heuristics as a provenance detector. Keep private page content out of public cards.

Every emitted public HTML page needs its own title, description, canonical URL, 1200x630 PNG, og:title/description/image/image:width/image:height/image:alt/url/type/ site_name and twitter:card/image/image:alt. Use absolute HTTPS image/page URLs.

node scripts/link-preview.mjs <built-dir> <https://site.example/> creates original title-based PNG cards at build time and installs metadata for each page. It uses the existing headless browser, local system fonts and no external media. Supply real title and description tags first. The command intentionally updates those preview tags; preserve a custom approved card by using the validator alone. node scripts/link-preview.mjs <built-dir> <https://site.example/> --check checks emitted metadata and local PNG dimensions without changing files.

Inspect generated images before shipping. After deploy verify image status, Content-Type, crawl access, absolute URLs and actual platform preview. Platforms cache cards; local validation does not prove a remote preview refreshed.

Sources checked 2026-11-01: Open Graph, Google canonical URLs. The old X large-image-card documentation URL redirects to the general API docs; its current detailed limits were not verified. 1200x630 is Gev's delivery contract.

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.