adapto-seo-wirelisted

Make stored SEO metadata actually render — a one-time, consent-gated, framework-aware setup that wires a head-render layer (title, meta, OG/Twitter, JSON-LD) reading the _adapto_seo collection, plus generates llms.txt / llms-full.txt from your content inventory. Edits your app templates (never the read-client), only after you approve the exact changes.
adaptocms/adapto-cms-agent-skills · ★ 1 · Data & Documents · score 75

Install: claude install-skill adaptocms/adapto-cms-agent-skills

# adapto:seo-wire `adapto:content-upload` **stores** SEO metadata in `_adapto_seo`, but the starters render only `<title>`. This skill **makes it render**: a **one-time, per-project** setup that installs a head-render layer reading `_adapto_seo` (emitting `<title>`, meta description, OG/Twitter tags, and JSON-LD) and generates `llms.txt` / `llms-full.txt` from your inventory. It is **consent-gated** and **only edits your own app templates** — **never the read-client** ([forbidden-actions.md](../../shared/forbidden-actions.md); see [seo-standards.md](../../shared/seo-standards.md) for what's rendered). ## When to use - "Make my SEO/meta render", "wire up the head tags", "generate llms.txt", "the OG tags aren't showing". - Once per project, after `adapto:content-upload` has written `_adapto_seo` items (or alongside the first upload). ## When not to use - Storing metadata (that's `adapto:content-upload`, into `_adapto_seo`). - Writing or uploading content → the content pipeline. - Just checking the environment → `adapto:doctor`. ## Inputs - The **scaffolded frontend** in the cwd, and its **framework** (Next / Astro / SvelteKit — detected as `adapto:doctor` does). - The **`_adapto_seo`** collection (read at render time, by `target_slug`). - **`inventory.md`** — the content list `llms.txt` is generated from. ## Outputs - A **head-render layer** in the app's own templates (per framework: Next `generateMetadata` / Astro `<head>` in the layout / SvelteKit `<svelte:head>`) th