An FAQ for a site only works when it answers questions people actually type into search, not ones that sound plausible to an editor. Invented questions tend to read too smooth and generic — real ones are far more specific, and often reveal exactly where a reader's doubt sits.
How the site FAQ is built
Given a topic or page URL, this skill pulls question-shaped search suggestions, checks how the current top results answer them, and selects 6-10 questions — the most common ones plus a few the top results don't answer well. It writes a short, concrete answer for each and saves the result as a document.
What you get
A library document with the questions and answers in order, plus a note on which ones deserve deeper coverage in the page's main text. Chat gets a short digest: how many questions, which were "uncovered" by the current search results, and where they came from. It's a fast way to preempt support questions on a new service or product page, or to spot why an existing page has a high bounce rate.
An FAQ pairs naturally with the other page-prep skills: alongside the question-and-answer block, write the title and description for the page, and run a page error check before publishing. The rest of the content skills live on the category page.