AgentStack
SKILL verified MIT Self-run

Adapto Seo Wire

skill-adaptocms-adapto-cms-agent-skills-adapto-seo-wire · by adaptocms

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.

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add skill-adaptocms-adapto-cms-agent-skills-adapto-seo-wire

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Adapto Seo Wire? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

adapto:seo-wire

adapto:content-upload stores SEO metadata in _adapto_seo, but the starters render only `. This skill **makes it render**: a **one-time, per-project** setup that installs a head-render layer reading adaptoseo (emitting , meta description, OG/Twitter tags, and JSON-LD) and generates llms.txt / llms-full.txt` from your inventory. It is consent-gated (§3.12) and only edits your own app templatesnever 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 ``

in the layout / SvelteKit `) that reads adaptoseo` and emits title/description/OG/Twitter/JSON-LD.

  • Generated llms.txt + llms-full.txt at the site root, from inventory.md.
  • If you decline the edits: the exact per-framework snippets written to .adapto/seo-render//

for you to paste, plus instructions. Nothing is changed without consent.

  • Next step: restart the dev server and check a page's ` (and /llms.txt`); re-run after big

inventory changes to refresh llms.txt.

Wiring (consent-gated — §3.12)

  1. Detect the framework and locate the layout/head entry point + the static/public dir.
  2. Inform + show the exact files/diffs you'd add/change (the head component + the llms.txt generator/route),

noting it edits app templates, not the read-client. Ask as a pickable question: Yes, wire it / Just give me the snippets (plus free-form).

  1. On consent: write the head-render layer (reads _adapto_seo by slug; falls back to the content title

when no metadata exists) and generate llms.txt/llms-full.txt from inventory.md. Idempotent — re-running updates rather than duplicating.

  1. If declined: write the snippets to .adapto/seo-render// + a short how-to; change nothing else.
  2. Then tell the user to restart the dev server and verify the ` + /llms.txt`. If you started

the dev server, leave it running (conventions §14).

Preconditions

  • Preflight with the adapto:doctor checks (CLAUDE.md §3.14).
  • A scaffolded frontend in the cwd (run adapto:scaffold first) on a supported framework.
  • _adapto_seo should exist (provisioned by adapto:schema-apply); if absent, the layer still installs and

simply renders title-only until metadata lands.

  • adapto CLI >= 0.0.7. No auth/tenant needed (no CMS writes).

Errors and recovery

  • Unsupported / undetected framework → stop; emit the generic snippets to .adapto/seo-render/ and explain.
  • Layout/head entry point not found (starter changed) → don't guess-edit; show the user where to add the

component and write the snippet.

  • User declines → snippets-only path (above); never edit without consent.
  • llms.txt would expose unpublished/draft URLs → include only published inventory entries; note the skip.

Forbidden actions

  • Never edit or replace the read-client (src/lib/adapto-sdk.ts + its paths) — app templates only, and

only with consent (§3.11 / forbidden-actions.md).

  • Never make host/file changes without explicit §3.12 consent — inform, show the diff, wait, then write.
  • Never write CMS content (mutates: false).
  • Never put draft-only or secret data into llms.txt / rendered tags.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.