page-restructurerlisted

Convert a candidate's existing prose page into an extraction-optimized Q&A format that AI engines can easily parse and cite. Use this skill whenever the user pastes an existing page, section, or block of prose (e.g. an "About", "My Vision", "Services", or bio section) and wants it rewritten so AI search engines and answer engines can lift and cite it — triggers include "make this citable", "restructure this page for AI", "optimize this for AI search / answer engines", "turn this into Q&A / FAQ", "why won't AI engines quote my page", "GEO / AEO this content", or any request to reformat owned prose into self-contained question-and-answer pairs with FAQPage schema. Restructures and tightens the wording without changing the substance or inventing claims.
meturley/trail-marker-geo · ★ 0 · Data & Documents · score 70

Install: claude install-skill meturley/trail-marker-geo

# Page Restructurer Rewrite a candidate's existing prose page into an **extraction-optimized Q&A format** so AI engines (ChatGPT, Perplexity, Google AI Overviews, Gemini, etc.) can easily parse, lift, and cite it. Then generate matching `FAQPage` JSON-LD. The problem this solves: AI answer engines cite *self-contained, answer-first sentences* far more readily than flowing prose where the point is buried mid-paragraph. This skill restructures owned content to match how engines actually extract — without changing what the candidate is saying. ## Hard rules (read first — these are non-negotiable) 1. **Owned content only.** Only restructure content the user owns or is authorized to rewrite. This is for reformatting a candidate's own page, not rewriting someone else's. 2. **Preserve the candidate's actual positions.** Restructure and tighten — never change the substance, soften a stance, or invent new claims, facts, numbers, dates, or credentials. Every fact in the output must trace to the source page. 3. **Never fabricate to fill gaps.** If the source is thin or vague, leave it thin. Do not invent specifics to make an answer sound more citable. 4. **Flag vague claims — don't fix them silently.** If the source contains vague or unsupported claims (e.g. "widely recognized," "years of experience," "many students"), list them and suggest the user run **`claim-strengthener`**. Do not fabricate the missing specifics yourself. 5. **Cross-check against `fact-sheet.md` if present.** I