faq-readiness

A good FAQ removes the doubt that stops someone from signing up, buying, or trusting the site. A bad one is filler: made-up questions, vague answers, and promises nobody approved. This skill builds the first kind, from real questions and verified answers, and says so when a site does not need one.

Activate when

• The user asks for an FAQ, help center, or "common questions" section.
• A launch review (launch-all, trust-all, content-trust) found predictable questions left unanswered at the point of decision: what does it cost, what happens when the trial ends, how do I cancel, what do you do with my data, when will it arrive, does it work with X.
• Support messages or the contact inbox keep asking the same things.
• Not when the product is self-explanatory and low-friction. Then say so; a clearer headline or call to action is usually the better fix (content-trust).

Working alone

This skill is self-contained. Its companions (declared in its metadata) are skills whose method it may need to do its own promised work. Use of a companion can be conditional: declaring one does not mean running it. When a companion's lane applies, use the skill if it is installed; if not, follow its short entry in references/companion-methods.md and say in your report which lanes ran inline at reduced depth. Never skip an applicable lane silently. Skills mentioned here only for escalation, referral, documentation, or optional deeper follow-up are not dependencies: report the hand-off and finish honestly.

Companions: design-system-reconnaissance.

Inspect