What problem does it solve? Creating ranking-grade local service pages (city + service landing pages) requires grounding in real client facts, correct LocalBusiness schema, and rigorous quality checks; doing this manually is slow and risks producing thin, spun city-swap pages that fail SEO quality standards. ## Core Features & Use Cases - Client-grounded generation: Resolves the client, pulls fresh context (NAP, proof points), and creates a local content job that the backend pipeline drafts and self-QAs. - 14-dimension QA gate: Returns a weighted scorecard covering fact grounding, local relevance, E-E-A-T experience, and information gain, with hard thresholds (85 total, 70 per dimension) enforced before approval. - Structured handoff: Outputs the draft, LocalBusiness JSON-LD, keyword data, and a pinned scorecard so a human lead can approve or route the job back to editing. - Use Case: An operator needs an "emergency plumbing in Austin" page for a client; the skill creates the job, waits for the pipeline, and returns the draft plus QA scorecard for lead review. ## Quick Start Ask the assistant to generate a local service page for a given client, city, and service, for example: create a local service page for client Acme Plumbing targeting water heater repair in Denver.
